Empirical assessment of UML class diagram layouts based on architectural importance

Sharif, Bonita

doi:10.1109/icsm.2011.6080828

Cited by 12 publications

(5 citation statements)

References 127 publications

(209 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, Sharif et al confirm that scan time and bug detection time are correlated [47]. Eyetracking has been used in studies of identifier style [49,8] and UML diagram layout [46,48], showing reduced comprehension when the code is not in an understandable format.…”

Section: Eye-tracking In Software Engineeringmentioning

confidence: 99%

Improving automated source code summarization via an eye-tracking study of programmers

Rodeghero

McMillan

McBurney

et al. 2014

Proceedings of the 36th International Conference on Software Engineering

169

106

View full text Add to dashboard Cite

Source Code Summarization is an emerging technology for automatically generating brief descriptions of code. Current summarization techniques work by selecting a subset of the statements and keywords from the code, and then including information from those statements and keywords in the summary. The quality of the summary depends heavily on the process of selecting the subset: a high-quality selection would contain the same statements and keywords that a programmer would choose. Unfortunately, little evidence exists about the statements and keywords that programmers view as important when they summarize source code. In this paper, we present an eye-tracking study of 10 professional Java programmers in which the programmers read Java methods and wrote English summaries of those methods. We apply the findings to build a novel summarization tool. Then, we evaluate this tool and provide evidence to support the development of source code summarization systems.

show abstract

Section: Eye-tracking In Software Engineeringmentioning

confidence: 99%

Improving automated source code summarization via an eye-tracking study of programmers

Rodeghero

McMillan

McBurney

et al. 2014

Proceedings of the 36th International Conference on Software Engineering

169

106

View full text Add to dashboard Cite

show abstract

“…(ii) improving the understanding of UML diagrams to facilitate its comprehension during software maintenance [74];…”

Section: ) About Design Documentsmentioning

confidence: 99%

Programmer eXperience: A Systematic Literature Review

et al. 2019

View full text Add to dashboard Cite

Programmers use various software development artifacts in their work, such as programming environments, design documents, and programming codes. These software artifacts can be studied and improved based on usability and User eXperience (UX) factors. In this paper, we consider programmers to be a specific case of users and analyze different elements that influence their experience in this specific context. We conducted a systematic literature review of papers published over the last ten years related to 1) the definition of the Programmer eXperience (PX); 2) the PX, UX, and usability factors regarding the programming environments, design documents, and programming codes; and 3) sets of heuristics to evaluate the software development artifacts mentioned before. We analyzed 73 articles, and the results obtained show that: 1) the important elements that influence the PX are the motivation of programmers and the choice of tools they use in their work, such as programming environments; 2) most of the identified studies (59%) aimed to evaluate the influence of the PX, UX, and usability on programming environments; 3) the majority of the studies (70%) used methods such as usability tests and/or heuristic evaluation methods; and 4) four sets of heuristics are used to evaluate software development artifacts in relation to programming environments, programming languages, and application programming interfaces. The results suggest that further research in this area is necessary to better understand and evaluate the concept of the PX.

show abstract

“…Sharif et al [40] study 3 different layout schemes of UML class diagrams using both questionnaires and eye tracking on maintenance tasks.…”

Section: Related Workmentioning

confidence: 99%

On the impact of size to the understanding of UML diagrams

Störrle

2016

Softw Syst Model

View full text Add to dashboard Cite

Document VersionAbstract Background: Practical experience suggests that usage and understanding of UML diagrams is greatly affected by the quality of their layout. While existing research failed to provide conclusive and comprehensive evidence in support of this hypothesis, our own previous work provided substantial evidence to this effect, also suggesting diagram size as a relevant factor, for a range of diagram types and layouts. Aims: Since there is no generally accepted precise notion of "diagram size", we first need to operationalize this concept, analyze its impact on diagram understanding, and derive practical advice from our findings. Method: We define three alternative, plausible metrics. Since they are all highly correlated on a large sample of UML diagrams, we opt for the simplest one. We use it to re-analyze existing experimental data on diagram understanding. Results: We find a strong negative correlation between diagram size and modeler performance. Our results are statistically highly significant, and exhibit a very large degree of validity. We utilize these results to derive a recommendation on diagram sizes that are, on average, optimal for model understanding. These recommendations are implemented in a plug-in to a widely used modeling tool, providing continuous feedback about diagram size to modelers. Conclusions: The effect sizes are varying, but generally suggest that the impact of size matches or exceeds that of other factors in diagram understanding. With the guideline and tool, modelers are steered towards avoiding too large diagrams.

show abstract

Empirical assessment of UML class diagram layouts based on architectural importance

Abstract: whose names I did not mention, but who contributed in any form towards the completion of the dissertation.

Cited by 12 publications

References 127 publications

Improving automated source code summarization via an eye-tracking study of programmers

Improving automated source code summarization via an eye-tracking study of programmers

Programmer eXperience: A Systematic Literature Review

On the impact of size to the understanding of UML diagrams

Contact Info

Product

Resources

About