Part $2-$ Figure $7\mathrm{.}11$ depicts a list of activities, immediate predecessors, and estimated durations for the

web$-$based reporting system project.

Web$-$based Reporting System Project

Figure $7\mathrm{.}11.$ List of Activities, Immediate Predecessors, and Estimated Durations $($Gido et$.$ Al$.,2017).$

A$)$ The project is required to be completed in $50$ days, and it needs to be started as soon as possible.

Each group must:

Identify the ES and EF times for each activity.

Identify the LS and LF times for each activity.

Create the project schedule table with the calculated total slack values for each activity.

Show the critical path for the development project.

B$)$ Beth and her team must determine a way to reduce the development time by $9$ days, request that the

project completion date be extended from $50$ to $59$ days, or find some compromise. After extensive

discussions with upper management, in which she stressed the importance of developing the system right

the first time and not having to rush through some critical phases of the system development life cycle,

Beth convinced her superiors to extend the project completion time to $60$ days. Beth and her team

proceeded with the project and completed activities $1$ through $6$ :

Activity $1,$ "Gather Data," actually finished on day $4.$

Activity $2,$ "Study Feasibility," actually finished on day $4.$

Activity $3,$ "Prepare Problem Definition Report," actually finished on day $5.$

Activity $4,$ "Interview Users," actually finished on day $10.$

Activity $5,$ "Study Existing System," actually finished on day $15.$

Activity $6,$ "Define User Requirements," actually finished on day $18.$