TOGAF 10 Foundation: Storing and Managing Requirements

Storing and Managing Requirements in TOGAF ADM

Why Storing and Managing Requirements is Important

Storing and managing requirements is a critical component of the TOGAF Architecture Development Method (ADM) because it ensures that:

• Traceability - Requirements are tracked throughout the entire architecture lifecycle, from initial concept to implementation
• Alignment - Business, application, and technology requirements remain aligned with organizational strategy
• Compliance - All stakeholder needs are documented and fulfilled, reducing the risk of missed requirements
• Change Management - Requirements can be updated and versions tracked, allowing for controlled evolution of the architecture
• Communication - A centralized repository enables clear communication among all stakeholders
• Quality Assurance - Ensures requirements are validated, complete, and measurable before implementation
• Risk Reduction - Prevents scope creep and ensures resources are allocated appropriately

What is Storing and Managing Requirements?

Storing and managing requirements in TOGAF refers to the systematic approach of collecting, organizing, documenting, and maintaining all architecture requirements throughout the ADM phases. This includes:

• Business Requirements - What the business needs to achieve
• Architecture Requirements - The architectural standards and guidelines needed
• Information Systems Requirements - Data and system specifications
• Technology Requirements - Infrastructure and technical specifications

A requirements management system typically includes:

• A centralized repository or database
• Version control mechanisms
• Change tracking and approval workflows
• Traceability matrices linking requirements to deliverables
• Metadata fields for classification, priority, and status

How Storing and Managing Requirements Works

1. Requirements Collection and Documentation

During the early ADM phases (particularly Phase A: Architecture Vision and Phase B: Business Architecture), requirements are collected through:

• Stakeholder interviews and workshops
• Business process analysis
• Current state assessment
• Risk and constraint identification

These requirements are documented in a structured format with clear definitions, acceptance criteria, and metadata.

2. Requirements Organization and Classification

Requirements are organized using:

• Categories - Business, Information Systems, Technology, Architecture Standards
• Priorities - Critical, High, Medium, Low
• Status - New, Reviewed, Approved, Implemented, Verified
• Ownership - Which stakeholder or team is responsible

3. Storing in a Repository

Requirements are stored in a centralized system such as:

• Specialized requirements management tools (e.g., IBM Requisite Pro, RequisitePro, Jira, Azure DevOps)
• Database systems with customized architectures
• Enterprise Architecture Management (EAM) platforms

The repository should support version control, audit trails, and access controls.

4. Traceability Management

Establishing traceability links ensures:

• Each requirement is linked to its source (stakeholder, business goal)
• Requirements are mapped to architecture deliverables
• Implementation components are linked back to requirements
• Test cases are associated with specific requirements

5. Change Management and Version Control

As the architecture evolves:

• Changes to requirements are tracked with version numbers
• A formal change control process is followed
• Impact analysis is performed before approving changes
• Stakeholder approval is documented

6. Monitoring and Compliance

Throughout the ADM cycle:

• Requirements are reviewed at key governance gates
• Metrics are tracked to ensure implementation is meeting requirements
• Deviations are identified and addressed
• Lessons learned are captured for future improvement

Key Principles of Requirements Management in TOGAF

• Completeness - All requirements are documented
• Clarity - Requirements are unambiguous and measurable
• Consistency - No conflicting requirements exist
• Traceability - Full audit trail from source to implementation
• Accessibility - Stakeholders can easily access and understand requirements
• Controllability - Changes are managed through formal processes

Exam Tips: Answering Questions on Storing and Managing Requirements

Tip 1: Understand the Context of ADM Phases

Exam questions often ask when requirements management occurs. Remember that requirements management runs parallel to all ADM phases, not just one. Questions may test whether you know that:

• Phase A focuses on initial business requirements
• Phases B, C, and D refine and expand requirements
• Phase E and beyond implement against these requirements

Answer approach: If asked about storing requirements, emphasize that it's a continuous process across all phases.

Tip 2: Focus on the Repository and Tool Aspects

Questions frequently address where and how requirements are stored. Key points to remember:

• A centralized repository is essential
• The system must support version control
• Access controls and audit trails are necessary
• Integration with other ADM tools is important

Answer approach: When asked about storing requirements, mention the repository/database, version control, and accessibility features.

Tip 3: Know the Traceability Concept

Traceability is a favorite exam topic. Understand that:

