top of page

Specify and Model Requirements

Purpose:

  • Refine elicitation into requirements/designs.

Description:

  • Practices for representing requirements/designs.

  • Outputs based on need/solution.

  • 'Design' often technical; all business outputs termed 'requirements'.

  • Capture metadata; applies to all requirement types.

Inputs:

  1. Elicitation Results: Drive modeling.

Elements:

  1. Model Requirements:

    • Visual aids: Matrices, Diagrams.

    • Categories: People, Rationale, Activity Flow, Capability, Data.

  2. Analyze Requirements:

    • Decompose information.

    • Identify changes, address gaps.

  3. Represent Requirements:

    • Explicitly categorize.

  4. Implement Abstraction:

    • Tailor for stakeholders.

    • Ensure coherence.

Guidelines and Tools

  • Modelling Notations/Standards:

    • Precisely specify requirements with templates and syntax.

  • Modelling Tools:

    • Software for drawing and storing requirement diagrams.

  • Requirements Architecture:

    • Ensures completeness and consistency of requirement models.

  • Requirements Life Cycle Management Tools:

    • Software for recording and organizing requirements.

  • Solution Scope:

    • Defines boundaries for requirement models.

Techniques

  • Acceptance and Evaluation Criteria:

    • Represent requirements' acceptance attributes.

  • Business Capability Analysis:

    • Analyze enterprise functions.

  • Business Model Canvas:

    • Describe rationale for requirements.

  • Business Rules Analysis:

    • Analyze and specify business rules.

  • Concept Modelling:

    • Define terms relevant to the change.

  • Data Dictionary:

    • Record details about involved data.

  • Data Flow Diagrams:

    • Visualize data flow requirements.

  • Data Modelling:

    • Model requirements showing data usage.

  • Decision Modelling:

    • Represent decision-making elements.

  • Functional Decomposition:

    • Identify parts of complex functions.

  • Glossary:

    • Record meaning of business terms.

  • Interface Analysis:

    • Identify solution inputs and outputs.

  • Non-Functional Requirements Analysis:

    • Analyze service attributes.

  • Organizational Modelling:

    • Model roles and responsibilities.

  • Process Modelling:

    • Show organization's activities.

  • Prototyping:

    • Visualize planned solution capabilities.

  • Roles and Permissions Matrix:

    • Specify user duties.

  • Root Cause Analysis:

    • Model problem root causes.

  • Scope Modelling:

    • Visually show scope boundaries.

  • Sequence Diagrams:

    • Specify process interactions.

  • Stakeholder List, Map, or Personas:

    • Identify stakeholders and their characteristics.

  • State Modelling:

    • Specify solution part states.

  • Use Cases and Scenarios:

    • Model desired solution behavior.

  • User Stories:

    • Specify requirements as brief statements.

  • Stakeholders

    • Analysts or stakeholders may handle the task.

  • Requirements

    • Delivered as text, matrices, or diagrams.

bottom of page