Files
ember-panda/app/templates/manual/project/dunlop.emblem
T

64 lines
4.6 KiB
Plaintext

d-breadcrumbs as |breadcrumb|
breadcrumb.item
= link-to 'Manual' 'manual.index'
breadcrumb.item
= t 'models.project'
breadcrumb.item active=true
= t 'project.dunlop.title'
= page-title 'project.dunlop.title'
h2.ui.dividing.header= t 'models.plural.workflow_group'
p= t 'manual.project.dunlop.workflow_group.text' modelPath='models.workflow_group' modelsPath='models.plural.workflow_group'
h3.ui.block.header= t 'manual.project.dunlop.workflow_group.duration_value.header'
h2.ui.dividing.header= t 'models.plural.workflow_action_definition'
h3.ui.block.header= t 'manual.project.dunlop.workflow_action_definition.action_confirmation.header'
p= t 'manual.project.dunlop.workflow_action_definition.action_confirmation.text'
h2.ui.dividing.header= t 'models.plural.workflow_action_offset'
h3.ui.block.header Offset diagram
p
| The offset diagram is a (digraph) representation of the actions. The direction top to bottom indicates time. This diagram is meant to indicate relative order, so this indication is for
one action relative to the other in time. Different action trees can be at different times and at the same horizontal level.
p The following diagram shows a configuration where B is configured to be 5 days before A (-5) and C 2 days after B
img src="../../assets/manual/action-offsets/non-rooted.png" title="non-rooted"
p
| Since none of these actions has any connection with the intended reference date (X), this tree is non-rooted. This green color is an indication of that.<br> Now lets root action A
to be 1 day before the intended reference date (X).
img src="../../assets/manual/action-offsets/rooted-critical-path.png" title="rooted-critical-path"
p
| The rooted action is indicated in blue, and the actions connected to rooted elements according to the critical path algorithm are indicated by a softer color green then the non-rooted actions.
The critical path indication here means that the configuration of action B being 5 days before A (-5) is located on action B. In other words, on the action having the longest path distance
to the X-rooted action. So the fact that action C is soft green indicates that the configuration of it being 2 days after B is located on action C.
p Another assumption for an action to belong to the critical path solution is that all actions at the other end of the connections configured in that action are also critical path actions.
p
| Configuring action B to be 2 days before C (-2) instead of C being 2 days after B will break the critical path assumption. Action C will be not connected to any other action, so being a
non-rooted tree in itself and action B will have a connection to this non-rooted tree (consisting only of 1 action in this case).
img src="../../assets/manual/action-offsets/rooted-non-critical-path.png" title="rooted-critical-path"
p The C action in this case also is a non critical path connection since it's connection with B is defined on B, so not the farthest away from the X-rooted (or specifically planned) action.
h4 Color explanations
.ui.list.offset-diagram-colors-explanation
.item.rooted-action
i.square.icon
.content This action is directly configured with respect to the reference date (X)
.item.critical-path
i.square.icon
.content This action is configured relative to other actions given the strategy to start with an X action and configure other actions 'aways' from X (critical path)
.item.non-critical-path
i.square.icon
.content This action is configured relative to other actions and the target date is determined using higher order non critical path resolve algorithms
.item.unresolved-path-action
i.square.icon
.content This action is configured relative to other actions but not connected to another action/tree that is rooted. So no target date can be determined!!
.item.attached-action
i.square.icon
.content This action is configured attached to other actions. Wether this action is visible/required can depend on the requirement configuration
.item.constraint-action
i.square.icon
.content This action is a constraint to another action and needs to be in a completed state before the other action can be completed. This action should have it's owd target date configuration and should therefore be displayed more than one time in the diagram.
.item.info-action
i.square.icon
.content This action is extra information to another action. This action should have it's owd target date configuration and should therefore be displayed more than one time in the diagram.
img src="../../assets/manual/action-offsets/more-elaborate-example.png" title="rooted-critical-path"