Achieving Quality Attributes
Software architects make design decisions to achieve the required quality attributes.
These decisions may be implemented using:
- Design patterns
- Architectural patterns
- Architectural strategies
Architectural Tactics
A tactic is a fundamental design decision that influences the response of a system to achieve a desired quality attribute.
For example, an architect may introduce redundancy to improve availability.
Purpose of Tactics
Tactics help architects:
- Achieve desired quality attributes.
- Control how a system responds to stimuli.
- Make important design decisions.
- Improve specific aspects of system quality.
Tactics and Architectural Strategies
An architectural strategy is a collection of tactics used together to achieve desired system qualities.
A tactic can also be refined into more specific tactics.
For example:
- Redundancy is a general tactic.
- Data redundancy and computational redundancy are more specific forms of redundancy.
Tactics and Patterns
An architectural pattern packages a collection of tactics into a reusable design solution.
For example, an availability pattern may use:
- Redundancy to provide alternative resources.
- Synchronization to coordinate redundant resources.
A pattern therefore represents a broader solution that can incorporate several tactics.
Where Tactics Fit in the Design Process
- Develop an idea about the system.
- Identify important quality attributes.
- Describe the requirements using quality attribute scenarios.
- Select tactics that help achieve the desired quality attributes.
Tactics provide the initial design decisions that guide the development of the architecture.
General Model of Architectural Tactics
Tactics control the response of a system to a stimulus.
The general model is:
Stimulus → Tactics to Control Response → Response
- Stimulus: An event or condition that affects the system.
- Tactics: Design decisions used to control the system’s response.
- Response: The resulting system behavior.
For example, when a component fails, availability tactics can help the system detect the fault and recover.
Categories of Architectural Tactics
| Quality Attribute | Main Goal |
|---|---|
| Availability | Detect faults, prevent faults, and recover from faults. |
| Modifiability | Make changes easier and limit their impact. |
| Performance | Generate responses within time constraints. |
| Security | Resist, detect, and recover from attacks. |
| Testability | Support testing through input/output and internal monitoring. |
| Usability | Support users through runtime and design-time mechanisms. |