Addressing non-functional properties in software architectures using ADL

Christopher van Eenoo; Osama Hylooz; Khaled M. Khan

Addressing non-functional properties in software architectures using ADL

Christopher van Eenoo, Osama Hylooz, Khaled M. Khan

Research output: Chapter in Book / Conference Paper › Conference Paper

Abstract

![CDATA[Architecture definition languages (ADLs) are used to specify high-level structural details of software systems. Many ADLs have emerged recently and whilst all address structural and functional elements such as components and connectors, few can be used to specify non-functional requirements such as security or performance. This paper proposes some constructs to one such ADL, WRIGHT, for specifying non-functional requirements and assurances. The proposed ADL constructs are used in an example to demonstrate their applicability. Although the constructs are informal at this stage of the research, this will enhance the user’s ability to understand the non-functional requirements and assurances of the system.]]

Original language	English
Title of host publication	Proceedings of the Sixth Australasian Workshop on Software System Architectures: AWSA 2005
Publisher	Swinburne University of Technology
Number of pages	7
ISBN (Print)	0855908122
Publication status	Published - 2005
Event	Australasian Workshop on Software and System Architectures - Duration: 1 Jan 2005 → …

Conference

Conference	Australasian Workshop on Software and System Architectures
Period	1/01/05 → …

Keywords

architecture definition languages
Wright
software architecture
non-functional requirements
computer security
performance

Cite this

@inproceedings{cc1e1dcdbee64811b90be822dedbe55a,

title = "Addressing non-functional properties in software architectures using ADL",

abstract = "![CDATA[Architecture definition languages (ADLs) are used to specify high-level structural details of software systems. Many ADLs have emerged recently and whilst all address structural and functional elements such as components and connectors, few can be used to specify non-functional requirements such as security or performance. This paper proposes some constructs to one such ADL, WRIGHT, for specifying non-functional requirements and assurances. The proposed ADL constructs are used in an example to demonstrate their applicability. Although the constructs are informal at this stage of the research, this will enhance the user{\textquoteright}s ability to understand the non-functional requirements and assurances of the system.]]",

keywords = "architecture definition languages, Wright, software architecture, non-functional requirements, computer security, performance",

author = "Eenoo, {Christopher van} and Osama Hylooz and Khan, {Khaled M.}",

year = "2005",

language = "English",

isbn = "0855908122",

booktitle = "Proceedings of the Sixth Australasian Workshop on Software System Architectures: AWSA 2005",

publisher = "Swinburne University of Technology",

note = "Australasian Workshop on Software and System Architectures ; Conference date: 01-01-2005",

}

TY - GEN

T1 - Addressing non-functional properties in software architectures using ADL

AU - Eenoo, Christopher van

AU - Hylooz, Osama

AU - Khan, Khaled M.

PY - 2005

Y1 - 2005

N2 - ![CDATA[Architecture definition languages (ADLs) are used to specify high-level structural details of software systems. Many ADLs have emerged recently and whilst all address structural and functional elements such as components and connectors, few can be used to specify non-functional requirements such as security or performance. This paper proposes some constructs to one such ADL, WRIGHT, for specifying non-functional requirements and assurances. The proposed ADL constructs are used in an example to demonstrate their applicability. Although the constructs are informal at this stage of the research, this will enhance the user’s ability to understand the non-functional requirements and assurances of the system.]]

AB - ![CDATA[Architecture definition languages (ADLs) are used to specify high-level structural details of software systems. Many ADLs have emerged recently and whilst all address structural and functional elements such as components and connectors, few can be used to specify non-functional requirements such as security or performance. This paper proposes some constructs to one such ADL, WRIGHT, for specifying non-functional requirements and assurances. The proposed ADL constructs are used in an example to demonstrate their applicability. Although the constructs are informal at this stage of the research, this will enhance the user’s ability to understand the non-functional requirements and assurances of the system.]]

KW - architecture definition languages

KW - Wright

KW - software architecture

KW - non-functional requirements

KW - computer security

KW - performance

UR - http://handle.uws.edu.au:8081/1959.7/40473

M3 - Conference Paper

SN - 0855908122

BT - Proceedings of the Sixth Australasian Workshop on Software System Architectures: AWSA 2005

PB - Swinburne University of Technology

T2 - Australasian Workshop on Software and System Architectures

Y2 - 1 January 2005

ER -

Addressing non-functional properties in software architectures using ADL

Abstract

Conference

Keywords

Other files and links

Fingerprint

Cite this