A requirement is defined as a property that must be exhibited in order to solve some real-world problem. SWEBOK decomposes the software requirements knowledge area into fundamentals, the requirements process, requirements elicitation, requirements analysis, requirements specification, requirements validation, and practical considerations.
Requirements Management (5)
updated
- Requirements Management involves managing requirements that have been developed, including change control and verification. It is a Level 2 (Managed) Process Area for the SEI CMMI for Development(CMMI-DEV), and is separate from requirements development (a Level 3 CMMI-DEV Process Area), although there is considearble overlap. It is also a Level 2 Prrocess Area for the CMMI for Acquisition.
The resources listed here primarily address requirements management, but could also address requirements development and use cases, two other subtopics for requirements engineering
Requirements Trade-Offs/Negotiations - This DACS Gold Practice describes how, within a funding constrained environment, one engages in the explicit trade-off between required functionality, schedule, time, project/product stability, and risk without compromising overall system objectives.
DACS Gold Practice Initiative
