PERT EXCERCISE

For an imaginary software development project the top level Work Breakdown Structure (WBS) looks like this: \begin{tabular}{|c|l|c|c|c|c|} \hline Activity & Description & Preceding Activity & Optimistic & Realistic & Pessimistic \\ \hline A & DefineRequirements & None & 2 & 10 & 18 \\ \hline B & Assign Team & A & 2 & 5 & 8 \\ \hline C & DesignSoftware & B & 10 & 25 & 34 \\ \hline D & Code Software & B & 12 & 20 & 34 \\ \hline E & Test Software & D & 30 & 50 & 64 \\ \hline F & DevelopPatentRequest & C, E & 9 & 11 & 14 \\ \hline G & BuildDeploymentPackage & D & 30 & 35 & 40 \\ \hline H & Deploy to Client & E, F, G & 7 & 15 & 17 \\ \hline \end{tabular} All duration estimates are in days, and the network proceeds from Activity A to Activity H. All duration estimates are in days, and the network proceeds from Activity A to Activity H. Assume a 5 day work week. 1. Draw an activity-on-arrow (AA) network diagram representing the project. 2. How many paths are possible? 3. Show, or identify the activities for the Critical Path of this project? How many days? 4. Which activities demonstrate Slack time? 5. What is the shortest possible time, in weeks, it will take to complete this project