Other meanings of Requirements management
Systems engineering
Requirements management is the systematic process of eliciting, documenting, analyzing, tracking, prioritizing, and agreeing upon requirements and then controlling changes to them throughout the lifecycle of a project or system. It is a critical discipline in systems engineering and software engineering, as poor requirements management is a leading cause of project failure.1 The discipline integrates technical, managerial, and communication activities to ensure that stakeholder needs are accurately captured, consistently maintained, and verifiably met by the final product or service.
Requirements management follows a structured lifecycle that begins with elicitation—gathering needs from stakeholders such as customers, users, and regulators—and continues through analysis, specification, validation, and continuous change control. The ISO/IEC/IEEE 29148 standard defines detailed processes for requirements engineering, including the use of well-formed requirement statements and traceability.1 Key activities include prioritizing requirements, establishing baselines, and managing changes via a change control board (CCB). Effective requirements management ensures that each requirement is unambiguous, complete, consistent, and verifiable, reducing rework and improving project outcomes.
Specialized software tools such as IBM Rational DOORS, Jama Connect, and ReqView support requirements management by providing centralized repositories, version control, and traceability matrices.2 The ReqIF (Requirements Interchange Format) standard enables the exchange of requirements data between tools, facilitating collaboration across organizations and supply chains.1 Techniques like impact analysis and traceability link each requirement to design elements, test cases, and risks, ensuring compliance and coverage. Agile teams often manage requirements as user stories in backlogs, leveraging iterative prioritization and incremental validation.
Common challenges include scope creep, ambiguous wording, and siloed communication among stakeholders.3 Best practices emphasize early and continuous stakeholder involvement, writing requirements in a clear, testable form, and using traceability to assess impact of changes. The Project Management Institute recommends regular requirements reviews and validation with prototypes to avoid misinterpretation.4 In agile environments, maintaining a well-groomed product backlog and holding sprint reviews help keep requirements aligned with evolving needs. Training in requirements engineering and adopting a common vocabulary further reduce misunderstandings.
While often associated with software, requirements management originated in aerospace and defense programs such as the Apollo missions, where MIL-STD-498 formalized the practice.5 Barry Boehm's spiral model explicitly integrated risk-driven requirements management, influencing later iterative methods.6 Outside traditional engineering, requirements management is applied in construction, pharmaceutical regulation, and even legal contracts. An emerging edge case is the management of requirements for AI systems, where non-deterministic behavior and ethical constraints demand novel traceability and validation approaches. The discipline also plays a key role in safety-critical systems (e.g., DO-178C for avionics) where every requirement must be linked to a test case.
The specific sense of 'requirements management' covered here refers to the engineering discipline applied across hardware, software, and systems, distinct from the narrower use as a software tool category.
Help improve the encyclopedia. Reports go straight to the site manager.