Catalog
concept#Product#Software Engineering#Delivery#Governance

Requirements Engineering

Systematic process for eliciting, analyzing and managing requirements for systems and products. Aims to ensure traceability, prioritization and to reduce misaligned development.

Requirements engineering is the systematic process of eliciting, analyzing and managing requirements for a system or product.
Established
Medium

Classification

  • Medium
  • Business
  • Organizational
  • Intermediate

Technical context

Requirements repository (e.g. RM tool)Issue tracker / agile boardsTest management systems

Principles & goals

Early stakeholder involvementTraceability of requirementsIterative validation and adaptation
Discovery
Domain, Team

Use cases & scenarios

Compromises

  • Incomplete or conflicting requirements
  • Scope creep due to insufficient control
  • Misunderstandings between business and engineering
  • Formulate small, testable requirements
  • Continuous validation with stakeholders
  • Ensure traceability from requirements to tests

I/O & resources

  • Stakeholder interviews
  • Business and product goals
  • Existing system documentation
  • Requirements specification (e.g. user stories, SRS)
  • Prioritized product roadmap
  • Traceability matrix

Description

Requirements engineering is the systematic process of eliciting, analyzing and managing requirements for a system or product. It aligns stakeholder needs with technical specifications, reduces rework and supports traceable decisions. Core activities include elicitation, specification, validation and change management. It is essential for delivering fit-for-purpose solutions.

✔

  • Fewer misdevelopments through clear requirements
  • Better prioritization of features by business value
  • Higher stakeholder satisfaction through transparency

✖

  • Effort and cost for extensive specifications
  • Over-specification can reduce flexibility
  • Dependence on stakeholder availability

  • Requirement stability

    Share of requirements unchanged across iterations.

  • Traceability

    Percentage of requirements with trace links to implementation/tests.

  • Number of open ambiguities

    Count of requirements still ambiguous or conflicting.

Use-case driven specification

Requirements described and prioritized based on concrete user scenarios.

User stories with acceptance criteria

Agile teams use user stories plus clear acceptance criteria for validation.

SRS (Software Requirements Specification)

Formal specification for contractual or regulatory purposes.

1

Identify stakeholders and clarify goals

2

Elicit and prioritize requirements

3

Validate, document and trace requirements

⚠️ Technical debt & bottlenecks

  • Incomplete documentation hinders later changes
  • Missing traceability increases cost of defects
  • Inconsistent requirements cause integration problems
Stakeholder availabilityDomain complexityCommunication interfaces
  • Skipping prioritization leads to scope creep
  • Documenting technical details instead of user needs
  • Selecting stakeholders by availability rather than relevance
  • Fixing requirements too early
  • Unclear responsibilities for requirements
  • Lack of traceability between artifacts
Facilitation and interviewing techniquesAnalytical thinking and modelingDomain knowledge and stakeholder understanding
Traceability of requirementsInterface and integration requirementsRegulatory and compliance requirements
  • • Time and budget constraints
  • • Regulatory constraints
  • • Technical legacy conditions