Channels ▼


The SPAMMED Architecture Framework

Discover Quality Attributes

Architecture is mainly concerned with ensuring that the system's quality attributes are covered. By quality attributes—also known as "nonfunctional" requirements or "ilities"—I mean requirements that have system-wide implications and cover areas such as performance, security, availability, flexibility, usability, testability, and the like.

Discovering or hatching quality attributes is extremely important because they provide the basis for modeling the architecture. I recommend using the scenarios-based approach detailed by Paul Clements et al. in Evaluating Software Architectures: Methods and Case Studies (Addison-Wesley, ISBN 020170482X). With this approach, you construct a "utility tree" that demonstrates the overall goodness of a system. The base quality attributes are refined to specific areas that are then further refined to scenarios in the application where the attributes are evident (the scenarios are used both for modeling and testing/evaluating the architecture). This is best explained by examples such as Figure 1.

[Click image to view at full size]

Figure 1: Scenario examples.

Once you have more than one quality attribute nailed down, it is important to prioritize them because it is unlikely the architecture will be able to address all of them (at least not equally). Prioritization doesn't have to be performed by the architect alone. It can be wise to get other stakeholders involved in the process. Doing so helps everyone understand the trade-offs later in the game.

One quality attribute the architect should introduce is flexibility. Architectural decisions are relatively hard to change. You should try to allow even a small amount of flexibility into the design because requirements are sure to change.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.