Extended Enterprise Modeling Language: Difference between revisions

Content deleted Content added
m top: bold
cap, punct., simplify headings
Line 16:
The objectives of the UEML Working group were to "define, to validate and to disseminate a set of core language constructs to support a Unified Language for Enterprise Modelling, named UEML, to serve as a basis for interoperability within a smart organisation or a network of enterprises".<ref>[http://www.ist-world.org/ProjectDetails.aspx?ProjectId=072ba8459dce4167a84182c016b32551 Unified Enterprise Modelling Language]. Accessed 29 Nov 2008.</ref>
 
==EEML Topics==
 
===Modeling domains===
Line 26:
Process modeling in EEML, according to Krogstie (2006) "supports the modeling of process logic which is mainly expressed through nested structures of tasks and decision points. The sequencing of the tasks is expressed by the flow relation between decision points. Each task has minimum an input port and an output port being decision points for modeling process logic, Resource roles are used to connect resources of various kinds (persons, organizations, information, material objects, software tools and manual tools) to the tasks. In addition, data modeling (using UML class diagrams), goal modeling and competency modeling (skill requirements and skills possessed) can be integrated with the process models".<ref name="Kro06"/>
 
===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.
* '''Specific Task Type''': At this layer, we deal with process modelling in another scale, which is more linked to the concretisation, decomposition and specialisation phases. Here process models are expanded and elaborated to facilitate business solutions. From an integration viewpoint, this layer aims at uncovering more efficiently the dependencies between the sub-activities, with regards for the resources required for actual performance.
Line 35:
These tasks are tied together through another layer called '''Manage Task Knowledge''' which allows to achieve a global interaction through the different layers by performing a real consistency between them. According to EEML 2005 Guide, this Manage Task Knowledge can be defined as the collection of processes necessary for innovation, dissemination, and exploitation of knowledge in a co-operating ensemble where interact knowledge seekers and knowledge sources by the mean of a shared knowledge base.
 
===Goal Modellingmodelling===
{{further|Goal modeling}}
Goal Modellingmodelling 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 class="center">
Line 59:
 
The relations of these resources can be of different types:
:a. Is Filled By - -this is the assignment relation between roles and resources. It has a cardinality of one-to-many relationship.
:b. Is Candidate For – candidate indicates the possible filling of the role by a resource.
:c. Has Member – this is a kind of relations between organization and person by denoting that a certain person has membership in the organization. Has a cardinality of many-to-many relation.
Line 69:
:i. Has Access to – creating of models with the access rights.
 
==Benefits of using EEML==
From a general point of view, EEML can be used like any other modeling languages in numerous cases. However we can highlight the virtual enterprise example, which can be considered as a direct field of application for EEML with regard to Extended Enterprise planning, operation, and management.
* Knowledge sharing: Create and maintain a shared understanding of the scope and purpose of the enterprise, as well as viewpoints on how to fulfil the purpose.
Line 79:
EEML can help organisations meet these challenges by modeling all the manufacturing and logistics processes in the extended enterprise. This model allows capturing a rich set of relationships between the organization, people, processes and resources of the virtual enterprise.<ref name=eeml5>H.D. Jørgensen (2004) Interactive Process Models. Department of Computer and Information Science Faculty of Information Technology, Mathematics and Electrical Engineering, Norwegian University of Science and Technology. Trondheim, Norway</ref> It also aims at making people understand, communicate, develop and cultivate solutions to business problems<ref name=eeml6>R. Matulevičius and P. Heymans (2007) Visually Effective Goal Models Using KAOS. PReCISE Research Center, Computer Science Department, University of Namur, rue Grandgagnage 21,5000 Namur, Belgium.</ref>
 
According to J. krogstieKrogstie (2008), Enterpriseenterprise Modelsmodels can be created to serve various purposes which include:
 
# Human sense making and communication -the main purpose of enterprise modeling is to make sense of the real world aspects of an enterprise in order to facilitate communicate with parties involved.
# Computer assisted analysis - the main purpose of enterprise modeling is to gain knowledge about the enterprise through simulation and computation of various parameters.
# Model deployment and activation - the main purpose of enterprise modeling is to integrate the model in an enterprise-wide information system and enabling on-line information retrieval and direct work process guidance.
 
EEML enables Extended Enterprises to build up their operation based on standard processes through allowing modeling of all actors, processes and tasks in the Extended Enterprise and thereby have clear description of the Extended Enterprise. Finally, models developed will be used to measure and evaluate the Extended Enterprise.