This practice also reinforces the importance of ensuring that you have the
???right??? requirements (i.e., the requirements that will produce a viable, accurate,
fully functioning product) early in the development process. It also somewhat overlaps
with the Validation Process Area.
In the previous CMMI, SP 1.2 from Technical Solution (Evolve Operational
Concepts and Scenarios) has been incorporated into RD SP 3.1 Establish Operational
Concepts. SP 3.5 has now combined validating requirements with validating
them with comprehensive methods from the previous CMMI.
Requirements Development is where requirements are initially defined and documented.
Requirements Management at Level 2 is where changes are administered.
Requirements Development gathers requirements and then must usually refine these
requirements in some way??”by stating them more clearly, determining whether they
are redundant or inconsistent with other requirements, and breaking them down into
more detailed and traceable requirements.
Some readers may think that they can skip this process area because they are
not doing ???development,??? that is, ???new??? development, because they are a Maintenance
shop.
Pages:
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225