Software engineering metrics for COTS-based systems
ComputerPublished 1 January 2001
Sahra Sedigh, A. Ghafoor, Raymond A. Paul
Citations90
SJR quartileQ2
SJR score0.55
SNIP1.02
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
Abstract
The paradigm shift to commercial off-the-shelf components appears inevitable, necessitating drastic changes to current software development and business practices. Quality and risk concerns currently limit the application of COTS based system design to noncritical applications. New approaches to quality and risk management will be needed to handle the growth of CBSs. Our metrics based approach and software engineering metrics can aid developers and managers in analyzing the return on investment in quality improvement initiatives for CBSs. These metrics also facilitate the modeling of cost and quality, although we need more complex models to capture the intricate relationships between cost and quality metrics in a CBS.
Keywords
Computer Science
Communications of the ACMEvaluating the cost of software quality
236 Citations1998Sandra A. Slaughter, Donald E. Harter +1 more
The time has come to financially justify investments in software quality improvements, just like other software projects, and there is some confusion about the business value of quality even outside the software development context.
ComputerCOTS integration: plug and pray?
177 Citations1999Barry Boehm, Chris Abts
The paper summarizes experience on the relative advantages and disadvantages of COTS solutions.
Medical Entomology and ZoologyPrinciples of Quality Costs: Principles, Implementation, and Use
151 Citations1990Jack Campanella
ComputerComponent-based systems: a classification of issues
151 Citations2000Pearl Brereton, David Budgen
This work describes software components as units of independent production, acquisition, and deployment that interact to form a functional system that software developers must address for component-based systems (CBS) to achieve their full potential.
Software Acquisition Capability Maturity Model (SA-CMM) Version 1.02
63 Citations1999Jack Cooper, M. Fisher +1 more
This new version of the Software Acquisition Capability Maturity Model (SA-CMM) incorporates change requests that have been received, as well as the results of lessons learned from conducting appraisals and from the use of Version 1.01.
IEEE Transactions on Knowledge and Data EngineeringSoftware metrics knowledge and databases for project management
32 Citations1999Raymond A. Paul, Tosiyasu L. Kunii +2 more
A generic framework that incorporates database and knowledge-base tools, a formal set of software test and evaluation metrics, and a suite of advanced analytic techniques for extracting information and knowledge from available data can enable highly efficient and cost-effective management of large and complex software projects.
Software metrics model for quality control
28 Citations2002Norman F. Schneidewind
A model is developed for validating and applying metrics for quality control, using the Space Shuttle flight software as an example, and metrics with respect to a quality factor are validated in accordance with the metrics validation methodology previously developed.
Case Study: Evaluating COTS Products for DoD Information Systems
19 Citations1998Carol A. Sledge, David Carney
A DoD program that undertook a detailed evaluation effort that examined several commercial products as candidates for a large information system and the lessons that were learned were more in the sphere of management and programmatic issues.
Journal of Systems and SoftwareAn evaluation of the business object approach to software development
14 Citations2000Manolis Tsagias, Barbara Kitchenham
It was found that producing software from scratch using UML was less productive during the development lifecycle, but productivity improved when substantial reuse was achieved, and defect rates appeared substantially lower for the new technology irrespective of reuse levels.
Assurance-based Y2K testing
12 Citations2003Wei‐Tek Tsai, Robin Paul +3 more
Two processes are described that use the model for ensuring that the software is reasonably safe from Y2K faults after testing, and these processes can be easily embedded in an existing testing process with minimal changes and minimal extra effort.
International Journal of Artificial Intelligence ToolsMETRICS-GUIDED REUSE
4 Citations1996Raymond A. Paul