PROJECT MANAGEMENT PLAN

AMBULANCE DISPATCH SYSTEM

Project Management Plan

Revision History
Author

Date

Description

Version

Project Management Plan

CONTENTS

1.

INTRODUCTION........................................................................................................3

1.1
1.2
1.3
1.4
1.5

PROJECT OVERVIEW..................................................................................................3
PROJECT DELIVERABLES...........................................................................................3
EVOLUTION OF THIS DOCUMENT..............................................................................4
REFERENCES.............................................................................................................4
DEFINITIONS, ACRONYMS AND ABBREVIATIONS.......................................................4

2.

PROJECT ORGANIZATION.......................................................................................5

2.1
2.2
2.3
2.4

PROCESS MODEL.......................................................................................................5
ORGANIZATIONAL STRUCTURE.................................................................................5
ORGANIZATIONAL BOUNDARIES AND INTERFACES...................................................6
PROJECT RESPONSIBILITIES......................................................................................6

3.

MANAGERIAL PROCESS..........................................................................................7

3.1
3.2
3.3
3.4

MANAGEMENT OBJECTIVES AND PRIORITIES............................................................7

ASSUMPTIONS, DEPENDENCIES AND CONSTRAINTS..................................................7
RISK MANAGEMENT..................................................................................................7
MONITORING AND CONTROLLING MECHANISMS......................................................8

4.

TECHNICAL PROCESS..............................................................................................9

4.1
4.2
4.3

METHODS, TOOLS, AND TECHNIQUES.......................................................................9

SOFTWARE DOCUMENTATION....................................................................................9
PROJECT SUPPORT FUNCTIONS..................................................................................9

5.

WORK ELEMENTS, SCHEDULE AND BUDGET.......................................................10

Project Management Plan

1. INTRODUCTION
1.1

Project overview

There is a great demand for a good ambulance dispatch system. This project is to define,
design, develop, test and deliver the Ambulance Dispatch System. An ambulance dispatch
system involves multiple people with extremely large amounts of timely communication. In
this system timely communication is very critical and any information transfer that can be
expedited can save a life. Information is received from a caller which is entered into the
system by the operator at which point, the Dispatcher is notified. The dispatcher reviews the
submitted information and creates an Incident report. The dispatcher must locate the
closest available ambulance and dispatch that vehicle to the proper location. If the subject
requires hospital care then the patient must be taken to the nearest hospital that is capable
of handling the case. The ambulance driver will take the shortest route as assisted by the
GPS mapping system on the vehicle.
The purpose of this project is to build a quick and reliable computer aid system to dispatch
ambulances. The ADS aims to let the dispatcher dispatch an ambulance in 3 minutes after
an incident call arrives, and for the ambulance to arrive at the incident location within 11
minutes. The high-level functionalities of the system are:

Dispatch ambulances and medical resources

Allocate ambulances and medical resources

Manage ambulances and medical resources

Emergency notification

Keep track of incidences, ambulances and medical resources

Record and query ambulance dispatch information

This project consists of 7 phases. They are Preliminary Project Plan, Requirement
Specification, Analysis, Architecture Specification, Component / Object Specification, Code
and Test Plan.
1.2

Project deliverables

Phase

Deliverable

Due Date

Preliminary Project Plan

June 4, 2016

Requirement Specification

June 23, 2016

Analysis

June 23, 2016

Architecture Specification

July 7, 2016

Component / Object Specification

July 28 July 30, 2016

Code

July 28 July 30, 2016

Test Plan

July 28 July 30, 2016

Project Management Plan

1.3

Evolution of this document

This document will be updated as the project progresses. A new revision will be released
after each modification. Every modification has to be logged in the Document Revision
History. Each log entry must include date, revision identifier, authors name and brief
description of the modification. The author of the modifications is responsible for updating
the Document Revision History.
Updates should be expected in the following sections:
a. References will be updated as necessary.
b. Definitions, acronyms, and abbreviations will be updated as necessary.
c. Organizational Structure will be updated as the roles and responsibilities are
assigned for each phase.
d. Management objectives and priorities will be updated to as priorities change.
e. Assumptions, dependencies and constraints will be updated as necessary.
f. Risk management will be updated as new risks are identified.
g. Technical Process will be updated as requirements become clearer.
h. Work elements, schedule and budget will be updated in the case of schedule or
budget changes.
1.4

References

[1] http://wwwbruegge.informatik.tumuenchen.de/twiki/bin/view/OOSE/SoftwareProjectManagementPlanTemplate
[2] http://www.utdallas.edu/~chung/CS6354/Project.doc
1.5

Definitions, acronyms and abbreviations

ADS Ambulance Dispatch System

Caller The one who calls 911 asking for ambulance service
Dispatcher Person who get call from caller and use the ADS to dispatch ambulances
GPS Global Positioning System
GUI Graphical User Interface
RAD Requirements Analysis Document
UML Unified Modeling Language

Project Management Plan

