Example of EEML Goal modeling and process modeling.

Overview

Extended Enterprise Modeling Language (EEML) is modelling language, which combines structural modeling, process modeling, goal modeling with goal hierarchies, and resource modeling. It is used in practice to bridge the type of goal modeling used in common requirements engineering to other modeling approaches. 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 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.

History

Extended Enterprise Modeling Language (EEML) is end 1990s developed in the EU project EXTERNAL as extention 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. It is the hypotheses of the project 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 has been further developed in the EU projects Unified Enterprise Modelling Language (EUML) from 2002 to 2003 and the ongoing ATHENA project.^[5] The objectives of UEML Working group has been 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.^[6]

EEML Topics

Modeling domains

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

• Process modeling
• Data modeling
• Resource modeling
• Goal modeling

Process modeling 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.^[7]

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: In this layer process models are expanded, concretised, decomposed and specialised to facilitate business solutions.
• Manage Task Instances: Here, more detailed decisions are taken regarding work in the actual work environment with its organisational, information, and tool resources.
• Perform Task Instances: 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.

Goal modelling principles

Within requirements engineering (RE), the notion of goal has increasingly been used. Goals generally describe objectives which a system should achieve through cooperation of actors in the intended software and in the environment ^[8]. Goals are central in some RE frameworks, and can play a supporting role in others. Goal-oriented techniques may particularly be useful in early-phase RE. Early-phase requirements consider e.g. how the intended system meets organizational goals, why the system is needed and how the stakeholders? interests may be addressed. ^[9]

• Expresses the relationships between systems and their environments : Earlier, requirements engineering focused only on what the system is supposed to do. Over the past years, there has been a more or less mutual understanding, that it is also very important to understand and characterize the interaction between the intended system and its environment. Relationships between systems and their environments are often expressed as goal-based relationships. The motivation for this is ?partly today's more dynamic business and organizational environments, where systems are increasingly used to fundamentally change business processes rather than to automate long-established practices?.^[10] Goals can also be useful when modelling contexts. ^[11]

• Clarifies requirements : Specifying goals leads to asking ?why?, ?how? and ?how else?. ^[12] Requirements of the stakeholders are often revealed in this process. The stakeholders may seem to be more likely to become aware of potential alternatives for fulfilling their goals, and thereby less likely to over-specify their requirements. Requirements from clients and stakeholders may often be unclear, especially the non-functional ones. A goal-oriented approach allows the requirements to be refined and clarified through an incremental process, by analyzing requirements in terms of goal decomposition.

• Deals with conflicts : Goals may provide a useful way of dealing with conflicts, such as tradeoffs between costs performance, flexibility, etc, and divergent interests of the stakeholders. Goals can deal with conflicts because meeting of one goal can interfere with the meeting of others. Different opinions on how to meet a goal has led to different ways of handling conflicts. ^[13]

• Decides requirements completeness : Requirements can be considered complete if they fulfil explicit goals in the requirement model.

• Connects requirements to design : Goals can be used in order to connect the requirements to the design. For some, goals are an important mechanism in this matter. (The Non-Functional Requirements (NFR) framework uses goals to guide the design process.)

Goal-oriented Requirements Language

Goal-oriented Requirements Language (GRL) is a language that is designed to support goal-oriented modeling and reasoning about requirements, especially the non-functional requirements [1]. It allows to express conflict between goals and helps to make decisions that resolve conflicts. There are three main categories of concepts in GRL: intentional elements, intentional relationships and actors [2]. They are called for intentional because they are used in models that primarily concerned with answering "why" question of requirements (for ex. why certain choices for behavior or structure were made, what alternatives exist and what is the reason for choosing of certain alternative.)

GRL Notation

Intentional elements

Intentional elements are: goal, soft goal, task, belief and resource.

• Goal is condition or situation that can be achieved or not. Goal is used to define the functional requirements of the system. In GRL notation goal is represented by a rounded rectangle with the goal name inside.
• Task is used to represent different ways of how to accomplish goal. In GRL notation task is represented by hexagon with the task name inside.
• Softgoal is used to define non-functional requirements. It?s usually a quality attribute of one of the intentional elements. In GRL notation softgoal is represented by irregular curvilinear shape with the softgoal name inside.
• Resource is a physical or informational object that is available for use in the task. Resource is represented in GRL as a rectangle.
• Belief is used to represent assumptions and relevant conditions. This construct is represented as ellipse in GRL notation.
• Actor is an active object that carries out actions to achieve the goal. In GRL notation actor is represented as a circle with the actor name inside.
• Agent is a concrete actor, such as a human individual or machine.

GRL relationships

Relationships

Intentional relationships are: means-ends, decomposition, contribution, correlation and dependency.

• Means-ends relationship shows how the goal can be achieved. For example it can be used to connect task to a goal.
• Decomposition relationship is used to show the sub-components of a task.
• Contribution relationship describes how one element influence another one.
• Correlation relationship describes side effects of existence of one element to others.
• Dependency relationship describe interdependences between agents.

See also

• Enterprise modelling
• i*
• Modeling language
• Semantic parameterization
• Software design
• Software development methodology

References

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", Master Thesis, University of Stuttgart, 2008.
• John Krogstie, EEML2005: Extended Enterprise Modeling Language
• John Krogstie. "A Semiotic Approach to Quality in Requirements Specifications" (Proc. IFIP 8.1)
• Lin Liu, Eric Yu. "Designing information systems in social context: a goal and scenario modelling approach"

External links

• Description of EEML
• GRL web site University of Toronto,
• "The Business Motivation Model Business Governance in a Volatile World", Relase 1.3, Business Rules Group, 2007.

---

Source: Wikipedia | The above article is available under the GNU FDL. | Edit this article