The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.05 - Sept.-Oct. (2013 vol.30)
pp: 16-18
ABSTRACT
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
REFERENCES
1. J. Cleland-Huang, “Meet Elaine: A Persona-Driven Approach to Exploring Architecturally Significant Requirements,” IEEE Software, vol. 30, no. 4, 2013, pp. 18-21.
2. O. Gotel et al., “Traceability Fundamentals,” Software and Systems Traceability, J. Cleland-Huang, O. Gotel, and A. Zisman eds., Springer, 2012, pp. 3-22.
3. M. Mirakhorli, and J. Cleland-Huang, “Tracing Non-functional Requirements,” Software and Systems Traceability, J. Cleland-Huang, O. Gotel, and A. Zisman eds., Springer, 2012, pp. 299-320.
258 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool