Software Project Management Plan Project: The Australasian Quaternary Association Webpage

plumpbustlingInternet και Εφαρμογές Web

4 Δεκ 2013 (πριν από 3 χρόνια και 11 μήνες)

96 εμφανίσεις



Software Project Management Plan


Project:
The Australasian Quaternary Association
Webpage





April

10
, 2012






Version 1.
3

Team member

Mohsen Rezaei

Sanat Thomas

Ying Li

Rayed
Mohammed
ALSABHAN




Submitted in partial fulfillment

Of the requirements of

Giants Studio
Project

University of Ballarat



Change History


Major Field Achievement Test

SPMP Version 1.0

Release date:
2
1
/03/12


Baseline Version

SPMP Version 1.1

Release date: 29/03/12

Add work break
down structure

SPMP Version 1.2

Release date: 29/03/12

Add work
breakdown structure

Release date: 02/04/12

Added team members,
coordinator and supervisor
contact detail

SPMP Version 1.3

Release date: 29/03/12

Add work breakdown structure

Release date: 02/04/12

Release date: 10/04/12

Modify

the content and technical
process





iii

Preface

The main purpose of this document is to clarify the project plan to develop the

Australasian Quaternary Association Webpage.
This project helps understand how the
project should be developed towards the
completion of deliverables. This SPMP is a
guide for the team and will be updated as the project progresses.




iv


Contents

Change History

................................
................................
................................
................................
...............

ii

Preface

................................
................................
................................
................................
...........................

iii

Contents

................................
................................
................................
................................
.........................

iv

1.

Overview

................................
................................
................................
................................
................

1

1.1

Project
Summary

................................
................................
................................
............................

1

1.1.1

Scope, Purpose and Objectives

................................
................................
...............................

1

1.1.2

Assumptions and Constraints

................................
................................
................................
.

1

1.1.3

Project Deliverables

................................
................................
................................
................

2

1.1.4

Client Information

................................
................................
................................
..................

2

1.1.5

Team member contact detail

................................
................................
................................
...

2

1.1.6

Coordinator and supervisor contact detail

................................
................................
..............

2

2

Project Organization

................................
................................
................................
...............................

3

2.1

Roles and Responsibilities

................................
................................
................................
..............

3

2.1.1

Project Manager

................................
................................
................................
......................

3

2.1.2

Cl
ient Liaison manager

................................
................................
................................
...........

3

2.1.3

Secretary

................................
................................
................................
................................
.

3

2.1.4

Webpage designer

................................
................................
................................
...................

4

2.1.5

Database designer

................................
................................
................................
...................

4

2.1.6

Meeting recorder

................................
................................
................................
.....................

4

2.2

Team Rules and Processes

................................
................................
................................
..............

4

3

Managerial Process Plans

................................
................................
................................
.......................

5

3.
1

Project Start
-
Up Plan

................................
................................
................................
......................

5

3.1.1

Estimation Plan

................................
................................
................................
.......................

5

3.1.2

Staffing plan

................................
................................
................................
...........................

6

3.1.3

Resource acquisition plan

................................
................................
................................
.......

7

3.1.4

Project staff training plan

................................
................................
................................
........

7

3.2

Work Plan

................................
................................
................................
................................
.......

8

3.2.1

Work Activities
................................
................................
................................
.......................

8

3.2.2

Sc
hedule Allocation

................................
................................
................................
................

8

3.2.3

Resource Allocation

................................
................................
................................
...............

9

3.2.4

Budget Allocation

................................
................................
................................
...................

9

3.3

Control Plan

................................
................................
................................
................................
....

9

3.3.1

Requirements Control Plan

................................
................................
................................
.....

9

3.3.2

Schedule Control Plan

................................
................................
................................
............

9

3.3.3

Budget Control Plan

................................
................................
................................
...............

9

3.3.
4

Quality Control Plan

................................
................................
................................
...............

9

3.3.5

Reporting Plan

................................
................................
................................
.......................
10

3.3.6

Metrics Collection Plan

................................
................................
................................
.........
10

3.4

Risk Management Plan

