Empirical study on the difficulties of software modeling through class diagrams

UML Class Diagrams: An Empirical Study of Comprehension

Software Visualization ◽

10.1007/978-1-4615-0457-3_6 ◽

2003 ◽

pp. 149-178 ◽

Cited By ~ 3

Author(s):

Helen C. Purchase ◽

Linda Colpoys ◽

David Carrington ◽

Matthew McGill

Keyword(s):

Empirical Study ◽

Class Diagrams

Download Full-text

An empirical study on the efficiency of different design pattern representations in UML class diagrams

Empirical Software Engineering ◽

10.1007/s10664-009-9125-9 ◽

2010 ◽

Vol 15 (5) ◽

pp. 493-522 ◽

Cited By ~ 30

Author(s):

Gerardo Cepeda Porras ◽

Yann-Gaël Guéhéneuc

Keyword(s):

Empirical Study ◽

Design Pattern ◽

Class Diagrams

Download Full-text

Supporting collaborative modelling in UML class diagrams

Revista Brasileira de Computação Aplicada ◽

10.5335/rbca.v11i3.8469 ◽

2019 ◽

Vol 11 (3) ◽

pp. 39-46

Author(s):

Raul Antonio Cortiana Neto ◽

Kleinner Farias ◽

Vinicius Bischoff ◽

Lucian José Gonçales

Keyword(s):

Communication Channel ◽

Qualitative Evaluation ◽

Software Modeling ◽

Modeling Tools ◽

Team Members ◽

Good Communication ◽

Collaborative Modeling ◽

Software Models ◽

Class Diagrams ◽

Industry Professionals

Background. Modeling architectural aspects of the system is an essential activity in software development. Inthis context, developers work in parallel, and collaborate to define application software models, such as classdiagrams. Problem. Although many software modeling tools have been proposed, there is a lack of distributed collaboration features. Solution. This study proposes C-SAMT, a web tool for collaborative modeling of UML class diagrams. Developers can benefit from using C-SAMT when performing modeling tasks, such as creating domain models in parallel, and collaboratively. Evaluation. We recruited 20 industry professionals to perform a qualitative evaluation of the tool through a questionnaire. Results. Majority of Industry professionals (85%, 17/20) reported that totally agree that the communication channel of the tool worked properly, they also (80%, 16/20) totally agreed the models generated collaboratively with C-SAMT had small numbers of conflicts, and they also (90%, 18/20) perceived improved productivity gains using the proposed tool. Conclusion. C-SAMT provided a collaborative environment, which were positively evaluated by developers, who reported that C-SAMT had a good communication channel between team members.

Download Full-text

OCL FORMAL SPECIFICATION BASED METRICS AS A MEASURE OF COMPLEXITY AND FAULT-PRONENESS

International Journal of Computer Science and Informatics ◽

10.47893/ijcsi.2014.1182 ◽

2014 ◽

pp. 103-113

Author(s):

A. JALILA ◽

D. JEYA MALA ◽

S. BALAMURUGAN ◽

K. SABARI NATHAN

Keyword(s):

Empirical Study ◽

Software Quality ◽

Formal Specification ◽

Relative Weight ◽

Model Specification ◽

Early Measurement ◽

Class Diagrams ◽

Fault Proneness ◽

Uml Models

Formal specification of UML models in OCL is essential to improve software quality. Owing to the use of OCL in precise model specification, its application has been looked in different perspectives such as early measurement of module complexity. Moreover, when UML class diagrams are complemented with OCL, the metrics collected from OCL specification can serve as an indicator of fault-prone components. In the proposed approach an empirical study has been conducted on five soft real time case study applications. In this paper, existing metrics which are applicable to OCL expression are validated using module complexity. Moreover, a new metrics suite, which can be extracted from OCL expressions, has been devoted to quantify module complexity. The proposed metrics suite can be directly extracted from OCL expressions. Relative weight has been assigned to each metric which is selected for the proposed study, based on its importance in fault-prone components identification. The study shows that an analysis on OCL formal specification based metrics is effective in identifying fault-prone components of the system. Furthermore, it helps to distribute efforts required for software development and testing activities.

Download Full-text