SPM Lab 9 – Activity Network Diagram

Roll no.: A017/A068/A104 Name: Harsh Chowdhary/

Sahat Shah/ Mihir Kotecha
Class: B. Tech IT Batch: A1/A2/A3
Date of Experiment: Date of Submission:
Grade:
Aim: Develop an Activity Task network required for the project.

Theory:

PERT was developed by the US Navy for the planning and control of the
Polaris missile program and the emphasis was on completing the program in
the shortest possible time. In addition PERT had the ability to cope with
uncertain activity completion times (e.g. for a particular activity the most likely
completion time is 4 weeks but it could be anywhere between 3 weeks and 8
weeks).

An Activity Network Diagram (AND) is also called an Arrow Diagram (because

the pictorial display has arrows in it) or a PERT (Program Evaluation Review
Technique) Diagram, and it is used for identifying time sequences of events
which are pivotal to objectives. In Critical Path Analysis this helps the teams to
comprehend specific event sequences driving time requirements for objective
achievement. Activity Network Diagrams are also very useful when a project has
multiple activities which need simultaneous management.

Activity Network Diagrams started out as an engineering and construction project

management tool. Critical Path Analysis draws on this methodology to identify
and standardize medical management activities.

An Activity Network Diagram helps to find out the most efficient sequence of
events needed to complete any project. It enables you to create a realistic
project schedule by graphically showing
 · the total amount of time needed to complete the project
· the sequence in which tasks must be carried out
· which tasks can be carried out at the same time
· which are the critical tasks that you need to keep an eye on.
The Activity Network diagram displays interdependencies between tasks through
the use of boxes and arrows. Arrows pointing into a task box come from its
predecessor tasks, which must be completed before the task can start. Arrows
pointing out of a task box go to its successor tasks, which cannot start until at least
this task is complete.

Procedure:
Tasks or Activities : Effective planning of projects requires careful thought and the
application of logic. To illustrate this planning tool, let's consider the manufacture
of a small item. Some typical processes might be:

Cutting, finishing, assembling, purchasing ,machining, testing

,designing : All these processes are called ‘ACTIVITIES’ or ‘TASKS’

Step 1: List WHAT has to be done.

Step 2: Decide the ORDER in which it is to be done.

Logic Network or PERT Chart : Writing this out as a network:

Output:

Activity Network Diagram for the project

List of Activites to be done

S Task Sub Task TO TL TP TE Start End Predecessor

N Date Date

1 Requirement Scope 15 18 22 17.6 16/06 02/07 -

Gathering Definition,
Tools
Identification
2 Literature Research on 20 22 28 21.8 03/07 25/07 1
Survey pre-existing
apps, Survey
Form
 3 UI Based App 18 21 23 20.8 26/07 15/08 2
Research Development,
UI used
4 Registration Front End 25 29 35 28.6 16/08 14/09 3
Module Development,
Development Back-end
coding,
Database and
user
Authentication
5 Healthcare 35 40 47 38.8 15/09 20/10 4
Module
Development

6 Integration of - 2 4 5 3.8 21/10 25/10 3, 4, 5

Modules
7 Testing - 16 19 21 18.5 26/10 13/11 6
8 Feedback Implementing 17 21 24 19.8 14/11 06/12 7
feedbacks, bug
fixes
9 Deployment - 5 6 8 6.2 07/12 13/12 8
Total Days 153 180 213 176

Where, TO = Most Optimistic (best case scenario)

TL = Most Likely (Normal Scenario)
TP = Most Pessimistic (Worst Case Scenario)
TE = Expected Duration
 Requirement Literature Registration
Gathering Survey UI Based Module
Research Development
15 20 25
1 2 3 4 5/ 5 Healthcare
Module
18
Development
45

Integration of
Modules
2 6

Testing

16
5 17
9 8 ` 7
Feedback
Deployment