Applying the LOT Methodology to a Public Bus Transport Ontology aligned with Transmodel: Challenges and Results

We present an ontology that describes the domain of Public Transport by bus, which is common in cities around the world. This ontology is aligned to Transmodel, a reference model which is available as a UML specification and which was developed to foster interoperability of data about transport systems across Europe. The alignment with this non-ontological resource required the adaptation of the Linked Open Terms (LOT) methodology, which has been used by our team as the methodological framework for the development of many ontologies used for the publication of open city data. The ontology is structured into three main modules: (1) agencies, operators and the lines that they manage, (2) lines, routes, stops and journey patterns, and (3) planned vehicle journeys with their timetables and service calendars. Besides reusing Transmodel concepts, the ontology also reuses common ontology design patterns from GeoSPARQL and the SOSA ontology. As part of the LOT data-driven validation stage, RDF data has been generated taking as input the GTFS feeds (General Transit Feed Specification) provided by the Madrid public bus transport provider (EMT). Mapping rules from structured data sources to RDF were developed using the RDF Mapping Language (RML) to generate RDF data, and queries corresponding to competency questions were tested.

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>

Extending UML specification for semantic modeling objects

In the article, propose mapping from UML class diagrams to SHOIQ. descriptive logic. Made approach through extension the UML notations by using stereotypes as close to semantic structures. Specified on the causes and problems that arise in such mapping.

Utilizing UML, cTLA, and SRN

To meet the challenge of conducting quantitative analysis at the early stage of the system development process, this chapter introduces an extensive framework for performance modeling of a distributed system. The goal of the performance modeling framework is the assessment of the non-functional properties of the distributed system at an early stage based on the system's functional description and deployment mapping of service components over an execution environment. System's functional description with deployment mapping has been specified using UML. To analyze the correctness of the UML specification style, we have used temporal logic, specifically cTLA, to formalize the UML model. We have shown in detail how UML models are formalized by a set of cTLA processes and production rules. To conduct the performance evaluation of a distributed system, the UML model is transformed into analytic model SRN. We have specified an automated model transformation process to generate SRN model from UML, which is performed in an efficient and scalable way by the use of model transformation rules.

Enhancement of Consistency of UML Diagrams by Cross Checking Rules

UML is a rich semantic language, but it is difficult to ensure consistency of the diagrams you have written. In this paper, we propose cross checking rules to improve consistency among UML diagrams, especially between UML static and dynamic diagrams. We derive integrated metamodels in order to reflect more clear interactions of UML elements in the checking rules and use OCL(Object Constraint Language) to represent the checking rules accurately. By comparing with the well-formed rules of UML specification, we study on consistency of UML diagrams. We also derive integrated metamodels of static and dynamic diagrams by analyzing the relationships of UML diagrams. Finally, we test the usability of derived rules through a case study.

Ontological Rules for UML-Based Conceptual Modeling

UML is used as a language for object-oriented software design, and as a language for conceptual modeling of applications domains. Given the differences between these purposes, UML’s origins in software engineering might limit its appropriateness for conceptual modeling. In this context, Evermann and Wand have proposed a set of well-defined ontological rules to constrain the construction of UML diagrams to reflect underlying ontological assumptions about the real world. The authors extend their work using a design research approach that examines these rules by studying the consequences of integrating them into a UML CASE tool. The paper demonstrates how design insights from incorporating theory-based modeling rules in a software artifact can be used to shed light on the rules themselves. In particular, the authors distinguish four categories of rules for implementation purposes, reflecting the relative importance of different rules and the degree of flexibility available in enforcing them. They propose distinct implementation strategies that correspond to these four rule categories and identify some redundant rules as well as some rules that cannot be implemented without changing the UML specification. The rules are implemented in an open-source UML CASE tool.

Formalization of UML Composition in OCL

With the increasing use of design models during the development process, developers now face a daunting task to maintain consistency between the design models and their implementation. Consistency maintenance is particularly challenging when a design model language introduces constructs that have no direct counterpart in programming languages. For example, the UML composition, an important relationship in software development, reflects some important principles in software engineering such as encapsulation. Unfortunately, influenced by the ownership model, existing approaches supporting UML composition require the non-accessibility property. However, composition in the UML specification does not support the ownership model. In this paper we present a UML composition formalization using the Object Constraint Language (OCL) that strictly adheres to the UML specification.