top of page

Maintain Requirements

Purpose:

  • Retain Requirement Accuracy and Consistency:
    Ensure requirements remain accurate and consistent throughout changes.

  • Support Reuse of Requirements:
    Facilitate the reuse of requirements in other solutions.

Description:

  • Ongoing Need Maintenance:
    Ensure requirements representing ongoing needs are continuously valid.

  • Maximizing Benefits:
    Requirements should be:

    • Consistently represented.

    • Reviewed and approved using standardized processes.

    • Easily accessible and understandable.

Inputs:

  • Requirements: Goals, business needs, stakeholder input.

  • Designs: Ongoing throughout the project.

Elements:

  • Maintain Requirements

    • Responsibility: Business analysts ensure accuracy.

    • Practices: Define clearly, maintain links, use repositories.

  • Maintain Attributes

    • During Elicitation: Gather source, priority, complexity.

    • Management: Use attributes for oversight.

  • Reusing Requirements

    • Identification: Spot reusable requirements.

    • Storage: Keep them accessible.

    • Levels of Abstraction: Reuse widely, watch out for specificity.

    • Validation: Stakeholders approve reuse.

Guidelines and Tools:

  • Information Management Approach: Strategy for managing requirements for reuse.

Techniques:

  • Business Rules Analysis: Identifies reusable rules.

  • Data Flow Diagrams: Identifies reusable flows.

  • Data Modeling: Identifies reusable structures.

  • Document Analysis: Uses existing documentation.

  • Functional Decomposition: Identifies reusable components.

  • Process Modeling: Identifies reusable processes.

  • Use Cases and Scenarios: Identifies reusable components.

  • User Stories: Identifies reusable story elements.

Stakeholders:

  • Domain SME: Ensures accurate reflection of needs.

  • Implementation SME: Utilizes for tests and analysis.

  • Operational Support: Confirms current state.

  • Regulator: Ensures compliance.

  • Tester: Aids in test creation.

Outputs:

  • Maintained Requirements:

    • Defined once for long-term use.

    • May become assets for future initiatives.

  • Maintained Designs:

    • Reusable components for future use.

bottom of page