UML with meaning

Health care systems are known to be complex and difficult to analyse. Unified Modelling Language (UML) tools have been extensively used to analyse complex systems in several domains, including health care. However, the utility of UML tools in the mapping of care processes has not been demonstrated. This paper reports on the findings of a project that employed UML tools to map the entire care process for patients presenting with symptoms of fractured neck of femur to an acute care hospital in the UK. We employed the UML activity diagram to capture the sequence and conditions of the progress of patients through care activities from a care-system perspective, use case to detail the function performed by each care activity depicted in the activity diagram, and use UML state diagram to capture the dynamic behaviour of patients by depicting states and transition specifications from a patient's perspective. We argue that UML tools can be beneficially employed in the mapping of care processes and to create an information library with the results of such mapping. We also argue that the process mapping method presented here can be used as a basis to develop requirements for simulation models of the flow of patients through the care process.

Unified Modeling Language (UML) plays an important role in the modern software development process by offering standardized methods for visual modeling, analysis, and design of complex systems. This paper discusses the main aspects of storing, editing, and integrating UML documents with integrated development environments (IDEs). The main focus is on comparing the two main formats for storing UML models – XML Metadata Interchange (XMI) and JavaScript Object Notation (JSON). XMI, being an official standard developed by Object Management Group, provides a high degree of detail and compatibility with various UML tools, making it preferable for large and complex projects that require support for the full UML specification. At the same time, JSON is simple and flexible, which makes it suitable for projects where speed of development and ease of integration are important, although it is inferior to XMI in describing complex aspects of UML models. The paper analyzes in detail the methods of editing UML documents, including manual editing and automated approaches, using APIs and scripts. Manual editing is useful when you need to make small changes to the structure of a UML document, but it can be time-consuming and error-prone when working with large projects. Automation, on the other hand, provides effective tools for mass editing and generating UML elements, which significantly speeds up development and minimizes the likelihood of errors, especially since modern tools such as StarUML offer the necessary tools for programmatically modifying UML documents by integrating them into development processes. Combining of UML documents with integrated development environments also plays a key role in increasing development efficiency, as this allows automating code generation based on UML models, maintaining synchronization between code and diagrams, and facilitating visualization and documentation of architectural solutions. Despite the significant advantages, there are challenges associated with limited support for all UML features and potential conflicts between models and code. This only emphasizes the need for further research in this area. Prospects for further research include the development of new methods and tools for working with UML documents, improving their integration with development environments, and using artificial intelligence to automate the analysis and design of UML models. Attention should also be paid to the using of UML with continuous integration processes, which can significantly increase the flexibility and adaptability of software development. Thus, the study of the structure of storing, editing, and integrating UML documents is an important area for optimizing the design and development of modern software systems.

Summary form only given. Since its adoption in 1997, the unified modeling language (UML) has proved very popular with software engineers and has become the de facto standard as a visual modeling language for software engineers. However, this software focus of UML has discouraged many systems engineers from adopting it in earnest. Those who did adopt UML developed strategies to cope with its shortcomings. A common approach was to model additional systems engineering concepts in other modeling tools. This made it difficult to integrate the different viewpoints and achieve traceability. Fortunately, with the release of UML 2.0 and the ensuing extensions to it in SysML - the soon-to-be adopted systems modeling language - the systems engineering community has a real alternative to systems modeling that provides a more integrated approach to systems and software engineering. Since its inception in 1997, ARTiSAN has endeavored to bridge the gap between systems and software engineering modeling by adding systems engineering extensions to the UML and, as a key member of the SysML initiative, is well poised to support these emerging standards for systems and software modeling. This presentation will provide a brief overview of the major extensions proposed by SysML, and will summarize how ARTiSAN's latest release of its flagship product Studio (version 6.0) takes the lead in supporting these concepts.

The emergence of Unified Modeling Language (UML) as a standard for modeling systems has encouraged the use of automated software tools that facilitate the development process from analysis through coding. The UML state machine diagram is used for modeling the dynamic aspects of systems and includes many concepts that are not present in most popular programming languages, like Java or C++. There exists a gap between high level modeling language and a programming language. This paper proposes an approach to narrow the gap between multiple UML models and an implemented system. The narrowing of gap is achieved by generating compact and efficient Java code directly from UML state machine having sequential and concurrent substates. The code generation is achieved by creating a mapping between UML behavior and the Java programming language. Our model can work as a basis for automatic code generation for object-oriented systems.

