scholarly journals Towards UML representation for BPMN and DMN models

2019 ◽  
Vol 252 ◽  
pp. 02007 ◽  
Author(s):  
Anna Suchenia ◽  
Paweł Łopata ◽  
Piotr Wiśniewski ◽  
Bernadetta Stachura-Terlecka
Keyword(s):  
Process Model ◽  
Business Models ◽  
Unified Modeling Language ◽  
Consistency Checking ◽  
Functional Requirements ◽  
Unified Modeling ◽  
Management Group ◽  
Design Alternatives ◽  
Software Engineers ◽  
Uml Models

Unified Modeling Language (UML) is a standardised Object Management Group (OMG) notation among software engineers. There have been many attempts to design alternatives to UML. Recently, new notations such as Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) have been proposed for modelling processes and decisions. These dedicated notations provide a simpler way of capturing functional requirements in a designer-friendly fashion. Moreover, some concepts as rules cannot be directly modelled in UML. Our research considers a method of translating business models such as BPMN and DMN into a set of consistent UML models, which can be later used by business analysts and developers to understand and implement the system. As a single notation design, it allows the user to take advantage of software supporting UML modelling and consistency checking, in addition using such translation can provide additional insights into OMG business models. Furthermore, the design provided in a single notation can be easier to follow and develop. This approach supports also visualisation of rules. It is important to mention that the proposed solution does not extend any custom UML artifacts and can be used with standard UML tools.

Towards the Meta-Modeling of Complex Inter-Organisationnel Collaborative Processes

2019 ◽  
Vol 15 (3) ◽  
pp. 16-34
Author(s):  
Kahina Semar-Bitah ◽  
Kamel Boukhalfa
Keyword(s):  
Information Exchange ◽  
Process Model ◽  
Business Processes ◽  
Unified Modeling Language ◽  
Unified Modeling ◽  
Transformation Rules ◽  
Collaborative Processes ◽  
Meta Modeling ◽  
Business To Business ◽  
Uml Models

Enterprises are progressively embedded in business to business atmospheres, in order to achieve their common business objectives. Such collaborations lead to Inter-Organizational Business Processes. Therefore, IOBP modeling involves new challenges, mainly the ability to deal with autonomy, privacy, heterogeneity. As a contribution in this area, a IOBP meta-model was designed. This model takes into account the maximum concepts related to the collaboration. Where, the process is complex, and its model in a global way affects its vision and complicates its implementation and hence the idea of its analysis into sub-IOBP to reduce the complexity of the global collaborative process, to streamline information exchange and to facilitate the understanding of the process by partners. A set of Atlas Transformation Language (ATL) transformation rules has been defined to convert Unified Modeling Language (UML) models to Business Process Model and Notation. Finally, the application of our approach has been demonstrated through a framework which can solve the problem of generic IOBP.

scholarly journals An Extended Rule of the SysML Requirement Diagram Transformation into OWL Ontologies

2021 ◽  
Vol 14 (1) ◽  
pp. 506-515
Author(s):  
Ahmad Ashari ◽  
◽  
Anny Sari ◽  
Helna Wardhana ◽  
◽  
...  
Keyword(s):  
Response Time ◽  
System Modeling ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Functional Requirements ◽  
Unified Modeling ◽  
Object Property ◽  
Transformation Rules ◽  
Owl Ontology ◽  
Time Required

The System Modeling Language (SysML) used the Requirement Diagram to model non-functional requirements, such as response time, size, or system functionality, which cannot be accommodated in the Unified Modeling Language (UML). SysML Requirement Diagram, in its implementation, integrates with several diagrams describing the requirements, which are referred to as additional elements. The absence of transformation rules for these additional elements to become OWL ontology causes difficulties in reading, understanding, and tracking the requirements. In this research, an extended rule of the Requirement Diagram transformation is proposed to solve the problems. First, some transformation rules are defined to make requirements easier to trace and realize the ontology generation's automatic transformation. Second, the time required during transformation processing to prepare and generate the OWL file shows the proposed model's performance. The ontology components produced from this research, such as class, subclass, object property, and data property, can be viewed in Protégé.

From MARTE to Reconfigurable NoCs

2010 ◽  
pp. 135-157
Author(s):  
Imran Rafiq Quadri ◽  
Majdi Elhaji ◽  
Samy Meftali ◽  
Jean-Luc Dekeyser
Keyword(s):  
System Modeling ◽  
Unified Modeling Language ◽  
Modeling And Analysis ◽  
Unified Modeling ◽  
Model Driven ◽  
Abstraction Level ◽  
Management Group ◽  
High Level Modeling ◽  
High Level ◽  
Abstraction Levels

Due to the continuous exponential rise in SoC’s design complexity, there is a critical need to find new seamless methodologies and tools to handle the SoC co-design aspects. We address this issue and propose a novel SoC co-design methodology based on Model Driven Engineering and the MARTE (Modeling and Analysis of Real-Time and Embedded Systems) standard proposed by Object Management Group, to raise the design abstraction levels. Extensions of this standard have enabled us to move from high level specifications to execution platforms such as reconfigurable FPGAs. In this chapter, we present a high level modeling approach that targets modern Network on Chips systems. The overall objective: to perform system modeling at a high abstraction level expressed in Unified Modeling Language (UML); and afterwards, transform these high level models into detailed enriched lower level models in order to automatically generate the necessary code for final FPGA synthesis.

