Proceedings. 12th IEEE International Requirements Engineering Conference, 2004.
DOI: 10.1109/icre.2004.1335674
|View full text |Cite
|
Sign up to set email alerts
|

COTS tenders and integration requirements

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 new COTS system with other systems are particularly hard because suppliers may integrate in different ways and with different other system… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
0

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 20 publications
(19 citation statements)
references
References 16 publications
0
19
0
Order By: Relevance
“…A requirementcomponent mismatch is a difference in functional feature or non-functional quality attributes from a given component and a desired requirement. On one hand, some studies see requirement negotiation as an approach to resolve the mismatches [2,8,8,9,14,15]. In these cases, the component is fixed beforehand and requirements are the target of changes [8].…”
Section: Requirements-components Mismatches Resolution Processmentioning
confidence: 99%
See 1 more Smart Citation
“…A requirementcomponent mismatch is a difference in functional feature or non-functional quality attributes from a given component and a desired requirement. On one hand, some studies see requirement negotiation as an approach to resolve the mismatches [2,8,8,9,14,15]. In these cases, the component is fixed beforehand and requirements are the target of changes [8].…”
Section: Requirements-components Mismatches Resolution Processmentioning
confidence: 99%
“…Rolland proposed a goal-oriented approach for considering mismatches at the business level and then defined goal matching as the conceptual framework for resolving them [8]. Other approaches focused on lower level but highly challenging requirement problems, with integration requirements in call-for-tender processes [15].…”
Section: Requirements-components Mismatches Resolution Processmentioning
confidence: 99%
“…An effective RE process must deal with situations where formalized description of both functional and nonfunctional requirements may not be available [27]. In software procurement and development projects "open-target requirements" are recommended since it is hard to specify requirements in detail upfront [28]. In such context the customers specify their demands and expectations and the vendor responds with how they can meet the demands.…”
Section: A Inevitability Of Infrcmentioning
confidence: 99%
“…Research in this area focuses on easing management tasks and improving analysis techniques. For example, researchers have proposed a number of prioritization [105], visualization [63,93], and analysis [122,139] techniques to help managers select an optimal combination of requirements to implement -or to help project managers identify acceptable off-the-shelf solutions [91,126]. Other researchers are investigating how to improve our ability to estimate the cost [33] of implementing the selected requirements, or the impact of new or modified requirements [88].…”
Section: State Of the Art Of Re Researchmentioning
confidence: 99%