• DocumentCode
    3453909
  • Title

    COTS tenders and integration requirements

  • Author

    Lauesen, Soren

  • Author_Institution
    IT Univ., Copenhagen, Denmark
  • fYear
    2004
  • fDate
    6-11 Sept. 2004
  • Firstpage
    166
  • Lastpage
    175
  • Abstract
    When buying COTS-based software, the customer has to choose between what is available. The supplier may add some minor parts, but not 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 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 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. 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. 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 (EPR).
  • Keywords
    formal specification; medical information systems; object-oriented programming; COTS system; COTS tenders; COTS-based software; EPR systems; electronic patient recording systems; integration requirements; Application software; Companies; Electronics packaging; Enterprise resource planning; Middleware; Monopoly; Operating systems; Paramagnetic resonance; Proposals; User interfaces;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International
  • ISSN
    1090-705X
  • Print_ISBN
    0-7695-2174-6
  • Type

    conf

  • DOI
    10.1109/ICRE.2004.1335674
  • Filename
    1335674