Extended Enterprise Modeling Language: Difference between revisions

Revision as of 14:27, 12 August 2008

Revision as of 23:54, 4 November 2008

Line 1:

'''Extended Enterprise Modeling Language''' ('''EEML''') is commonly used for [[business process modeling]] across a number of layers. '''EEML''' is intended to be a simple language, which makes it easy to update models. In addition to capturing the various tasks(can consist of several sub-tasks) and their interdependencies, models show which roles perform each task, and the tools, services and information they apply.

'''EEML''' is the result of several years of research. Originally developed in <ref>[http://research.dnv.com/external/default.htm EXTERNAL]</ref> to support development and use of interactive models.

==History==

'''EEML''' is the result of several years of research. Originally developed in [http://research.dnv.com/external/default.htm EXTERNAL] to support development and use of interactive models.

== EEML Topics ==

==Different= modelingModeling domains===

The modeling language currently includes four modeling domains, in addition to general modeling mechanisms and primitives provided in [[Metis (modelling)]]

*Process modeling

Line 12:

*Goal modeling

**The modeling of goal and rule structures in an organisation

**See [[Goal Modelling]], [[Goal modeling in EEML]]

*Data modeling (UML Class Diagram)

**See [[Unified Modeling Language]]

=== EEML Layers ===

'''EEML''' has four layers of interest

*Generic Task Type

**This layer identifies the constituent tasks of generic, repetitive processes and the logical dependencies between these tasks.

Line 27:

**This layer covers the actual execution of tasks.

=== Goal Modelling ===

Goal Modelling is one of the four EEML modeling domains age. A goal expresses the wanted (or unwanted) state of affairs (either current or future) in a certain context. Example of the goal model is depicted below. It shows goals and relationships between them. It is possible to model advanced goal-relationships in EEML by using goal connectors. A goal connector is used when one need to link several goals.

<gallery>

Image:Eemlgoal.JPG|Goal modeling in EEML

Image:Tabell.gif|Connecting relationships

Image:Goalandprocess.JPG|Goal modeling and process modeling

</gallery>

In goal modeling to fulfil Goal1, one must achieve to other goals: both Goal2 and Goal3 (goal-connector with “and” as the logical relation going out). If Goal2 and Goal3 are two different ways of achieving Goal1, then it should be “xor” logical relationship. It can be an opposite situation when both Goal2 and Goal3 need to be fulfilled and to achieve them one must fulfil Goal1. In this case Goal2 and Goal3 are linked to goal connector and this goal connector has a link to Goal1 with ”and”-logical relationship.

The table indicate different types of connecting relationships in EEML goal modeling. Goal model can also be interlinked with a process model.

==References==

{{reflist}}

[http://www.idi.ntnu.no/emner/tdt4250/pensum/EEML2005-autumn2005.doc Description of EEML]

== Further reading ==

* Jørgensen, Håvard D.: "Process-Integrated eLearning"

* John Krogstie, EEML2005: Extended Enterprise Modeling Language

* John Krogstie, John: "A Semiotic Approach to Quality in Requirements Specifications" (Proc. IFIP 8.1)

== External links ==

* [http://www.idi.ntnu.no/emner/tdt4250/pensum/EEML2005-autumn2005.doc Description of EEML]

Krogstie, John: "A Semiotic Approach to Quality in Requirements Specifications" (Proc. IFIP 8.1)

Jørgensen, Håvard D.: "Process-Integrated eLearning"

[[Category:Business models]]