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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