................................
................................
................................
..................
10

3.4.
1

Risk management plan

................................
................................
................................
...........
10

3.4.2

New risks

................................
................................
................................
...............................
11

3.5

Closeout Plan

................................
................................
................................
................................
.
11

3.5.1

Clos
eout plan

................................
................................
................................
.........................
11

4

Technical Process

................................
................................
................................
................................
..
11

4.1

Process Model

................................
................................
................................
...............................
11

4.2

Methods, Tools, and Techniques

................................
................................
................................
...
12

4.2.1

Fundamentals:

................................
................................
................................
........................
12

4.2.2

Project
Management:

................................
................................
................................
.............
12

4.2.3

Design:

................................
................................
................................
................................
...
12

4.2.4

Implementation:

................................
................................
................................
.....................
12

4.3

Document distribution

................................
................................
................................
...................
12

4.4

Infrastructure Plan

................................
................................
................................
.........................
13

4.5

Product Acceptance Plan

................................
................................
................................
...............
13



v

5

Support Process Plans

................................
................................
................................
............................
14

5.1

Configuration Management Plan

................................
................................
................................
...
14

5.2

Validation & Verification Plan

................................
................................
................................
......
14

5.3

Documentation Plan

................................
................................
................................
......................
14

5.4

Quality Assurance Plan

................................
................................
................................
.................
15

5.5

Review and Audits
................................
................................
................................
.........................
15

5.6

Problem Resolution Plan

................................
................................
................................
...............
15

5.6.1

Problem prioritizing

................................
................................
................................
...............
15

Appendix A

................................
................................
................................
................................
...................
16

Appendix B: Tender bid

................................
................................
................................
................................
17

1.

Cov
er letter

................................
................................
................................
................................
............
19

2.

Project introduction

................................
................................
................................
...............................
20

2.1

Project title
................................
................................
................................
................................
.....
20

2.2

Project details

................................
................................
................................
................................
20

3.

Clien
t information

................................
................................
................................
................................
.
20

3.1

Client’s initial requirements

................................
................................
................................
..........
20

3.2

Client detail

................................
................................
................................
................................
...
2
0

4.

Team introduction

................................
................................
................................
................................
.
21

4.1

Team

members information

................................
................................
................................
...........
21

4.2

Skills, roles and responsibilities

................................
................................
................................
....
21

5.

Reasons for consideration

................................
................................
................................
......................
22

6.

Declaration

................................
................................
................................
................................
............
23

Appendix C: Work breakdown structure

................................
................................
................................
.......
24






vi

Table of Figures

Figure 1: Schedule

................................
................................
................................
................................
..........

5

Figure 2: Staffing plan

................................
................................
................................
................................
....

6

Figure 3: Gantt chart

................................
................................
................................
................................
.......

8

Figure 4: Risk management table

................................
................................
................................
..................
10

Figure 5: closure checklist

................................
................................
................................
.............................
11

Figure 6: Project over view

................................
................................
................................
...........................
16




Project proposal


1

1.

Overview

1.1


Project Summary

1.1.1

Scope, Purpose and Objectives

The purpose of this project is to update an out
-
date webpage of Australasian

Quaternary Association, and
produce a functional database of all their members,

which will give the AQUA an international
face and helps them be recognized leading to
better

understanding of the association by its
visitors;

also complete online payment fu
nction for renew membership

will be applied
.


The project is to be completed over the course of the semester at the University of Ballarat.
The scope of the project covers the main requirements of our client.

A detailed scope of the project will be added d
uring the requirement specification phase.


1.1.2

Assumptions and Constraints


The team members of this project and author of this PMP

believe this project will be
completed in one
semester. This

project is counting heavily on
member’s

time and effort, and
will mostly

use

the open source technology tools to achieve the goal.

This project will be under
the direct
supervision

of Dr. Shamsheer S
yed who will
guide

us in the right path and timetable
for the project.


This project after completion will be the property of University of Ballarat and
Australasian
Quaternary Association
will have a life time license for using the final product.




Project proposal


2

1.1.3

Project Deliverables

The list of project deliverables is:



