Software metrics: an overview of recent results
Journal of Systems and Software
Evaluating Software Complexity Measures
IEEE Transactions on Software Engineering
A Study of the Applicability of Complexity Measures
IEEE Transactions on Software Engineering
Software Complexity and its Impact on Software Reliability
IEEE Transactions on Software Engineering
An experiment in software sizing with structured analysis metrics
Journal of Systems and Software
Comments on 'A Metrics Suite for Object Oriented Design'
IEEE Transactions on Software Engineering
Property-Based Software Engineering Measurement
IEEE Transactions on Software Engineering
Object-oriented metrics: measures of complexity
Object-oriented metrics: measures of complexity
Estimation of effort and complexity: an object-oriented case study
Journal of Systems and Software
Deriving complexity information from a formal communication protocol specification
Software—Practice & Experience
UML components: a simple process for specifying component-based software
UML components: a simple process for specifying component-based software
Function-point analysis using design specifications based on the unified modelling language
Journal of Software Maintenance: Research and Practice
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
Elements of Software Science (Operating and programming systems series)
Elements of Software Science (Operating and programming systems series)
Building Reliable Component-Based Software Systems
Building Reliable Component-Based Software Systems
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
Complexity Measure Evaluation and Selection
IEEE Transactions on Software Engineering
Quantitative Analysis of Faults and Failures in a Complex Software System
IEEE Transactions on Software Engineering
Measuring the Maintainability of a Communication Protocol Based on Its Formal Specification
IEEE Transactions on Software Engineering
A Comprehensive Interface Definition Framework for Software Components
APSEC '98 Proceedings of the Fifth Asia Pacific Software Engineering Conference
Component Metrics to Measure Component Quality
APSEC '01 Proceedings of the Eighth Asia-Pacific on Software Engineering Conference
Few important considerations for deriving interface complexity metric for component-based systems
ACM SIGSOFT Software Engineering Notes
Mapping component specifications to Enterprise JavaBeans implementations
ACM-SE 42 Proceedings of the 42nd annual Southeast regional conference
Architectural-Level Risk Analysis Using UML
IEEE Transactions on Software Engineering
Architecting in software ecosystems: interface translucence as an enabler for scalable collaboration
Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Component Point: A system-level size measure for Component-Based Software Systems
Journal of Systems and Software
A mapping study to investigate component-based software system metrics
Journal of Systems and Software
CAME: component assembly metrics extraction using UML
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
A component-based system (CBS) is integration centric with a focus on assembling individual components to build a software system. In CBS, component source code information is usually unavailable. Each component also introduces added properties such as constraints associated with its use, interactions with other components and customizability properties. Recent research suggests that most faults are found in only a few system components. A complexity measure at a specification phase can identify these components. However, traditional complexity metrics are not adequate for a CBS as they focus mainly on either lines of code (LOC) or information based on object and class properties. There is therefore a need to develop a new technique for measuring the complexity of a CBS specification (CBSS). This paper describes a structural complexity measure for a CBSS written in Unified Modelling Language (UML) from a system analyst's point of view. A CBSS consists of individual component descriptions characterized by its syntactic, semantic and interaction properties. We identify three factors, interface, constraints and interaction, as primary contributors to the complexity of a CBSS. We also present an application of our technique to a university course registration system. Copyright © 2006 John Wiley & Sons, Ltd.