Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Software Architecture in Practice
Software Architecture in Practice
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
The Past, Present, and Future for Software Architecture
IEEE Software
Characterizing Relations between Architectural Views
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
The notion of variability in software architecture: results from a preliminary exploratory study
Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems
ECSA'13 Proceedings of the 7th European conference on Software Architecture
| Hi-index | 0.00 |
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.