Requirements and design

SOUP / external service SOUP (software of unknown provenance) or an external service: a third-party component the system inc...

HIPAA addressable decision The recorded decision for a HIPAA Security Rule implementation specification marked addressable. The...

PHI flag The medical flag on a requirement that says whether it involves protected health information. For a...

Risk control A requirement whose purpose is to control an identified hazard or threat. It links the risk id and a...

Business scenario A future-state scenario in an analysis document. It names its actors by role, its trigger, its preco...

Context (black box) The system seen as a black box: every external system and actor, the information exchanged across ea...

Stakeholder and concern A stakeholder is a role with an interest in the system, listed with its concerns and its authority o...

Quality scenario The form of a quality or architecture requirement, in six parts: source, stimulus, environment, arti...

Architecture principle A rule that guides design choices. It has a name, a statement, a rationale and its implications.

Constraint A limit on the design that names its source (a contract, a regulation, a policy or a decision by a n...

Architecture decision (ADR) A design choice recorded with its rationale, not stated as a requirement. An ADR has a title, contex...

Technical design The design output. It takes each requirement of the analysis document and states how it is met, with...

Analysis document A design input. It specifies what the system must do in the target state, as owned, scoped, traceabl...

Change authority The person, team or automated rule that decides a change, assigned by the change's risk. A change ad...

Change request A request to change an approved requirement. The requirement goes to change-requested with an impact...

Requirement lifecycle The states a requirement moves through: proposed, analyzed, approved (baselined), allocated, impleme...

Baseline The set of approved requirements fixed as design input, identified by a baseline id. A requirement j...

Traceability The links that tie each requirement to what it comes from and to what carries it out. Up: goal, stak...

Validation Confirming that the system meets the user need behind the requirement. A requirement is validated ag...

Verification Confirming that the system meets the requirement as written, using the requirement's verification me...