Seamless Formalizing the UML Semantics through Metamodels

2001 ◽  
pp. 225-249 ◽  
Author(s):  
Jose Luis Fernandez Aleman ◽  
Ambrosio Toval Alvarez
Keyword(s):  
Formal Model ◽  
Language Evolution ◽  
Formal Semantics ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Algebraic Specification ◽  
Unified Modeling ◽  
Management Group ◽  
Specification Theory ◽  
Insight Into

Despite the fact that the Unified Modeling Language (UML) has been adopted by the Object Management Group (OMG2 ) as the standard notation for use in Object-Oriented (OO) Systems Development, it still does not have a truly formal semantics. There is currently much effort directed towards formalizing particular aspects or models of UML. However, the literature gives little insight into the appropriate strategy for tackling this problem within an integrated basis including the language evolution. This chapter identifies and discusses three feasible strategies which can be applied to formalize UML. One of these strategies is selected to underpin the four-layer architecture on which UML is based. The approach is based on the soundness of algebraic specification theory, which, in addition, provides suitable theorem-proving capabilities for exploiting the UML formal model obtained. The formal models proposed are specified using an executable algebraic specification language called Maude.

scholarly journals DESAIN NON-PLAYER CHARACTER PERMAINAN TIC-TAC-TOE DENGAN ALGORITMA MINIMAX

2019 ◽  
Vol 21 (3) ◽  
pp. 223-233
Author(s):  
Gunadi Emanuel ◽  
R. Kristoforus J. Bendi ◽  
Arieffianto Arieffianto
Keyword(s):  
Process Model ◽  
Development Process ◽  
Unified Modeling Language ◽  
Visual Basic ◽  
Software Modeling ◽  
Game Development ◽  
Unified Modeling ◽  
Board Games ◽  
Linear Sequence ◽  
Analysis Phase

Abstract :  Tic-Tac-Toe is one of the board games. It is played by filling the columns on the board with X or O in such a way as to form parallel lines vertically, horizontally and diagonally. This study aims to design Non-Player Characters (NPC) in the tic-tac-toe game with the minimax algorithm. The Tic-tac-toe game will be designed with two game modes: easy and minimum random modes. While in minimax NPC mode will determine the best step. The game development process of the tic-tac-toe application is based on a linear sequence process model. In the analysis phase, the NPC will be designed based on the concept of minimax. Software modeling was designed using Unified Modeling Language (UML), and coded with Visual Basic programming. Our tests show that NPCs with the Minimax algorithm can work well.

Use Cases in the UML

2011 ◽  
pp. 3909-3913
Author(s):  
Brian Dobing ◽  
Jeffrey Parsons
Keyword(s):  
Software Development ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Use Cases ◽  
Use Case ◽  
Unified Modeling ◽  
Systems Analysis And Design ◽  
Text Document ◽  
Management Group ◽  
Uml 2.0

The unified modeling language (UML) emerged in the mid-1990s through the combination of previously competing object-oriented systems analysis and design methods, including Booch (1994), Jacobson, Christerson, Jonsson, and Overgaard (1992), Rumbaugh, Blaha, Premerlani, Eddy, and Lorensen (1991) and others. Control over its formal evolution was placed in the hands of the object management group (www.omg.org), which recently oversaw a major revision to UML 2.0 (OMG, 2005). The UML has rapidly emerged as a standard language and notation for object-oriented modeling in systems development, while the accompanying unified software development process (Jacobson, Booch, & Rumbaugh, 1999) has been developed to provide methodological support for applying the UML in software development. Use cases play an important role in the unified process, which is frequently described as “use case driven” (e.g., Booch et al., 1999, p. 33). The term “use case” was introduced by Jacobson (1987) to refer to a text document that outlines “a complete course of events in the system, seen from a user’s perspective” (Jacobson et al., 1992, p. 157). The concept resembles others being introduced around the same time. Rumbaugh et al. (1991), Wirfs-Brock, Wilkerson, and Wiener (1990), and Rubin and Goldberg (1992) use the terms “scenario” or “script” in a similar way. While use cases were initially proposed for use in object-oriented analysis and are now part of the UML, they are not inherently object-oriented and can be used with other methodologies.

Information Modeling in UML and ORM

2005 ◽  
pp. 1471-1475 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Information Modeling ◽  
Code Design ◽  
Domain Experts ◽  
Weak Support ◽  
Unified Modeling ◽  
Data Intensive ◽  
Management Group ◽  
Data Intensive Applications

The Unified Modeling Language (UML) was adopted by the Object Management Group (OMG) in 1997 as a language for object-oriented (OO) analysis and design. After several minor revisions, a major overhaul resulted in UML version 2.0 (OMG, 2003), and the language is still being refined. Although suitable for object-oriented code design, UML is less suitable for information analysis, since it provides only weak support for the kinds of business rules found in data-intensive applications. Moreover, UML’s graphical language does not lend itself readily to verbalization and multiple instantiation for validating data models with domain experts.

