A field study in static extraction of runtime architectures
Proceedings of the 8th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Applying empirical software engineering to software architecture: challenges and lessons learned
Empirical Software Engineering
Developers ask reachability questions
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Questions about object structure during coding activities
Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering
Journal of Systems and Software
A case study in evaluating the usefulness of the run-time structure during coding tasks
Human Aspects of Software Engineering
Verification and validation in the context of domain-specific modelling
Proceedings of the 10th Workshop on Domain-Specific Modeling
Empirical investigation on the benefits of using UML in software maintenance
Proceedings of the 12th International Conference on Product Focused Software Development and Process Improvement
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Does the level of detail of UML models affect the maintainability of source code?
MODELS'11 Proceedings of the 2011th international conference on Models in Software Engineering
Empirical validation of a usability inspection method for model-driven Web development
Journal of Systems and Software
An approach for synchronizing UML models and narrative text in literate modeling
MODELS'12 Proceedings of the 15th international conference on Model Driven Engineering Languages and Systems
Proceedings of the Second Edition of the International Workshop on Experiences and Empirical Studies in Software Modelling
Research Review: A Systematic Literature Review on the Quality of UML Models
Journal of Database Management
Enhancing design models with composition properties: a software maintenance study
Proceedings of the 12th annual international conference on Aspect-oriented software development
Evaluating usage and quality of technical software documentation: an empirical study
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
The value of design rationale information
ACM Transactions on Software Engineering and Methodology (TOSEM) - In memoriam, fault detection and localization, formal methods, modeling and design
On the impact of UML analysis models on source-code comprehensibility and modifiability
ACM Transactions on Software Engineering and Methodology (TOSEM)
Evaluating the benefits of using domain-specific modeling languages: an experience report
Proceedings of the 2013 ACM workshop on Domain-specific modeling
Knowledge-based approaches in software documentation: A systematic literature review
Information and Software Technology
Hi-index | 0.01 |
The Unified Modeling Language (UML) is the de facto standard for object-oriented software analysis and design modeling. However, few empirical studies exist that investigate the costs and evaluate the benefits of using UML in realistic contexts. Such studies are needed so that the software industry can make informed decisions regarding the extent to which they should adopt UML in their development practices. This is the first controlled experiment that investigates the costs of maintaining and the benefits of using UML documentation during the maintenance and evolution of a real, non-trivial system, using professional developers as subjects, working with a state-of-the-art UML tool during an extended period of time. The subjects in the control group had no UML documentation. In this experiment, the subjects in the UML group had on average a practically and statistically significant 54% increase in the functional correctness of changes (p=0.03), and an insignificant 7% overall improvement in design quality (p=0.22) - though a much larger improvement was observed on the first change task (56%) - at the expense of an insignificant 14% increase in development time caused by the overhead of updating the UML documentation (p=0.35).