Goal modeling: Difference between revisions

Revision as of 18:39, 10 February 2014

Revision as of 22:35, 10 February 2014

Line 33:

* "Strategic Rationale" (SR), analyzing the goals identified on the SD model into subsidiary goals and tasks.

i* shows each role (an actor, agent or position) as a large circle containing the goals, tasks, and resources which that role owns. Ownership in i* means that the role desires the satisfaction of its goals, either for its own benefit or for the benefit of some other role. (A 'role' may actually be an actor, agent or position.) Goals may be accompanied by "Obstaclesobstacles" (negative goals) to be surmounted (note that obstacles in GORE were first introduced by KAOS). Non-functional goals can be modeled as "soft goals" in i*: they are diagrammed as clouds or indented ovals.

[[http://istar.rwth-aachen.de Further information on i*, including guidelines and examples, can be found at the i* wiki.]]

===Goal modeling in KAOS===

{{main|KAOS (software development)}}

The KAOS goal modeling notation provides a way of defining goals and obstacles, underpinned by a formal (mathematical) method of analysis.<ref>van Lamsweerde, 2009.</ref>

===Goal modeling in UML===

Line 63 ⟶ 61:

* [http://www.cs.toronto.edu/km/istar/ i* Official Website, with tutorial and bibliography] - "an agent- and goal-oriented modelling framework"

[* [http://istar.rwth-aachen.de Further information on i*, includingwiki with guidelines and examples, can be found at the i* wiki.]]

* [http://www.objectiver.com/fileadmin/download/documents/KaosTutorial.pdf KAOS tutorial]

* [http://ceur-ws.org/Vol-337/paper9.pdf Using EEML for Combined Goal and Process Oriented Modeling: A Case Study] - John Krogstie