How can you train your system architecture team on quality attributes?

1 Define quality attributes

The first step to train your system architecture team on quality attributes is to define what they are, and why they matter. Quality attributes are the properties of a system that affect its satisfaction, success, and value for the stakeholders. They are not features or functions, but rather characteristics or constraints that influence the design and implementation of a system. Quality attributes are often conflicting, trade-off, and context-dependent, which means that they require careful analysis, prioritization, and negotiation among the stakeholders. Quality attributes are also dynamic, and may change over time as the system evolves or the environment changes.

2 Identify stakeholders and scenarios

The second step to train your system architecture team on quality attributes is to identify the stakeholders and scenarios that are relevant for the system. Stakeholders are the people or groups who have an interest or influence in the system, such as users, customers, developers, managers, regulators, etc. Scenarios are the situations or events that involve the system, such as normal operation, failure, change, attack, etc. By identifying the stakeholders and scenarios, you can elicit and specify the quality attributes that are important for each of them, and how they affect the system behavior and performance.

3 Use quality attribute frameworks

The third step to train your system architecture team on quality attributes is to use quality attribute frameworks to organize and communicate them. Quality attribute frameworks are models or taxonomies that classify and describe quality attributes in a systematic and consistent way. They help to avoid ambiguity, confusion, and inconsistency among the stakeholders and the architects. Some examples of quality attribute frameworks are ISO/IEC 25010, which defines a set of quality characteristics and sub-characteristics for software products; or ATAM, which is a method for evaluating and improving architectures based on quality attribute scenarios.

4 Apply quality attribute patterns

The fourth step to train your system architecture team on quality attributes is to apply quality attribute patterns to design and implement the system. Quality attribute patterns are reusable solutions or best practices that address common quality attribute problems or challenges. They provide guidance and principles for choosing and combining architectural elements, such as components, connectors, styles, views, etc., that influence the quality attributes of the system. Some examples of quality attribute patterns are MVC, which separates the concerns of user interface, business logic, and data access; or REST, which enables scalability, interoperability, and evolvability for web-based systems.

5 Measure and monitor quality attributes

The fifth step to train your system architecture team on quality attributes is to measure and monitor them throughout the system lifecycle. Measuring and monitoring quality attributes means collecting and analyzing data and feedback that indicate how well the system meets the quality attribute requirements and expectations. This can be done by using various techniques and tools, such as metrics, tests, surveys, logs, dashboards, etc., that provide quantitative and qualitative information about the system quality. Measuring and monitoring quality attributes helps to identify and resolve issues, validate and verify assumptions, and improve and optimize the system architecture.

6 Review and update quality attributes

The sixth and final step to train your system architecture team on quality attributes is to review and update them periodically. Reviewing and updating quality attributes means evaluating and revising them based on the changes and feedback that occur in the system and its environment. This can be done by using various methods and processes, such as reviews, audits, inspections, retrospectives, etc., that involve the stakeholders and the architects. Reviewing and updating quality attributes helps to ensure that they are aligned with the current and future needs and expectations of the system and its stakeholders.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?