A framework for classifying and comparing architecture description languages
ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Reconciling the needs of architectural description with object-modeling notations
Science of Computer Programming - Special issue on unified modeling language (UML 2000)
Integrating the ConcernBASE Approach with SADL
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Statistical Constraints and Verification
Object Modeling with the OCL, The Rationale behind the Object Constraint Language
Experiences in deploying model-driven engineering
SDL'07 Proceedings of the 13th international SDL Forum conference on Design for dependable systems
SAM'12 Proceedings of the 7th international conference on System Analysis and Modeling: theory and practice
| Hi-index | 0.00 |
A critical level of abstraction in the modeling of a large, complex system is its architecture. At an architectural level one models the principal system elements and their interaction. Architectural models are typically used to provide an intellectually tractable, birds-eye view of a system and to permit design-time reasoning about system-level concerns such as performance, reliability, portability, and conformance to external standards and architectural styles. In practice most architectural descriptions are informal documents. They are usually centered on box-and-line diagrams, with explanatory prose. Visual conventions are idiosyncratic, and usually project specific. As a result, architectural descriptions are only vaguely understood by developers, they cannot be analyzed for consistency or completeness, they are only hypothetically related to implementations, their properties cannot be enforced as a system evolves, and they cannot be supported by tools to help software architects with their tasks. There exist several architecture description languages, but we are interested in the use of UML. We aim to identify requirements on architectural modeling and how different modeling concepts of UML meet these requirements. This paper is not intended as a critique of the UML but as a discussion of approaches to modeling architectures that have been tried, more or less successfully.