Unified Modeling Language Specification Research Articles

Formalizing UML State Machines for Automated Verification – A Survey

The Unified Modeling Language (UML) is a standard for modeling dynamic systems. UML behavioral state machines are used for modeling the dynamic behavior of object-oriented designs. The UML specification, maintained by the Object Management Group (OMG), is documented in natural language (in contrast to formal language). The inherent ambiguity of natural languages may introduce inconsistencies in the resulting state machine model. Formalizing UML state machine specification aims at solving the ambiguity problem and at providing a uniform view to software designers and developers. Such a formalization also aims at providing a foundation for automatic verification of UML state machine models, which can help to find software design vulnerabilities at an early stage and reduce the development cost. We provide here a comprehensive survey of existing work from 1997 to 2021 related to formalizing UML state machine semantics for the purpose of conducting model checking at the design stage.

A Graph Transformation Approach for Modeling and Verification of UML 2.0 Sequence Diagrams

Unified Modeling Language (UML) 2.0 Sequence Diagrams (UML 2.0 SD) are used to describe interactions in software systems. These diagrams must be verified in the early stages of software development process to guarantee the production of a reliable system. However, UML 2.0 SD lack formal semantics as all UML specifications, which makes their verification difficult, especially if we are modeling a critical system where the automation of verification is necessary. Communicating Sequential Processes (CSP) is a formal specification language that is suited for analysis and has many automatic verification tools. Thus, UML and CSP have complementary aspects, which are modeling and analysis. Recently, a formalization of UML 2.0 SD using CSP has been proposed in the literature; however, no automation of that formalization exists. In this paper, we propose an approach on the basis of the above formalization and a visual modeling tool to model and automatically transform UML 2.0 SD to CSP ones; thus, the existing CSP model checker can verify them. This approach aims to use UML 2.0 SD for modeling and CSP and its tools for verification. This approach is based on graph transformation, which uses AToM3 tool and proposes a metamodel of UML 2.0 SD and a graph grammar to perform the mapping of the latter into CSP. Failures-Divergence Refinement (FDR) is the model checking tool used to verify the behavioral properties of the source model transformation such as deadlock, livelock and determinism. The proposed approach and tool are illustrated through a case study.

An integration of uml use case diagram and activity diagram with Z language for formalization of library management system

Unified Modeling Language (UML) is the effective standard for modeling object-oriented software systems. However, the ambiguity of semantics and the absence of consistency among UML diagrams lead to lack of precisely defining the requirements of a system. On the other hand, formal methods are techniques and tools use the mathematical notations, and they involve the precise syntax and semantics of the unambiguous software requirements specification. It applied in early stages of Software Development Life Cycle (SDLC). Therefore, an integrated between UML specification and formal specification is required to reduce the requirements' ambiguity and error, and to improve the quality and security of software systems. This paper proposes an approach involves the combining UML use-case diagram and activity diagrams with Z language for formalization of Library Management System (LMS). The focus of this paper is on consistency between the UML diagrams to Z Schema, and then verified by using the Z / EVEs tool.

Using the Object Mapping Approach from Analysis to Implementation for Developing Student Registration System

<table width="593" border="1" cellspacing="0" cellpadding="0"><tbody><tr><td valign="top" width="387"><p>The Unified Modeling Language (UML) is the effective standard language of an object-oriented based system analysis and design. The using of object-oriented approach based on UML specification can offer an understandable model, which can reduce the system's complexity. The use-case diagram, class diagram and sequence diagram are important models of the system development during early stages. The object mapping approach between UML class diagram in the analysis phase and source code in the implementation phase is a significant process in the software development life cycle. In order to ensure the consistency of system requirements from analysis to implementation. This paper presents the student registration system by using object mapping based on UML. The UML specification and the generation of Java source code influenced by specific features of class in object-oriented such as inheritance and the association between the classes.</p></td></tr></tbody></table>

Automated deserializer generation from CIM ontologies: CIM $${+}{+}$$ + + —an easy-to-use and automated adaptable open-source library for object deserialization in C $${+}{+}$$ + + from documents based on user-specified UML models following the Common Information Model (CIM) standards for the energy sector

