Content deleted Content added
Wikification - a start + Goal modeling in EEML merged here |
Wikification some more + merged Goal-oriented Requirements Language here |
||
Line 6:
=== Modeling domains===
The modeling language currently includes four modeling domains, in addition to general modeling mechanisms and primitives provided in [[Metis (modelling)]]
*
*
▲** Process logic is modeled through nested structures of tasks and decision points.
* Data modeling (UML Class Diagram), which uses [[Unified Modeling Language]]▼
▲**Roles are used to connect resources of various kinds (people, organisations, information, and tools) to the tasks.
▲**The modeling of goal and rule structures in an organisation
▲*Data modeling (UML Class Diagram)
=== EEML Layers ===
EEML has four layers of interest
*
*
▲**This layer identifies the constituent tasks of generic, repetitive processes and the logical dependencies between these tasks.
*
▲**In this layer process models are expanded, concretised, decomposed and specialised to facilitate business solutions.
▲**Here, more detailed decisions are taken regarding work in the actual work environment with its organisational, information, and tool resources.
▲**This layer covers the actual execution of tasks.
=== Goal Modelling ===
Line 39 ⟶ 30:
The table indicate different types of connecting relationships in EEML goal modeling. Goal model can also be interlinked with a process model.
=== 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.)
[[Image:GRL_legend.GIF|thumb|320px|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.
[[Image:GRL_relationships.GIF|thumb|320px|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.
==References==
{{reflist}}
Line 47 ⟶ 62:
* 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 ==
* [http://www.idi.ntnu.no/emner/tdt4250/pensum/EEML2005-autumn2005.doc Description of EEML]
* [http://www.cs.toronto.edu/km/GRL/ GRL web site] University of Toronto,
[[Category:Business models]]
| |||