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.
Keywords :
formal specification; program diagnostics; software architecture; software maintenance; architectural decisions; architectural degradation; architecturally significant requirements; change maintenance; code quality; long-lived software systems; requirements engineers; strategic traceability; trace links; Data models; Software architecture; Software systems; architecture; quoins; requirements; traceability;
