Authors:
Hafeez Osman
1
;
Arjan van Zadelhoff
1
and
Michel R. V. Chaudron
2
Affiliations:
1
Leiden University, Netherlands
;
2
Leiden University and Chalmers University of Technology, Netherlands
Keyword(s):
Software Engineering, Reverse Engineering, UML, Class Diagram, Simplification.
Related
Ontology
Subjects/Areas/Topics:
Applications and Software Development
;
Languages, Tools and Architectures
;
MetaModeling
;
Methodologies, Processes and Platforms
;
Model Quality Assurance Techniques
;
Model-Driven Software Development
;
Models
;
Paradigm Trends
;
Reasoning about Models
;
Software Engineering
;
Software Process Modeling, Enactment and Execution
;
Syntax and Semantics of Modeling Languages
Abstract:
Class diagrams may include an overwhelming amount of information. For a large and complex class diagrams there is a possibility that not all information in the class diagram is important for understanding the system. In this paper, we study how to identify essential and secondary information in class diagrams. To this end, we performed a survey with professionals, academics and students to enquire information in class diagrams that is considered important. In total, 25 complete responses were received with 76% of the respondents having average or above skills with class diagrams. As the results, we discovered that the metric that counts the number of public operations is the most important metric for indicating importance of a class in a diagram. Also, we discovered that class names and coupling were influencing factors when it comes to excluding classes from a class diagram.