This open version of the Guide Wiki Page displays the guideline as per the i* Style of the University of Toronto. Use Comment tab above to read or write comments about this guideline. Scroll down to see variations of this guideline for other i* modeling styles.
4.3.2 Task Dependency
In a task dependency, the depender depends on the dependee to carry out an activity. The dependum names a task which specifies how the task is to be performed, but not why. The depender has already made decisions about how the task is to be performed. Note that a task description in i* is not meant to be a complete specification of the steps required to execute the task. It is a constraint imposed by the depender on the dependee. The dependee still has freedom of action within these constraints.
Return to the stable version of this page
Instructions for Guideline authors/contributors
Below is the space designated to post possible variations. Please do not edit or alter the original guideline above.
Please provide the following information for each variation:
1. Name of Modeling Framework/School/Location/Research Group
2. Variation and explanation
3. Example(s)
Learn how to upload and use an image in the wiki page
You can use the Comment tab to post additional comments about this guideline or its variations outside this space. The Comment tab displays your comments at the bottom of this page. (Do not use the Discuss tab).
Variation: RESCUE Methodology
In the RESCUE Methodology, users are encoraged to expand or investigate task dependencies, with the goal of eventually replacing all tasks dependencies with goal or softgoal dependencies. The idea is that an SD model, which contains dependencies and dependums, should depict the "why" of why actors are depending on other actors, not "what" they are depending on them to do. So if a task dependency exists, modellers should ask "why is that task needed" and replace the dependency with the motivating goal.
Return to the stable version of this page