Managing Non-Technical Requirements in COTS Components Selection

The selection of COTS components is made not only by an analysis of their technical quality but also (and sometimes mostly) by considering how they fulfill the nontechnical requirements considered relevant, which refer to licensing, reputation, and similar issues. In this paper we present an approach for managing non-technical requirements during COTS selection. The proposal is based on extending the ISO/IEC 9126-1 catalogue of quality factors by adding factors related to non-technical issues, obtaining a cohesive and comprehensive framework for managing requirements during selection. We show how we can use this catalogue for eliciting non-technical requirements, and how the metrics included in the catalogue may be used to define fit criteria for requirements. We illustrate our approach with an industrial experience that took place in the telecommunications field.

[1]  Douglas Kunda,et al.  STACE: Social Technical Approach to COTS Software Evaluation , 2003, Component-Based Software Quality.

[2]  Marco Torchiano,et al.  COTS products characterization , 2002, SEKE '02.

[3]  M. Krystkowiak.  Efficient COTS selection with OPAL tool , 2004, ICSE 2004.

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

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

[6]  Laurence Brooks,et al.  Identifying and classifying processes (traditional and soft factors) that support COTS component selection: a case study , 2000, ECIS.

[7]  Carme Quer,et al.  COSTUME: a method for building quality models for composite COTS-based software systems , 2004, Fourth International Conference onQuality Software, 2004. QSIC 2004. Proceedings..

[8]  William W. Gregory,et al.  The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models , 1994 .

[9]  P. Botella.  ISO / IEC 9126 in practice : what do we need to know ? , 2004 .

[10]  Wing Lam,et al.  Evaluating tools to support component based software engineering , 1997, Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies.

[11]  Jyrki Kontio,et al.  A case study in applying a systematic method for COTS selection , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[12]  Xavier Franch,et al.  Using Quality Models in Software Package Selection , 2003, IEEE Softw..

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

[14]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[15]  Horst Zuse,et al.  A Framework of Software Measurement , 1998 .

[16]  Xavier Franch,et al.  A quality-model-based approach for describing and evaluating software packages , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[17]  Carme Quer,et al.  A Quality Model for Requirements Management Tools , 2005 .

[18]  Juan Pablo Carvallo,et al.  Supporting Organizational Induction and Goals Alignment for COTS Components Selection by Means of i* , 2006, ICCBSS.

[19]  Søren Lauesen.  COTS tenders and integration requirements , 2005, Requirements Engineering.

[20]  Carme Quer,et al.  A Framework for Selecting Workflow Tools in the Context of Composite Information Systems , 2004, DEXA.

[21]  D. Ross Jeffery,et al.  A Framework for Software Quality Evaluation , 2002, PROFES.