COTS Product Selection for Safety-Critical Systems

There is an increasing interest in acquiring commercial-off-the-shelf (COTS) functionality for safety-critical applications. However, the selection of COTS products for such applications is still carried out in an ad hoc manner. This creates great difficulties for realistic cost and effort estimation, integration of the selected COTS product, and the certification of final COTS-based safety-critical systems. We believe that selection of an appropriate COTS product is the vital first step towards a successful COTS-based solution, especially for safety-critical applications. In this paper, we propose a pragmatic COTS selection approach in order to alleviate the perceived difficulties by providing a safety-informed decision on COTS selection. Reasoning from the perspective of the application context and application-specific hazards, the proposed approach defines a COTS acquisition contract from the safety requirements derived for the required COTS functionality. The terms of the COTS acquisition contract act as the evaluation and selection criteria against which any COTS candidates must be evaluated thus providing informed decisions on COTS selection for safety-critical applications.

[1]  B. Craig Meyers,et al.  Managing Software Acquisition: Open Systems and COTS Products , 2001 .

[2]  Peter Neumann,et al.  Safeware: System Safety and Computers , 1995, SOEN.

[3]  Lisa Brownsword,et al.  The Opportunities and Complexities of Applying Commercial-Off-the-Shelf Components , 1998 .

[4]  John L. Goodman,et al.  The Space Shuttle and GPS: A Safety-Critical Navigation Upgrade , 2003, ICCBSS.

[5]  John Dean,et al.  COTS-Based Software Systems , 2001, Lecture Notes in Computer Science.

[6]  Neil R. Storey,et al.  Safety-critical computer systems , 1996 .

[7]  Barry W. Boehm,et al.  COTS Integration: Plug and Pray? , 1999, Computer.

[8]  George T. Heineman,et al.  Component-Based Software Engineering: Putting the Pieces Together , 2001 .

[9]  David Garlan,et al.  Architectural Mismatch or Why it's hard to build systems out of existing parts , 1995, 1995 17th International Conference on Software Engineering.

[10]  Cornelius Ncube,et al.  Selecting the right COTS software: why requirements are important , 2001 .

[11]  Ljerka Beus-Dukic,et al.  Non-functional requirements for COTS software components , 2000 .

[12]  Jeffrey M. Voas,et al.  COTS Software: The Economical Choice? , 1998, IEEE Softw..

[13]  Nancy G. Leveson,et al.  An experimental evaluation of the assumption of independence in multiversion programming , 1986, IEEE Transactions on Software Engineering.

[14]  Bruce P. Douglass,et al.  Doing hard time: developing real-time systems with uml , 1999 .

[15]  Dietmar Pfahl,et al.  A COTS Acquisition Process: Definition and Application Experience , 2000 .

[16]  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.

[17]  Laurence Brooks,et al.  CHAPTER 53 APPLYING SOCIAL-TECHNICAL APPROACH FOR COTS SELECTION * , 1999 .