ICRAD: AN INTEGRATED PROCESS FOR THE SOLUTION OF REQUIREMENTS CONFLICTS AND ARCHITECTURAL DESIGN
Andrea Monika Herrmann, Barbara Paech, Damian Plaza · International Journal of Software Engineering and Knowledge Engineering · 2006
In order to solve requirements conflicts when developing or enhancing an IT system, it is essential to understand its architecture. Frequently, the costs for the realization of certain requirements are a decision criterion. Requirements negotiation and architectural design must be treated together, as conflicts cannot be solved before the architecture has been designed. So far, no integrated process exists which clearly defines input and output among these activities, and which takes into account a variety of different types of dependencies among requirements and between requirements and architecture. In this paper, we develop a detailed iterative process named ICRAD (Integrated Conflict Resolution and Architectural Design). ICRAD integrates requirements negotiation and architectural design and takes into account nine types of dependencies. We define three types of requirements conflicts. We also present a case study.