Project Management

Plan



Software Requirements Specification



Software Design Description



Software Quality Assurance Plan (including the Software Verification and Validation
Plan and the Test Design Document)



Working System with an Access Database



Final Studio Document

Refer

to section 1.1.4 for the expected delivery dat
es of the project deliverables.

1.1.4

Client Information

The client is a staff of University of Ballarat, Jessica Reeves, and Ms Jesscia Reeves will be
contacted via Email: j.reeves@ballarat.edu.au.

1.1.5

Team member cont
act detail

Name

Mobile Phone

Email address

Mohsen R
EZAEI

0401348908

mr8362@hotmail.com

Sanat T
HOMAS

0423947720

sanatthomas@gmail.com

Ying L
I

0423467484

tarely@163.com

Rayed Mohammed
ALSABHAN

0403120059

rayed_sabhan@hotmail.com


1.1.6

Coordinator and supervisor contact detail


Title

Name

Email

Coordinator

Shamsheer SYED

s.syed@ballarat.edu.au

Supervisor

Shamsheer SYED

s.syed@ballarat.edu.au

Project proposal


3

2

Project Organization

2.1


Roles and Responsibilities

This section describes the roles and responsibilities the project team.

Because
the whole team has only 4 members, so each member will play more than one roles in the
project.



2.1.1

Project Manager



To provide regular feedback to supervisor.



To manage team member and work tasks.



To keeps the project
run on schedule.



To arrange every meeting.



To

provide learning materials and resources.

2.1.2

Client Liaison manager



To contact client.



To arrange client meeting.



To resolve all doubts to client.


2.1.3

Secretary



To keep all the meeting records.



To prepare meeting plan and complete meeting minutes.


Role

Team member

Project manager

Mohsen Rezaei

Database designer

Sanat Thomas
, Mohsen Rezaei

Secretary

Ying Li

Meeting recorder

Ying Li

Webpage designer

Rayed Mohammed ALSABHAN
,
Ying Li

Client Liaison manager

Mohsen Rezaei

Project proposal


4

2.1.4

Webpage
designer



To design webpage



To complete all the requirements about the webpage.



To maintain webpage

2.1.5

Database designer



To design database



To enter all the data into database



To maintain database


2.1.6

Meeting
recorder



Have to attend all the meeting.



Have to take
records for all the meeting.



Have to keep softcopy for all the meeting minutes.


2.2


Team Rules and Processes



All the tasks have to complete in time and all team members have to take part in all
their work tasks.



Have team meeting every week, include two internal meeting, and one supervisor
meeting, and
at least
meet the client three times.





Project proposal


5

3

Managerial Process Plans

3.1


Project Start
-
Up Plan

This section contains our project’s estimation plan, staffing plan, resou
rce acquisition
plan, and training plan.

3.1.1

Estimation Plan

3.1.1.1

Schedule


Figure
1
: Schedule


Task


Due Date

Team statement

Fri, March 9, 2012

Project selection

Fri, March 9, 2012

Tender bid

Fri, March 16, 2012

SPMP Document

Fri, March 23, 2012

Presentation on project
requirement

Thu, April 20, 2012

Draft of SRS and SDD

Thu, April 20, 2012

Final SRS and SDD

Fri, May 18, 2012

Poster presentation

Thu, May 31, 2012

Test report and user
document

Fri, Jun 1,
2012


Maintenance, PM,
Participation and
research

Mon, Jun 25, 2012

Final interview

Mon, Jun 25, 2012


3.1.1.2

R
esource requirements



The resource requirement is depend
on experiences of team members.

The

following
resources are

required in this project:

a.

Technical Resources

1.

Project team webpage

This will be used as a personal webpage and contain links and
documents for everyone who
is
interested in the project.

2.

Email

This will be used to make contact with every team member.

Project proposal


6

3.

Development software



Dreamweaver: for design the webpage

layout



PHP
and MySQL package (XAMPP)



HTML and PHP
testing

server (Joomla)

4.

DropBox

This is used to share resources, documents and folders between
each team members

as document repository
.


b.

Written Resources

1.

