Page 13 - Software and Systems Requirements Engineering in Practice
P. 13
xii S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e
Business Object Modeling . . . . . . . . . . . . . . . . 108
Coherent Low-Level Processes Should
Be Defined with State or Activity
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Elicit Requirements and Processes by Starting
at Boundaries and Modeling Inward . . . . 112
Hide Complexity by Using Compound
Business Objects . . . . . . . . . . . . . . . . . . . . . . 112
Initiate Prototyping Efforts Quickly . . . . . . . 112
Determining Model Completeness . . . . . . . . . . . . . . 113
Diagram Quality . . . . . . . . . . . . . . . . . . . . . . . . 113
Content Correctness . . . . . . . . . . . . . . . . . . . . . 113
Model Faults That Should Be Corrected
Before a Model Is Completed . . . . . . . . . . . 113
Transitioning from Analysis to Design . . . . . . . . . . . 115
Suggested Model Conversion Heuristics . . . . . . . . . 115
Design Model Package Structure . . . . . . . . . . 115
Use Case Tracing . . . . . . . . . . . . . . . . . . . . . . . . 115
Interface Tracing . . . . . . . . . . . . . . . . . . . . . . . . 115
Artifact Tracing . . . . . . . . . . . . . . . . . . . . . . . . . 115
Design Model Structure . . . . . . . . . . . . . . . . . . . . . . . . 117
Tracing Requirements Through
the Design Model . . . . . . . . . . . . . . . . . . . . . 117
Intermodel Quality Assurance Checks . . . . . 117
Design Model Initial Construction . . . . . . . . 118
Use of Tooling for MDRE . . . . . . . . . . . . . . . . . . . . . . 120
Tips for Modeling Requirements . . . . . . . . . . . . . . . . 120
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Discussion Questions . . . . . . . . . . . . . . . . . . . . . . . . . . 122
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5 Quality Attribute Requirements . . . . . . . . . . . . . . . 125
Why Architectural Requirements Are Different . . . 126
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
An Integrated Model . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Quality Attribute Scenarios . . . . . . . . . . . . . . . 131
Quality Attribute Requirements . . . . . . . . . . . 131
Factors, Issues, and Strategies . . . . . . . . . . . . 132
Product Architecture . . . . . . . . . . . . . . . . . . . . 132
Quality Attribute Requirements . . . . . . . . . . . . . . . . . 132
Selecting Significant Stakeholders . . . . . . . . . . . . . . . 140
Identifying Potential Stakeholders . . . . . . . . 141
Methods for Architectural Requirements
Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Quality Attribute Workshop . . . . . . . . . . . . . . 143
