Solution Steps and Terminology: ... Care With Over-And Under-Refinement Here
Solution Steps and Terminology: ... Care With Over-And Under-Refinement Here
1. Define individual activities (tasks) that make up the project. ...care with over- and under-refinement here 2. 3. Identify precedence relationships. Estimate necessary data, e.g., times for each activity, costs.
Table 1. Software Development Project Duration Immediate Activity Code (Days) Predecessor(s) Design A 5 Code module 1 B 15 A Code module 2 C 10 A Code module 3 D 8 A Test E 12 B, C, D 4. Construct network of arcs and nodes
Activity-On-Arc (AOA) design: Activities as arcs (directed arrows); events, milestones, or pointsin-time as nodes. Activity-On-Node (AON) design: Activities as nodes, arcs as precedence relationships. See PERT Graph (Figure 4) on p. 3. Figure 1. AOA Network Diagram Without Dummy Activities
B A 1 2 C
Figure 2. AOA Network Diagram With Dummy or Phantom Activities On phantom activities:
D 3
E 4
A 1 2
B 3 D
Phantom 1 E 5 6
C 4
Phantom 2
May need to preserve unique (i,j) node labeling May need to preserve proper precedence relationships Have zero durations and don't take up resources.
5.
Class Exercise
Determine completion time along each path.
Need not be unique. Identifies critical activities and project completion time. Critical activities must be carefully monitored in ongoing project. If any take longer than anticipated, the project itself is delayed. Time estimates for each activity... Early start time, late start time, early finish time, late finish time, slack time. Table 2. Software Development Project Times
Earliest Latest Earliest Latest Critical Activity Start Start Finish Finish Slack Activity? -------------------------------------------------------------------------------A 0 0 5 5 0 Yes B 5 5 20 20 0 Yes C 5 10 15 20 5 D 5 12 13 20 7 E 20 20 32 32 0 Yes -------------------------------------------------------------------------------Critical Path: A-B-E Project Completion Time = 32