Proceedings ArticleDOI
An empirical assessment of completeness in UML designs
Christian F. J. Lange,Michel R. V. Chaudron +1 more
- pp 111-119
Reads0
Chats0
TLDR
A definition of completeness of a UML model is proposed and a set of rules to assess model completeness are presented to assess the level of comple completeness in practice.Abstract:
Delivering high quality software in an economic way requires advanced control over the software development process and the product in all stages of its life-cycle. The use of metrics as means of control and improvement plays an important role in software engineering. Interviews with industrial software engineers identified incompleteness of UML designs as a potential problem for subsequent stages of development. In this paper we propose a definition of completeness of a UML model and present a set of rules to assess model completeness. We report results from industrial case studies to assess the level of completeness in practice. The amount of completeness and consistency rule violations was very high. Different case studies showed large variations in conformance to and violations of rules.read more
Citations
More filters
Software engineering economics
TL;DR: In this article, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
Journal ArticleDOI
Empirical evidence about the UML: a systematic literature review
TL;DR: To determine how widely the notations of the UML, and their usefulness, have been studied empirically, and to identify which aspects of it have been study in most detail, a mapping study of the literature was undertaken.
Assessing and improving the quality of modeling : a series of empirical studies about the UML
TL;DR: This thesis addresses the assessment and improvement of the quality of modeling in software engineering with a focus on the Unified Modeling Language (UML), which is the de facto standard in industrial practice and proposes task-oriented views for UML.
Proceedings ArticleDOI
Effects of defects in UML models: an experimental investigation
TL;DR: A classification of defect types based on a ranking of detection rate and risk for misinterpretation is presented and can be used for improving quality assurance techniques for UML-based development.
Proceedings ArticleDOI
Managing Model Quality in UML-Based Software Development
TL;DR: A quality model for managing UML-based software development is presented that enables identifying the need for actions for quality improvement already in early stages of the life-cycle.
References
More filters
Software engineering economics
TL;DR: In this paper, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
Book
A metrics suite for object oriented design
TL;DR: This research addresses the needs for software measures in object-orientation design through the development and implementation of a new suite of metrics for OO design, and suggests ways in which managers may use these metrics for process improvement.
Book
Software Engineering Economics
TL;DR: In this article, the authors provide an overview of economic analysis techniques and their applicability to software engineering and management, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.
Book
Software Metrics: A Rigorous and Practical Approach
TL;DR: The Second Edition of Software Metrics provides an up-to-date, coherent, and rigorous framework for controlling, managing, and predicting software development processes.
Journal ArticleDOI
A validation of object-oriented design metrics as quality indicators
TL;DR: Several of Chidamber and Kemerer's OO metrics appear to be useful to predict class fault-proneness during the early phases of the life-cycle and are better predictors than "traditional" code metrics, which can only be collected at a later phase of the software development processes.