Finance:Extended Enterprise Modeling Language

From HandWiki
Revision as of 05:13, 6 March 2023 by John Stpola (talk | contribs) (linkage)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Example of EEML Goal modeling and process modeling.

Extended Enterprise Modeling Language (EEML) in software engineering is a modelling language used for Enterprise modelling across a number of layers.

Overview

Extended Enterprise Modeling Language (EEML) is a modelling language which combines structural modelling, business process modelling, goal modelling with goal hierarchies and resource modelling. It was intended to bridge the gap between goal modelling and other modelling approaches. According to Johannesson and Söderström (2008) "the process logic in EEML is mainly expressed through nested structures of tasks and decision points. The sequencing of tasks is expressed by the flow relation between decision points. Each task has an input port and the output port being decision points for modeling process logic".[1]

EEML was designed as a simple language, making it easy to update models. In addition to capturing tasks and their interdependencies, models show which roles perform each task, and the tools, services and information they apply.

History

Extended Enterprise Modeling Language (EEML) is from the late 1990s, developed in the EU project EXTERNAL as extension of the Action Port Model (APM) by S. Carlsen (1998).[2] The EXTERNAL project [3] aimed to "facilitate inter-organisational cooperation in knowledge intensive industries. The project worked on the hypothesis that interactive process models form a suitable framework for tools and methodologies for dynamically networked organisations. In the project EEML (Extended Enterprise Modelling Language) was first constructed as a common metamodel, designed to enable syntactic and semantic interoperability".[4]

It was further developed in the EU projects Unified Enterprise Modelling Language (UEML)[5] from 2002 to 2003 and the ongoing ATHENA project.[6]

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".[7]

Topics

Modeling domains

The EEML-language is divided into 4 sub-languages, with well-defined links across these languages:[8]

  • Process modelling
  • Data modelling
  • Resource modelling
  • Goal modelling

Process modelling 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, organisations, 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".[8]

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.
  • Manage Task Instances: The purpose of this layer consists in providing constraints but also useful resources (in the form of process templates) to the planning and performance of an enterprise process. The performance of organisational, information, and tool resources in their environment are highlighted through concrete resources allocation management.
  • Perform Task Instances: Here is covered the actual execution of tasks with regards to issues of empowerment and decentralisation. At this layer, resources are utilised or consumed in an exclusive or shared manner.

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 means of a shared knowledge base.

Goal modelling

Further information: Goal modeling

Goal modelling is one of the four EEML modelling 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.

  • Goal modeling in EEML

  • Connecting relationships

  • Goal modeling and process modeling

In goal modelling 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 indicates different types of connecting relationships in EEML goal modelling. Goal model can also be interlinked with a process model.

Goal and process oriented modelling

We can describe process model as models that comprise a set of activities and an activity can be decomposed into sub-activities.[9] These activities have relationship amongst themselves. A goal describes the expected state of operation in a business enterprise and it can be linked to whole process model or to a process model fragment with each level activity in a process model can be considered as a goal.[9]

Goals are related in a hierarchical format where you find some goals are dependent on other sub goals for them to be complete which means all the sub goals must be achieved for the main goal to be achieved. There is other goals where only one of the goals need to be fulfilled for the main goal to be achieved. In goal modelling, there is use of deontic operator which falls in between the context and achieved state.[10] Goals apply to tasks, milestones, resource roles and resources as well and can be considered as action rule for at task. EEML rules were also possible to although the goal modelling requires much more consultation in finding the connections between rules on the different levels.[11] Goal-oriented analysis focuses on the description and evaluation of alternatives and their relationship to the organisational objectives.[12]

Resource modeling

Resources have specific roles during the execution of various processes in an organisation. The following icons represent the various resources required in modelling.

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 organisation and person by denoting that a certain person has membership in the organisation. Has a cardinality of many-to-many relation.
d. Provide Support To – support pattern between resources and roles.
e. Communicates With – Communication pattern between resources and roles.
f. Has Supervision Over – shows which role resource supervises another role or resource.
g. Is Rating Of – describes the relation between skill and a person or organisation.
h. Is required By – this is the primary skill required for this role
i. Has Access to – creating of models with the access rights.

