Conference Paper

UML collaboration diagram syntax: an empirical study of comprehension

Dept. of Comput. Sci., Glasgow Univ.;
DOI: 10.1109/VISSOF.2002.1019790 Conference: Visualizing Software for Understanding and Analysis, 2002. Proceedings. First International Workshop on
Source: IEEE Xplore

ABSTRACT The UML syntactic notation used in texts, papers, documentation and CASE tools is often different, despite UML being considered a software engineering standard. Our initial empirical study considered variations in the notation used for UML class diagrams; the experiment reported concentrates on UML collaboration diagrams. The decision as to which of the semantically equivalent notational variations within the UML standard to use appears to be according to the personal preference of the author or publisher, rather than based on any consideration of the ease with which the notation can be understood by human readers. This paper reports on an experiment that takes a human comprehension perspective on UML collaboration diagrams. Five notations were considered: for each, two semantically equivalent (yet syntactically or stylistically different), variations were chosen from published texts. Our experiment required subjects to indicate whether a supplied pseudo-code specification matched each of a set of experimental UML collaboration diagrams. The results reveal that our informal, personal intuitions (which were based on our view of the complexity of the notation) are validated with respect to confirming that a specification matches a diagram, but not when errors in a diagram are to be identified. The subjects' preferences are in favour of the more concise notational variants.

  • [Show abstract] [Hide abstract]
    ABSTRACT: In this paper, we attempt to address the relative absence of empirical studies of model driven engineering through describing the practices of three commercial organizations as they adopted a model driven engineering approach to their software development. Using in-depth semi-structured interviewing we invited practitioners to reflect on their experiences and selected three to use as exemplars or case studies. In documenting some details of attempts to deploy model driven practices, we identify some ‘lessons learned’, in particular the importance of complex organizational, managerial and social factors – as opposed to simple technical factors – in the relative success, or failure, of the endeavour. As an example of organizational change management the successful deployment of model driven engineering appears to require: a progressive and iterative approach; transparent organizational commitment and motivation; integration with existing organizational processes and a clear business focus.
    Proceedings of the 33rd International Conference on Software Engineering, ICSE 2011, Waikiki, Honolulu , HI, USA, May 21-28, 2011; 01/2011
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: So far, research on model merging has mostly focused on algorithmic problems. But, there are various situations when software engineers have to compare and merge different models manually or at least make important decisions. In this paper, we provide insights into the process of how users compare and merge visual models. To this end, we observed people's activities when manually merging UML class diagrams and analyzed the recorded data following the Grounded Theory approach. To illustrate the usefulness of our results we derived some guidelines for tool design.
    Proceedings of the 5th International Symposium on Empirical Software Engineering and Measurement, ESEM 2011, Banff, AB, Canada, September 22-23, 2011; 01/2011
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Practical experience suggests that use and understanding of UML diagrams is greatly affected by the quality of their layout. However, existing experimental evidence for this effect is been weak and inconclusive. In this paper, we explore two explanations. Firstly, we observe that the visual qualities of diagrams are more prominent in earlier life cycle phases so that the impact of layout quality should be more apparent in models and diagram types used there, an aspect not studied in previous research. Secondly, in practice, good layouts use many different heuristics simultaneously whereas previous research considered them in isolation only. In this paper, we report the results of a series of controlled experiments using compound layouts on requirements analysis models. With very high significance, we find a notable impact of the layout quality measured by different aspects of cognitive load.
    Visual Languages and Human-Centric Computing (VL/HCC), 2011 IEEE Symposium on; 01/2011

Full-text (2 Sources)

Available from
Aug 11, 2014