UML Profiles for Design Decisions and Non-Functional Requirements
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
- Research Organization:
- Pacific Northwest National Lab. (PNNL), Richland, WA (United States)
- Sponsoring Organization:
- USDOE
- DOE Contract Number:
- AC05-76RL01830
- OSTI ID:
- 947505
- Report Number(s):
- PNNL-SA-54913; TRN: US200909%%111
- Resource Relation:
- Conference: 2nd International Workshop on SHAring and Reusing architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI 2007)
- Country of Publication:
- United States
- Language:
- English
Similar Records
Development of Analysis Methods that Integrate Numeric and Textual Equipment Reliability Data
Next Generation System Analysis Model Recently Added Features and Future Plans - Abstract