Fuzzy Information Modeling with the UML

2011 ◽  
pp. 153-176 ◽  
Author(s):  
Zongmin Ma
Keyword(s):  
Knowledge Engineering ◽  
Unified Modeling Language ◽  
Data Modeling ◽  
Data Models ◽  
Information Modeling ◽  
Fuzzy Information ◽  
Unified Modeling ◽  
Management Group ◽  
Conceptual Data ◽  
Design Databases

Computer applications in nontraditional areas have put requirements on conceptual data modeling. Some conceptual data models, being the tool of design databases, were proposed. However, information in real-world applications is often vague or ambiguous. Currently, less research has been done in modeling imprecision and uncertainty in conceptual data models. The UML (Unified Modeling Language) is a set of object-oriented modeling notations and is a standard of the Object Data Management Group (ODMG). It can be applied in many areas of software engineering and knowledge engineering. Increasingly, the UML is being applied to data modeling. In this chapter, different levels of fuzziness are introduced into the class of the UML and the corresponding graphical representations are given. The class diagrams of the UML can hereby model fuzzy information.

Modeling Imprecise and Uncertain Engineering Information in EXPRESS-G and Relational Data Models

2005 ◽  
Author(s):  
Z. M. Ma
Keyword(s):  
Systems Engineering ◽  
Manufacturing Systems ◽  
Data Modeling ◽  
Database Systems ◽  
Data Models ◽  
Information Modeling ◽  
Uncertain Information ◽  
Engineering Applications ◽  
Engineering Information ◽  
Conceptual Data

Computer-based information systems have become the nerve center of current manufacturing systems. Engineering information modeling in databases is thus essential. However, information imprecision and uncertainty extensively arise in engineering design and manufacturing. So contemporary engineering applications have put a requirement on imprecise and uncertain information modeling. Viewed from database systems, engineering information modeling can be identified at two levels: conceptual data modeling and logical database modeling and correspondingly we have conceptual data models and logical database models, respectively. In this paper, we first investigate information imprecision and uncertainty in engineering applications. Then EXPRESS-G, which is a graphical modeling tool of EXPRESS for conceptual data modeling of engineering information, and nested relational databases are extended based on possibility distribution theory, respectively, in order to model imprecise and uncertain engineering information. The formal methods to mapping fuzzy EXPRESS-G schema to fuzzy relational schema are developed.

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.

Information Analysis in UML and ORM

2002 ◽  
pp. 307-323 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Data Modeling ◽  
Object Oriented ◽  
Information Analysis ◽  
Domain Experts ◽  
Unified Modeling ◽  
Data Intensive ◽  
Class Diagrams ◽  
Conceptual Data ◽  
Data Intensive Applications

Since its adoption by the Object Management Group as a language for object-oriented analysis and design, the Unified Modeling Language (UML) has become widely used for designing object-oriented code. However, UML has had only minimal adoption among practitioners for the purposes of information analysis and database design. One main reason for this is that the class diagrams used in UML for data modeling provide only weak, and awkward, 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. These defects can be remedied by using a fact-oriented approach for information analysis, from which UML class diagrams may be derived. Object-Role Modeling (ORM) is currently the most popular fact-oriented modeling approach. This chapter examines the relative strengths and weaknesses of UML and ORM for conceptual data modeling, and indicates how models in one notation can be translated into the other.

METHOD FOR SYNTHESIS OF CONCEPTUAL DATA MODELS BASED ON PROCESS DOMAIN MODELS

2020 ◽  
pp. 80-87
Author(s):  
С.И. Рябухин
Keyword(s):  
Data Modeling ◽  
Database Design ◽  
Data Models ◽  
Process Models ◽  
Domain Models ◽  
Conceptual Data

Процессные модели предметной области широко применяются при проектировании баз данных, а именно в ходе концептуального моделирования данных. Предлагается решение проблемы неоднозначности преобразования процессных доменных моделей типа SADT в концептуальные модели данных. Domain process models are widely used in database design, namely in conceptual data modeling. The solution of the problem of ambiguity of transformation of process domain models of the SADT type into conceptual data models is proposed.

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.

Essential, Mandatory, and Shared Parts in Conceptual Data Models

2010 ◽  
pp. 17-52 ◽  
Author(s):  
Alessandro Artale ◽  
C. Maria Keet
Keyword(s):  
Life Cycle ◽  
Formal Semantics ◽  
Data Modeling ◽  
Data Models ◽  
Modeling Language ◽  
The Novel ◽  
Conceptual Data ◽  
Temporal Modality

This chapter focuses on formally representing life cycle semantics of part-whole relations in conceptual data models by utilizing the temporal modality. The authors approach this by resorting to the temporal conceptual data modeling language ERVT and extend it with the novel notion of status relations. This enables a precise axiomatization of the constraints for essential parts and wholes compared to mandatory parts and wholes, as well as introduction of temporally suspended part-whole relations. To facilitate usage in the conceptual stage, a set of closed questions and decision diagram are proposed. The longterm objectives are to ascertain which type of shareability and which lifetime aspects are possible for part-whole relations, investigate the formal semantics for sharability, and how to model these kind of differences in conceptual data models.

Databases Modeling of Engineering Information

2009 ◽  
pp. 338-361
Author(s):  
Z. M. Ma
Keyword(s):  
Data Storage ◽  
Database Systems ◽  
Data Models ◽  
Information Modeling ◽  
Database Modeling ◽  
Business Applications ◽  
Database Models ◽  
Engineering Information ◽  
Computer Based ◽  
Conceptual Data

Information systems have become the nerve center of current computer-based engineering applications, which hereby put the requirements on engineering information modeling. Databases are designed to support data storage, processing, and retrieval activities related to data management, and database systems are the key to implementing engineering information modeling. It should be noted that, however, the current mainstream databases are mainly used for business applications. Some new engineering requirements challenge today’s database technologies and promote their evolvement. Database modeling can be classified into two levels: conceptual data modeling and logical database modeling. In this chapter, we try to identify the requirements for engineering information modeling and then investigate the satisfactions of current database models to these requirements at two levels: conceptual data models and logical database models. In addition, the relationships among the conceptual data models and the logical database models for engineering information modeling are presented in the chapter viewed from database conceptual design.

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 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.

Sign in / Sign up

Export Citation Format

Share Document