The main purpose of this paper is to present knowledge-based Enterprise model (EM) sufficiency as data repository for Unified Modelling Language (UML) models generation. UML models are one of the most usable modelling languages in system lifecycle design stage, despite the problem domain of the system. UML models can be generated from Enterprise Model by using particular transformation algorithms presented in previous researches. Generation process from Enterprise model is represented by certain Hospital Information Management process example. Generated UML dynamic Use Case, Activity, Sequence and State models of different perspectives of Hospital Information Management process prove sufficiency of stored information in Enterprise model.

The two most critical phases of SDLC are the specification and the designing phase as they involve the transformation of the semantics from real world domain to computer software systems. Unified Modelling Language (UML) has been accepted as blue print for design and specification of software critical systems. But, UML structures have the weakness in preciously defining the semantics of a system. Any misinterpretation in safety critical system’s specification may risks loss of lives. Formal methods are mathematical tools and techniques which are proven very adequate, principally, at requirement specification and design level. However, formal methods are not welcomed because of rigorous use of mathematics. Therefore, a bridge is required between UML and formal methods to overcome the above insufficiencies. The endeavour of this paper is to propose a new approach by integrating UML and Z notation, a formal specification language. The main focus of this paper is on transforming the UML diagram: use case diagram, class diagram and sequence diagram to Z Schema for capturing both the syntax and semantics, particularly for safety critical system. The resultant formal model of the approach are analyzed and verified by using Z/Eves tool.

As a powerful and object-oriented graphical modeling language, Unified Modeling Language (UML) has been introduced into the design and development of safety-critical computer systems. However, UML model is difficult to reflect the concurrency and consistency of constraint rules between objects and impossible to completely demonstrate the dynamic behavior characteristics of a system. Further, it cannot be directly expressed and analyzed by mathematical tools. Petri net modeling technology uses graphical element place and transition to clearly describe the internal interactions of a system. Meanwhile, Petri net has mature mathematical analysis methods. We have proposed to combine these two tools for designing and analyzing a system with a set of transformation rules from UML statecharts to Petri net. In this paper, an automatic conversion tool is introduced. The tool performs the transformation with three steps as follows: (1) Transforming UML model into XML document, which makes information extraction of the UML model become easier. (2) Analyzing semantics of UML model and Petri net model, then designing data structure for transformation, and completing the transformation based on the transformation rules. (3) Analyzing the transformed Petri net model to verify the characteristics of the UML model. The transformation rules and the tools are developed based on a new railway interlocking system.

Unified Modeling Language (UML) has emerged as the software industry’s dominant modeling language. It is the de facto modeling language standard for specifying, visualizing, constructing, and documenting the components of software systems. Despite its prominence and status as the standard modeling language, UML has its critics. Opponents argue that it is complex and difficult to learn. Some question the rationale of having nine diagramming techniques in UML and the raison d’être of those nine techniques in UML. Others point out that UML lacks a comprehensive methodology to guide its users, which makes the language even more convoluted. A few studies on UML can be found in the literature. However, no study exists to provide a quantitative measure of UML complexity or to compare UML with other object-oriented techniques. In this research, we evaluate the complexity of UML using complexity metrics. The objective is to provide a reliable and accurate quantitative measure of UML complexity. A comparison of the complexity metrical values of UML with other object-oriented techniques was also carried out. Our findings suggest that each diagram in UML is not distinctly more complex than techniques in other modeling methods. But as a whole, UML is very complex–2-11 times more complex than other modeling methods.

Unified Modeling Language (UML) has emerged as the software industry’s dominant modeling language. It is the de facto modeling language standard for specifying, visualizing, constructing, and documenting the components of software systems. Despite its prominence and status as the standard modeling language, UML has its critics. Opponents argue that it is complex and difficult to learn. Some question the rationale of having nine diagramming techniques in UML and the raison d’être of those nine techniques in UML. Others point out that UML lacks a comprehensive methodology to guide its users, which makes the language even more convoluted. A few studies on UML can be found in the literature. However, no study exists to provide a quantitative measure of UML complexity or to compare UML with other object-oriented techniques. In this research, we evaluate the complexity of UML using complexity metrics. The objective is to provide a reliable and accurate quantitative measure of UML complexity. A comparison of the complexity metrical values of UML with other object-oriented techniques was also carried out. Our findings suggest that each diagram in UML is not distinctly more complex than techniques in other modeling methods. But as a whole, UML is very complex–2-11 times more complex than other modeling methods.

