GovernanceGrid

CHG-02 · Requirements definition

Catalogue · Build & Change

Business, security, resilience and compliance requirements are captured and agreed before solutions are built or bought.

Typical activities

  • Capture functional and non-functional requirements including security, availability and regulatory needs
  • Review requirements with business owners, security and risk before approval
  • Trace requirements to design and test cases

Evidence an assessor would expect

  • Requirements documents or backlog with non-functional items
  • Review sign-offs
  • Traceability matrix

Capability scale

0 · Absent
The practice is not performed, or happens so rarely that it produces no recognisable outcome.
1 · Initial
The practice is performed informally and its results depend on the people involved.
2 · Repeatable
The practice is planned, assigned and tracked, with basic records kept.
3 · Defined
The practice follows a documented, organisation-wide approach with clear roles and measurable outputs.
4 · Measured
The practice is managed with quantitative targets and its performance is monitored and reported.
5 · Optimising
The practice is continuously improved using performance data, external comparison and automation.

Regulatory requirements

Not directly mapped to a regulation in the current catalogue.

Cross-references

  • COBIT® 2019 BAI02
  • ISO/IEC 27001:2022 A.5.8

Identifiers only, for orientation. Consult the original publications for their content.