Benefits

From a general point of view, EEML can be used like any other modelling 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.
  • Dynamically networked organisations: Make knowledge as available as possible within the organisation.
  • Heterogeneous infrastructures: Achieve a relevant knowledge sharing process through heterogeneous infrastructures.
  • Process knowledge management: Integrate the different business processes levels of abstraction.
  • Motivation: creates enthusiasm and commitment among members of an organisation to follow up on the various actions that are necessary to restructure the enterprise.

EEML can help organisations meet these challenges by modelling all the manufacturing and logistics processes in the extended enterprise. This model allows capturing a rich set of relationships between the organisation, people, processes and resources of the virtual enterprise.[13] It also aims at making people understand, communicate, develop and cultivate solutions to business problems[14]

According to J. Krogstie (2008), enterprise models can be created to serve various purposes which include:

  1. Human sense making and communication – the main purpose of enterprise modelling is to make sense of the real world aspects of an enterprise in order to facilitate communicate with parties involved.
  2. Computer assisted analysis – the main purpose of enterprise modelling is to gain knowledge about the enterprise through simulation and computation of various parameters.
  3. Model deployment and activation – the main purpose of enterprise modelling 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 modelling 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.

See also

References

  1. ↑ Paul Johannesson and Eva Söderström (2008) .Information Systems Engineering. p.58-61.
  2. ↑ Carlsen, S. (1998). "Action port model: A mixed paradigm conceptual workflow modeling language". In: Proceedings of Third IFCIS Conference on Cooperative Information Systems (CoopIS'98), New York.
  3. ↑ EXTERNAL EXTERNAL - Extended Enterprise Resources, Networks And Learning, EU Project, IST-1999-10091,
  4. ↑ Håvard D. Jørgensen (2004). Interactive Process Models . Thesis Norwegian University of Science and Technology Trondheim, Norway. p.173-202.
  5. ↑ François Vernadat (2002). "UEML: towards a unified enterprise modelling language". In: Int. J. Production Research, 40 (17), 4309-4321.
  6. ↑ John Krogstie and T.A. Halpin, Keng Siau (2004). Information Modeling Methods and Methodologies. Idea Group Inc (IGI), p.73.
  7. ↑ Unified Enterprise Modelling Language. Accessed 29 Nov 2008.
  8. ↑ 8.0 8.1 John Krogstie (2006). " Using EEML for Combined Goal and Process Oriented Modeling: A Case Study".
  9. ↑ 9.0 9.1 Yun Lin and Arne Sølvberg Goal Annotation of Process Models for Semantic Enrichment of Process Knowledge
  10. ↑ J. Krogstie (2005) EEML2005: EXTENDED ENTERPRISE MODELING LANGUAGE
  11. ↑ John Krogstie (2008) Using EEML for Combined Goal and Process Oriented Modeling: A Case Study. IDI, NTNU,Trondheim, Norway. Proceedings of EMMSAD 2008.
  12. ↑ Mylopoulos, Chung, and Yu (1999) : “From Object-oriented to Goal-oriented Requirements Analysis”. Communications of the ACM, January
  13. ↑ 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
  14. ↑ 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.

Further reading

  • Bolchini, D., Paolini, P.: "Goal-Driven Requirements Analysis for Hypermedia-intensive Web Applications", Requirements Engineering Journal, Springer, RE03 Special Issue (9) 2004: 85-103.
  • Jørgensen, Håvard D.: "Process-Integrated eLearning"
  • Kramberg, V.: "Goal-oriented Business Processes with WS-BPEL"[yes|permanent dead link|dead link}}], Master Thesis, University of Stuttgart, 2008.
  • John Krogstie (2005). EEML2005: Extended Enterprise Modeling Language
  • John Krogstie (2001). "A Semiotic Approach to Quality in Requirements Specifications" (Proc. IFIP 8.1) IFIP 8.1. Working Conference on Organizational Semiotics.
  • Lin Liu, Eric Yu. "Designing information systems in social context: a goal and scenario modelling approach"

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Finance:Extended_Enterprise_Modeling_Language&oldid=2591016"