Maintain Requirements
The purpose of Maintain Requirements is to retain requirement accuracy and consistency throughout and beyond the change during the entire requirements life cycle, and to support reuse of requirements in other solutions.
Guidelines/Tools and Techniques
The guidelines/tools and techniques used to maintain and model requirements
Maintain Requirements - Uses Functional Decomposition, Data Flow Diagrams, Data Modeling, Document Analysis, User Stories, Business Rules Analysis, Process Modeling and Use Case techniques s to maintain requirements.
Requirements – Use the Information Management Approach as guidelines.
The relationships between these guidelines, tools, techniques and Requirements, are detailed in the BABOK under the Guidelines and Tools and Techniques sections of the Maintain Requirements task.
Workers
The people involved with maintaining Requirements.
The relationships between these roles and the task, are detailed in the BABOK under the Stakeholders section of the Maintain Requirements task.
Domain Subject Matter Expert - Ensure requirements and designs accurately reflecting stated needs.
Implementation Subject Matter Expert - Uses maintained requirements and designs when developing regression tests.
Operational Support - maintained requirements are likely to be referenced to confirm the current state.
Regulator - Ensures maintained requirements and designs conform to standards..
Tester - Used maintained requirements and designs to create test plans and test cases.
