A general framework for formalizing UML with formal languages

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.

: This report describes the detailed operation of the quality control component of the Navy Coupled Ocean Data Assimilation system for processing two- (2D) and three-dimensional (3D) fields. In addition to the conventional flow charts and tree diagrams used to describe sequential programs, several Unified Modeling Language (UML) diagrams are used to demonstrate the relationship between objects within the system. This Object Oriented (OO) analysis is intended to aid in future development and application of the NCODA system. UML is an abstract model of a system, which can be used to describe/develop systems that can be implemented in different computer languages. The UML model can be transformed to other representations (e.g., FORTRAN) for application. The UML diagrams are used to demonstrate three aspects of the NCODA system: (1) the static structure of the system can easily cast as OO classes; (2) functional requirements (user-computer interaction) of the system; and (3) the dynamic behavior of the system with respect to file system access.

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 Modelling Language (UML) has a graphical notation for 13 different types of diagrams and can be used as a general modelling tool. Well-known examples of diagram types are class diagrams for modelling classes that can be instanced into objects, state machine diagrams for modelling states in systems and activity diagrams for modelling process flows. A literature survey shows that UML has been used to model concepts and methodologies of risk assessment and risk management. One example is the Coras Framework. The international standard CEI IEC 61882 Hazard and operability (HAZOP) studies describes concepts for investigating and detecting possible hazards in systems. In CEI IEC 6882, guide words like ‘More’ and ‘Less’ are applied to system parameters to invoke deviations in the system and assess possible hazards due to the deviation from the design intent. In this paper, we have used UML to model concepts of CEI IEC 61882 Hazards and operability studies. Diagrams of UML were used to show dependencies and relations between parts of the target system and concepts of CEI IEC 61882. Extensions of UML are suggested to better capture and display the concepts of CEI IEC 61882, the results of a HAZOP study and emerging risk. These extensions are referred to as UML for emerging risks (UML-ER).

Transportation data models traditionally are represented in Unified Modeling Language (UML). UML diagrams are intuitive for understanding transportation concepts and their relationships and thus provide standardized ways to construct transportation data models. Many UML models have been developed for this purpose. However, because UML does not consider semantics, sharing UML data is difficult. Reusing UML diagrams also is difficult. In contrast, web ontology language (OWL) describes the semantics of ontology and thus is good for knowledge sharing and reasoning. OWL data are easier to share and better for performing logical inference. Unfortunately, no automatic method is available to transform data models from UML to OWL. A method to automate the transformation process is presented, using transportation data as a case study. Results indicate that transportation data represented in OWL have many advantages, including facilitated data sharing and inference. They also indicate that although many elements in UML can be transformed to OWL, some do not have OWL counterparts.

