The Community for Technology Leaders
RSS Icon
Issue No.04 - July-Aug. (2012 vol.29)
pp: 22-24
Frank Buschmann , Siemens Corporate Technology
David Ameller , Barcelona­Tech—Universitat Politècnica de Catalunya
Claudia P. Ayala , Barcelona­Tech—Universitat Politècnica de Catalunya
Jordi Cabot , École des Mines de Nantes
Xavier Franch , Barcelona­Tech—Universitat Politècnica de Catalunya
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.
architecture design decisions, nonfunctional requirements elicitation, architecture quality, architecture design
Frank Buschmann, David Ameller, Claudia P. Ayala, Jordi Cabot, Xavier Franch, "Architecture Quality Revisited", IEEE Software, vol.29, no. 4, pp. 22-24, July-Aug. 2012, doi:10.1109/MS.2012.77
1. D. Ameller et al., Non-functional Requirements in Software Architecture Practice, report ESSI-TR-12-1, Universitat Politècnica de Catalunya, Barcelona, 2012;
2. F. Buschmann, "Learning from Failure, Part 2: Featuritis, Performitis, and Other Diseases," IEEE Software, vol. 27, no. 1, 2010, pp. 10–11.
3. F. Buschmann, "Value-Focused System Quality," IEEE Software, vol. 27, no. 6, 2010, pp. 84–86.
4. F. Buschmann, "A Week in the Life of an Architect," IEEE Software, vol. 29, no. 3, 2012, pp. 94–96.
5. F. Buschmann, "On Architecture Styles and Paradigms," IEEE Software, vol. 27, no. 5, 2010, pp. 92–94.
6. B. Foote and J.W. Yoder, "Big Ball of Mud," Pattern Languages of Program Design 4,. Harrison B. Foote, and H. Rohnert eds., Addison-Wesley, 2000, pp. 653–692.
37 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool