Abstract
Managing dependencies between software development artifacts helps achieve traceability and consistency in software-intensive systems. Traceability supports the alignment between different stakeholder concerns, development artifacts, and various products of the software development process. Consistency ensures that different software development artifacts are used in different parts of a software-intensive system (or in the description of this system), without causing contradictions between the different parts of the system (or its description). In this position paper we explore how software architecture viewpoints and views can help represent dependencies and facilitate traceability and consistency in software architecture. Here, correspondences, which are parts of viewpoint definitions, express consistency, traceability, dependencies, obligations, etc. in the architecture. We provide examples of viewpoints and their mechanisms to support the description of dependencies. Furthermore, based on our experience we discuss challenges that occur when ensuring traceability, consistency, and managing dependencies between software development artifacts, with an emphasis on software architecture elements.
Sign-in/Register to access full text options 
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.
