liveBook · Manning

Quality attribute scenario

As explained in Microservices Patterns, Second Edition

A quality attribute scenario is a structured specification of an event, its source, the resulting response, the response measure, the environment, and the affected system artifact.

A quality attribute scenario turns an architectural requirement into a specific event, expected response, and measure. It applies to runtime qualities, such as availability and performance, and development-time qualities, such as modifiability, testability, and deployability. section 3.1.3

Specify each scenario with six parts:

  • Stimulus: the event that occurs. section 3.1.3
  • Stimulus source: where the event comes from. section 3.1.3
  • Response: the activity triggered by the event. section 3.1.3
  • Response measure: a criterion, such as latency, throughput, or time to make a change, used to assess the architecture. section 3.1.3
  • Environment: the conditions under which the scenario occurs. section 3.1.3
  • Artifact: the affected part of the system. section 3.1.3

Modifiability

An Orders team changes a business rule in Order Management without coordinating with other teams or changing the Discount Service; a survey records whether the change felt straightforward. This makes both the desired scope of change and its assessment explicit. section 5.2.1

Figure 3.3 An example availability scenario, which specifies that the application continues to handle requests when a service instance, such as the FTGO application’s Order Service, fails
availability scenario

The availability scenario illustrates a runtime requirement: requests continue to be handled when a service instance fails. section 3.1.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines six scenario fields and illustrates measurable availability, modifiability, testability, and deployability requirements.
Examples
Uses service failure, independent business-rule changes, timed tests, and deployments that trigger rollback.
What you can do after
Evaluate whether an architecture satisfies a quality requirement using a specified response measure.
How it connects
Connects architecture requirements with availability, modifiability, testability, and deployability.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.