This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Twin Peaks of Requirements and Architecture
March-April 2013 (vol. 30 no. 2)
pp. 24-29
Jane Cleland-Huang, DePaul University
Robert S. Hanmer, Alcatel-Lucent
Sam Supakkul, Sabre
Mehdi Mirakhorli, DePaul University
Quality concerns, often referred to as nonfunctional requirements, service-level agreements, quality attributes, performance constraints, or architecturally significant requirements, describe system-level attributes such as security, performance, reliability, and maintainability. In conjunction with functional requirements, these quality concerns drive and constrain a system's architectural design and often introduce significant trade-offs that must be carefully considered and balanced. The dependencies that exist between requirements and architecture have been referred to as the twin peaks of requirements and architecture. The guest editors of this special issue describe this unique situation.
Index Terms:
quality,software development,architecture,requirements,design
Citation:
Jane Cleland-Huang, Robert S. Hanmer, Sam Supakkul, Mehdi Mirakhorli, "The Twin Peaks of Requirements and Architecture," IEEE Software, vol. 30, no. 2, pp. 24-29, March-April 2013, doi:10.1109/MS.2013.39
Usage of this product signifies your acceptance of the Terms of Use.