Requirements Management
1: Key Considerations
1.1: General Approach
General Overview of Requirements Management in ADM
Dynamic Process
- The Requirements Management circle in the ADM indicates a continuous process rather than a static set of requirements.
Continuous Flow of Requirements
- Requirements for Enterprise Architecture are identified, stored, and exchanged throughout the ADM phases and across cycles.
Importance of Flexibility
- The ability to manage changes in requirements is essential due to the inherent uncertainty in architecture activities. - Architectural requirements often change in response to various drivers and constraints that may be outside the enterprise's control (e.g., market shifts, new regulations).
Role of Requirements Management
- The Requirements Management process does not prioritize or address requirements; this is handled within the specific ADM phases. - It serves to manage requirements throughout the entire ADM lifecycle.
Architecture Requirements Repository
- Recommended for recording and managing all architecture requirements. - It differs from the Architecture Requirements Specification and Requirements Impact Assessment by storing information from multiple ADM cycles.
1.2: Requirements Development Approach
Requirements Development in ADM
Initial High-Level Requirements
- The first high-level requirements are articulated during the Architecture Vision phase using business scenarios or similar techniques.
Requirement Selection for Each Phase
- Each ADM phase, from Preliminary to Phase H, must select approved requirements from the Architecture Requirements Repository and Architecture Requirements Specification.
Update Requirement Status
- At the end of each phase, the status of all selected requirements must be updated.
Document New Requirements
- New requirements generated during the phase execution that fall within the current Statement of Architecture Work should be documented in the Architecture Requirements Specification. - New requirements outside the current scope must be entered into the Architecture Requirements Repository for further management.
Types of Requirements to Identify
- Functional Requirements - Non-Functional Requirements
Considerations When Defining Requirements
- Assumptions related to requirements - Constraints affecting requirements - Domain-specific principles driving requirements - Policies influencing requirements - Standards that must be met - Organizational guidelines for requirements - Specifications for requirements
Deliverables and Mappings
- Deliverables in later ADM phases include mappings to design requirements and may generate new types of requirements (e.g., conformance requirements, time windows for implementation).
1.3: Resources
Resources for Requirements Management
General Overview
- The field of requirements engineering offers numerous emerging recommendations and processes for effective Requirements Management. - The TOGAF Standard does not specify any particular process or tool; rather, it outlines what an effective Requirements Management process should achieve (the "requirements for requirements").
Business Scenarios
- A technique to analyze how a business goal or objective can be achieved through a process or value stream. - It focuses on identifying and clarifying architecture requirements by examining the activities performed by human and computer actors within the process. - Detailed guidance on this technique can be found in the TOGAF® Series Guide: Business Scenarios.
Requirements Tools
- There is a growing variety of Commercial Off-The-Shelf (COTS) tools available for supporting Requirements Management. - These tools may not be specifically designed for architecture requirements but can be useful in the broader context of requirements management.
2. Activities
Step 1: ADM Phase Steps
Identifying and Documenting Architecture Requirements
Requirement Identification
Analyze how business goals/objectives can be met through: - Designing value streams - Developing business scenarios - Enhancing user experiences - Providing management information
Documentation
- Document requirements in the Architecture Requirements Specification - Store requirements in the Requirements Repository
Step 2 : Requirements Management Steps
Establishing Baseline Requirements
Determine Priorities
Identify and set the priorities for the requirements.
Confirm Stakeholder Agreement
Ensure that stakeholders agree to the established priorities.
Documentation
- Record the baseline requirements in the Architecture Requirements Specification. - Store them in the Requirements Repository.
Step 3 : Requirements Management Steps
Monitoring Baseline Requirements
Track Progress
Continuously monitor the status of baseline requirements to ensure they are being met.
Manage Changes
Identify any deviations or changes in requirements and address them accordingly.
Ensure Compliance
Verify that the implementation aligns with the documented baseline requirements.
Update Documentation
Reflect any changes or updates in the Architecture Requirements Specification and Requirements Repository.
Step 4: ADM Phase Steps
Identifying New and Changed Requirements
Remove or Reassess Priorities
- Evaluate existing requirements to determine if any should be removed or if their priorities need to be reassessed.
Add Requirements and Reassess Priorities
- Identify new requirements that need to be added. - Reassess the priorities of all requirements in light of the new additions.
Modify Existing Requirements
- Review and update existing requirements as necessary to reflect any changes in business needs or objectives.
Step 5: Requirements Management Steps
Identifying Changed Requirements and Recording Priorities
Identify Changed Requirements
- Recognize and document any changed requirements. - Ensure that requirements are prioritized by the architects responsible for the current phase and relevant stakeholders.
Record New Priorities
- Update the requirements documentation with the newly established priorities.
Manage Conflicts
- Identify any conflicts among requirements. - Manage these conflicts throughout the phases to ensure successful prioritization.
Generate Requirements Impact Statement
- Create a Requirements Impact Statement (see the TOGAF Standard — Architecture Content) to guide the architecture team.
Notes:
Changed requirements can originate from various sources.
The process should effectively direct the ADM phases and document all decisions related to requirements.
The Requirements Management phase must assess stakeholder satisfaction with decisions made.
In cases of dissatisfaction, the phase is responsible for resolving issues and determining next steps.
Step 6: ADM Phase Steps
Assessing the Impact of Changed Requirements
Assess Impact on Current Phase
- Evaluate how changed requirements affect the ongoing (active) phase of the architecture development.
Assess Impact on Previous Phases
- Analyze the implications of changed requirements on earlier phases to ensure consistency and coherence.
Determine Implementation Approach
- Decide whether to implement the change now or defer it to a later ADM cycle. - If implementing, assess the timescale for change management.
Issue Requirements Impact Statement
- Release the updated Requirements Impact Statement (Version n+1) to reflect the changes and their implications.
Step 7: ADM Phase Steps
Implementing Requirements Arising from Phase H
Architecture Change Management
- Recognize that the architecture can be modified throughout its lifecycle during the Architecture Change Management phase (Phase H).
Manage New or Changing Requirements
- Utilize the Requirements Management process to ensure that any new or changed requirements originating from Phase H are appropriately managed and integrated.
Step 8: Requirements Management Steps
Updating the Architecture Requirements Repository
Document Changes Requested
- Record all information related to the changes requested, ensuring clarity and completeness.
Include Stakeholder Views
- Capture and document the perspectives and opinions of stakeholders affected by the changes.
Ensure Repository Accuracy
- Regularly update the Architecture Requirements Repository to maintain accurate and current information regarding all changes and stakeholder input.
Step 9: ADM Phase Steps
Implementing Change in the Current Phase
Initiate Change Implementation
- Begin the process of integrating the approved changes into the current phase of the architecture development.
Communicate Changes
- Inform all relevant stakeholders about the changes and how they will be implemented.
Update Documentation
- Revise all relevant architectural documents and specifications to reflect the changes made.
Monitor Implementation
- Continuously oversee the implementation process to ensure changes are executed as planned and address any issues that arise.
Evaluate Impact
- Assess the effects of the implemented changes on the overall architecture and project objectives.
Step 10: ADM Phase Steps
Assessing and Revising Gap Analysis for Past Phases
Review Gap Analysis
- Reevaluate the gap analysis conducted in ADM Phases B through D to identify discrepancies between the Baseline and Target Architectures.
Identify Types of Gaps
- Recognize the two kinds of gaps described in the ADM: 1. Eliminated Gaps: Present in the baseline but missing in the target (eliminated by accident or design). 2. New Gaps: Not in the baseline but included in the target.
Define Gap Requirements
- Identify "gap requirements," which are elements that have been unintentionally eliminated and require changes to the Target Architecture.
Address Gap Requirements
- Ensure that all identified gap requirements are documented and recorded in the Architecture Requirements Repository.
Revise Target Architecture
- Update the Target Architecture to reflect the changes necessitated by the identified gap requirements.
Last updated
