10. Quality Requirements

This section contains all relevant quality requirements.

The most important of these requirements have already been described in section Quality Goals (quality goals), therefore they should only be referenced here. In this section Quality Requirements you should also capture quality requirements with lesser importance, which will not create high risks when they are not fully achieved (but might be nice-to-have).

10.1. Quality Tree

@startmindmap quality-tree *_ Product Quality ** Functional Suitability ***_ Functional Completeness ***_ Functional Correctness ***_ Functional Appropriateness ** Flexibility ***_ Adaptability ***_ Scalability ***_ Installability ***_ Replaceability ** Interaction Capability ***_ Appropriateness recognizability ***_ Learnability ***_ Operability ***_ User error protection ***_ User engagement ***_ Inclusivity ***_ User assistance ***_ Self-descriptiveness ** Compatibility ***_ Co-existence ***_ Interoperability ** Performance Efficiency ***_ Time behaviour **** Quality Scenario 01 ***_ Resource utilization ***_ Capacity ** Safety ***_ Operational constraint ***_ Risk identification ***_ Fail safe ***_ Hazard warning ***_ Safe integration ** Security ***_ Confidentiality ***_ Integrity ***_ Non-repudiation ***_ Accountability ***_ Authenticity ***_ Resistance ** Maintainability ***_ Modularity ***_ Reusability ***_ Analysability ***_ Modifiability ***_ Testability ** Reliability ***_ Faultlessness ***_ Availability ***_ Fault tolerance ***_ Recoverability @endmindmap

Fig. 10.1 The quality scenarios and their place in the quality tree. For more information about the quality characteristics, please refer to iso25000.com.

10.2. Quality Scenarios

Fig. 10.1 shows …

Todo

  • Highlight the qualities from chapter Quality Goals in the tree.

  • Find the quality scenarios, focussing on the chosen qualities.

  • Put the quality scenarios into the tree Fig. 10.1.

10.2.1. Quality Scenario 1

' @see https://plantuml.com/sequence-diagram @startuml quality-scenario-01 !pragma teoz true hide footbox autonumber participant System participant Neighbor {t_start} [-> System++: IF_USER_SYS (x = a) {t_a} System -> Neighbor++: IF_SYS_NB (y = a 3.141592) ||50|| {t_b} System <-- Neighbor-- {t_end} [<-- System--: {t_start} <-> {t_end}: {<= 0.67s} {t_a} <-> {t_b}: {[0.2s .. 0.5s)} @enduml

Fig. 10.2 Sequenz des Qualitätsscenario 1

Fig. 10.2 shows …