Software architecture in practice
Software architecture in practice
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Systematic Formulation of Non-Functional Characteristics of Software
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Quantifying the value of architecture design decisions: lessons from the field
Proceedings of the 25th International Conference on Software Engineering
Designing information systems in social context: a goal and scenario modelling approach
Information Systems - Special issue: The 14th international conference on advanced information systems engineering (CAiSE*02)
Unified Modeling Language Reference Manual, The (2nd Edition)
Unified Modeling Language Reference Manual, The (2nd Edition)
Architecture Decisions: Demystifying Architecture
IEEE Software
ECBS '05 Proceedings of the 12th IEEE International Conference and Workshops on Engineering of Computer-Based Systems
Model Driven Development with non-functional aspects
EA '09 Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design
Scaling up software architecture evaluation processes
ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Using rationale to support pattern-based architectural design
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
A model for specifying rationale using an architecture description language
ECSA'11 Proceedings of the 5th European conference on Software architecture
Extending SysML to explore non-functional requirements: the case of information system design
Proceedings of the 27th Annual ACM Symposium on Applied Computing
| Hi-index | 0.00 |
A software architecture is composed of a collection of design decisions. Each design decision helps or hinders certain Non-Functional Requirements (NFR). Current software architecture views focus on expressing components and connectors in the system. Design decisions and their relationships with non-functional requirements are often captured in separate design documentation, not explicitly expressed in any views. This disassociation makes architecture comprehension and architecture evolution harder. In this paper, we propose a UML profile for modeling design decisions and an associated UML profile for modeling non-functional requirements in a generic way. The two UML profiles treat design decisions and nonfunctional requirements as first-class elements. Modeled design decisions always refer to existing architectural elements and thus maintain traceability between the two. We provide a mechanism for checking consistency over this traceability. An exemplar is given as a way to demonstrate the feasibility of our approach.