IEEE Standar
ds

2.

Various web sites



www.ieee.com



Php.resourceindex.com


3.1.2

Staffing plan


This project will require the human resources as the following table shown below.


Figure
2
:

S
taffing plan



Type

Key periods

Key project phases

Qty

Project manager

Fri, March 9, 2012 to
Mon, June 25, 2012

All

1

Webpage
designer

Fri, March 9, 2012 to
Mon, June 25, 2012

Design, system
allocation

1

Database
designer

Fri, March 9, 2012 to
Mon, June
25, 2012

Design, Requirements

1

Project Analyst

Fri, March 9, 2012 to
Mon, June 25, 2012

Requirements,
documentation

1

Tester

Fri, March 9, 2012 to
Mon, June 25, 2012

Implementation

1


Project proposal


7

3.1.3

Resource acquisition plan

The project manager should acquire all

software and hardware resources for this
project. And the required non
-
human resources are:



Printing services

Required dates: every report document due date. See figure 1.

Project team will use library printer for all the printing requirements.



Computer s
oftware

Required dates: Fri, March 23, 2012.

All design softwares are having existing licenses and
will be
use
d

legally.



Data repository

Required dates: Fri, March 9, 2012.

Data repository storage is provided
by

Drop Box

and all team members can
have
access
.


3.1.4

Project staff training plan

There will no training for project participants. The project team members are all
already trained in their respective disciplines and spend many hours for learning
personal software and teamwork.

All the team members
are committed to search and learn new skills as required
during the project progress.


The related knowledge about PHP language and development, we have our limited
experience in this area but the self
-
learn skill, database and webpage design
training cour
ses we have before will fill our knowledge gap in this area.


Project proposal


8

3.2

Work Plan

3.2.1

Work Activities

Refer to section 5.1.2 Gantt chart.

3.2.2

Schedule Allocation

Figure
3
: Gantt chart

*not include the weekend.


Activity

Complete
status (%)

Weekly
date

M
ar
5~
9

M
ar
12
~1
6

M
ar

19
~2
3

M
ar
26
~3
0

A
pr
16
~2
0

A
pr
23
~2
7

A
pr
30
~
M
ay
4

M
ay
7~
11

M
ay
14
~1
8

M
ay
21
~2
5

M
ay
28
~J
u
n
1

J
u
n
4~
8

J
u
n
11
~1
5

Ju
n
18
~2
2

Ju
n
25
~2
9

W
1

W
2

W
3

W
4

W
5

W
6

W
7

W
8

W
9

W
10

W
11

W
12

W
13

W
14

W
15

Team format

100%
















Tender
bid

100%
















SPMP draft

100%
















SPMP

0
















SRS and SDD

0
















Database design

0
















Poster

0
















Webpage
design

0
















programming

0
















Test

0
















Maintenance

0
















Final product
delivery

0
















Test report

0
























Gantt chart Symbols

W
=
Week




Project proposal


9

3.2.3

Resource Allocation

Resources are allocated according the time
table (
Appendix A), and due date of deliverables.

3.2.4

Budget Allocation

There is no concern about this matter.

3.3

Control Plan

3.3.1

Requirements Control Plan

When changes are to be made in the requirements after the Software Requirement
Specification (SRS) is

created, any further changes should be advised to team mem
bers and
supervisor and according to the status of project at that moment and considering the project
schedule, and skills needed, the team with the prior approval of the supervisor decides on
applying the new requirements.

In case of change an update to S
RS is necessary and a new version of SRS will be created.

Ideally no changes will be made after SRS is completed.

3.3.2

Schedule Control Plan

If the work plan falls behind the schedule, all the team members are prepared to do some extra
work time on their own ti
me, and in
-
between project plan or during the mid
-
semester holiday
to bring the project back to the schedule and delivery time.


3.3.3

Budget Control Plan

There is no concern about this matter.

3.3.4

Quality Control Plan

Following each implementation a full user test
will be applied to product for maximum
assurance of code quality, any required debugging will be implemented immediately.

Project proposal


10

3.3.5

Reporting Plan

