1 / 15

UEML

UEML. Agenda. Why UEML is needed? UEML Overview. Common Enterprise Models.

chastity-battle
Download Presentation

UEML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UEML

  2. Agenda • Why UEML is needed? • UEML Overview

  3. Common Enterprise Models Ref.:TheUnified Enterprise Modelling Language Overview and Further Work-Victor Anaya, Giuseppe Berio, MouniraHarzallah, Patrick Heymans, RaimundasMatulevičius, Andreas L. Opdahl, HervéPanettoand Maria Jose Verdecho

  4. Somewell-known EM techniques • Data Flow Diagrams: SSAD, Yourdon, De Marco, … • Entity-relationship methods: MERISE, NIAM, M*, T-SER, … • SADT • IDEF suite of methods: IDEF0, IDEF1x and IDEF3 • GRAI nets • OMT and UML • CIMOSA • IEM • ARIS method • SA / RT • Harel'sStatecharts • Activity-BasedCostingmethods

  5. Somewell-known EM tools • ARIS ToolSet • FirstSTEP • KBSI suite • NCR Metis • PrimeObjects • Bonapart • CimTool • … • Worfklowsystems (WorkParty, IBM FlowMark, IBM VisualAge, Action Workflow, COSA, Ensemble, …)

  6. Issues • Too many EM languages • Unstable vocabulary and modelling paradigms • Many incompatible EM tools / weak process interoperation -> UEML

  7. What is UEML intended to be • Not the ultimate EM language to replace all previous ones • But a standard meta-model(and underlying ontologies) widely accepted by business users and tool developers • Easy to learn and to use with sufficient descriptiveapabilities • Consensus in the EM community • Provide a uniform interface to enterprise modellingtools and a neutral format for exchange of enterprise models

  8. UEML’s Vision:

  9. UEML Principles • Not propose a new language, integrate existing ones • Prioritise industrial languages, allow academic ones • Allow UEML to continue to grow • Allow local tailoring/adaption of UEML • Separation of syntax from semantics • Both ontological and mathematical semantics • Provide 'semantic' (or referential) integration through a common ontology

  10. UEML comprises:

  11. UEML Language Description Structure

  12. Language and Construct Description

  13. Separation of Reference • What a modelling construct is intended to represent is described in terms of: • The classes it is intended to represent • The properties it is intended to represent, if any • The states it is intended to represent, if any • The events it is intended to represent, if any • The instantiation levels it is intended to represent: • Classes, instances or either • The modality it is intended to represent: • Does it assert facts or express beliefs, knowledge, intentions etc. • The classes, properties, states and events are mapped onto the common UEML ontology

  14. The UEML Meta-Meta Model

  15. The Common UEML Ontology • Four interrelated taxonomies: • Class specialisation • Property precedence • State and transformation specialisation • The hierarchies are interrelated • The concepts are attributed

More Related