View in EDS PDF Full Text

COTS tenders and integration requirements.

Saved in:
Bibliographic Details
Title: COTS tenders and integration requirements.
Authors: Lauesen, Søren1 slauesen@itu.dk
Source: Requirements Engineering. May2006, Vol. 11 Issue 2, p111-122. 12p. 1 Diagram, 4 Charts, 1 Graph.
Subjects: Computer interfaces, CORBA (Computer architecture), Internetworking, Computer software, Information technology, Computer systems
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. [ABSTRACT FROM AUTHOR]
Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
FullText Links:
  – Type: pdflink
Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 19617675
AccessLevel: 6
PubType: Academic Journal
PubTypeId: academicJournal
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: COTS tenders and integration requirements.
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Lauesen%2C+Søren%22">Lauesen, Søren</searchLink><relatesTo>1</relatesTo><i> slauesen@itu.dk</i>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22Requirements+Engineering%22">Requirements Engineering</searchLink>. May2006, Vol. 11 Issue 2, p111-122. 12p. 1 Diagram, 4 Charts, 1 Graph.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22Computer+interfaces%22">Computer interfaces</searchLink><br /><searchLink fieldCode="DE" term="%22CORBA+%28Computer+architecture%29%22">CORBA (Computer architecture)</searchLink><br /><searchLink fieldCode="DE" term="%22Internetworking%22">Internetworking</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+software%22">Computer software</searchLink><br /><searchLink fieldCode="DE" term="%22Information+technology%22">Information technology</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+systems%22">Computer systems</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: 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. [ABSTRACT FROM AUTHOR]
– Name: AbstractSuppliedCopyright
  Label:
  Group: Ab
  Data: <i>Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.)
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=19617675
RecordInfo BibRecord:
  BibEntity:
    Identifiers:
      – Type: doi
        Value: 10.1007/s00766-005-0022-5
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 12
        StartPage: 111
    Subjects:
      – SubjectFull: Computer interfaces
        Type: general
      – SubjectFull: CORBA (Computer architecture)
        Type: general
      – SubjectFull: Internetworking
        Type: general
      – SubjectFull: Computer software
        Type: general
      – SubjectFull: Information technology
        Type: general
      – SubjectFull: Computer systems
        Type: general
    Titles:
      – TitleFull: COTS tenders and integration requirements.
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Lauesen, Søren
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 05
              Text: May2006
              Type: published
              Y: 2006
          Identifiers:
            – Type: issn-print
              Value: 09473602
          Numbering:
            – Type: volume
              Value: 11
            – Type: issue
              Value: 2
          Titles:
            – TitleFull: Requirements Engineering
              Type: main
ResultId 1