Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
27 Cards in this Set
- Front
- Back
Path
|
A sequence of connected, dependent activities
|
|
Critical Path
|
The longest path through the activity network that allows for the completion of all project related activities; the shortest expected time in which the entire project can be completed. Delays on the critical path will delay completion of the entire project.
|
|
Project Network
|
A flow chart that graphically depicts the project activities, the sequences, interdependencies, and start and finish times of activities (on the critical path) through the network.
|
|
Activity (=task=work package)
|
An element of the project that requires time
|
|
Merge activity
|
An activity that has two or more preceding activities on which it depends
|
|
Parallel (concurrent) activities
|
Activities that can occur independently and, if desired, not at the same time
|
|
Event
|
A point in time when an activity is started or completed. It does not consume time
|
|
Burst Activity
|
An activity that has more than one activity IMMEDIATELY following it (more than one dependency arrow flowing from it)
|
|
What are the two approaches to constructing a project network?
|
1. Activity-on-node (AON)
2. Activity-on-arrow (AOA) |
|
Activity-on-node (AON)
|
Uses a node to depict an activity
|
|
Activity-on-arrow (AOA)
|
Uses an arrow to depict an activity
|
|
Approaches to network computation process:
|
1. Forward Pass - Earliest times
2. Backward Pass - Latest times |
|
Forward Pass - Earliest times
|
How soon can the activity start? (Early start - ES)
How soon can the activity finish? (Early finish - EF) How soon can the project finish? (Expected time - ET) |
|
Backward Pass - Latest times
|
How late can the activity start? (late start - LS)
How late can the activity finish? (early finish - EF) Which activities represent the critical path? How long can it be delayed? (slack or float SL) |
|
Slack (or float)
|
The amount of time an activity can be delayed after the start of a longer parallel activity or activities
|
|
Total slack (SL)
|
The amount of time an activity can be delayed without delaying the entire project
|
|
Total Slack formula
|
SL=LS-ES
SL=LF-EF |
|
Critical path
|
It's the network path(s) that has (have) the least slack in common
|
|
Laddering
|
Activities are broken into segments so the following activity can begin sooner and not delay de work
|
|
Lag
|
The minimum amount of time a dependent activity must be delayed to begin or end
|
|
Finish-to-start (FS) relationship
|
The next activity in a sequence must be delayed when the preceding activity is complete
(días que tienen que pasar sin hacer nada entre una actividad y otra) |
|
Start-to-start (SS) relationship
|
The next activity can start (after a lag) when the preceding activity starts.
|
|
Start-to-start relationship
|
The next activity in a sequence must finish (after a lag) when the preceding activity finishes
|
|
Start-to-start relationship example
|
Activity "testing" should be finished after four days when activity "prototype" is finished
|
|
Start-to-finish relationship (SF)
|
The finish of an activity depends on the start of another activity
|
|
Start-to-finish relationship example
|
After 3 days when the job "testing" starts, the job "system documentation" must be finished.
|
|
Combinations of lag relationship
|
More than one lag relationship can be attached to an activity:
1. Debug cannot begin until two days after coding has started 2. Debug must be finished after coding is finished |