UML Profiles for Design Decisions and Non-Functional Requirements

Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007) Pub Date : 2007-05-20 DOI:10.1109/SHARK-ADI.2007.14

Liming Zhu, I. Gorton

{"title":"UML Profiles for Design Decisions and Non-Functional Requirements","authors":"Liming Zhu, I. Gorton","doi":"10.1109/SHARK-ADI.2007.14","DOIUrl":null,"url":null,"abstract":"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.","PeriodicalId":393813,"journal":{"name":"Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007)","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2007-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"65","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SHARK-ADI.2007.14","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 65

Abstract

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.

查看原文本刊更多论文

用于设计决策和非功能需求的UML概要文件

软件体系结构由一组设计决策组成。每个设计决策有助于或阻碍某些非功能需求(NFR)。当前的软件体系结构视图关注于表达系统中的组件和连接器。设计决策及其与非功能需求的关系通常在单独的设计文档中捕获，而不是在任何视图中明确表达。这种分离使得架构理解和架构进化更加困难。在本文中，我们提出了一个用于建模设计决策的UML概要文件，以及一个用于以通用方式建模非功能需求的相关UML概要文件。这两个UML概要文件将设计决策和非功能需求视为一级元素。建模的设计决策总是引用现有的体系结构元素，从而保持两者之间的可追溯性。我们提供了一种机制来检查这种可追溯性的一致性。最后给出了一个算例，说明了该方法的可行性。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007)

自引率

0.00%

发文量