|
The authors |
5 |
|
|
Preface and Dedications |
7 |
|
|
Table of Contents |
8 |
|
|
1 Introduction |
12 |
|
|
1.1 Aim of Book |
12 |
|
|
1.2 Benefit to be gained from book |
12 |
|
|
1.3 Definition of terms |
13 |
|
|
1.4 Structure of the Book |
15 |
|
|
1.5 How to read this book |
18 |
|
|
2 Why Requirements Management and Engineering |
21 |
|
|
2.1 General |
21 |
|
|
2.2 Advantages of RM&E in project management |
23 |
|
|
2.3 Advantages for finding solutions in design and architecture |
26 |
|
|
2.4 Advantages in purchase and supplier management |
28 |
|
|
2.5 Advantages in customer service, sales and marketing |
28 |
|
|
2.6 Advantages in test and verification management |
29 |
|
|
3 Processes and Methods in Requirements Management and Engineering |
31 |
|
|
3.1 The roots of Requirements Management and Engineering |
31 |
|
|
3.2 Common concepts in Requirements Management and Engineering |
39 |
|
|
3.3 Processes and methods in Requirements Management and Engineering |
41 |
|
|
3.4 Summary |
48 |
|
|
4 Introduction to Requirements Engineering |
49 |
|
|
4.1 History of Requirements Engineering |
49 |
|
|
4.2 HOOD Requirements Definition Process |
52 |
|
|
4.3 Requirements Development and Requirements Engineering |
65 |
|
|
4.4 Summary |
67 |
|
|
5 Introduction to Requirements Management |
69 |
|
|
5.1 What is Requirements Management |
69 |
|
|
5.2 Why we need Requirements Management |
69 |
|
|
5.3 The benefits of a working Requirements Management |
75 |
|
|
5.4 Why some people are against Requirements Management |
81 |
|
|
5.5 How resistance can be avoided |
83 |
|
|
5.6 After the introduction of Requirement Management |
86 |
|
|
5.7 Summary |
87 |
|
|
6 Project Management interface |
89 |
|
|
6.1 What is Project Management |
89 |
|
|
6.2 How Requirements Management can support the writing of proposals |
90 |
|
|
6.3 How Requirements Management can support the definition of the project scope |
93 |
|
|
6.4 How Requirements Management can support estimating resources and costs |
94 |
|
|
6.5 How Requirements Management can support project planning ( scheduling) |
95 |
|
|
6.6 How Requirements Management can support project monitoring |
98 |
|
|
6.7 How Requirements Management can support quality management |
100 |
|
|
6.8 How Requirements Management can support reporting |
105 |
|
|
6.9 How Requirements Management can support managing people |
106 |
|
|
6.10 Summary |
108 |
|
|
7 Configuration Management interface |
110 |
|
|
7.1 Of versions, configurations, and releases |
111 |
|
|
7.2 Management Disciplines and the German Government V- Modell |
116 |
|
|
7.3 Configurations in the Context of Requirements Management |
117 |
|
|
7.4 Traceability in Requirement Management and Configuration Management |
123 |
|
|
7.5 Tool Use for Version and Configuration Management |
124 |
|
|
7.6 Summary |
126 |
|
|
8 Metrics and Analysis |
129 |
|
|
8.1 Metrics – general |
129 |
|
|
8.2 The Importance of Metrics |
130 |
|
|
8.3 Attributes of Metrics |
131 |
|
|
8.4 Typical Improvement Goals with RM&E |
134 |
|
|
8.5 Example of a Metric |
138 |
|
|
8.6 The Evaluation of a Metric by Management |
140 |
|
|
8.7 Psychological Aspects of Introducing RM&E Metrics |
141 |
|
|
8.8 Summary |
143 |
|
|
9 Risk Management interface |
145 |
|
|
9.1 What is a risk |
145 |
|
|
9.2 What is Risk Management |
146 |
|
|
9.3 Preparing a Risk Management |
146 |
|
|
9.4 The Risk Management process |
149 |
|
|
9.5 Summary |
162 |
|
|
10 Test Management (Validation and Verification) interface |
164 |
|
|
10.1 What are Validation and Verification? |
164 |
|
|
10.2 The Validation and Verification planning process |
165 |
|
|
10.3 The role of Requirements Management in Validation and Verification |
167 |
|
|
10.4 Summary |
180 |
|
|
11 Change Management interface |
182 |
|
|
11.1 General |
182 |
|
|
11.2 Basics of Change Management |
182 |
|
|
11.3 Factors Influencing Change |
183 |
|
|
11.4 Number of Changes during Development |
184 |
|
|
11.5 Two Phases of Change Management: Informing and Approval- based |
185 |
|
|
11.6 Turning Change Management theory into practice |
193 |
|
|
11.7 Procedure for Introducing Structured Change Management |
196 |
|
|
11.8 Summary |
198 |
|
|
12 Advanced Requirements Management: the complete specification |
199 |
|
|
12.1 Interfaces between other Systems Engineering disciplines and Requirements |
199 |
|
|
12.2 Getting away from the document view |
201 |
|
|
12.3 Implementing Requirements Management |
204 |
|
|
12.4 Summary |
219 |
|
|
13 The HOOD Capability Models |
221 |
|
|
13.1 The meaning of capability models |
221 |
|
|
13.2 Why we need capability models |
222 |
|
|
13.3 Two example capability models |
224 |
|
|
13.4 HOOD Capability Model for Requirements Definition |
227 |
|
|
13.5 HOOD Capability Model for Requirements Management |
228 |
|
|
13.6 Summary |
228 |
|
|
14 The HOOD Capability Model for Requirements Definition |
229 |
|
|
14.1 Brief repetition of the HOOD Requirements Definition Process |
229 |
|
|
14.2 The idea behind the HOOD capability model for requirements definition |
230 |
|
|
14.3 The structure of the HOOD capability model for requirements definition |
232 |
|
|
14.4 How to use the HOOD capability model for requirements definition |
234 |
|
|
14.5 Summary |
248 |
|
|
15 The HOOD Capability Model for Requirements Management |
249 |
|
|
15.1 The structure of the HOOD capability model for requirements management |
249 |
|
|
15.2 How to use the HOOD capability model for requirements management |
250 |
|
|
15.3 Summary |
271 |
|
|
List of References |
273 |
|
|
Index |
278 |
|