Several Issues on the Layout of the UML Sequence and Class Diagram (original) (raw)

Analysis of Sequence Diagram Layout in Advanced UML Modelling Tools

Applied Computer Systems, 2016

System modelling using Unified Modelling Language (UML) is the task that should be solved for software development. The more complex software becomes the higher requirements are stated to demonstrate the system to be developed, especially in its dynamic aspect, which in UML is offered by a sequence diagram. To solve this task, the main attention is devoted to the graphical presentation of the system, where diagram layout plays the central role in information perception. The UML sequence diagram due to its specific structure is selected for a deeper analysis on the elements’ layout. The authors research represents the abilities of modern UML modelling tools to offer automatic layout of the UML sequence diagram and analyse them according to criteria required for the diagram perception.

Several Issues on the Definition of Algorithm for the Layout of the UML Class Diagrams

Proceedings of the 3rd International Workshop on Model-Driven Architecture and Modeling-Driven Software Development

System modeling is one of the important tasks to be solved during software development. As more complex software systems become as higher requirements are defined for demonstrative presentation of the system to be developed. To solve this task the main attention is devoted to the transparency of the model elements within the graphical presentation of the system. The paper defines the classification of different types of UML diagrams, which are created during development of the software system. This classification is based on the different combinations of nodes and arcs of the diagram graph. The UML class diagram is selected for deeper analysis to the elements' layout. Authors offer to use main principles of the genetic algorithm to automate the replacement of the diagram created in the manual way. Current results are quite theoretical yet and authors will continue the research based on the issues defined in this paper. Galapovs A. and Nikiforova O.. Several Issues on the Definition of Algorithm for the Layout of the UML Class Diagrams.

UML Diagram Layouting: the State of the Art

Scientific Journal of Riga Technical University. Computer Sciences, 2011

UML Diagram Layouting: the State of the ArtThe usual aim of the modern computer-aided system modelling is to improve a connection between software model and code components. Therefore, the task of a diagram import/export becomes very important during software development. Layouting of diagrams after importation from another tool and application plays the main role. Authors of this paper describe some concepts, which are currently being considered in the area of diagram layouting and indicate several problems and their potential solutions for use in the development of CASE tools.

Empirical assessment of UML class diagram layouts based on architectural importance

2011 27th IEEE International Conference on Software Maintenance (ICSM), 2011

The paper presents a family of experiments that investigate the effectiveness of different layout techniques for class diagrams in the Unified Modeling Language (UML). Three different layout schemes are examined based on architectural importance of class stereotypes. The premise is that layout techniques for UML class diagrams significantly impact comprehension. Both traditional questionnaire-based studies as well as eye-tracking studies are done to quantitatively measure the performance of subjects solving specific software maintenance tasks. The main contribution is the detailed empirical validation of a set of layout techniques with respect to a variety of software maintenance tasks. Results indicate that layout plays a significant role in the comprehension of UML class diagrams. In particular, there is a significant improvement in accuracy, time, and visual effort for one particular layout scheme, namely multi-cluster. The end goal is to determine effective ways to adjust the layout of existing UML class diagrams to support program comprehension during maintenance.

Layout of (Software) Engineering Diagrams

2007

The Unified modeling language (UML) is a family of largely visual notations which has become the "lingua franca" of software engineering. In industrial settings the UML is used mainly as a means for facilitating communication between humans and so its visual qualities are decisive for its usefulness and practical value. However, it is rare to see any sort of analysis of the visual qualities and their effectiveness. Also, since the UML is continually evolving, some guidelines and criteria to help analyse any changes or additional proposed notations would be beneficial. Building on some basic frameworks and design criteria, we develop some principles for effective design, especially when considering languages with vague semantics. We use this to identify a number of problems of the UML that show up in the diagrammatic representation of models and propose improvements which overcome these difficulties. The methodology is applicable for analysing other complex languages with vague semantics in order to try to reduce human errors.

Definition of the Criteria for Layout of the UML Use Case Diagrams

Applied Computer Systems, 2019

Nowadays, the topicality and applicability of model-driven development in the object-oriented development approach has increased, so it is important that created models and diagrams display not only the content, but also visually reflect information. Transparent diagram placement that influences work productivity is important for displaying information. Manual layout of diagrams is a time-consuming activity, which can also be ineffective, so in this paper the application of UML use case automatic layout is reviewed. The paper also examines the requirements of use case diagrams and placement criteria, which will serve as a basis for the creation of an automatic use case diagram layout algorithm.

Developing Sequence Diagrams in UML

Lecture Notes in Computer Science, 2001

The UML (Unified Modeling Language) has been widely accepted as a standard language for object-oriented analysis and design. Among the UML diagrams, one of the most difficult and time-consuming diagrams to develop is the object interaction diagram (OID), which is rendered as either a sequence diagram or a collaboration diagram. Our experience shows that developers have significant trouble in understanding and developing OIDs. In this paper, we present an effective ten-step heuristic for developing sequence diagrams and illustrate the technique with a case study. In this technique, we show a proper use of control objects and boundary objects when developing sequence diagrams. In our heuristic the relationships among multiple sequence diagrams in a single use case are elegantly represented using control objects. We found that developers effectively developed sequence diagrams using this heuristic method.

Evaluating UML class diagram layout based on architectural importance

2005

The paper presents and assesses a layout scheme for UML class diagrams that takes into account the architectural importance of a class in terms of its stereotype (e.g., boundary, control, entity). The design and running of a user study is described. The results of the study supports the hypothesis that layout based on architectural importance is more helpful in class diagram comprehension compared to layouts focusing primarily on aesthetics and/or abstract graph guidelines.

Challenges in Developing Sequence Diagrams (UML)

Journal of Information Technology and Computer Science (JITeCS), 2020

During the object-oriented software design phase, the designers have to describe the dynamic aspect of the system under development through the most common interaction diagram variant in UML 2.0, i.e. sequence diagrams. Some novice designers, including undergraduate and postgraduate students, suffer from making inappropriate models due to insufficiently detailed guidance required to develop such sequence diagrams. This paper classifies some potential mistakes which are likely performed by such novice designers, and discusses the corresponding corrections. We summarized such mistakes based on our long experiences in teaching software modeling classes as well as software analysis and design classes. There were classified twenty-one potential mistakes with respect to the syntactical and semantical correctness of the developed models. It is concluded that novice designers have to be aware and take into account the identified mistakes in such a way they can produce correct sequence diagrams.

A Multi-level Methodology for Developing UML Sequence Diagrams

Lecture Notes in Computer Science, 2008

Though the importance of UML Sequence Diagrams is well recognized by the object-oriented community, they remain a very difficult UML artifact to develop. In this paper we present a multi-level methodology to develop UML Sequence Diagrams. Our methodology is significant in three aspects. First, it provides a multilevel procedure to facilitate ease of the development process. Second, it makes use of certain patterns to ensure the validity of SQDs. Third, it uses consistency checks with corresponding use-case and class diagrams. Throughout the steps of the method we present rules and patterns demonstrating correct and incorrect diagramming of common situations through examples. The purpose of this study is to serve as a reference guide for novice sequence diagram modelers. This methodology is particularly useful for novice practitioners in this field who face challenges in learning the process of SQD development.