Resolving Requirement Conflicts through Non-Functional Decomposition

Authors:
Affiliations:
Venue:
WICSA '04 Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture
Year:
2004

Citing 0
Cited 3

Software architecting without requirements knowledge and experience: What are the repercussions?

Journal of Systems and Software
Controversy Corner: On the similarity between requirements and architecture

Journal of Systems and Software
Conflict detection and resolution for product line design in a collaborative decision making environment

Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work

Quantified Score

Hi-index	0.00

Visualization

Abstract

A lack of insight into the relationship between (non-)functional requirements and architectural solutions oftenleads to problems in real life projects. This paper presents amodel that concentrates on the mapping of non-functionalrequirements onto functional requirements for architecturedesign. We build a framework that both provides a modeland a repeatable method to transform conflicting requirementsinto a system decomposition. This paper presents theframework, and discusses two cases onto which the methodis applied. In one case, the method is successfully used toreconstruct the high-level structure of a system from its requirements.The second case is one in which the method wasactually used to create a system design fitting the stakeholders'needs, and that is reproducible from its requirements.