The SPMP will be updated to new versions during the project, and after SRS cycle. The
updated versions will be
reported to the supervisor and adviser for meeting the approval.

After approval all the documents will go back to team members to work accordingly.

3.3.6

Metrics Collection Plan

None

3.4


Risk Management Plan

3.4.1

Risk management plan

3.4.1.1

Risk management table


A risk
management table will be provided for the project. And this table will indicate
the current project risks, and determine the rating (High, Medium, Low) of the current
risks.

Figure
4
: Risk management table

Factor

Risk
rating(H,M,L
)

Response

comments

goals

L

Change
project or
apply
extensions.

This risk should be
solved at the beginning.

customer

L

Meeting the
client

Project team need to
keep in touch with client.

Schedule

H

Analysis the
schedule and
reallocate
the human
resources

Plan the schedule well at
the beginning

Staff

H

Reallocate
the human
resources

When conflicts exist,
project manager has
responsibility to solve
this problem.

Techniques

H

Ask help
from
external
environment

Team members should
keep learning
about the
related knowledge

Project proposal


11


3.4.2

New risks

When new risk
is born
,
it
will be added to the Risk management table by project
manager. And team internal meeting will discuss the change of new risks and give
responses for all of them.

3.5


Closeout Plan

3.5.1

Closeout plan

There will
be

a number of closure activities that will be performed before the project is
closed, and all activities are captured in the following checklist:

Figure
5
: closure checklist


Item


Due date

Done

Final S
RS and SDD

Fri, May 18, 2012


Poster

Thu, May 31, 2012


Test report and user
document

Fri, Jun 1, 2012


Final report

Mon, Jun 25, 2012



All the details about project report, presentation and the milestones
reached

would be
stated

in

the final report at the end of semester.


4

Technical Process

4.1


Process Model

The

Australasian Quaternary Association Webpage

will be
progressed using agile
methodology

with emphasize on extreme programing(XP),
a
s we will be in
continuous

contact
with the client as the project progresses to fulfill the deliverables

as desired by the client

in our
limited time schedule.

Project proposal


12

4.2


Methods, Tools, and Techniques

After talking to the project owner,
it has

been realized that the project is better to be
implemented in open source environments.

The following is the tools that will satisfy the needs of project.

4.2.1

Fundamentals:

Microsoft windows 7 desktop operating system

Microsoft Office 2010

Drop
b
ox

4.2.2

Project
Management:

Microsoft project 2010

4.2.3

Design:

Enterpri
se Architect

4.2.4

Implementation:

Adobe
Dreamweaver

CS5

Paintshop Pro XI

XAMPP

Joomla

4.3

Document distribution

All documents distributed electronically will first be created in Microsoft open XML document
format using Microsoft Word 2010. A PDF version of the
completed files will be available on
team document repository for easy accessing and flawless printing if required.

Project proposal


13

4.4


Infrastructure Plan

All team members will work within the facilities of

university of Ballarat, Mt Helen campus.
All the team members curre
ntly have access to
these facilities via security username and
password.

4.5


Product Acceptance Plan

The group will test the final product and applications for acceptance. Web server will be tested
in order to assure problem free connection of users to the
database.



Main process
of

test will be appropriateness of the overall operations with database such as update of the
users’ details, etc.

Acceptance of work products is eventually reached when approval is granted by the person
with such authority.











Project proposal


14

5

Support

Process Plans

5.1


Configuration Management Plan

This section briefly describes the configuration management approach for the project.

Further details will be added.

5.2


Validation & Verification Plan

This section briefly describes the Verification and
Validation (V&V) approach for the
project.

Further details will be added to this part after development.

5.3


Documentation Plan

This section describes the documentation plan for the project. And there are two
subsections of those documents: deliverable and
non
-
deliverable.



Deliverable documents:

Sees figure 1 for detail information.



Non
-
deliverable documents:

Meeting plans, Meeting minutes, design summaries, webpage design plan, closure
checklist.

Creating every document will be according to the IEEE standar
ds.

All the deliverable documents will be discussed with supervisor and improved before
delivery.


Project proposal


15

