An architectural pattern for non-functional dependability requirements

被引:17
作者
Xu, Lihua [1 ]
Ziv, Hadar [1 ]
Alspaugh, Thomas A. [1 ]
Richardson, Debra J. [1 ]
机构
[1] Univ Calif Irvine, Donald Bren Sch Informat & Comp Sci, Dept Informat, Irvine, CA 92697 USA
关键词
software architecture; architectural patterns; aspects; non-functional requirements;
D O I
10.1016/j.jss.2006.02.061
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
We address the research question of transforming dependability requirements into corresponding software architecture constructs, by proposing first that dependability needs can be classified into three types of requirements and second, an architectural pattern that allows requirements engineers and architects to map the three types of dependability requirements into three corresponding types of architectural components. The proposed pattern is general enough to work with existing requirements techniques and existing software architectural styles, including enterprise and product-line architectures. (C) 2006 Elsevier Inc. All rights reserved.
引用
收藏
页码:1370 / 1378
页数:9
相关论文
共 28 条
[1]  
ALSPAUGH TA, 2005, 11 INT WORKSH REQ EN, P187
[2]  
[Anonymous], 1996, Pattern-Oriented Software Architecture: A System of Patterns
[3]   Basic concepts and taxonomy of dependable and secure computing [J].
Avizienis, A ;
Laprie, JC ;
Randell, B ;
Landwehr, C .
IEEE TRANSACTIONS ON DEPENDABLE AND SECURE COMPUTING, 2004, 1 (01) :11-33
[4]   Theme: An approach for aspect-oriented analysis and design [J].
Baniassad, E ;
Clarke, S .
ICSE 2004: 26TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, PROCEEDINGS, 2004, :158-167
[5]  
BARBACCI MR, 2002, CMUSEI2002TN005
[6]  
BRANDOZZI M, 2003, 2 INT SOFTW REQ ARCH, P107
[7]  
CHUNG L, 1999, WICSA1 P TC2 1 WORK, P545
[8]  
Chung L., 2000, Non-functional Requirements in Software Engineering
[9]  
CLEMENTS P, 2002, DOCUMENTING SOFTWARE
[10]   A framework for integrating non-functional requirements into conceptual models [J].
Cysneiros L.M. ;
Leite J.C.S.D.P. ;
Neto J.D.M.S. .
Requirements Engineering, 2001, 6 (2) :97-115