The Unified Modeling Language (UML) has become a widely adopted standard in the software development industry. Unfortunately, the UML is a semi-formal language which lacks precisely defined constructs. Z language is a formal specification language. Formal languages are used to ensure that systems meet regulations and standards. This paper aims to reduce risks associated with software development and increase safety and reliability. This goal is achieved by formalizing the syntax of (a sub-set of the popular UML diagrams (Use Case diagram, Class diagram, and State Machine diagram) using Z specifications.

The Unified Modeling Language (UML) has been designed to be a full standard notation for Object-Oriented Modelling. UML is a rather complete set of notations, but it lacks of formal semantics. This article introduces formal semantics for UML based on algebraic abstract data types. We currently consider only class and object diagrams. These diagrams include class structures, associations, multiplicities, constraints, instances as well as specialization relationships. We give a formal semantics for each of these elements by interpreting the structure of a class as an abstract data type, associations as values of type Association, and specialization as structural projection. We show that a tool like Larch Prover is able to support proofs over UML diagrams. We use the critical pair computation to find out inconsistencies. Several different inconsistencies of class diagrams are shown on a library example.

Most visual diagramming tools provide point‐and‐click construction of computer‐drawn diagram elements using a conventional desktop computer and mouse. SUMLOW is a unified modelling language (UML) diagramming tool that uses an electronic whiteboard (E‐whiteboard) and sketching‐based user interface to support collaborative software design. SUMLOW allows designers to sketch UML constructs, mixing different UML diagram elements, diagram annotations, and hand‐drawn text. A key novelty of the tool is the preservation of hand‐drawn diagrams and support for manipulation of these sketches using pen‐based actions. Sketched diagrams can be automatically ‘formalized’ into computer‐recognized and ‐drawn UML diagrams and then exported to a third party CASE tool for further extension and use. We describe the motivation for SUMLOW, illustrate the use of the tool to sketch various UML diagram types, describe its key architecture abstractions and implementation approaches, and report on two evaluations of the toolset. We hope that our experiences will be useful for others developing sketching‐based design tools or those looking to leverage pen‐based interfaces in software applications. Copyright © 2007 John Wiley & Sons, Ltd.

To solve the identification and comprehension problem of crosscutting concerns in existing legacy software system, a framework of aspects-oriented software reverse engineering was proposed. An approach on re-modularizing traversal features of legacy system was presented, which based on various Unified Modeling Language (UML) diagrams. While modeling crosscutting concerns in UML use case diagrams, the non-functional requirements that affect several use case modules can be enveloped into aspects modules with stereotype mechanism. The recurring message transmission patterns can be re-modularized as aspects in UML sequence diagrams with UML collaborations. Standard UML activity diagram notations were extended and modified by nodes fusion and addition, which support the graphical composition operation between crosscutting behaviors and primary business rules of concurrent system. The case study indicates traversal features of software system can be extracted and re-modularized from various perspectives in aspects-oriented reverse engineering, which improves the comprehensibility and maintainability of legacy system.

Debugging on computer program is a complex cognitive activity. Although it is complex, it’s still one of the popular issues in computer programming task. It is a difficult task, which is to understand what the error is and how to solve such error? In computer programming the difficulty is to understand the Object-Oriented programming concept together with the programming logic. If the programming logic is incorrect, the program codes will have such error named as logic error and can caused highly maintenance cost. Logic error is a bug in a program that causes it to operate incorrectly, without terminating or crashing the program. It will produce unintended output or other behavior than what we are expecting. Method that use to develop a propose model Object Oriented Debugger is Unified Modeling Language (UML). It is the best choice model and suitable to design the Object Oriented Debugger which will be developed in an object oriented programming environment. The model will provide an ability to capture the characteristics of a system by using notations in the process of designing and implementing the system. The model of Object Oriented Debugger has been successfully implemented. This model has been developed using Unified Approach methodology, which consists of two methods such as Object-Oriented Analysis (OOA) and Object-Oriented Design (OOD). The model developed is to capture the structure and behavior of the Object Oriented Debugger by using the UML diagram. The model also can ease the readability of the documentation for the maintenance purposes. The design of the Object Oriented Debugger Model has been developed using the UML notation. It’s consisting of two parts that are object-oriented analysis and object-oriented design. All the developing and designing are based on the model in UML.

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 modelling language (UML) 2.0 introduced in 2002 has been developing and influencing object-oriented software engineering and has become a standard and reference for information system analysis and design modelling. There are many concepts and theories to model the information system or software application with UML 2.0, which can make ambiguities and inconsistencies for a novice to learn to how to model the system with UML especially with UML 2.0. This article will discuss how to model the simple software application by using some of the diagrams of UML 2.0 and not by using the whole diagrams as suggested by agile methodology. Agile methodology is considered as convenient for novices because it can deliver the information technology environment to the end-user quickly and adaptively with minimal documentation. It also has the ability to deliver best performance software application according to the customer's needs. Agile methodology will make simple model with simple documentation, simple team and simple tools.

The Web Services Choreography Description Language (WS-CDL) is a specification developed by the W3C and can be viewed as a blueprint for the development of end-point services. Consequently, it is worth providing a systematic approach for its modeling, analysis and verification. The Unified Modeling Language (UML) is an industry standard for modeling. Applying UML to model WS-CDL is obviously a promising solution to bring together academics and practitioners through a unique standard language. In this paper, we propose to use different UML diagrams to model WS-CDL. UML Component Diagram is used to model the underlying structure of WS-CDL. UML Sequence Diagram is utilized to model the activities in WS-CDL. UML State Machine Diagram is utilized to model the behaviors of each role participating in a WS-CDL specification. We then enrich the UML State Machine Diagram with data by the use of UML Class Diagram. Given the UML specification of WS-CDL, we then provide a systematic way of formally analyzing and verifying WS-CDL against desired properties. Some experiments show that our approach can verify structural, behavioral and data properties in a middle-scale data-enriched WS-CDL specification.

To analyze the temporal aspects of symptoms, including their temporal uncertainty, in order to develop a high-level conceptual data model representation of this domain. A basic tenet of existing temporal models is that events occur not only relative to a particular date or time, but also relative to the time of some other event. The time an event occurs, particularly when the event is a symptom being recalled by a patient or collected by a busy provider, is frequently incomplete or uncertain, and this uncertainty must also be represented in a temporal data model. The object-oriented modeling technique used in this study is becoming popular among U.S. medical informatics standards developers. A conceptual data model for the temporal aspects of symptom data, including temporal uncertainty, has been developed. The object-oriented modeling approach used enables the temporal objects and attributes defined in this model to be inherited by other medical objects, such as problems. The temporal comparators presented here have previously been defined, and may serve as the basis for standardizing the terms used to describe how one event temporally relates to another. In an attempt to achieve domain completeness, this study concentrated more on developing a model that is highly expressive than on developing one that is easily queried. This trade-off in representation versus "queryability" will require further analysis and may require modifications to the underlying model.

The Unified Modelling Language (UML) is a language for specifying, visualising, constructing and documenting software systems. The UML proved to be extremely successful and it has achieved tremendous popularity making it the de facto industry standard for object oriented system development. As such, many researchers presented empirical studies on the practical usage of UML but as well criticisms for UML complexity, difficulty to be learnt, etc. Even though a large number of articles and books are devoted to various aspects of UML language, there is little evidence on how UML is used. This study attempts to identify the profile of persons using UML, to pinpoint UML diagrams that are being used and their effectiveness, to discover whether CASE tools are being used and to record the perceived usefulness of UML language. For conducting the study a survey was developed and it was distributed to mailing lists of Greek IT professionals and to university students. The findings indicate that UML is used successfully in the majority of software development projects and that most users perceive UML positively since it supports faster system building, development of higher quality software systems, and for specific cases, it leads to software development cost‐decrease.