Software product line (SPL) is a software engineering paradigm for software development. A software product within a product line often has specific functionalities that are not common to all other products within the product line. Those specific functionalities are termed “variant features” in a product line. SPL paradigm involves the modeling of variant features. However, little work in SPL investigates and addresses the modeling of variant features specific to user interface (UI). Unified Modeling Language (UML) is the de facto modeling language for object-oriented software systems. It is known that UML needs better support in modeling UIs. Thus, much research developed UML extensions to improve UML support in modeling UIs. Yet little of this work is related to developing such extensions for modeling UIs for SPLs in which variant features specific to UI modeling must be addressed. This research develops a UML extension -Web User Interface Modeling Language (WUIML) to address these problems. WUIML defines elements for modeling variant features specific to user interfaces for Web-based SPLs. The model elements in WUIML extend from the metaclass and BasicActivity of the UML2.0 metamodel. WUIML integrates the modeling of variant features specific to user interfaces to UML. For example, in a Web-based patient registration software product line, member products targeting British users may use British date format in the user interface, while member products targeting United States users may use United States date format in the user interface. Thus, this is a variant feature for this product line. WUIML defines a model element, XOR, to represent such exclusive or conditions in a product line user interface model. WUIML would reduce SPL engineers’ efforts needed in UI development. To validate the WUIML research outcome, a case study was conducted. The results of this empirical study indicate that modeling UIs for Web-based SPLs using WUIML is more effective and efficient than using standard UML.

This tutorial presents the modeling concepts of the standard object modeling language, the Unified Modeling Language (UML). Particular attention is paid to the use of the UML for modeling system/software requirements and designs. A system development process and an example of its application is presented. The materials will be based on the recently released UML 1.4 standard. The tutorial also presents some of the major issues and challenges facing the evolution of the UML.

This research focuses on helping Laundry Kilometer 28 in recording cash in and cash out transactions which are still manual so it is not efficient because of the increase in customers. Researchers conducted an analysis using the PIECES method to find out how the system is running, what are the system deficiencies and what the system needs. The researcher designed a system for recording incoming and outgoing cash at Laundry Kilometer 28 using the waterfall method with UML (Unified Modeling Language) tools. Methods of data collection in the form of interviews and direct observation to analyze the Kilometer 28 Laundry business process to owners, cashiers and regular customers. The results of this study are system design with use case diagrams, activity diagrams, class diagrams and sequence diagrams compiled with draw.io, Microsoft Visio Drawing which is then visualized for its interface with Microsoft Power Point.

In this chapter, we provide the essential theory and practical details of employing the principles of Object Orientation (OO) in system architecture modeling. We do not attempt to provide an exhaustive OO tutorial, since there exists a very large literature on this subject (see the references to this chapter). Our goal, instead, is to give the reader the level of understanding needed to master the MBSAP methodology and apply it to practical system architecting challenges. First, we present the rationale for OO and define the essential concepts and terminology, stressing the benefits it delivers in dealing with complex entities. Although we use the Systems Modeling Language (SysML) as the basis for this book, we begin by discussing and illustrating the primary diagrams of the Unified Modeling Language (UML), which is the root language standard for OO. This is then followed by a description of the changes to UML introduced by the SysML, which is defined as a Profile of UML. The reality is that a large part of the SysML is taken directly from the UML language specification. We believe understanding of this material is enhanced by first considering the parent UML and then explicitly showing how UML modifies and extends the language. We include generic UML and SysML diagrams that illustrate important principles and syntax and that can serve as format samples in developing real architecture models. Appendices A and B are concise references to UML and SysML, respectively, intended to give readers a quick and easy way to look up the details. Chapter objective: the reader will be able to create and read UML and SysML diagrams and to describe the role of each.

Unified Modeling Language (UML) provides various diagrams to depict system characteristics and complex environment from different viewpoints and different application layers. It also contains a lot of standard elements with vague and sparse semantics. Researching how to combine Unified Modeling Language (UML) with formal method in order to improve UML semantic accuracy is a hotspot of researches in software engineering because of the half formal characteristic of UML. This paper defines Syntax Domains, Abstract Syntax, Semantic Domains, Semantic Functions of UML sequence diagram using Denotational Semantics, formally depicts sequence diagram on the function of the each syntax object of sequence diagram. It provides the foundation for accuracy and consistency validation of UML sequence diagram.

The IEEE 1588 standard specifies a protocol enabling precise synchronization of clocks in measurement and control systems implemented with technologies such as network communication, and distributed objects. The Unified Modeling Language (UML) is a powerful tool for object-oriented modeling, design, and development of complex distributed systems. This paper describes an object-oriented model for the IEEE 1588 standard-v2, which has been developed using UML tool at National Institute of Standards and Technology (NIST). Tliis model consists of the data types, datasets, entities, and devices of IEEE 1588 standard-v2. The model has been used to produce C++ source codes, and create C++ libraries for the IEEE 1588 standard-v2. With the help of this object model, the development time of IEEE 1588-basd distributed measurement and control applications can be reduced dramatically.