Anda di halaman 1dari 11

July 19

Project
Plan

2013

ARTEFACT 1
S0222184 - Jonghardi,
Cardven
S0224244 - Nemkul, Bishnu
S0213317 - Teran Montero,
Christian

Table of Contents
Introduction........................................................................................................... 3
Objective............................................................................................................... 3
Constraint of the project:....................................................................................... 3
Project Organisations............................................................................................. 5
First Period:......................................................................................................... 5
Second Period:.................................................................................................... 6
Third Period:....................................................................................................... 6
Requirement:......................................................................................................... 8
Client Requirement:............................................................................................ 8
Server Requirement:........................................................................................... 8
WBS & Schedule.................................................................................................... 9
Risk Plan................................................................................................................ 9
Monitoring and reporting..................................................................................... 11

Project Plan
Introduction
We are employed as software engineers by XYZZY company to design and
implement a proof of the concept information kiosk for DVD store. So 12 weeks
were given for the demonstration. If the demonstration is successful, it will be
further taken to prototype development. The basic functionalities for both
customers and manager for both customers and managers are provided in
demonstration. So for this we formed the group of three as the company has
budgeted for three people and started our project.

Objective
The Application will need to be finished before 27 September 2013.
Most of the functionality for both customers and managers be provided
The scope must be working according the use.

Constraint of the project:


1. Resource Constraint:
Number of Engineer

: 3 person

Software available

:
NetBeans IDE will be used for this project as
a java technology is to be used to design the
system. Because it is easy to develop Java
desktop , mobile and web applications with
NetBeans IDE.
GlassFish is an open source development
project was build for Java EE5 application
server

We will be using java technology as required


by the client. Java technology is becoming
more and more popular because of ease of
use.
Particularly for this project Java database is to
be used to store information. It is a relational
database management system that can be
embedded in Java Programs.
The front end will be provided in website so
the web browser will be required to get access
to the front end .

2. Time Constraint:
12 hours per person for 12 weeks. Total work hours: 432 hours
3. Scope Constraint:
Design and Implement a proof of concept information kiosk for DVD
stores.
Web driven Application with 3 tier layer.
Basic functionality for the Customers and the Managers.

Project Organisations
The project will have a different project management to ensure the output quality
of the project.
The Project organisation has been categorise by the delivery time of the project.

First Period:

Week 1-4

Project Manager:
He will be the in charge of the project planning and dividing the work
load among the group. WBS, project organisation will be done by project
manager.
Application Analyst:
As for the current period both analyst are to work on a risk plan,
hardware and software requirement,

Second Period:

Week 5-8

Project Manager:
The project manager will be the in charge of weekly progress reports.
Web Designer:
He will be in charge of Document design for designing
Software Analyst:
He will be in charge of requirement specification

Third Period:

Week 9-12

Project Manager:
For this period project manager will be reporting the progress report and
in the final week he will be responsible for the project review
Software Engineer:
Work on the implementation of design to implementation
Developer:
Work on the required coding of the project

For more detailled information about the responsibility of each of the


member, please refer to Who does what.xps.

Requirement:
We are required to create GUI - driven the three tier system using the Java
technology more importantly suing the Java database to store the information.
The hardware and software requirement are as given below:

Client Requirement:

Server Requirement:

1. Hardware Requirement:
- Desktop or Tablet with more than
7 screen
- At least 500 MB RAM.
- At least 100 MB free HDD space

1. Hardware Requirement:
- At least 2 GB RAM
- At least 300 GB free HDD space
- 32 bit or 64 bit processor
- 500 GB bandwidth

2. Software Requirement:
- HTML5 compatible web browser.

2. Software Requirement:
- Glassfish
- Derby database
- Java SDK 7.0

WBS & Schedule


For Work Breakdown Structure and the scheduling please refer to the Microsoft
Project document under name appdevproject-final.mpp

Risk Plan
Risk is required to be considered in all kinds of scenario because danger is
inevitable all the time. Some of the risks are very unlikely to happen but still need
to be accounted for to make sure the countermeasure is ready on the side so
problem can be solved if it arises.
Risk

Date

Mitigation Strategy

Workload from
other courses
becomes
excessive in
weeks 7-12
One of the
member getting
hospitalised
Work load from
the work place
being excessive

01/07/13

1.0

Design system as early as


possible.

Could
occur
anytime
Could
occur
anytime

0.5

Members need to be careful;


of their health

1.0

Losing of the data

Could
occur
anytime

1.0

10

10

Change of the
project during
implementation
period

08/07/1
3

0.3

10

0.1

10

Manage the time,


communicate with the
project members to work
out the plan
Backup the data and if
possible upload them to
cloud after update.
Using cloud service to store
the data (Google Drive)
Communicate with the
project members and the
lectures to consult about
any problem that has
arisen
We will require to work
out with the client for
the project

Client cancelling
the project

P = Probability that risk will occur


(0-1).
I = Degree of impact to the project
(1-10).

J = P*I = Jeopardy to the success


of the project. Positive action is
required if J > 6.

Monitoring and reporting


To monitor the project progress and to ensure the project is progressing
accordingly, there are several things that is need to be recorded:
The team need to meet regularly
Gather data on actual performance or actual result
Record changes by writing the progress report
Compare actual project with the baseline project
Take any needed corrective action immediately- will involve decisions and
will often involve trade-off of times, scope and cost
This Project will based on Shared Responsibility Structure. In this structure,
every and each member have common responsibility which is to ensure the
Project progress accordingly.
In this team, the Project Manager are the person is the decision maker if there is
a conflict between each team member interest. Every progress that has been
made will be reported to each and every other team member. At the end of each
milestone, the Project Manager will have a responsibility to submit the required
document. On the other hand, if the Project Manager are not be able to perform
his/her task, other team member is allowed to do it for him/her.