Managing conflicts among non-functional requirements

Non-functional requirements (NFRs) tend to interfere, conflict, and contradict with one other. Unlike functional requirements, this inevitable conflict arises as a result of inherent contradiction among various types of NFRs. A number of techniques to deal with this conflict have been developed. Majority of them focus on categorizing, documenting, or listing the potential conflicts among NFRs. Several models that represent the positive or negative relationships among NFRs have also been published in literature. However, the interpretation of NFRs may vary depending on numerous factors, such as the context of the system being developed and stakeholder involvement. Consequently, the relationships among them are not always obvious. This paper investigates the gaps in the existing research literature about the conflicts among NFRs and proposes a framework to manage this type of conflict. Keywordsconflicts, non-functional requirements,

[1]  C. Ebert.  Putting requirement management into praxis: dealing with nonfunctional requirements , 1998, Inf. Softw. Technol..

[2]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[3]  Leonard J. Bass,et al.  Scenario-Based Analysis of Software Architecture , 1996, IEEE Softw..

[4]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[5]  David J Grimshaw,et al.  Non-functional requirements analysis: deficiencies in structured methods , 2001, Inf. Softw. Technol..

[6]  Capers Jones,et al.  Patterns of software system failure and success , 1996 .

[7]  Didar Zowghi,et al.  A study of the impact of requirements volatility on software project performance , 2002, Ninth Asia-Pacific Software Engineering Conference, 2002..

[8]  Mark Klein,et al.  Attribute-Based Architectural Styles , 1999 .

[9]  Jan Bosch,et al.  Software architecture design: evaluation and transformation , 1999, Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems.

[10]  Jan Bosch,et al.  Architecture level prediction of software maintenance , 1999, Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090).

[11]  Martin Glinz,et al.  On Non-Functional Requirements , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[12]  Rick Kazman,et al.  An approach to software architecture analysis for evolution and reusability , 1997, CASCON.

[13]  Barry Boehm,et al.  4.5.3 A Comparison Study in Software Requirements Negotiation , 1998 .

[14]  Barry Boehm,et al.  Aids for Identifying Conflicts Among Quality Requirements , 1996 .

[15]  Jan Bosch,et al.  Scenario-based software architecture reengineering , 1998, Proceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203).

[16]  William N. Robinson,et al.  Requirements interaction management , 2003, CSUR.

[17]  Rick Kazman,et al.  The architecture tradeoff analysis method , 1998, Proceedings. Fourth IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.98EX193).

[18]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[19]  Julio Cesar Sampaio do Prado Leite,et al.  The world?s a stage: a survey on requirements engineering using a real-life case study , 1999, J. Braz. Comput. Soc..

[20]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[21]  Sooyong Park,et al.  Managing requirements conflicts in software product lines: A goal and scenario based approach , 2007, Data Knowl. Eng..

[22]  John Mylopoulos,et al.  An actor dependency model of organizational work: with application to business process reengineering , 1993, COCS '93.

[23]  Barry W. Boehm,et al.  Applying WinWin to quality requirements: a case study , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[24]  Alexander Egyed,et al.  A Comparison Study in Software Requirements Negotiation , 1998 .

[25]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[26]  Eric S. K. Yu,et al.  Using non-functional requirements to systematically support change , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[27]  Ian Sommerville,et al.  Integrated requirements engineering: a tutorial , 2005, IEEE Software.

[28]  Chris Ford,et al.  Non-Functional Requirements , 2007 .

[29]  Donald Firesmith,et al.  Using Quality Models to Engineer Quality Requirements , 2003, J. Object Technol..

[30]  Eric S. K. Yu,et al.  Dealing with change: An approach using non-functional requirements , 2005, Requirements Engineering.

[31]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[32]  Martin Glinz,et al.  Rethinking the Notion of Non-Functional Requirements , 2005 .

[33]  João Araújo,et al.  Multi-dimensional separation of concerns in requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[34]  Xiaoqing Frank Liu,et al.  Analysis of Conflicts among Non-Functional Requirements Using Integrated Analysis of Functional and Non-Functional Requirements , 2007, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007).

[35]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[36]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[37]  Steve M. Easterbrook,et al.  Using ViewPoints for inconsistency management , 1996, Softw. Eng. J..

[38]  Norazlin Yusop,et al.  The impacts of non-functional requirements in web system projects , 2008 .

[39]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[40]  Barry Boehm,et al.  WinWin Requirements Negotiation Processes: A Multi-Project Analysis , 1999 .

[41]  Peter H. N. de With,et al.  Resolving requirement conflicts through non-functional decomposition , 2004, Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004).

[42]  Peter G. Neumann,et al.  Computer-related risks , 1994 .

[43]  G. V. Uma,et al.  Elicitation of Non-functional Requirement Preference for Actors of Usecase from Domain Model , 2006, PKAW.

[44]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[45]  Ying Guan,et al.  Use Constraint Hierarchy for Non-functional Requirements Analysis , 2005, ICWE.

[46]  Alexander Egyed,et al.  Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help , 2004, IEEE Software.

[47]  Steve Easterbrook,et al.  Handling conflict between domain descriptions with computer-supported negotiation , 1991 .

[48]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.