5.4


Quality Assurance Plan

The product will be tested. Errors will be corrected directly if discovered during initial coding
of the module. Errors discovered wh
ile coding different modules or during the
partial testing of
product after each implementation and
final testing will be documented and presented to the
group for correction
.

5.5


Review and Audits

Review and audits will be addressed in quality assurance pla
n.



A Review and Audits Plan is to be developed according to the recommended standards of the educational
department. Reviews and Audits plan presupposes cyclic review of the current state of each developed
module and its compliance with the project’s objec
tives. The schedule of review and audits is flexible
and will be created according to the needs during the process of project development.

5.6


Problem Resolution Plan

All problems must be reported to the project manager

and accordingly to the
supervisor.


5.6.1

Problem prioritizing

Detected problems should be prioritize as critical,

high,
medium

and low priority and should
be dealt with as soon as possible.



Project proposal


16

Appendix A


ID


Task Name


Duration

Start/Finish

1


Team formation



06
-
Mar
-
12

2


Making communication

plans



06
-
Mar
-
12

3


Creating documentation repository



12
-
March
-
12

4


Building basic work breakdown
structure



21
-
Mar
-
12

5


Identifying The project Nature



21
-
Mar
-
12

6


Allocating activities to staff



21
-
Mar
-
12

7


Detecting Tools required





8


Acquiring Software needs



23
-
Mar
-
12

9


Creating Software Repository
(backup & Share)



25
-
Apr
-
12


Figure
6
: Project over view


Project details is inserting in a Microsoft project file for better management and
accessibility.



Project proposal


17

Appendix B: Tender bid















Giants Studio


The Australasian Quaternary Association Webpage

Project Proposal


Team Members


Mohsen R
EZAEI

Sanat T
HOMAS

Ying L
I

Rayed Mohammed ALSABHAN



20

March 2012

School of Information
Technology and Engineering


University of Ballarat


Content

1.

Cover letter

................................
................................
................................
.......................

19

2.

Project introduction

................................
................................
................................
..........

20

2.1

Project title

................................
................................
................................
................

20

2.2

Project
details

................................
................................
................................
............

20

3.

Client information
................................
................................
................................
.............

20

3.1

Client’s initial requirements

................................
................................
......................

20

3.2

Client detail

................................
................................
................................
...............

20

4.

Team introduction
................................
................................
................................
.............

21

4.1

Team members information

................................
................................
......................

21

Name

................................
................................
................................
................................
.....

21

Mobile Phone

................................
................................
................................
........................

21

Email address

................................
................................
................................
........................

21

4.2

Skills, roles and responsibilities

................................
................................
................

21

5.

Reasons for consideration

................................
................................
................................
.

22

6.

Declaration
................................
................................
................................
........................

23




1.

Cover letter


20 March 2012

Shamsheer Syed

Room T160

School of Information Technology and Mathematical Sciences

University

Drive

Mt Helen Campus

VIC 3353


RE: Tender Proposal for Australasian Quaternary Association Webpage Project


Dear Mr Syed,


The following document is an official expression of interest of our project team to develop a
solution for the Australasian Quatern
ary Association Webpage.

Giants Studio has five members; all having a great passion to deliver what is required for this
project. Giants Studio is an enthusiastic team that would be eager to work on this project. Please
make your decision to accept our tea
m’s proposal so that we can begin to work on this project
immediately.


Giants Studio humbly thanks you for your consideration and looks forward to meeting you in
person.


Yours Sincerely,

Mohsen Rezaei

Giants Studio Project Manager

mr8362@hotmail.com



2.

Pro
ject introduction

2.1


Project title

Australasian Quaternary Association Webpage

2.2


Project
details

Type of Project: Web page and Database System

Platform: IBM PC

Project Description: the
Australasian Quaternary Association (short for AQUA), is a
small scholarly

association, currently have around 250 members. Australasian
Quaternary Association Webpage had been created for 12 years ago and badly out
of date. Every member’s information is still on paper and has to take a long time to
collect their members’ applica
tion form, and they also lost contact with a number of
members because they have changed addresses.

