Quality Attribute Scenarios

A quality attribute scenario describes how a system should respond to a particular situation.

It provides a structured way to specify quality requirements so that the expected response can be evaluated and tested.

Six Parts of a Quality Attribute Scenario

A quality attribute scenario consists of six parts.

PartDescription
Source of StimulusThe entity that generates the stimulus, such as a user, computer system, or another actor.
StimulusThe event or condition that needs to be handled by the system.
EnvironmentThe condition of the system when the stimulus occurs, such as normal operation or overload.
ArtifactThe part of the system being stimulated. It may be a component or the whole system.
ResponseThe activity performed by the system after the stimulus arrives.
Response MeasureA measurable result used to evaluate whether the requirement has been satisfied.

General and Concrete Scenarios

General Quality Attribute Scenarios

A general scenario is system-independent and can potentially apply to different systems.

It describes a common quality-related situation without referring to one particular implementation.

Concrete Quality Attribute Scenarios

A concrete scenario is specific to the system being considered.

It defines how a particular system should respond to a specific situation.

Example: Availability Scenario

An availability scenario describes how a system responds when a fault occurs.

PartExample
Source of StimulusInternal or external source
StimulusOmission, crash, timing fault, or incorrect response
EnvironmentNormal operation or degraded operation
ArtifactProcess, storage, processor, or communication component
ResponseRecord the fault, notify relevant parties, disable a component, continue operating, or become unavailable
Response MeasureRepair time, degraded-operation interval, or unavailability interval

Example: Modifiability Scenario

A modifiability scenario describes how easily a system can be changed.

PartExample
Source of StimulusDeveloper
StimulusWishes to change the user interface
EnvironmentDesign time
ArtifactCode
ResponseThe modification is completed without side effects
Response MeasureThe modification is completed within three hours

Why are Scenarios Useful?

Quality attribute scenarios help to:

  • Clarify quality requirements.
  • Describe expected system behavior under specific conditions.
  • Identify measurable acceptance criteria.
  • Communicate requirements among stakeholders.
  • Evaluate whether an architecture supports the required qualities.

A good scenario describes not only what should happen but also how the result will be measured.

Written by October 22, 2026 3 min read
Was this helpful?