Concern to Measure — Interactive Worksheet

1 · Raw Statement

Who / role

Date

System / service

Raw statement (verbatim)

Context — when / where / which user journey or business scenario Include environment assumptions: peak / normal / degraded · locations · user groups.

Impact — what is at risk (harm / cost / delay / compliance / operations)

2 · Classify Concern Type — tick all that apply

Possible conflict (forces)? Yes No If yes — name competing concerns and treat them as forces, not personal disagreement.

3 · Reframe as a Concern — neutral, actionable

Template: "Our concern is [topic] so that [stakeholder outcome], under [context]." — ISO 42010 defines concern as a stakeholder interest; TOGAF emphasises concerns as roots of requirements decomposition.

Reframed concern

4 · Scenario — make it refutable (SEI QAW / ATAM structure)

Environment (assumptions)

Hint

Load / degraded mode / location / user group

Stimulus (event / load / failure / threat / change)

Hint

What triggers the scenario?

Scope (service / transaction / user group / component)

Hint

Boundary of concern

Response (observable behaviour)

Hint

What the system does in response

Response measure (how success is measured)

Hint

Quantitative target — feeds directly into the Requirement instance

5 · Measure — requirement instance + evidence

BCS: NFRs are usually quantitatively measurable; link each SMART "shall" statement to an acceptance test, monitoring threshold, or audit criterion.

Requirement instance (SMART "shall" statement)

Metric(s) & target(s)

Measurement point (where measured)

Time window / conditions

Owner

Due / gate

Evidence method

Concern to Measure — Worksheet

Review your completed worksheet below. Print or save as PDF using your browser.