| The TaskJuggler Manual | ||
|---|---|---|
| Prev | Chapter 7. Property Reference | Next |
id>
<name>scenario
<id>
<name>
| |||
|---|---|---|---|
| Description | Specifies the different project scenarios. A scenario that is nested into another one inherits all inheritable values from the enclosing scenario. There can only be one top-level scenario. It is usually called plan scenario. By default this scenario is pre-defined but can be overwritten with any other scenario. In this documenation each attribute is listed as scenario specific or not. A scenario specific attribute can be overwritten in a child scenario thereby creating a new, slightly different variant of the parent scenario. This can be helpful to do plan/actual comparisons if what-if-anlysises. By using bookings and enabling the projection mode you can capture the progress of your project and constantly get updated project plans for the future work. | ||
| Attributes | Name | Type | Description |
id | ID | ||
name | STRING | ||
| Optional Attributes | baseline, disabled, enabled, maxpaths, minslackrate, projection, scenario | ||
| Context | project, scenario, | ||
| Inheritable | No | Scenario Spec. | No |
| See also | scenarios | ||
project prj "Example" "1.0" 2005-05-29 - 2005-07-01 {
scenario plan "Planned Scenario" {
scenario actual "Actual Scenario"
scenario test "Test Scenario" {
disabled
}
}
}
task t "Task" {
start 2005-05-29
actual:start 2005-06-03
test:start 2005-06-07
}