Generic vs. Domain-specific Modeling Languages

Similar documents
Meta-Modeling and Modeling Languages

Enterprise Architecture Modelling with ArchiMate 3 - Overview

ArchiMate symbols for relating system elements

ArchiMate 2.0. Structural Concepts Behavioral Concepts Informational Concepts. Business. Application. Technology

TOGAF The Open Group Architecture Framework

Modelling in Enterprise Architecture. MSc Business Information Systems

What is a Data Model?

HPE Enterprise Maps Data Model, ArchiMate, TOGAF. HPE Software, Cloud and Automation

Relations: Data and Organisation Models

Business Architecture Implementation

Hippo Software BPMN and UML Training

ArchiMate 2.0. A Step Towards A Common Language. Michelle van den Berg EA Consultant. 44 Montgomery Street Suite 960 San Francisco, CA USA

Enterprise Architecture Views and Viewpoints in ArchiMate - Reference

ArchiMate Trick or Treat?

Enterprise Architecture Frameworks

Chapter 8: Enhanced ER Model

INF5120 and INF9120 Modelbased System development

Enterprise Architect Training Courses


Chapter 6: Entity-Relationship Model

Enterprise Architecture Views and Viewpoints in ArchiMate

UML: Unified Modeling Language

Chapter 6: Entity-Relationship Model

Process modeling. PV207 Business Process Management

Introduction to UML. Danang Wahyu utomo

ArchiMate

Enterprise Architecture Frameworks

Alignment of Business and IT - ArchiMate. Dr. Barbara Re

COSC 3351 Software Design. An Introduction to UML (I)

Enterprise Architecture

Chapter 2: Entity-Relationship Model

A new Action Rule Syntax for DEmo MOdels Based Automatic workflow process generation (DEMOBAKER) Carlos Figueira and David Aveiro

A database can be modeled as: + a collection of entities, + a set of relationships among entities.

Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys

Enterprise Architect. User Guide Series. Domain Models

Chapter 2: Entity-Relationship Model. Entity Sets. Entity Sets customer and loan. Attributes. Relationship Sets. A database can be modeled as:

SABSA Security Architecture Extension

SABSA Security Architecture Extension

Strategy & Architecture Framework. Modeling Language Alain De Preter - All rights reserved - Tous droits réservés

6.1 RELATIONSHIP CONCEPTS

Chapter 6: Entity-Relationship Model. The Next Step: Designing DB Schema. Identifying Entities and their Attributes. The E-R Model.

Final Exam. Final Exam Review. Ch 1: Introduction: Object-oriented analysis, design, implementation. Exam Format

Credit where Credit is Due. Goals for this Lecture. Introduction to Design

The Next Step: Designing DB Schema. Chapter 6: Entity-Relationship Model. The E-R Model. Identifying Entities and their Attributes.

E-R Diagram. Bagian I Entity Concept

Chapter 6: Entity-Relationship Model

MDSE USE CASES. Chapter #3

LOG8430: Architecture logicielle et conception avancée

Data Warehouse and Data Mining

Reasoning on semantically annotated processes

The three element types, connected by relations, can form sentences of sorts.

Copyright 2016 Ramez Elmasri and Shamkant B. Navathe

Architecture and the UML

IS 0020 Program Design and Software Tools

OMG Specifications for Enterprise Interoperability

DATABASE DESIGN I - 1DL300

Business Process Modelling

COMP102: Introduction to Databases, 9.1

Unified Modeling Language (UML)

ISO compliant verification of functional requirements in the model-based software development process

06. Analysis Modeling

Chapter 8 The Enhanced Entity- Relationship (EER) Model

Defining Classes and Methods

Chapter 7: Entity-Relationship Model

Lecture 14 of 42. E-R Diagrams, UML Notes: PS3 Notes, E-R Design. Thursday, 15 Feb 2007

Object-Oriented Software Engineering Practical Software Development using UML and Java

a paradigm for the Introduction to Semantic Web Semantic Web Angelica Lo Duca IIT-CNR Linked Open Data:

Lecture 2: Entity Relationship Data Model 2. 1

Chapter 7: Entity-Relationship Model

Intro to DB CHAPTER 6

COMP102: Introduction to Databases, 13

BSIF. A Freeware Framework for. Integrated Business Solutions Modeling. Using. Sparx Systems. Enterprise Architect

Introduction to Data Management. Lecture #3 (Conceptual DB Design) Instructor: Chen Li

OMG Systems Modeling Language Tutorial May, 2012

INF5120 Modelbased System development

Delivering Enterprise Architecture with TOGAF and ArchiMate

Course 3 7 March

DATABASE DESIGN I - 1DL300

Lecture 09. Spring 2018 Borough of Manhattan Community College

Business Process Modeling with BPMN