Now Australasian Quaternary Association needs to update their webpage, create a
new database system for their members, and make secure online payments for r
enew
membership status.



Additional comments from Australasian Quaternary Association Webpage: due date
of product delivery: May 31, 2012.



Current webpage: www.aqua.org.au



3.

Client information

3.1


Client
’s

initial
requirements

Australasian Quaternary
Association Webpage needs a new database to manage a
membership system and update current webpage, and available online payments.

3.2


Client detail

Name:
Jessica Reeves

Email Address:
j.reeves@ballarat.edu.au


P
hone contact number: 0425 772 505

Postal Address: Centre for Environmental Management

SITE

University of Ballarat

PO Box 663

Ballarat VIC 3353

















4.

Team introduction

4.1

Team members information



4.2

Skills, roles and responsibilities

4.2.1. Mohsen Rezaei

Skills
:



Organizational and communication skills (Planning, scheduling and writing
reports);



Designing skills (Corel Draw, InDesign, Flash);




Database knowledge (Access, SQL server);




Networking skills


Interest
: Research, Networks,
Multimedia and Database


Roles and responsibilities
: Project manager, Client liaison manager

Mohsen has to manage and schedule team efforts, distribute workload to team
members according to their skills and capabilities and time table which leads
Giants S
tudio to meet the client’s need.

Mohsen is managing the resources and researching materials for the
knowledge that needs to be learnt for the project accomplishment.



Academic Qualifications:

o

2010


2012: Currently undergoing Masters of Information Technolo
gy (4th
semester), University of Ballarat, Australia.



4
.
2.2. Sanat Thomas



Skills:
Communication, Listening, Writing reports, reviewing materials,
Organising



Interest
: Multimedia, Database, Java, C and C# programming, Mobile device
programming, gaming

Name

Mobile Phone


Email address

Mohsen Rezaei

0401348908

mr8362@hotmail.com

Sanat Thomas

0423947720

sanatthomas@gmail.com

Ying Li

0423467484

tarely@163.com

Rayed
Mohammed
ALSABHAN

0403120059

rayed_sabhan@hotmail.com





R
oles and responsibilities
: Database webpage designer



Academic Qualifications:

o

2006


2010: Bachelor of Technology in Electrical and Electronics
Engineering, National Institute of Technology, Hamirpur, India.

o

2010


2012: Currently undergoing Masters of Information Technology (4th
semester), University of Ballarat, Australia.




4.2.3. Ying Li



Skills
: Scheduling, Analysis, Planning, Interface design.



Interest
: Multimedia, Database



Roles and respon
sibilities
: Record keeping, documenting, secretary,
webpage designer.

Ying has the responsibilities to note down the proceedings of all upcoming
meetings of the team in work towards the completion of the project. She
would also be actively involved in webp
age and database design.



Academic Qualifications:

o

2010


2011: Graduate Diploma of Information Technology,
University of Ballarat, Australia.

o

2011


2012: Currently undergoing Masters of Information
Technology (
4th

semester), Univer
sity of Ballarat, Australia.


4.2.4.
Rayed Mohammed Alsabhan




Skills
: Designing technical solutions, analysis, testing software, Organising.



Interest
: Java
Programming, Database, Multimedia, Electronic Commerce,
Gaming


using game engines



Roles and responsibilities
: document reviewer, business analyst, database
designer, Programmer.



Academic Qualification
:

o

Advance diploma from Swinburne University.

o

Associated diploma from Riyadh Technical College.

o

Training certificate

from the College of

Technology

in Riyadh
(three

months study)

o

Bachelor of Information Technology (to be completed June 2012).



5.

Reasons for consideration



All team members have already d
iscussed some solutions that might be devised to
satisfy the client. The project manager would plan the schedule and have the weekly
meeting to prepare the documentation. If accepted, our group is eager to begin working
on this project.



Our team has great
passion for completing this project to a high degree of quality to
fulfil the client’s needs. We believe that developing a solution to this project is going to
take our cooperation, dedication, team work spirit and our diverse range of skills
.







6.

Declarat
ion


Declaration:



