K-BACEE: knowledge-based automated component ensemble evaluation

Seacord, Robert C.; Mundle, D.; Boonsiri, Somjai

doi:10.1109/eurmic.2001.952438

Cited by 14 publications

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As work has progressed in the area of COTS research, specific solutions have been proposed to address some of these issues. Recently, solutions to the problems of how to evaluate [Addy, 1998;Brenner and Derado, 2001;Briand, 1998;Korel, 1998;Morisio and Tsoukias, 1997;Morris, 2000], describe [Addy andSitaraman, 1998, 1999;Morisio et al, 2000;Yen et al, 2002Yen et al, , 2001, select [Briand, 1998;Hissam et al, 2002;Illa, Franch, and Pastor, 2000;Kunda and Brooks, 1999;Morisio et al, 2000;Morisio and Tsoukias, 1997;Seacord, Mundie, and Boonsiri, 2001], and integrate [Hissam et al, 2002;Seacord, Mundie, and Boonsiri, 2001;Yen et al, 2002Yen et al, , 2001 COTS components have been proposed in the literature. Issues related to testing [Hissam and Carney, 1999;Hissam, 1998], and maintaining [Carney, Hissam, and Plakosh, 2000;Hybertson, Ta, and Thomas, 1997;Vidger and Dean, 1998] COTS intensive systems have also been presented.…”

Section: Related Workmentioning

confidence: 99%

Defining goals in a COTS‐aware requirements engineering approach

Chung

Cooper

2003

Systems Engineering

View full text Add to dashboard Cite

The goals of developing systems better, faster, and cheaper continue to drive software engineering practitioners and researchers to investigate software engineering methodologies. In requirements engineering, the focus has traditionally been on modeling the software engineering process and products for systems that are being built from scratch. As the size and complexity of systems continues to grow the use of commercial off the shelf (COTS) components is being viewed as a solution. Effective use of COTS components, however, requires a systematic approach that provides both a set of concepts for modeling the subject matter and a set of guidelines for using such concepts. In particular, the process needs to recognize and address the people oriented problems including the identification and resolution of conflicting goals, bridging the gaps between stated requirements and "approximately fitting" components while still satisfying the customer. In this paper, we present a goal and agent oriented requirements engineering process model that explicitly addresses the use of COTS components. More specifically, we present (part of) our model for a COTS-Aware Requirements Engineering (CARE) process and illustrate it using a Digital Library System (DLS).

show abstract

Section: Related Workmentioning

confidence: 99%

Defining goals in a COTS‐aware requirements engineering approach

Chung

Cooper

2003

Systems Engineering

View full text Add to dashboard Cite

show abstract

“…However, this proposal deals only with components offering simple interfaces, and therefore the problems of service gaps and overlaps do not appear. Furthermore, we highlight an important work: Seacord et al [23] propose a process for identifying component ensembles that satisfy a system requirements specification based on a knowledge base of system integration rules.…”

Section: Related Workmentioning

confidence: 99%

Selecting software components with multiple interfaces

Iribarne

Troya

Vallecillo

Proceedings. 28th Euromicro Conference

View full text Add to dashboard Cite

show abstract

“…This process may be optimised to select components displaying particular properties, for example, performance, security or ease of integration. One approach to component selection is K-BACEE -a system for selecting the best ensemble of components based on a weighting of their performance against certain criteria [6]. Other work takes the context of the component into account when using an in-house repository [7].…”

Section: Component Selectionmentioning

confidence: 99%