Specify and Model Requirements


The purpose of Specify and Model Requirements is to analyze, synthesize, and refine elicitation results into requirements and designs.


Specify and Model Requirements describes the practices for analyzing elicitation results and creating representations of those results. When the focus of the specifying and modelling activity is on understanding the need, the outputs are referred to as requirements. When the focus of the specifying and modelling activity is on a solution, the outputs are referred to as designs.

Important: In many IT environments, the word ‘design’ is used specifically for technical designs created by software developers, data architects, and other implementation subject matter experts. All business deliverables are referred to as ‘requirements’.

In addition to the models used to represent the requirements, this task also includes capturing information about attributes or metadata about the requirements. The specifying and modelling activities relate to all requirement types.

  • Elicitation Results (any state)
  • Elements:
    • Model Requirements
      • Types
        • Matrices
        • Diagrams
      • Categories
        • People and Roles
        • Rationale
        • Activity Flow
        • Capability
        • Data and Information
    • Analyze Requirements
    • Represent Requirements and Attributes
    • Implement the Appropriate Levels of Abstraction
    Guidelines and Tools:
    • Modelling Notations/Standards
    • Modelling Tools
    • Requirements Architecture
    • Requirements Life Cycle Management Tools
    • Solution Scope
  • Acceptance and Evaluation Criteria
  • Business Capability Analysis
  • Business Model Canvas
  • Business Rules Analysis
  • Concept Modelling
  • Data Dictionary
  • Data Flow Diagrams
  • Data Modelling
  • Decision Modelling
  • Functional Decomposition
  • Glossary
  • Interface Analysis
  • Non-Functional Requirements Analysis
  • Organizational Modelling
  • Process Modelling
  • Prototyping
  • Roles and Permissions Matrix
  • Root Cause Analysis
  • Scope Modelling
  • Sequence Diagrams
  • Stakeholder List, Map, or Personas
  • State Modelling
  • Use Cases and Scenarios
  • User Stories
  • Stakeholders:
    • Any stakeholder
  • Requirements (specified and modelled)
  • Knowledge Area:
  • Requirements Analysis and Design Definition