The information of Giants Studio provided in this document is true.



Giants Studio will do the best of all members’ skills and abilities and meets the client’s
requirements on time.



All team members are agreeing to work together as a team.



All team members will follow team processes and complete all tasks.


Name

Signature

Date

Mohsen REZAEI



Sanat THOMAS



Ying L
I



Rayed Mohammed ALSABHAN































Appendix C: Work breakdown structure

The following table is
breakdown tasks of whole project.

Mileston
e

Code

T
ask

N
a
m
e

D
u
rati
o
n


1

I
n
i
t
i
a
t
ion

3

d
a
y
s


1
.1

T
e
a
m

format

1

da
y


1
.2

Sel
e
ct

p
r
o
je
c
t topic

1

da
y


1
.
3

Prepare

t
ende
r

proposal

1

d
a
y


2

P
roject Planning



2
.
1

Complete the draft of tender proposal

2

days


2
.2

Internal

m
e
e
t
i
n
g

of tender proposal

1

da
y

M

2.3


Deliver tender proposal

1 day


3

C
r
ea
te
p
r
o
j
e
c
t

ma
na
g
e
m
en
t

p
l
a
n (SPMP)

7
d
ay
s


3.1

Prepare SPMP

4

days


3.2

P
r
es
e
n
t

d
ra
f
t

of
SPMP

2

day
s

M

3.3

D
el
i
v
er

SPMP

1

day


4

Project Ex
e
c
u
t
i
on

61
d
a
y
s


4.1

An
al
y
se

7

d
ay
s


4.2


P
r
odu
c
e

So
f
t
w
a
r
e

R
eq
u
ir
e
me
n
t

Spec
i
f
i
c
a
t
i
o
n

5

d
ay
s


4.2.1

Receive

clie
n
t

r
eq
u
ir
e
m
ents

1

day


4.2.2

Devel
o
p

s
o
l
u
t
i
o
n

o
v
e
r
v
i
e
w
s

1

d
a
y


4.2.3

P
r
epa
r
e

p
r
e
sentat
i
o
n

1

day


4.2.4

P
r
es
e
n
t

d
ra
f
t

SRS

1

day

M

4.2.5

D
el
i
v
er

SRS

1

day


4.3

Produce SDD

3

d
ay
s


4.3.1

Prepare draft

o
f
S
D
D

2

day
s

M

4.3.2

D
el
i
v
er

S
D
D

1

day


P
a
g
e

1
8
o
f

30






4.4

I
mpleme
n
t

46

d
ay
s


4.4.1

I
n
itia
l
ize

s
o
u
r
c
e

c
o
n
t
r
o
l

s
o
l
u
t
i
o
n

1

day


4.
4.2



Design system structure

1
2

d
ay
s


4.
4.2.1

I
n
t
e
rfa
c
e

2

days


4.
4.2.2

M
a
j
o
r
functions


10

days


4.
4.3



Design system database

24

d
ay
s


4.
4.3.1

User

aut
h
entic
a
ti
o
n

8

days


4.
4.3.2

Main window

and coding

16

days


4.
4.4



T
e
st
i
n
g

20
d
a
y
s


4.
4.4.1

Interface

t
es
t
i
n
g

10

days


4.
4.4.2

User

ac
c
e
p
tance

t
e
s
ti
n
g

5

days


4.
4.4.3

S
y
s
t
e
m
/
i
m
p
l
e
m
ent
a
t
i
o
n

t
e
sting

5

days


4.
5

Ma
i
n
t
a
i
n

1
0
d
a
y
s


4.
5
.1

E
m
ail su
pp
o
r
t

9

day
s


4.
5
.
2

D
o
c
u
m
ent
a
ti
o
n

a
m
en
d
m
ents

1

day
s


4
.
6

Cl
o
s
i
n
g

7

d
a
y
s


4
.
6
.
1

P
r
o
j
ect

r
ep
o
r
t

5

days

M

4
.
6
.
2

P
r
o
j
ect

p
r
es
e
n
t
a
ti
o
n

1

day


4
.
6
.
3

T
eam

dismissed

1

day