Quality Attribute Workshops (QAWs) provide a method for identifying a system's architecture-critical quality attributes, such as availability, performance, security, interoperability, and modifiability, that are derived from mission or business goals. The QAW does not assume the existence of a software architecture. It was developed to complement the SEI Architecture Tradeoff Analysis Method (ATAM) in response to customer requests for a method to identify important quality attributes and clarify system requirements before there is a software architecture to which the ATAM could be applied.
In the QAW, an external team facilitates meetings among stakeholders during which scenarios representing the quality attribute requirements are generated, prioritized, and refined (i.e., adding additional details such as the participants and assets involved, the sequence of activities, and questions about quality attributes requirements). The process of refining the scenarios allows stakeholders to communicate among themselves, thereby exposing assumptions that may not have surfaced during requirements elicitation. The refinement also provides insights as to how these attributes interact, forming a basis for making tradeoffs between these attributes.
There may be more than one scenario-generation workshop, depending on the number and type of organizations and stakeholders involved in the development, maintenance, or use of the system. The QAW process ends with the list of prioritized, refined scenarios. The refined scenarios can be used in different ways, for example as seed scenarios for ATAM or as test cases in an acquisition effort.
The QAW involves these steps:
In addition, stakeholders get a chance to ask questions and raise any concerns they have about those scenarios.
Organizations can use the QAW results to
In addition, after the architecture is created, the scenarios can be used as seed scenarios during an ATAM evaluation.
The QAW helps you determine the right qualities for your system before it is developed—something that is crucial for system success and for your stakeholders' satisfaction. Clarifying those requirements and then achieving them in the first version of your system saves money and avoids future rework. The QAW provides a structured and efficient setting for communicating with your stakeholders and supports analysis and testing throughout the life of the system.
The QAW provides a forum for a wide variety of stakeholders to gather in one room at one time early in the development process. It is often the first time such a meeting takes place and generally leads to the identification of conflicting assumptions about system requirements.
Organizations that are in the early stage of system development and need to clarify the system’s quality attribute requirements and stakeholders’ expectations for the system.