Tactics for Quality Attributes

Availability Tactics

Availability tactics help a system remain operational or recover when faults occur.

So it groups availability tactics into three categories:

  • Fault detection
  • Fault recovery
  • Fault prevention

Fault Detection

Fault detection tactics identify faults that may affect system operation.

TacticDescription
Ping/EchoOne component sends a message to another and checks whether a response is received.
HeartbeatA component periodically sends a signal indicating that it is operating.
ExceptionsExceptional conditions are reported so they can be handled.

Fault Recovery

Fault recovery tactics help a system continue operating or restore operation after a fault.

TacticDescription
VotingMultiple results are compared or voted on to determine the accepted result.
Active Redundancy(hot restart)Redundant components operate actively.
Passive Redundancy(warm restart)A backup component is maintained for recovery.
SpareA replacement resource is available when a component fails.
Shadow OperationA secondary system operates alongside the primary system to support a controlled transition or recovery.
State SynchronizationRedundant components are kept consistent by synchronizing their state.
Checkpoint/RollbackThe system records a recoverable state and returns to it when necessary.

Fault Prevention

Fault prevention tactics help prevent faults from affecting normal system operation.

TacticDescription
Removal from ServiceA component is taken out of service when necessary to prevent further problems.
TransactionsOperations are managed as transactions to help preserve consistency.
Process MonitorA monitoring mechanism observes processes and helps manage their operation.

Modifiability Tactics

Modifiability tactics make changes easier and help limit the impact of modifications on other parts of a system.

Two main approaches:

  • Localize modifications.
  • Defer binding time.

Localize Modifications

The goal is to reduce the number of system elements affected by a change.

TacticDescription
Maintain Semantic CoherenceKeep related responsibilities together so changes to one concern are localized.
Anticipate Expected ChangesConsider likely future changes when designing the system.
Generalize the ModuleDesign a module so it can support a suitable range of related requirements.
Limit Possible OptionsRestrict unnecessary choices to reduce the complexity of future changes.

Defer Binding Time

Binding time is the point at which a design decision or association becomes fixed.

Deferring binding time allows certain decisions to be changed later.

TacticDescription
Runtime RegistrationRegister a component or service while the system is running.
Configuration FilesStore configurable choices outside the main program code.
PolymorphismAllow different implementations to be used through a common interface.
Component ReplacementReplace one component with another compatible component.
Adherence to Defined ProtocolsUse established interaction rules so components can be changed while maintaining compatibility.

Performance Tactics

Performance tactics help a system generate responses within specified time constraints.

Events arrive → Performance tactics → Response within time constraints

The design must consider how events are handled and how the system responds within the required time.

Security Tactics

It groups security tactics into three categories.

CategoryGoal
Resisting AttacksPrevent or withstand attacks against the system.
Detecting AttacksIdentify attacks that affect the system.
Recovering from AttacksRestore or maintain acceptable operation after an attack.

Testability Tactics

Testability tactics help determine whether a system behaves as expected and make it easier to identify problems.

It identifies two categories:

  • Input/Output: Supports testing by providing inputs and observing outputs.
  • Internal Monitoring: Provides information about internal system behavior to support testing.

Usability Tactics

Usability tactics support the usability of a system.

It identifies two categories:

  • Runtime: Tactics that support users while the system is running.
  • Design-time: Tactics that support usability through design decisions.
Written by October 22, 2026 4 min read
Was this helpful?