By Topic

Architecture Quality Revisited

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

5 Author(s)

There is a common belief in the software community that nonfunctional quality is fundamentally important for architecture sustainability and project success. A recent study, however, suggests that nonfunctional quality is of little relevance for users and customers, but instead mainly a concern for architects. Nontechnical constraints, such as licenses and technology providers, appear to be driving design as prominently as quality requirements. Quality requirements, such as performance, are mainly defined by architects on the basis of their experiences, and are often poorly documented and validated. This column explores whether the software community actually overestimates the relevance of nonfunctional qualities or whether the study's observations indicate a valid position on nonfunctional quality for certain types of application domains, development approaches, and organizational setups.

Published in:

Software, IEEE  (Volume:29 ,  Issue: 4 )