# Research Infusion 2008

# Tool or Technology Information

**[Contact Information]{.underline}**

Name of Tool/Technology: Quality Attribute Workshops (QAW)

Name of Technology Provider: Software Engineering Institute

Primary Point of Contact (PPC): David Scherb

PPC Phone No.: 412-268-3946

PPC e-mail: <dscherb@sei.cmu.edu>

Alternate Contact Name (APC): Bill Wood

APC Phone No.: 412-268-7723

APC e-mail: <wgw@sei.cmu.edu>

Technology Provider Website:
<http://www.sei.cmu.edu/architecture/qaw.html>

Technology Provider Address: Software Engineering Institute

Customer Relations

4500 Fifth Avenue

Pittsburgh, PA 15213-2612

USA

**[Tool/Technology Details]{.underline}**

Description of Tool/Technology: 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 complements the Architecture Tradeoff Analysis
Method (ATAM) developed by the SEI. In an ATAM evaluation, an external
team facilitates sessions during which scenarios are developed
representing the quality attributes of the system. These scenarios are
then prioritized, and the highest priority scenarios are analyzed
against the software architectural approaches chosen for the system. The
results are expressed as risks, sensitivity points, and tradeoffs.
However an ATAM evaluation would be of limited value in the early phases
of the life cycle, before there is a software architecture. The QAW does
not assume the existence of a software architecture. It was developed to
complement the 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 between
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 refined scenarios can be used in different ways, for
example as seed scenarios for ATAM or as test cases in an acquisition
effort.

For details, see:

Barbacci, M.; Ellison, R.; Lattanze, A.; Stafford, J.; Weinstock, C.; &
Wood, W. [Quality Attribute Workshops, 3rd
Edition](http://www.sei.cmu.edu/publications/documents/03.reports/03tr016.html)
(CMU/SEI-2003-TR-016). Pittsburgh, PA: Software Engineering Institute,
Carnegie Mellon University, 2003.

Commercial or Research Technology: Research

Associated Program:

Potential Benefits: A multitude of people have a stake in a system\'s
architecture, and all of them exert whatever influence they can on the
architect(s) to make sure that their goals are addressed. For example,
the users want a system that is easy to use and has rich functionality.
The maintenance organization wants a system that is easy to modify. The
developing organization (as represented by management) wants a system
that is easy to build, and will employ the existing work force to good
advantage. The customer (who pays the bill) wants the system to be built
on time and within budget. All of these stakeholders will benefit from
applying the ATAM and QAW approaches. And needless to say the architect
is also a primary beneficiary.

We have seen many benefits of using the QAW including:

-   Clarified quality attribute requirements

-   Improved architecture documentation

-   Documented basis for architectural decisions

-   Identified risks early in the life-cycle

-   Increased communication among stakeholders

QAW contributes to software assurance by providing quality attribute
scenarios with a concrete response measure that can be used to guide
development to ensure the system achieves important quality attribute
goals.

Supported Platforms: QAW is described by technical reports (PDF), and a
reference guide (PDF). Conducting a QAW is supported by a QAW kit
consisting of slides and templates in Microsoft Office PowerPoint and
Word.

Required Inputs: Description of the business drivers (business goals and
requirements), description of the architectural plan

Outputs Produced: Quality attribute requirements in the form of
prioritized and refined scenarios

**[Maturity Level]{.underline}**

Applied to Real Problems? Yes No

If Yes, Level of Success Achieved: Examples and case studies are
available in:

Bergey, J.; & Wood, W. [Use of Quality Attribute Workshops (QAWs) in
Source Selection for a DoD System Acquisition: A Case
Study](http://www.sei.cmu.edu/publications/documents/02.reports/02tn013.html)
(CMU/SEI-2002-TN-013). Pittsburgh, PA: Software Engineering Institute,
Carnegie Mellon University, 2002.

John Bergey, Mario Barbacci, William Wood, [Using Quality Attribute
Workshops to Evaluate Architectural Design Approaches in a Major System
Acquisition: A Case
Study](http://www.sei.cmu.edu/publications/documents/00.reports/00tn010.html)
(CMU/SEI-2000-TN-010).

Already in Use within NASA? Yes No

If Yes, at what center(s): Used once. Information is not publicly
available. Contact PPC for details.

**[Support]{.underline}**

User/Ref. Documentation Available: Yes

Phone Support Available: No, but education materials are available.

Is Tool/Technology Developer willing to support infusion effort? Yes No

**[Licensing]{.underline}**

Is Tool/Technology Developer willing to provide Evaluation Copy for
extended period of time? Yes No N/A

**[Other Information]{.underline}**

The QAW method has been described in a technical report. It has been
used by the SEI mostly in command and control application domains. The
SEI is currently looking for organizations that would like to help us
improve QAW by testing the method in other domains.

<http://www.sei.cmu.edu/architecture/products_services/qaw.html>

All technical reports and technical notes on the subject are freely
available for download:

[http://www.sei.cmu.edu/architecture/pub_by_topic.html#qaw](http://www.sei.cmu.edu/architecture/pub_by_topic.html%23qaw)