Specification and Checking of Dependency Relations between UML Models

2011 ◽  
pp. 237-253
Author(s):  
Claudia Pons ◽  
Roxana Giandini ◽  
Gabriel Baum ◽  
Jose L. Garbi ◽  
Paula Mercado
Keyword(s):  
Development Process ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Formal Description ◽  
Unified Modeling ◽  
Intelligent Analysis ◽  
Software Engineers ◽  
Different Dimensions ◽  
Definition Of ◽  
Analysis Models

During the object-oriented software development process, a variety of models of the system is built. All of these models are not independent; they are related to each other. Elements in one model have trace dependencies to other models; they are semantically overlapping and together represent the system as a whole. It is necessary to have a precise definition of the syntax and semantics of the different models and their relationships since the lack of accuracy in definition can lead to wrong model interpretations and inconsistency between models. In this chapter, we classify relationships between models along three different dimensions and propose a formal description of them. The goal of the proposed formalization is to provide formal foundations for tools that perform intelligent analysis on models thereby assisting software engineers throughout the development process. In this direction, we discuss the construction of a tool based on the formalization and support the verification of traces between requirement and analysis models specified in the Unified Modeling Language.

Reverse Engineering OWL 2 Ontologies to UML Models

2014 ◽  
Vol 644-650 ◽  
pp. 3133-3136
Author(s):  
Wei Jun Li
Keyword(s):  
Semantic Web ◽  
Knowledge Representation ◽  
Reverse Engineering ◽  
Knowledge Engineering ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Web Ontology Language ◽  
Unified Modeling ◽  
Ontology Language ◽  
Uml Models

The OWL 2 Web Ontology Language is an ontology language for the Semantic Web with formally defined meaning and widely used in knowledge representation. The Unified Modeling Language (UML) can be applied for many of software, knowledge engineering and data modeling. For the sake of reusing the OWL 2 ontologies, we propose a reverse engineering approach of constructing UML models from OWL 2 ontologies. In this paper, we propose formalized definitions of OWL 2 ontologies and UML models, and then propose an approach of formally mapping OWL 2 ontologies to UML models.

scholarly journals RANCANG BANGUN SISTEM ANTREAN MULTI FUNGSI DENGAN MENGGUNAKAN CREDIT CARD-SIZED COMPUTER UNTUK PENDAFTARAN MAHASISWA BARU

Transmisi ◽  
2018 ◽  
Vol 20 (2) ◽  
pp. 79
Author(s):  
Sadr Lufti Mufreni
Keyword(s):  
Credit Card ◽  
Process Model ◽  
Software Process ◽  
Unified Modeling Language ◽  
Raspberry Pi ◽  
Modeling Language ◽  
Input Output ◽  
Unified Modeling ◽  
Waterfall Model

Universitas ‘Aisyiyah Yogyakarta menerima mahasiswa baru setiap tahun. Jumlah mahasiswa baru mengalami peningkatan dari tahun ke tahun. Pada tahun 2017 mahasiswa yang mendaftar berjumlah 18.000 dengan jumlah yang diterima sebesar 1829. Melihat pendaftar yang banyak diperlukan sistem informasi antrean yang mumpuni. Selain mumpuni, sistem dapat dimodifikasi untuk keperluan antrean kegiatan lainnya. Karena rancang bangun perangkat lunak sistem ini dibuat pertama kali maka pemilihan metode waterfall model sebagai software process model sangat tepat. Di samping metode yang tepat, penggunaan bahasa analisa Unified Modeling Language(UML) sebagai bahasa analisa standar membantu dalam pembuatan dokumentasi, spesifikasi, dan analisa sistem. Penelitian sistem antrean yang sudah ada menggunakan komputer dan beberapa perangkat tambahan. Perangkat tambahan diperlukan untuk menghubungkan antara komputer dengan tombol-tombol pada mesin antrean. Untuk mengurangi biaya, teknologi Raspberry Pi dipilih karena mempunyai kemampuan dasar layaknya komputer pribadi ditambah fasilitas general input output pin. Komputer mini seukuran kartu kredit, Raspberry Pi, harganya relatif lebih murah daripada komputer pribadi dan adanya tambahan fasilitas pin diharapkan biaya yang diperlukan dapat ditekan. Hasil penelitian ini diharapkan dapat membantu proses penerimaan mahasiswa baru sehingga pihak Universitas dapat memberikan layanan yang prima untuk calon mahasiswanya. Selain itu biaya pengadaan komputer untuk sistem antrean dapat ditekan seminimal mungkin. Dengan sedikit modifikasi, hasil rancang bangun sistem dapat digunakan untuk kegiatan antrean lainnya seperti sistem antrean pendaftaran pasien di rumah sakit. Diharapkan dengan kemudahan modifikasi, penelitian ini bisa dijadikan langkah pertama untuk pembuatan Sistem Informasi Kesehatan yang ingin diwujudkan oleh Universitas ‘Aisyiyah Yogyakarta.

Sign in / Sign up

Export Citation Format

Share Document