• Requirements must be traceable to their source (why they exist)
• Requirements must be traceable to deliverables (what satisfies them)
• Requirements must be traceable to implementation (how they're realized)

Answer approach: When describing requirements management, always mention bidirectional traceability. Use phrases like "traced back to" and "mapped to."

Tip 4: Recognize Change Management Components

Questions about managing requirements often include change scenarios. Remember:

• Changes go through a formal approval process
• Impact analysis is performed before approval
• Versioning tracks all changes
• Stakeholder sign-off is documented

Answer approach: When a question involves updating or modifying requirements, discuss the change control process, not just the update itself.

Tip 5: Distinguish Between Requirement Types

Exam questions may ask you to categorize or manage different types:

• Business Requirements - What the organization needs
• Architecture Requirements - How the architecture will be built
• Information Systems Requirements - Data and system needs
• Technology Requirements - Technology standards and infrastructure

Answer approach: When asked about storing requirements, consider mentioning how different types might be categorized or prioritized differently.

Tip 6: Link Requirements to ADM Deliverables

The exam often tests whether you understand how requirements relate to architecture deliverables. Key points:

• Each requirement should be addressed by at least one deliverable
• Requirements management documents are key ADM outputs
• Traceability matrices link requirements to deliverables

Answer approach: Connect requirements management to specific ADM outputs like the Architecture Requirements Specification and Requirements Impact Assessment.

Tip 7: Understand Governance and Approval Gates

Questions may address how requirements are validated and approved. Remember:

• Requirements are reviewed at governance gates
• Stakeholder approval is essential before implementation
• Requirements that conflict must be resolved
• Prioritization ensures resource alignment

Answer approach: Mention governance, stakeholder approval, and review processes when discussing requirements management.

Tip 8: Watch for "Best Practice" Style Questions

Exam questions might ask "What is the best approach to..." regarding requirements. Good practices include:

• Centralizing all requirements in one system
• Establishing clear ownership and accountability
• Using metrics to track requirements status
• Regularly communicating status to stakeholders
• Training users on the requirements management system

Answer approach: Choose answers emphasizing standardization, centralization, and stakeholder communication.

Tip 9: Avoid Common Misconceptions

Misconception 1: Requirements are finalized in Phase A and don't change.
Reality: Requirements evolve throughout the ADM cycle and are refined in later phases.

Misconception 2: Requirements management is only the responsibility of the architecture team.
Reality: Requirements management is a shared responsibility involving business stakeholders, architects, and implementation teams.

Misconception 3: Any tool can be used for requirements management.
Reality: The tool must support traceability, version control, and integration with architecture processes.

Tip 10: Practice with Scenario Questions

The exam may present scenarios like:

• "A stakeholder requests a significant change to a requirement that was approved in Phase A. What should happen?"
  Good answer: The change should go through formal change control, impact analysis should be performed, and stakeholder approval should be documented.
• "How should a conflict between two requirements be handled?"
  Good answer: A traceability matrix should identify the conflict, stakeholders should review both requirements, and resolution should be documented with approval.
• "What ensures that implementation matches the original requirements?"
  Good answer: Traceability links and verification against the Requirements Specification ensure alignment.

Tip 11: Know the Terminology

Use precise TOGAF terminology in answers:

• Requirements Repository - Centralized storage system
• Traceability Matrix - Document showing links between requirements and deliverables
• Requirements Impact Assessment - Analysis of how changes affect other requirements
• Architecture Requirements Specification - Formal document of all architecture requirements
• Change Request - Formal submission for requirement modification

Tip 12: Remember ADM Iteration

TOGAF emphasizes that the ADM is iterative. When answering questions about requirements management:

• Acknowledge that requirements are refined across iterations
• Understand that traceability becomes more detailed in later iterations
• Recognize that version control is crucial to managing iterations

Sample Exam Question and Answer Strategy

Question: "Which of the following best describes the purpose of storing and managing requirements in a centralized repository during the ADM?"

Options (Example):

• A) To eliminate the need for stakeholder meetings
• B) To ensure traceability from source through implementation and to enable change management
• C) To reduce the number of architecture deliverables
• D) To replace the need for an Architecture Requirements Specification

Answer Strategy: Eliminate options that don't align with TOGAF principles. Option A is incorrect (centralized storage doesn't replace stakeholder engagement). Option C is incorrect (repository doesn't reduce deliverables). Option D is incorrect (repository complements, doesn't replace, the Specification). Option B correctly identifies both purposes: traceability and change management.

Conclusion

Storing and managing requirements is a foundational element of the TOGAF ADM. Success in exam questions on this topic requires understanding:

• Why it matters: Traceability, alignment, compliance, and risk reduction
• What it includes: Repository, version control, traceability, and change management
• How it works: Collection, organization, storage, linking, monitoring, and evolution
• When it occurs: Throughout all ADM phases as a continuous process

Focus on the interconnected nature of requirements management with other ADM elements, emphasize governance and stakeholder involvement, and always mention traceability as a key benefit. With these principles and exam tips, you'll be well-prepared to answer questions confidently.