Please enable JavaScript.

Coggle requires JavaScript to display documents.

SA_2:QA - Coggle Diagram

- - - - Customer provide scenarious, mainly based on concerns
      - SA should not critisize. just collect here
      - Each Scenario should have all 6 points
    - - Merge some scenarios,consolidate similar scenarious
    - - `Provide to stackholders ability to vote for some scenarious
    - - Define scope, constraints, components
    - - Why we need it from bussiness prospective
      - SA should map "bussiness needs" to quality attribute
        
        like "we need to improve reputation". == make good security, scalability, etc...
    - - QAW Scenarious
        
        Prioritizied
        
        Refined
        
        raw
      - Readty QAW + Scenarious is a driver for the next steps. It provides ability to clarify Quality Attribute requirements
      - Provide ability to evaluate the next arhitecture
- - - - Interoperability, Maintanability, Portability
    - - Maintanability
    - - Performance, Availability, Modifiability
- - - - artefacts - part of the system which was stimulated by the stimulus
      - environment - the condition under which stimulus occured (run time, start-up, shutdown, rebalancing...)
      - stimulus - a condition, that affect the system (event, request... = specific action..)
      - response - the activities which is result of the stimulation
      - source - who produce the event
      - response measure - the measure by which system's response is evaluated
      - There is a General Templates in the Book Architecture in Practise
        
        We need this Scenatious to Disscuss with Stakeholders. As they cann't provide "own scenarious of availability, etc". It helps eliciteta scenarios.
        
        There are scenarious for 7 QAs