Chapter 7: Entity-Relationship Model

Relational Model. Course A7B36DBS: Database Systems. Lecture 02: Martin Svoboda Irena Holubová Tomáš Skopal

MSO Analysis & UML. Hans Philippi (based on the course slides of Wouter Swierstra) August 24, Analysis & UML 1 / 56

High Level Database Models

Requirements & Domain Models. Lecture 13: Object Oriented Modelling. Nearly anything can be an object. Object Oriented Analysis

Relational Model. Courses B0B36DBS, A4B33DS, A7B36DBS: Database Systems. Lecture 02: Martin Svoboda

Metamodeling with Metamodels. Using. UML/MOF including OCL

The ERA of Enterprise Architecture 2.0

Ontologies & Business Process modeling languages: two proposals for a fruitful pairing

Enterprise Architect basic usage

Analysis of BPMN Models

Introduction to UML What is UML? Motivations for UML Types of UML diagrams UML syntax Descriptions of the various diagram types Rational Rose (IBM.. M

Christian Doppler Laboratory

INF5120 Modellbasert Systemutvikling Modelbased System development

OBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization

BIM Standardization in ISO

The Open Group SOA Ontology Technical Standard. Clive Hatton

1 Executive Overview The Benefits and Objectives of BPDM

Modeling ITIL Business Motivation Model in ArchiMate

Enhanced Entity-Relationship (EER) Modeling

Transcription:

Generic vs. Domain-specific Modeling Languages Knut Hinkelmann

Generic vs. Domain-specific Modeling Languages Domain-specific languages are notation which are defined to model knowledge about a specific domain Generic modeling languages can be used to represent any kind of knowledge Generic and Domain-specific Modeling Languages 2

Domain-specific Modeling Languages Domain-specific languages have modeling elements for representing concepts and relations of a domain of discourse Examples: BPMN domain-specific language for business processes Modeling elements: task, event, gateway,. relations: sequence flow, message flow, data association, BMM domain-specific language for business motivation Modeling elements: vision, mission, goal, strategy, influencer, relations: judges, channels efforts, ArchiMate domain-specific language for enterprise architectures Modeling elements: process, actor, role, business object, relations: uses, realizes, Generic and Domain-specific Modeling Languages 3

Generic Modeling Languages Generic modeling languages can be used to represent any kind of knowledge There are a wide range of generic modeling languages Natural language allows to express any knowledge Formal languages: Typically a subset of Logic Graphical Notations Generic and Domain-specific Modeling Languages 4

Graphical Diagrams for Generic Modeling Generic graphical modeling languages have been developed in a many difference fields: Artificial Intelligence: Semantic networks, Description Logics Data Modeling: Entity Relationship Diagrams Object-Oriented Programming: UML Class Diagrams Although having different notations these generic modeling languages typically allow to represent objects properties of objects relations between objects constraints (e.g. cardinalities, type restrictions) Generic and Domain-specific Modeling Languages 5

A Semantic Network A Semantic Network consists of nodes and relations. Example: This semantic network about university courses. role study program is part of module lecturer course project dean telesko fills role has name "Rainer Telesko" BPM has ECTS has title 6 EA has ECTS has title 6 hinkelmann has name "Knut Hinkelmann" Business Process Management Enterprise Architecture Generic and Domain-specific Modeling Languages 6

Nodes and Relations in a Semantic Networks subclass-of rope bridge bridge Golden Gate Bridge individual concept general concepts (classes) "Orange" has color It is now common to distinguish different kinds or relations and nodes in a semantic network There are two kinds of nodes: general concepts (also called classes) individual concepts (also called instances) There are different kinds of relationships generalisation ("") between classes (subclass of) between individual and class () aggregation "part-of" relationship associations any other kind of relationship property Properties can be regarded as associations whose value is not node but is of a primitive type (number, string). real object That value of a property does not have relations or properties Generic and Domain-specific Modeling Languages 7

A Semantic Network distinguishing Kinds of Nodes General Concepts role study program lecturer is part of course module subclass of subclass of project Individual Concepts dean fills role hinkelmann telesko BPM EA Properties has name "Knut Hinkelmann" has name "Rainer Telesko" has title Business Process Management 6 has ECTS has title Enterprise Architecture has ECTS 6 Generic and Domain-specific Modeling Languages 8

UML Class Diagrams and Object Diagrams Subsets of UML Class Diagrams and UML Object Diagrams are often used as generic modeling language classes attributes associations (incl. generalisation, aggregation, composition) objects UML Class diagrams where originally designed for modeling in object-oriented programming. This is why they contain operations, which are not relevant for most modeling languages Generic and Domain-specific Modeling Languages 9

The Semantic Network modeled in UML Generic and Domain-specific Modeling Languages 10