Investigating Conflicts in Cots Decision-Making

The development of COTS-based systems largely depends on the success of the selection process. This activity encompasses the evaluation of COTS packages against customer requirements, so that it is necessary to perform a complex decision-making process to select the most suitable package. We argue that analysing the matching between features and requirements is a core task of COTS decision-making. In particular, it is very likely that mismatches occur, as COTS are designed to meet very general requirements rather than specific needs. In this paper, we investigate the different types of conflicts that can arise from these mismatches. We propose a goal driven framework to deal with such conflicts. We demonstrate the approach with the mail server case study.

[1]  T. Saaty,et al.  The Analytic Hierarchy Process , 1985 .

[2]  Barry Boehm,et al.  Comparing software system requirements negotiation patterns , 1999 .

[3]  Carina Frota Alves,et al.  Challenges in COTS decision-making: a goal-driven requirements engineering perspective , 2002, SEKE '02.

[4]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[5]  Evangelos Triantaphyllou,et al.  Multi-criteria Decision Making Methods: A Comparative Study , 2000 .

[6]  Dov M. Gabbay,et al.  Inconsistency Handling in Multi-Perspective Specifications , 1993, ESEC.

[7]  D. Gabbay,et al.  Inconsistency Handling in Multiperspective Specifications , 1994 .

[8]  S.A. Hissam,et al.  Building systems from commercial components , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[9]  Lawrence Chung,et al.  A knowledge-based COTS-aware requirements engineering approach , 2002, SEKE '02.

[10]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[11]  William N. Robinson,et al.  Negotiation behavior during requirement specification , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[12]  Jyrki Kontio,et al.  A COTS Selection Method and Experiences of Its Use , 1995 .

[13]  B. Nuseibeh,et al.  Linking the Selection of Requirements to Market Value : A Portfolio-Based Approach Siv , 2001 .

[14]  S. Easterbrook,et al.  A Survey of Empirical Studies of Conflict , 1993 .

[15]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[16]  Pamela Zave.  Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[17]  Joachim Karlsson,et al.  Prioritizing Software Requirements In An Industrial Setting , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[18]  John Mylopoulos,et al.  From Organization Models to System Requirements: A 'Cooperating Agents' Approach , 1995, CoopIS.

[19]  Carme Quer,et al.  Defining a Quality Model for Mail Servers , 2003, ICCBSS.

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

[21]  Cornelius Ncube,et al.  PORE : Procurement Oriented Requirements Engineering Method for the Component-Based Systems Engineering Development Paradigm , 1999 .

[22]  A. Finkelstein,et al.  Software package requirements and procurement , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[23]  Björn Regnell,et al.  Challenges in Market-Driven Requirements Engineering - an Industrial Interview Study , 2002 .