Nothing Special   »   [go: up one dir, main page]
Skip to main content
Springer Nature Link
Log in

COTS tenders and integration requirements

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

When buying COTS-based software, the customer has to choose between what is available. The supplier may add some minor parts, but rarely everything the customer wants. This means that the customer cannot write down his requirements and expect that they can all be met. A scoring system is necessary rather than traditional mandatory requirements. Requirements for integrating the new COTS system with other systems are particularly hard because suppliers may integrate in different ways and with different other systems. A related problem is that once the new COTS system is purchased, the COTS supplier may have a de facto monopoly. Only he can expand the system or integrate it with other systems. The traditional way to purchase COTS is to iteratively find the right product. However, in a tender process this is not possible, and another solution is necessary. Experience shows that customers fail to deal with these issues adequately. As an example they may believe that asking for open interfaces is sufficient to guard them against monopoly. In this paper we analyze the problems and show ways to deal with them. We illustrate the problems and solutions with real-life examples from electronic patient recording systems.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6

Similar content being viewed by others

References

  1. Albert C, Brownsword L (2002) Meeting the challenges of commercial-off-the-shelf (COTS) products. In: Dean J, Gravel A (eds) International conference on COTS-based software systems, ICCBSS 2002, LNCS 2255, pp 10–20

  2. Balk LD, Kedia A (2000) PPT: a COTS integration case study. In: International conference on software engineering, ICSE 2000, pp 42–49

  3. Bansler JP, Havn EC (1994) Information systems development with generic systems. In: Walter RJ Baets (ed) Second European conference on information systems, Nijenrode University Press, pp 707–715

  4. Bao Y, Horowitz E (1996) Integrating through user interface: a flexible integration framework for third-party software. In: Proceedings of COMPSAC ‘96. IEEE Comput, pp 336–342

  5. Boehm B, Abts C (1999) COTS integration: plug and pray? IEEE Comput, January 1999, pp 135–38

  6. Brownsword L, Oberndorf T, Sledge CA (2000) Developing new processes for COTS-based systems. IEEE Software, July/August 2000, pp 48–55

  7. Davis L, Flagg D, Gamble R, Karatas C (2003) Classifying interoperability conflicts. In: International conference on COTS-based software systems, ICCBSS 2003, LNCS 2580, pp 62–71

  8. Gorton I, Liu A (2002) Streamlining the acquisition process for large-scale COTS middleware components. In: Dean J, Gravel A (eds) International conference on COTS-based software systems, ICCBSS 2002, LNCS 2255, pp 122–131

  9. Guo J (2000) Interoperability technology assessment. Electronic notes. vol 65, No. 4. Elsevier, Amsterdam

  10. Helokunnas T, Nyby M (2002) Collaboration between a COTS integrator and a vendor. In: Kontio J, Conradi R (eds) European conference on software quality, ECSQ 2002, LNCS 2349, pp 267–273

  11. Hornstein RS, Willoughby JK (2002) Realizing the potential for COTS utilization: a work in progress. In: Dean J, Gravel A (eds) International conference on COTS-based software systems, ICCBSS 2002, LNCS 2255, pp 142–150

  12. Lauesen S (2002) Software requirements—styles and techniques. Addison-Wesley, Reading

    Google Scholar 

  13. Lauesen S (2003) Task descriptions as functional requirements. IEEE Software 2003, March/April, pp 58–65

  14. Lauesen S, Vium JP (2004) Experiences from a tender process. In: International workshop on requirements engineering, REFSQ’04

  15. Lauesen S, Vium JP (2005) Communication gaps in a tender process. Requirements Eng J 10(Sept):247–261

    Article  Google Scholar 

  16. Lewis GA, Wrage L (2004) A case study in COTS product integration using XML. In: International conference on COTS-based software systems, ICCBSS 2004, LNCS 2959, pp 41–52

  17. Liu A, Gorton I (2003) Accelerating COTS middleware acquisition: The i-Mate process. IEEE Software, March/April 2003, pp 72–79

  18. Maiden NA, Ncube C (1998) Acquiring COTS software selection requirements. IEEE Software, March/April 1998, pp 46–56

  19. Morisio M, Torchiano M (2002) Definition and classification of COTS: a proposal. In: Dean J, Gravel A (eds) International conference on COTS-based software systems, ICCBSS 2002, LNCS 2255, pp 165–175

  20. Perrone V (2004) A wish list for requirements engineering for COTS-based information systems. In: International conference on COTS-based software systems, ICCBSS 2004, LNCS 2959, pp 146–158

  21. Sai V (2003) COTS acquisition evaluation process: the preacher’s practice. In: International conference on COTS-based software systems, ICCBSS 2003, LNCS 2580, pp 196–206

  22. Saur LD, Clay RL, Armstrong R (2000) Meta-component architecture for software interoperability. IEEE Comput, November 2000, pp 75–84

  23. Semancik SK, Conger AM (2002) The standard autonomous file server, a customized, off-the-shelf success story. In: Dean J, Gravel A (eds) International conference on COTS-based software systems, ICCBSS 2002, LNCS 2255, pp 234–244

  24. Wileden JC, Kaplan A (1999) Software interoperability: principles and practice. In: Proceedings of software engineering 1999, ACM, pp 675–676

  25. Yakimovich D, Bieman JM, Basili VR (1999) Software architecture classification for estimating the cost of COTS integration. In: International conference on software engineering, ICSE ‘99, ACM, pp 296–302

Download references

Acknowledgements

I want to thank Jens-Peder Vium, Henrik Willumsen, David Simonsen, Niels R. Larsen and Henrik Lindholm for some of the ideas behind this paper, Andrew Gabb for assuring me that I was dealing with important problems, and Torben Elin for comparing the approach with what he, as a customer, had been trying to do.

Author information

Authors and Affiliations

  1. IT University of Copenhagen, Rued Langgaardsvej 7, 2300, Copenhagen S, Denmark

    Søren Lauesen

Authors
  1. Søren Lauesen
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Søren Lauesen.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Lauesen, S. COTS tenders and integration requirements. Requirements Eng 11, 111–122 (2006). https://doi.org/10.1007/s00766-005-0022-5

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-005-0022-5

Keywords

Search

Navigation