The increasing complexity of ICT systems in smart grids requires that all actors improve their interoperability. To this aim, IEC 61970/61968 specify the Common Information Model (CIM) which describes terms in the energy sector and relations between them. One of the key features of CIM is its object-oriented design based on the Unified Modeling Language (UML). This makes CIM easy to maintain and extensible by visual UML editors leading to a continuous standardization process keeping up with new developments. But this means that CIM based software must be kept up-to-date as well. Therefore, this paper presents our Model-Driven Architecture (MDA) based approach with which CIM, as specified by a visual UML editor, can be mapped to a compilable C $${+}{+}$$ codebase. Moreover, it shows how this codebase can be used for an automated generation of a C $${+}{+}$$ objects deserializer from CIM based documents following the UML specification. All presented approaches are implemented in an open-source project called CIM $${+}{+}$$ and evaluated on a real-world use case.

Metamodeling generalization and other directed relationships in UML

ContextGeneralization is a fundamental relationship in object orientation and in the UML (Unified Modeling Language). The generalization relationship is represented in the UML metamodel as a “directed relationship”. ObjectiveBeing a directed relationship corresponds to the nature of generalization in the semantic domain of object orientation: a relationship that is directed from the subclass to the superclass. However, we claim that the particular form this relationship adopts in the metamodel is erroneous, which entails a series of inconveniencies for model manipulation tools that try to adhere to the UML specification. Moreover, we think that this error could be due to a misinterpretation of the relationships between metamodeling levels in the UML: represented reality (M0), model (M1) and metamodel (M2). This problem also affects other directed relationships: Dependency and its various subtypes, Include and Extend between use cases, and others. MethodWe analyze the features of the generalization relationship in various domains and how it has been metamodeled in UML. We examine the problems, both theoretical and technological, posed by the UML metamodel of generalization. We then compare it with the metamodel of other directed relationships. ResultsWe arrive at the conclusion that the metamodel of all directed relationships could be improved. Namely, we claim that, at level M2, the metamodel should not contain any one-way meta-associations: all meta-associations should be two-way, both for practical and theoretical reasons. ConclusionsThe rationale for our main claim can be summarized as follows: connected graphical symbols do know each other, and the goal of a metamodel is to specify the syntactic properties of a language, ergo meta-associations must be two-way. This, of course, does not preclude at all the use of one-way associations at the user model level (M1).

Modeling and Analyzing Flight Control Software of Unmanned Aerial Vehicle Using UML and B Method

B is a formal method which enables the automatic generation of an executable code through successive refinements from an abstract specification. Unified Modeling Language (UML) specifications can be formally verified by analyzing the corresponding B specification, and integration of UML specifications and B method can overcomes the drawbacks of UML. In this paper the Class diagram of the flight control system is presented and each class operation is mapped to a B abstract machine. The flight control software behaviors are presented in the form of statecharts The B method is adopted to translate the statecharts into B specification of flight control software.Using UML and B method, flight control is refined and failure management is added. Finally proof obligations are presented to ensure the safety for the ertical control of artificial navigation of UAV.

MODEL AND VERIFICATION OF WS-CDL BASED ON UML DIAGRAMS

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.

A two-stage framework for UML specification matching

Context Specification matching techniques are crucial for effective retrieval processes. Despite the prevalence for object-oriented methodologies, little attention has been given to Unified Modeling Language (UML) for matching. Objective This paper presents a two-stage framework for matching two UML specifications and quantifying the results based on the systematic integration of their structural and behavioral similarities in order to identify the candidate component set for reuse. Method The first stage in the framework is an evaluation of the similarities between UML class diagrams using the Structure-Mapping Engine (SME), a simulation of the analogical reasoning approach known as the structure-mapping theory. The second stage, performed on the components identified in the first stage, is based on a graph-similarity scoring algorithm in which UML class diagrams and sequence diagrams are transformed into an SME representation and a Message-Object-Order Graph (MOOG). The effectiveness of the proposed framework was evaluated using a case study. Results The experimental results showed a reduction in potential mismatches and an overall high precision and recall. Conclusion It is concluded that the two-stage framework is capable of performing more precise matching compared to those of other single-stage matching frameworks. Moreover, the two-stage framework could be utilized within a reuse process, bypassing the need for extra information for retrieval of the components described by UML.

From UML Specification into Implementation Using Object Mapping

