Requirements Trade-offs During UML Design
Andrews, Anneliese ; Runeson, Per LU
and France, Robert
(2004)
p.282-291
- Abstract
- Designs almost always require trade-offs between competing
design choices to meet pervasive system dependability
requirements (e.g., security, performance and fault tolerance
system goals). In some cases, dependability requirements
are realized by functionality that cross-cuts designs.
Aspect-Oriented Modeling (AOM) methods allow developers
to localize such cross-cutting functionality in design
modeling views called aspects. Aspects can be composed
with other design views to obtain an integrated view of a design.
This paper presents a technique that extends such
methods to cover dependability requirements that are not
directly realized by... (More) - Designs almost always require trade-offs between competing
design choices to meet pervasive system dependability
requirements (e.g., security, performance and fault tolerance
system goals). In some cases, dependability requirements
are realized by functionality that cross-cuts designs.
Aspect-Oriented Modeling (AOM) methods allow developers
to localize such cross-cutting functionality in design
modeling views called aspects. Aspects can be composed
with other design views to obtain an integrated view of a design.
This paper presents a technique that extends such
methods to cover dependability requirements that are not
directly realized by functional structures in a design. Performance
goals provide examples of such requirements. We
also present a trade-off mechanism to rank feasible solutions
with respect to requirements priorities between different
dependability requirements. The paper applies this
technique to an example that has performance, fault-tolerance,
and security requirements. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/701535
- author
- Andrews, Anneliese
; Runeson, Per
LU
and France, Robert
- organization
- publishing date
- 2004
- type
- Chapter in Book/Report/Conference proceeding
- publication status
- published
- subject
- host publication
- Proceedings 11th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems
- pages
- 282 - 291
- publisher
- IEEE - Institute of Electrical and Electronics Engineers Inc.
- external identifiers
-
- scopus:7744236146
- language
- English
- LU publication?
- yes
- id
- 0535dda9-6672-4e14-9293-9fa41fab8434 (old id 701535)
- date added to LUP
- 2016-04-04 10:16:31
- date last changed
- 2022-01-29 20:04:28
@inproceedings{0535dda9-6672-4e14-9293-9fa41fab8434,
abstract = {{Designs almost always require trade-offs between competing<br/><br>
design choices to meet pervasive system dependability<br/><br>
requirements (e.g., security, performance and fault tolerance<br/><br>
system goals). In some cases, dependability requirements<br/><br>
are realized by functionality that cross-cuts designs.<br/><br>
Aspect-Oriented Modeling (AOM) methods allow developers<br/><br>
to localize such cross-cutting functionality in design<br/><br>
modeling views called aspects. Aspects can be composed<br/><br>
with other design views to obtain an integrated view of a design.<br/><br>
This paper presents a technique that extends such<br/><br>
methods to cover dependability requirements that are not<br/><br>
directly realized by functional structures in a design. Performance<br/><br>
goals provide examples of such requirements. We<br/><br>
also present a trade-off mechanism to rank feasible solutions<br/><br>
with respect to requirements priorities between different<br/><br>
dependability requirements. The paper applies this<br/><br>
technique to an example that has performance, fault-tolerance,<br/><br>
and security requirements.}},
author = {{Andrews, Anneliese and Runeson, Per and France, Robert}},
booktitle = {{Proceedings 11th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems}},
language = {{eng}},
pages = {{282--291}},
publisher = {{IEEE - Institute of Electrical and Electronics Engineers Inc.}},
title = {{Requirements Trade-offs During UML Design}},
year = {{2004}},
}