This document outlines the steps and timeline for developing a new network system. It involved the following phases: 1) Preparation and Planning from November to December 2003, which included developing a project proposal, approving the proposal, and recruiting a project team. 2) Development and Testing from January to March 2004, consisting of specifying requirements, developing a prototype, approving the prototype, and developing a beta version. 3) Implementation from April to June 2004, including testing the beta version, applying final corrections, approving the final version, training users, and rolling out the final version. The document provides a detailed Gantt chart scheduling each task within the project phases.

1. Network Basic

2. 1.6.2004Roll-out final version
31.5.20041.5.2004Train users
I mplementation
11.5.2004Approve final version
10.5.20041.5.2004Apply final corrections
30.4.20041.4.2004Test beta version
31.3.200417.3.2004Develop beta version
16.3.2004Approve prototype
15.3.20041.2.2004Develop prototype
31.1.20045.1.2004Specify detail requirements
Development and Test
31.12.200314.12.2003Recruit project team
13.12.2003Approve project proposal
10.12.200315.11.2003Develop project proposal
Preparation and Planning
EndStartTask
1.6.2004Roll-out final version
31.5.20041.5.2004Train users
I mplementation
11.5.2004Approve final version
10.5.20041.5.2004Apply final corrections
30.4.20041.4.2004Test beta version
31.3.200417.3.2004Develop beta version
16.3.2004Approve prototype
15.3.20041.2.2004Develop prototype
31.1.20045.1.2004Specify detail requirements
Development and Test
31.12.200314.12.2003Recruit project team
13.12.2003Approve project proposal
10.12.200315.11.2003Develop project proposal
Preparation and Planning
EndStartTask
Preparation and Planning
Developproject proposal
Approveproject proposal
Recruit project team
Development and Test
Specifydetailrequirements
Developprototype
Approveprototype
Developbetaversion
Test betaversion
Applyfinalcorrections
Approvefinal version
Implementation
Trainusers
Roll-out finalversion
11.03 12.03 1.04 2.04 3.04 4.04 5.04 6.04
Preparation and Planning
Developproject proposal
Approveproject proposal
Recruit project team
Development and Test
Specifydetailrequirements
Developprototype
Approveprototype
Developbetaversion
Test betaversion
Applyfinalcorrections
Approvefinal version
Implementation
Trainusers
Roll-out finalversion
11.03 12.03 1.04 2.04 3.04 4.04 5.04 6.04

3. What was the NEED for
developing a system

4. 4
Network Techniques:
PERT and CPM
 With the exception of Gantt charts, the most common
approach to scheduling is the use of network
techniques such as PERT and CPM
 The Program Evaluation and Review Technique
(PERT) was developed by the U.S. Navy in 1958
 The Critical Path Method was developed by DuPont,
Inc at about the same time
 PERT has been primarily used for research and
development projects
 CPM was designed for construction projects and has
been generally embraced by the construction industry
 The two methods are quite similar

5. 5
Terminology
Activity
 A specific task or set of tasks that are required
by the project, use up resources, and take
time to complete

6. 6
Terminology
Event
The result of completing one or more activities. An
identifiable end state occurring at a particular time.
Events use no resources.

7. 7
Terminology
Network
The combination of all activities and events
define the project and the activity
precedence relationships

8. 8
Terminology
Path
The series of connected activities (or
intermediate events) between any two
events in a network

9. 9
Terminology
Critical
Activities, events, or paths which, if delayed, will
delay the completion of the project. A project’s
critical path is understood to mean that sequence
of critical (slowest) activities that connect the
project’s start event to its finish event

10. 10
Terminology
 An activity can be in any of these conditions:
 It may have a successor(s) but no predecessor(s) -
starts a network
 It may have a predecessor(s) but no successor(s) -
ends a network
 It may have both predecessor(s) and successor(s) -
in the middle of a network
 The interconnections depend on the technological
relationships described in the action plan

11. 11
Drawing Networks
 Activity-on-Arrow (AOA) networks use
arrows to represent activities while nodes
stand for events
 Activity-on-Node (AON) networks use nodes
to represent activities with arrows to show
precedence relationships
 The choice between AOA and AON
representation is largely a matter of personal
preference.