In information systems, a system is analyzed using a modeling tool. Analysis is an important phase prior to implementation in order to obtain the correct requirements of the system. During the requirements phase, the software requirements specification (SRS) is used to specify the system requirements. Then, this requirements specification is used to implement the system. The requirements specification can be represented using either a structure approach or an object-oriented approach. A UML (Unified Modeling Language) specification is a well-known for representation of requirements specification in an object-oriented approach. In this paper, we present one case study and discuss how mapping from UML specification into implementation is done. The case study does not require advanced programming skills. However, it does require familiarity in creating and instantiating classes, object-oriented programming with inheritance, data structure, file processing and control loop. For the case study, UML specification is used in requirements phase and Borland C++ is used in implementation phase. Based on the case study, it shows that the proposed approach improved the understanding of mapping from UML specification into implementation.

Efficient test case generation for validation of UML activity diagrams

Unified Modeling Language (UML) is widely used as a system level specification language in embedded system design. Due to the increasing complexity of embedded systems, the analysis and validation of UML specifications is becoming a challenge. UML activity diagram is promising to modeling the overall system behavior. However, lack of techniques for automated test case generation is one major bottleneck in the UML activity diagram validation. This article presents a methodology for automatically generating test cases based on various model checking techniques. It makes three primary contributions: First, we propose coverage-driven mapping rules that can automatically translate activity diagram to formal models. Next, we present a procedure for automatic property generation according to error models. Finally, we apply various model checking based test case generation techniques to enable efficient test case generation. Our experimental results demonstrate that our approach can reduce the validation effort drastically by reducing both test case generation time and required number of test cases to achieve a functional coverage goal.

A Meta-Model for Textual Use Case Description.

A Use Case is a specification of interactions involving a system and external actors of that system. The capability for use case modeling has been integrated to the Unified Modeling Language (UML) since its inception. However, use cases are only defined at an abstract level, as the UML Specification does not discuss use case description in text form. In this paper, we propose an abstract syntax for textual use case description as a meta-model extension of the UML Specification. This meta-model is based on elements commonly found in use case templates. The meta-model also includes OCL constraints for ensuring consistency with the UML specification.

A Model-Driven Development Approach to Mapping UML State Diagrams to Synthesizable VHDL

With the continuing rise in the complexity of embedded systems, there is an emerging need for a higher level modeling environment that facilitates efficient handling of this complexity. The aim here is to produce such a high-level environment using model- driven development (MDD) techniques that map a high-level abstract description of an electronic embedded system into its low-level implementation details. The Unified Modeling Language (UML) is a high-level graphical-based language that is broad enough in scope to model embedded systems hardware circuits. The authors have developed a framework for deriving very high speed integrated circuit hardware description language (VHDL) code from UML state diagrams and defined a set of rules that enable automated generation of synthesizable VHDL code from UML specifications using MDD techniques. By adopting the techniques and tools described in this paper, the design and implementation of complex state-based systems is greatly simplified.

Towards an integrated graph-based semantics for UML

This paper shows how a central part of the Unified Modeling Language (UML) can be integrated into a single visual semantic model. It discusses UML models composed of class, object, state, sequence and collaboration diagrams and presents an integrated semantics of these models. As formal basis the theoretically well-founded area of graph transformation is employed which supports a visual and rule-based transformation of UML model states. For the translation of a UML model into a graph transformation system the operations in class diagrams and the transitions in state diagrams are associated with graph transformation rules that are then combined into one system in order to obtain a single coherent semantic description. Operation calls in sequence and collaboration diagrams can be associated with applications of graph transformation rules in the constructed graph transformation system so that valid sequence and collaboration diagrams correspond to derivations, i.e., to sequences of graph transformation rule applications. The main aim of this paper is to provide a formal framework that supports visual simulation of integrated UML specifications in which system states and state changes are modeled in a straightforward way.

An extension of UML for the modeling of WIMP user interfaces

