2001
DOI: 10.1007/3-540-45588-4_6
|View full text |Cite
|
Sign up to set email alerts
|

Combined Selection of COTS Components

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2003
2003
2009
2009

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 24 publications
(13 citation statements)
references
References 2 publications
0
13
0
Order By: Relevance
“…In other words, such bug scripts will provide empirical evidence for the server they were reported for but not for the other servers. We called these "dialect-specific" 12 We could have used the number of known bugs for each of the partition to construct a profile consistent with the observations. This is not acceptable for two reasons: i) it will favour poor bug reporting practices, and ii) we would have used the bugs twice -once in the inference procedure and another time for the profile, which is theoretically unsound.…”
Section: Observationsmentioning
confidence: 99%
See 1 more Smart Citation
“…In other words, such bug scripts will provide empirical evidence for the server they were reported for but not for the other servers. We called these "dialect-specific" 12 We could have used the number of known bugs for each of the partition to construct a profile consistent with the observations. This is not acceptable for two reasons: i) it will favour poor bug reporting practices, and ii) we would have used the bugs twice -once in the inference procedure and another time for the profile, which is theoretically unsound.…”
Section: Observationsmentioning
confidence: 99%
“…An essential part of component-based software development is the assessment of available COTS components. Various assessment methods have been proposed [1], [2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [13], [14]. The results of these assessment techniques crucially depend on assuming that the values of the assessed attributes will be known with certainty at the end of the assessment.…”
Section: Introductionmentioning
confidence: 99%
“…Other assessment methods include: CISD (COTS-based Integrated System Development) [4], STACE (Socio Technical Approach to COTS Evaluation) [10], CDSEM (Checklist Driven Software Evaluation Methodology) [3], CRE-COTS-Based Requirements Engineering Method [6], CEP (Comparative Evaluation Process Activities) [7], CBA Process Decision Framework [8], A Proactive Evaluation Technique [19], CAP-COTS Acquisition Process method [5], Storyboard Process [11], Combined Selection of COTS Components [12], PECA Process [13] or COTS-DSS [14].…”
Section: Related Workmentioning
confidence: 99%
“…An initial and essential part of component based software development is the assessment of available COTS components. There exist a plethora of available methods for COTS assessment [1], [2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [13], [14]. An often overlooked aspect in the existing assessment techniques is the inherent uncertainty in the values of the parameters being assessed.…”
Section: Introductionmentioning
confidence: 99%
“…To minimize this risk, several software engineering practices can be applied. In the last years, some methods have been proposed for dealing with COTS component selection [1,2,3,4]. In all of them, a key point is the comparison of the user requirements that drive the selection process with the capabilities of the evaluated COTS components.…”
Section: Introductionmentioning
confidence: 99%