This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Architectural degradation is a common problem in most nontrivial, long-lived software systems. By identifying architecturally significant requirements and establishing trace links from those requirements, via architectural decisions, to code, we can keep developers informed of underlying architectural decisions and help preserve code quality during change maintenance. The Web extra at http://youtu.be/U6MAlOvJpQY is an audio podcast of author Jane Cleland-Huang reading her Requirements column, in which she discusses how requirements engineers can keep developers informed of underlying architectural decisions and help preserve code quality during change maintenance.
Index Terms:
Software architecture,Data models,Software systems,quoins,requirements,architecture,traceability
Citation:
Jane Cleland-Huang, "Thinking about Quoins: Strategic Traceability of Architecturally Significant Requirements," IEEE Software, vol. 30, no. 5, pp. 16-18, Sept.-Oct. 2013, doi:10.1109/MS.2013.117
Usage of this product signifies your acceptance of the Terms of Use.