The Unified Modeling Language (UML) [OMG, Unified Modeling Language Specification, Version 2.0, Technical Report, Object Management Group 〈 http://www.omg.org/technology/documents/formal/uml.htm 〉 , 2005] provides system architects working on analysis and design (A&D) with one consistent language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for the business modeling. The user interface (UI), as a significant part of most applications, should be modeled using UML, and automatic CASE tools may help to generate UIs from UML designs. In this paper, we describe how to use and specialize UML diagrams in order to describe the UIs of a software system based on WIMP ( Windows, Icons, Menus and Pointers). Use case diagrams are used for extracting the main UIs. Use cases are described by means of user-interaction diagrams, a special kind of activity diagrams in which states represent data output actions and transitions represent data input events. Input and output interactions in the user-interaction diagrams help the designer to extract the UI components used in each UI. We obtain a new and specialized version of the use case diagram for the UI modeling (called UI diagram) and a class diagram for UI components—called UI-class diagram. The user-interaction, UI and UI-class diagrams, can be seen as the UML-based UI models of the system. Finally, UI prototypes can be generated from UI-class diagrams with CASE tool support. As case study of our technique, we will describe an Internet book shopping system.

Tracking product specification dependencies in collaborative design for conflict management

The main difficulty associated with a collaborative design process is understanding the product data exchanged during the design. Efficient and effective coordination of design activities relies on a thorough understanding of the dependencies between shared product specifications throughout the entire development cycle. This paper explores the linkages between the design process features and product specification dependencies, and suggests ways of identifying and managing specification dependencies to improve collaborative process performance. Using a UML (Unified Modeling Language) specification, we propose a process traceability tool to track the design process in an ongoing manner. Based on the information captured, the dependencies between specifications involved in the tracked process are identified and inserted in a dependency network, which is maintained throughout the design process. A set of mechanisms is then proposed to qualify the identified dependencies. Extracting and qualifying specification dependencies could be useful in many design situations; for example, during an engineering change management process to assess impacts and study change feasibility, or during a conflict management process to assist designers in resolving conflicts and maintaining the coherence of the design process (knowing that change management is a tool to conduct conflict management). Special attention is paid to the conflict management process. By means of a case study, we show how the solution we propose can assist designers during the conflict management process.

Integration of statechart and B method based analysis and verification for flight control software of unmanned aerial vehicle

B is a formal method which enables the automatic generation of an executable code through successive refinements from an abstract specification. Unified Modeling Language (UML) specifications can be formally verified by analyzing the corresponding B specification, and integration of UML specifications and B method can overcomes the drawbacks of UML. In this paper Statemate, one tool supporting the virtual prototype technology, is used, and the flight control software behaviors are presented in the form of statecharts The B method is adopted to translate the statecharts into B specification of flight control software.

Java Fuzzy Kit (JFK): A shell to build fuzzy inference systems according to the generalized principle of extension

In this article the author presents JFK, which stands for Java Fuzzy Kit. JFK is an Application Programming Interface (API) that complies with both, a general structure of a fuzzy rule base and the necessary processing to compute the generalized principle of extension. A recurrent structure is found for a class of fuzzy expert systems, known as the Mamdani model. This leads to claim that a design pattern exists, since core objects, which are present regardless the specific application are identified. However, there is not a general shell to build fuzzy expert systems, and this provokes that current fuzzy expert systems are build on an ad-hoc basis. The modelling of JFK is done according to the Unified Modelling Language specifications. Along with the UML modelling three important algorithms are described, which serve to perform the generalized principle of extension. The usage of JFK is illustrated with an example, namely the ranking of swimmers. Preliminary results on this study case are the basis to propose the realization of fuzzy distributed decision systems. This goal is accomplished by providing agents with fuzzy expert systems, with the integration of JFK and the standardized platform JADE (Java Agent Development Environment).

UML specification of access control policies and their formal verification

Security requirements have become an integral part of most modern software systems. In order to produce secure systems, it is necessary to provide software engineers with the appropriate systematic support. We propose a methodology to integrate the specification of access control policies into Unified Modeling Language (UML) and provide a graph-based formal semantics for the UML access control specification which permits to reason about the coherence of the access control specification. The main concepts in the UML access control specification are illustrated with an example access control model for distributed object systems.

TremorFlash: Earthquake warning and follow-up system

This paper describes the design approach towards the construction of an earthquake warning and follow-up system, TremorFlash. The approach consists in integration of software engineering and hardware organization. On software front, we utilize Unified Modeling Language specifications and tools of object-oriented analysis and design. Starting from requirements analysis using Use Case model, different tasks such as static modeling, behavioral modeling, implementation modeling and environment modeling is carried out. The hardware is assembled using locally available piece meal components. Extra effort has been applied to make TremorFlash a reliable, safe and fault-tolerant system. For this, careful hazards and risk analysis is performed along with system dependability analysis in order to map out all risks involved with the system. Furthermore, a unique application instance redundancy technique is devised for fault tolerance. Keywords: TremorFlash, core system, user module, fault-tolerant system. Nepalese Journal of Engineering Vol.1(1) 2005 pp.3-9