2. PROJECT ORGANIZATION
2.1

Process model

The ADS will be developed under waterfall process model. This model encompasses the
following activities: system engineering, requirement analysis, software design,
implementation, and testing. Every phase will have certain deliverables. Finally, an
executable application will be delivered, with the test plan.
2.2

Organizational structure

The team consists of 7 members, and each member will be involved in a phase of the
project as a team leader.
Team Leaders

Phase

Bonas Khanal
Ed Beck

0-1

Haibo Shi

Edward Mao

Enoch Asamrah

Ganesh Prabu, Marcus Parker

Table of Role Play:

Phase

Manager

Customer

Developer

Tester

0-1

Bonas Khanal

Ed, Haibo

Edward,
Enoch

Marcus,
Ganesh

Ed Beck

Bonas,
Haibo

Edward,
Enoch,
Ganesh

Marcus

Haibo Shi

Bonas,
Ed

Edward,
Enoch,
Ganesh

Marcus

Edward Mao

Bonas,
Ed

Haibo,
Enoch,
Ganesh

Marcus

Enoch Asamrah

Bonas,
Ed

Haibo,
Edward

Marcus,
Ganesh

Ganesh Prabu,
Marcus Parker

Bonas,
Ed

Haibo,
Edward

Enoch

Project Management Plan

2.3

Organizational boundaries and interfaces

For each phase, there will be a team leader. The rests are common members. In order to
give leadership experience to every member, the team leaders will change in different
phases.
2.4

Project responsibilities

The team leaders are responsible for arranging and coordinating the tasks of each team
members, organizing team meetings, integrating every members work and submitting the
deliverables.

Project Management Plan

3. MANAGERIAL PROCESS
3.1

Management objectives and priorities

The main management objective is to develop a routine process, which allows us to

concentrate on core elements at different phases more efficiently and every team member
is able to contribute his power to the team.
3.2

i.

Assumptions, dependencies and constraints

The project assumptions are as follows:

Each team member has basic knowledge of Programming, Software Engineering,
and Database.

Equipment and software availability

Approval of funding for this project

Organized traffic system

ii.

The project dependencies are as follows:

Ambulance dispatch locations in proximate distance

Availability of subject matter expertise in ambulance dispatch system.

Availability of the existing GPS system/service in the ADS

Availability of maintenance of ambulance

iii.

The project constraints are as follows:

Time

Budget

Man hours

Availability of existing software

3.3

Risk management

Risk
Unavailable
resource

Team member
absence
Unfamiliar with
technique

Possibility

Impact

Description

Solution

Medium

Unavailability of
certain resource,
including Google
doc/group, internet
and etc

All important document and

message are sent to email
accounts.

Medium

Medium

Team member is
unable to come to
team meetings or
finish assigned work.

Do regular knowledge
backup. Share knowledge of
everyones work to the whole
team.

High

High

Team member is not

familiar with tools or
techniques used in this

Do team tutorial, selflearning. Evaluate team

member skills before each

Low

Project Management Plan

Unable to
Reuse

Lack of
communication

3.4

High

High

project.

phase and/or re-assign team

roles.

Medium

Team is not able to

reuse code and/or
documentation.

Only reuse if parts are well

understood, otherwise create
it from scratch.

High

Team members fail to

communicate at critical
times

Be active and effective in

communication, monitor
team member response and
project involvement. Provide
friendly environment.

Monitoring and controlling mechanisms

Each phase will have a team leader. This person will deliver a work schedule with
weekly goals at the beginning of each phase. Weekly meetings will be set up to review and
assign key components at current stage. Further discussions will be made
between meetings through online group (Google group). Documentation will also be
updated after each meeting. Team leader can adjust the weekly goals by
checking the progress of each phase to ensure each phase will meet the requirements and
artifacts will be delivered on time.

Project Management Plan

4. TECHNICAL PROCESS
4.1

Methods, tools, and techniques

The project will be implemented using the water fall methodology.

There will be traceability between all phases of the project.
The project will follow an object oriented analysis technique.
Microsoft Office tools will be used to create and maintain all documentation. Rational Rose
will be used to create the UML models. The database will be implemented MYSQL.
The system will be implemented with HTML, JavaScript, and ASP.NET.
There will be a naming convention followed during software development.
4.2

Software documentation

Documentation such as Business Requirement, Functional Specification, Cost Benefit

Analysis, Technical Specification, Detail Design, Test Plan, Implementation Plan, and
Benefit Realization document will be completed.
4.3

Project support functions

Online Team Collaboration: Google Groups

Project Management Plan

5. WORK ELEMENTS, SCHEDULE AND BUDGET

Deliverable

Due Date

Preliminary Project Plan

June 4, 2016

Requirement Specification

June 23, 2016

Analysis

June 23, 2016

Architecture Specification

July 7, 2016

Component / Object Specification

July 28 July 30, 2016

Code

July 28 July 30, 2016

Test Plan

July 28 July 30, 2016