SPMP - student.atilim.edu.tr

weaverchurchSoftware and s/w Development

Aug 15, 2012 (5 years and 3 months ago)

475 views




SOFTWARE PROJECT MANAGEMENT PLAN

RESOURCE CLOUD FOR EDUCATI
ON

Version 1.1


14/09/11

TEAM
-
06

http://student.atilim.edu.tr/~sproject1128


ATILIM UNIVERSITY


DEPARTMENT OF COMPUTER ENGINEERING



SUBMITTED TO:
Mohamma
d Rehan



PREFACE


In SPMP document,
purpose, scope, objectives and detailed plan of project are described
in
detail. The assumptions and c
onstraints are decided and discussed by group members and supervisors.
Project deliverables are estimated
by group members. Schedule
and b
udget s
ummary of project is
determined by group members.

P
roject of group members is

about roles and responsibilitie
s of in the project. Roles and
r
esponsibilities will be given base on experiences and intere
sts of group members. We will estimate

how

much work done in this time.

After, we

estimate how much work needed to finish our project and every group me
mbers can
calculate their
work
ing

times.

Finally,
FP and COCOMO will be calculated but
this calculation may not be
estimated

well,

so we will identify

risk management plan. Risk Management Plan will be searched step by step in
detail and all security problems will be shown.














List of Tables

:

Table 1



Project Deliverables…………………………………………………
……………..
6
-
7

Table 2



Roles Table
…………………………………………………………
………….

10

Table 3



Roles and Responsibilities Matrix …….
……………………………

…………….
11

Table 4



Product Function I/O & Summary &Function Point Metrics
…………
…………..
12
-
13

Table 5


Value Adjustment Factor …..
……………………………………
………………..
13




Table 6

-

Effort e
stimation……………………………………………………
………………
15

Table 7
-

Resource Allocation for Work Activity ……………………………

18
-
19

Table 8

-

Resou
rce Allocation for Preparing PS

……………………………

19

Table 9

-

Reso
urce Allocation for Preparing IP

………………………………

19
-
20

Table 10

-

Reso
urce Allocation for Preparing SPMP
……………………………
20

Table 11

-

Resour
ce Allocation for Preparing SRS

…………………………

20

Table 12

-

Resource Allocation

for Preparing
SDD
………………
…………

20
-
21

Table 13
-

Resource Allocation for coding
………………..
…………………… 21

Table 14

-

Resource Allocation for Preparing testing
……………
……
…………… 21

Table 15
Resource Allocation for demo
……………………………………

……
21

Table 16

Schedule and budget allocation for definition PS
…………………

….
22

Table 17
Schedule and budget
allocation for preparing IP
……………………….22
-
23

Table 18
Schedule and budget allocation for preparing SPMP
…………………23

Table 19
Schedule and budget allocation for preparing SRS…………………….23

Table 20
Schedule and budget allocation for preparing SDD…………………….24

Table 21
Risk Management……………………………………………………..26,27

Table 22
Product Time Schedule…………………………………………………28

Table 23
Project Delivery Schedule Table…………………………………………
29


Table of Contents

Preface
………………………………………………………………

1

List of Tables
……………………………………………………2
-
3
-
4

Table of Contents
………………………………………………….

3

1. Overview
………………
…………………………………………

5


1.1.

Project Summary
……………………………………………

5



1.1.1.

Purpose, Scope and Objectives
………………………

5




1.1.1.1.
Purpose
…………………………………..

5

1.1.1.2.
Scope
…………………………………..

5

1.1.1.3.
Objective
s
…………………………………..

5



1.1.2.

Assumptions and Constraints
………………………..

5
-
6



1.1.3.

Project Deliverables
………………………………..

6



1.1.4.

Schedule and Budget Summary
……………………..

7


1.2.

Evolution of SPMP
………………………………………

7

2. References
……………………………………………………..

8

3.
Definitions
………………………………………………………

9

4. Project Organization
………
…………………………………..

10


4.1.

External Interfaces
…………………………………………

10


4.2.

Internal Structure
………………………………………….

10


4.3.

Roles and Responsibilities
…………………………………

10

5. Managerial Process Plans
……………………………………

12


5.1.

Startup Plan
…………
……………………………………

12



5.1.1.

Estimation Plan
…………………………………..

12



5.1.2.

Staffing Plan
……………………………………15
-
16



5.1.3.

Resource Acquisition Plan
…………………………

16




5.1.3.1.
Hardware Acquisition….
…………………..

16




5.1.3.2.
Soft
ware Acquisition….
…………………..

16




5.1.3.3.
Transportation and Facility Acquisition
……..

16




5.1.3.4.
Constraints on Resource Acquisition Plan
……..

17



5.1.4.

Project Staff Training Plan
………………………….

17


5.2.

Wo
rk Plan…………………………………………………………….17
-
18



5.2.1.

Wo
rk Activities…………………………………………......17
-
18



5.2.2.
Resou
rce Allocation…………………………………………

18



5.2.3
.

Budget
& Schedule Allocation………………………………
22


5.3.

Contr
ol Plan…………………………………………………………..

24



5.3.1.

Requirem
ents Control Plan…………………………………24
-
25



5.3.2.

Sched
ule Control Plan………
………………………………25



5.3.3.

Budget

Control Plan……………………………………..

25



5.3.4.

Quality

Control Plan……………………………………..

25



5.3.5.

Re
porting Plan……………………………………………

25



5.3.6.

Metrics C
ollection Plan…………………………………..

25


5.4.

Risk Mana
gement Plan…………
……………………………
………

26


5.5.

Closeout Plan……………………………………………………….

27

6. Technical Process Plans
…………………………………………

28


6.1.

Process M
odel…………………………………………………......

28


6.2.

Methods, Tools
, and Techniques…………………………………

29


6.3.

Infrastru
cture Plan ………………………………………………

29
-
30


6.4.

Product Ac
ceptance Plan…………………………………………

30

7. Supporting Process Plans

……………………………………

31


7.1.

Configuration
Management Plans……………………………….

31


7.2.

Verification and

Validation Plan…………………………………

31


7.3.

Document
ation
S
hedule Plan………………………………………
….31


7.4.

Quality As
surance Plan………………………………………….

31


7.5.

Reviews a
nd Audits……………………………………………..

31


7.6.
Problem Re
solution Plan…………………………………………

32


7.7.

Subcontractor

Management Plan…………………………………

32


7.8.

Process Imp
rovement Plan…………………………………………

32

Appendix
…………………………………………………………34
-
35

1.
Overview

In this part, executive summary of “Resource Cloud for Education” will be given which


contents an overview of the project. These contents are definitions, deliverables, plans, a


strategy for

t
he evolution

of this plan and list of references will be given
.


1.1

Project Summary

1.1.1 Purpose, Scope, and Objectives


1.1.1.1 Purpose

The purpose of the “Research Cloud for Education” will be provided to use the cluster and


communicating between computers
in visual area. A
lso, we will

keep
on remote servers and data




on

a single ser
ver and also
distributed servers can hold on.



1.1.1.2 Scope

The scope of the RCE is

to use
the cluster and rea
ch the data such as

music,
movie and picture

etc..
document
s are loaded

from one computer to other computers. Nowadays, many companies use the
cloud computing, but for using the cloud computing, there are many security systems.


1.1.1.3 Objectives

* Have lower cost.


* Have high come at able.


* Use indepentdent platform.


* Open ınternet access from every where.


* Have not need back up and maintanance process.


* Easy to use resourc
e offers tracking and reporting.



1.1.2 Assumptions and constraints


It is assumed that,

*
Users can use

connect to other computers by i
d and password .


*
Cloud computing will be used high security levels.


*
Users can use whichever get at their pc.



Constraints,

Cloud computing have not constraints, but the only constraint is security so cloud


comput
ing should have high security so info will been hidden.




1.1.3 Project Deliverables




Deliverable

Description

Deadline

SPMP

Sof
t
ware Project Manag
e
ment
plan

OCT.17,2011

SRS

Software Requirements
Specification

NOV.11,2011

SDD

Software Design
Description

DEC.5,2011

Revised SPMP

Draft protype re
v
iew

In
Sof
t
ware Project manag
e
ment
plan

there

will be
some changes
and additions and the
n

our
supervisor will evaluate

this
document
.


DEC.30,2011

Revised SRS

Presantation

In
Sof
t
ware Requirements
Spe
cification

there

will be

some

change
s and additions and the
n

our supervisor will evaluate

this
document
.


Jan.18.19.20,2012

Revised SDD

In
Sof
t
ware Design Description
will be

some

change
s

and
add
itions

and the
n

our supervisor
will evaluate

this document
.

FEB.27,2012

STD

Code re
v
iew 1

In Software Test Documentation

We will write code for our project,
we will test these

code
s. I
f we find
mistake
s
,

we will define mis
take
and
these codes are revised.


MAR.19,2012

Code re
v
iew 2

Codes are
revised second time.

APR.16,2012

Revised STD

Code re
v
iew 3

Codes are revised lastly.

MAY.21,2012

Presantation

Final version of docs

All the documents are looked up
and all team members will prepare
for presentation.

JUNE.13,14,15,2012




TABLE 1
-
Project Deliverables


1.1.4 Schedule and Budget Summary:

The schedule wil
l

be estimated for our Project. We will

do

not

have certain estimation in
experiment


so we will

calculate approximate dat
e.
And all group members are in department of c
omputer


engineering. When
Project will be developed
, we
will

have an exam, homework and project. Project


schedule will be
depend
ed on supervisor’s deadline. The budget summary will not been in this part bu
t


budget plan will be make in this report

chapter 5.3.3.



1.2. Evolution of SPMP


Now Project(cloud computing) is

at

development phases. Until Project have been progress
ed
, we


will add information or change in SPMP document.






2.
REFERENCES


1.
http://www.gercekportal.com/2011/09/11/cloud
-
computingbulut
-
bilisimnedircloud
-

computing
-
faydalari
-
nelerdir/


2
.
http://www.microsoft.com/en
-
us/showcase/details.aspx?uuid=a6baab18
-
e830
-
4851
-
8c6b
-



f764eb67477b


3.
http://www.hakandemirel.com.tr/blog/cloud
-
computing
-
nedir


4.
http://techimind.blogspot.com/2010/09/waterfall
-
model.html


5.Web Site of
Compe 491,


http://www.atilim.edu.tr/~aakca/2011/491_492/refs.html#references
,


accessed on October 11




































3.DEFINITI
ONS


RCE

Resource Cloud for Education


COCOMO

Constructive Cost Model


FP

Function Points


DB

Database


GUI

Graphic User Interface


HTLM

Hypert Markup Language


IE


Internet Explorer



I/P

Iınput/Output


IP

Initial Plan


KLOC

1000 Lines Of Code


KU

Knowledge Unit


LOC

Line of Code


SDD

Software Desing Description


SPMP

Sofware Project Management Plan


SRS

Sofware Requirements Specification


SW

Sofware


HW

Hardware


WBS

Work Breakdown Structure

RELY
Required Software Reliability Cost Driver

DATA

Database Size Cost Driver

CPLX

Product Complexity Cost Driver

RUSE

Developed for Reusability Cost Driver

DOCU

Do
cumentation Match to Lifecycle Needs Cost Driver



4. Project Organization


4.1. External Interfaces

This project is senior project. Senior project will be u
sed
. Our
goal for project is to use this system


between system members who have right of loginning the system
will have one external interface.


Thanks
to this external interface

access
ing a function on from a

computer to another computer by


login
n
ing id and password. So
other computers will access

a
function.


4.2
. Internal Interfaces

Our Project will have one internal interfa
ce and this system will not seen by other

users.

Users will not see

this thing

which name
’s

is cluster. Cluster will come datas this dates will be

collect
ed

in
cluster,

so users will
communicate with

other c
omputer and users will work whatever they


want.

4.3. Roles and Responsibilities

Project manager:

Responsible for all group members and
administrate


Project.


Reporter
: Responsible which preparing SPMP, SRS and SDD o
f Project.


Contact person:

Responsible communication group members and arrange meeting


time.


Database designer
: Responsible project of database application design.


Tester:

Responsible for test data and all documants.


Researcher:
Responsible to
research about ınformation of Project.


Web designer:

Responsible design web of the Project useJava platform.


Web interface designer:

Responsible to developt interface of web.


Web Publisher:

Responsible to update
and announcement of

p
roject.


Table 2



Roles Table












Didem DAL

Yasemin AKSU

Kevser İYİ

䵵jt慦愠䑥湩z
aro单k

Project
Manager




X

Reporter

X

X

X

X

Contact Person

X

X



Database
Designer


X

X

X

X

Tester

X

X

X


Researcher

X

X

X

X

Web Designer




X

Web Interface
Designer

X

X

X

X

Web Publisher



X


Table 3



Roles and Responsibilities Matrix




















5. Managerial Process Plans

5.1. Start up Plan


5. chapter will inculude estimation plan, staffing plan, resource
acquisition plan,
project staff training plan.

5.1.1. Estimation Plan


When proje will be begin, we will not best estimation plan in our project. Function point


process will be use in our project and than we will use “COCOMO” model in this project so
,



we will calculate what effort in this project.




Function Points (FP)

We will calculate function point so we will determine dates for this project.



Weighting Factor

Parameter

Count

Factor

Total

External Inputs

User Name

Password

Real
Name

Email Address

Old Password

New Password

Sync Folder Select

Sync Locale

Choose User

Files Button Set

3

3

3

3

3

3

3

4

6

3

34

External Outputs

Synchronization Status

Disk Usage Statistics

Free Disk Space

Synchronization Messages

Validation Messages

5

7

4

5

4

4

29

External Inquiries

Synchronized Folders

Shared Folders

Allowed Users

Conflicted Files

3

3

3

4

19

Current Sessions

6

Internal Logical Files

Synchronized Folders List

Last Update Times

Last Hash Values

Conflicted Files List

7

10

10

15

42

External Interface Files

Remote Shared Files

10

10


134


TABLE 4
-
Product Function I/O Summary &
Function Point Metrics



Value Adjustment Factors

No

Criteria

Weight

Explanation

1

Backup and recovery

4

All file system and
database must be backed up.
Disk storage can be rescued on
-
the
-
fly.

There is no need to any backup at clients.

2

Data Communication

5

All process runs on Internet.

3

Distributed data processing

5

Many number of servers can be worked together.

4

Performance

3


5

Heavily used configuration

3


6

Online data entry

5

All process runs on Internet.

7

End user efficiency

3


8

Online update

5

All process runs on Internet.

9

Complex processing

3


10

Internal processing

3


11

Code re
-
usability

2

All
server will be coded in POJOs. There is no
need to extra work.

12

Conversion and installation

4

Client application must be cross platform and
ready to install by end users.

13

Multiple installations

4

Server application can be installed at many
number of

servers.

14

Facilitate change

3



Total Degree of Influence

fi)

52



TABLE 5
-

Value Adjustment Factors








COCOMO


FP = count total * [0.65 + 0.01 * Ʃ(Fi)]


FP = 134 * [0.65 + 0.01 * 52] = ~157


LOC = FP
* language factor


Assume that the language factor of C++ is
53
;


LOC = 235 * 53 = 8321



To estimate project effort, person
-
months equation of COCOMO II is being used.


PM = A * Size ^ E * sum(EM)


Where
A = 2.94

(for COCOMO II.2000) and calculating E
(scale factors) scale factor equation is
being

used.


E = B + 0.0.1 * sum(SF)


G

Where

B = 0.91

(for COCOMO II.2000)



PREC


3.72

FLEX


3.04

RESL


4.24

TEAM


4.38

PMAT


4.68

SUM


20.06





E = 0.91

+ 0.01 * 20.06 = ~1.11


To calculate the product of the EMs,


RELY


1

DATA


1.14

CPLX


0.87

RUSE


1

DOCU


1.11

Product


1.1




A = 2.94

Size = 8321/1000 = 8.321

E = 1.11

Product of
EMs = 1.1




PM = 2.94 * 8.3 ^ 1.11 * 1.1 = ~34 Person Months



To estimate time for development, the initial baseline schedule equation is being used


TDEV = [C * (PM)^(D+0.2*(E
-
B))]*SCED / 100



where
C = 3.67
,
D = 0.28
,
B = 0.91

,
SCED = 1

(Nominal)


TDEV = 3.67 * 34 ^ 0.32 * 1 = ~11 months


As a result,


Source lines of code

8321

Effort

34 Person
-
months

Time

11 Months





Activity

Work Days

Estimated Human Effort
Time (hour / man)

Defining Problem Statement


3

9

Initial Planning

4

20

Reviewing of IP

3

9

SPMP Documenting

10

60

Reviewing of SPMP

5

9

SRS Documenting

15

65

Reviewing of SRS

5

10

SDD Documenting

15

60

Reviewing of SDD

5

10

Coding and Testing

20

90

DEMO
Presenting

4

5

Total

89 days

347 hour/man


Table 6
-

Effort estimation

5.1.2. Staffing Plan

Project is created by 4 senior project students. Students are always contact with each other. Life cycle
of the pproject is 2 semi
-
annual so, one academic year. Anaylsis and research are created by in the firs
semi
-
annual. Coding and design are created b
y in the second semi
-
annual. If the project will be
finished;



Team members will study hard.



Team members will search the project attributes.



Team members will have an experiences.



Team members will know experienceand the stages of development.

5.1.3
Resource Acquisition Plan


5.1.3.1 Hardware Acquisition


The hardware equipments of project are our personal computers. Also we have a designing web
interface of login system. There is a cluster, so our files are storaged in the cluster.

For personal comp
uters



Min. Intel Core2 2.53 GHz



Min.

3072 MB
RAM



Ethernet card


recommended screen resolution of 1366 x 768

For Database Server



Oracle


5.1.3.2 Software Acquisition


We will use this lower part software product.




MS project



NetBeans IDE



MS office 2007



Oracle


5.1.3.3 Transportation and Facility Acquisition

Atılım unıversıty is not city center. Our home are far away to the Atılım university so transport is
very important problem for our members especially in th
e winters. Group members will provide car
and public transportation.


5.1.3.4 Constraints on Resource Acquisition Plan


Team members will research books, internet, etc. So, all team members of the project will do
the project documents.

5.1.4. Project Staf
f Training Plan

This project will include web application, cluster and network. We will use Java technologies, Oracle
and C++ in this project group members are not take java technologies lessons,
so each members will
develop

our skills.

We will do meetings to exchange information about to the project.

5.2. Work Plan

5.2.1. Work Activities

1 Defining Problem Statement


1.1

Researching the problem

1.2

Defining problem and our scope

1.3

Determination of requirements

1.4

Documentation

1.5

Summarizing problem
statement


2

Intial Planning

2.1

Project describing

2.2

Project planning

2.2.1

staff planning

2.2.2

resource planning

2.3

reviewing initial planning

2.4

approving initial planning


3

Preparing SPMP

3.1

Defining responsibilities

3.2

Schedulimg & determination of process model

3.3

Technial planning

3.4

Documentation of SPMP

3.5

Building website of Project

3.6

Reviewing SPMP

3.7

Approving SPMP

4

Preparing SRS

4.1

Meeting with customer

4.2

User group determining

4.3

Defining product functions

4.4

Behavioral requirements specifiying

4.5

Non
-
behavioral requirements specifying

4.6

Documenting

4.7

R
eviewing SRS

4.8

Approving SRS


5

preparing SDD

5.1

SDD basic concepts

5.2

Database design

5.3

İnterface design

5.4

Algorithm design

5.5

Documentation

5.6

Reviewing SDD

5.7

Approving SDD


6

coding

6.1

web service applicaiton coding

6.1.1

data Access objects designed by database design

6.1.2

enterprise
services BUSes coded with Java EE

6.1.3

soap or restful services created with apache Axis2

6.1.4

file transfer protocol implemented without using web services


6.2

desktop applicaton coding

6.2.1

user interface design

6.2.2

web service client design

6.2.3

algorithm to track file changes


7

testing

7.1

unit test for both web service and desktop application

7.2

selenium like robot test


8
demo

8.1 preparing of demonstration

8.2 demonstration

8.3 reviewing of demonstration

8.4 approving of demonstration




5.2.2

Resource Allocation



WORK
ACTIVITY


REQUIRED SKILLS


BASED ON


initial planning

Knowledge of IEEE Std,
Estimation Techniques

IEEE Std. 1058
-
1998

Preparing SPMP

Knowledge of IEEE Std and
Estimation Techniques,
Planning And Coordination

IEEE Std. 1058
-
1998

Preparing SRS

SW Engineering, Knowledge
of DFD & ER, Human
IEEE Std. 830
-
1998,facetoface
-
email

interaction

Preparing SDD

SW Engineering

IEEE Std. 1016
-
1998

C
oding

Knowledge Of Java
Programming Language
,Knowledge Of c++
programming language

IEEE Standards

Testing

Knowledge of control
engineering&testing
techniques

IEEE Standards

Demo

System Engineering

IEEE Standards

Reviewing & Approving of
Work Activities

Knowledge of Review
Techniques

IS502 Standards


TABLE

7
-
Resource allocation for work activity





WBS

WORK
PACKAGES

SW TOOLS

HUMAN
RESOURCES

HW
RESOURCES

1.

Defining problem
statement

-

Team

-

1.1

Researching the
problem

-

Team

-

1.2

Defining problem
and our scope

MS Office
2010
,
MS Project

Team

PC and
Peripherals

1.3

Determination of
requirements

-

Team

-

1.4

Documentation

MS Office

2010
,
MS Project

Team

PC and
Peripherals

1.5

Summarizing
problem
statement

-

-

-


TABLE

8
-
Resource Allocation for
Preparing PS


WBS

WORK
PACKAGES

SW TOOLS

HUMAN
RESOURCES

HW
RESOURCES

2.1

Project describing

Ms Office

2010

Team

PC and
peripherals

2.2

Project planning

Ms Office
2010

Team

PC and
peripherals

2.2.1

Staff planning

Ms
Office

2010

Team

PC and
peripherals

2.2.2

Resource
planning

Ms
Office

2010

Team

PC and
peripherals

2.3

Reviewing
planning

Ms
Office

2010

Team


2.4

Approving
Ms
Office

2010

-

-

planning

Table 9
-

Resource Allocation for
Preparing IP



WBS

WORK
PACKAGES

SW TOOLS

HUMAN
RESOURCES

HW
RESOURCES

3.1

Definining
responsibilities

-

Team

-

3.2

Scheduling &
determination of
process model

Ms
Office
2010

Team

PC and
Peripherals

3.3

Technical
planning

Ms Office

2010

Team

PC and
Peripherals

3.4

Documentation of
SPMP

Ms Office

2010

Team

PC and
Peripherals

3.5

Building website
of
Project

H
tml

Team

PC and
Peripherals

3.6

Reviewing of
SPMP

-

Team

PC and
Peripherals

3.7

Approving SPMP

-

-


Table 10
-

resource allocation for
Preparing
SPMP



WBS

WORK
PACKAGES

SW TOOLS

HUMAN
RESOURCES

HW
RESOURCES

4.1

Meetings with
customer

-

Team

-

4.2

User group
determining

Ms Office

2010

Team

PC &
Peripherals

4.3

Defining product
functions

Ms Office

2010

Team

PC&Peripherals

4.4

Behavioral
requirements
specification

Ms Office

2010
,
Java EE

Team

PC&Peripherals

4.5

Non
-

Behavioral
requirements
specification

Ms Office

2010

Team

PC&Peripherals

4.6

D
ocumentation

Ms Office

2010
,Java EE

Team

PC&Peripherals

4.7

Review of SRS

-

Supervisor and
customer

PC&Peripherals

4.8

Approval of SRS

-

-

PC&Peripherals

TABLE 11
-
Resource A
llocati
on for P
reparing SRS



WBS

WORK
PACKAGES

SW TOOLS

HUMAN
RESOURCES

HW
RESOURCES

5.1

SDD Basic
Concepts

Ms Office

2010

Team

PC and
peripherals

5.2

Database design

Ms Office

2010
,
oracle

Team

PC and
peripherals

5.3

İnterface Design

䵳⁏ffice

㈰OM

qe慭

偃⁡湤
灥pi灨pr慬s

㔮R

Alg潲it桭⁄敳ign

䵳⁏ffice

㈰OM

qe慭

偃⁡湤
peripherals

5.5

Documentation

Ms Office

2010
,
Java EE

Team

PC and
peripherals

5.6

Review of SDD

-

-

-

5.7

Approval of SDD

-

-

-

TABLE
12
-

Resource A
llocation for
Preparing
SDD



CODING

WBS

WORK PACKAGES

SW
TOOLS

HUMAN
RESOURCES

HW
RESOURCES

6.1

Web service application coding

C#.net

Team

PC &Peripherals

6.1.1

Data access objects designed by db
design

oracle

Team

PC &Peripherals

6.1.2

Enterprise service buses coded with
java

Java EE

Team

PC &Peripherals

6.1.3

Soap or restful services

Apache
axis2

Team

PC &Peripherals

6.1.4

File transfer protocol implementation
without using webservices


Team

PC &Peripherals

6.2

Desktop application coding

C++ QT

Team

PC &Peripherals

6.2.1

User interface design


Team

PC &Peripherals

6.2.2

Web
service client design

XML,
c++QT

Team

PC &Peripherals

6.2.3

Algorithm to track file changes

Java EE

Team

PC &Peripherals

TABLE 13:Resource Allocation for Coding


TESTING

WBS

WORK PACKAGES

SW TOOLS

HUMAN RESOURCES

HW
RESOURCES

7.1

Unit Test

Java
EE,c#.net

Team

PC &Peripherals

7.2

Robot test

Selenium

Team

PC &Peripherals

Table 14:

Resource Allocation for preparing Testing

DEMO

WBS

WORK PACKAGES

SW TOOLS

HUMAN
RESOURCES

HW
RESOURCES

8.1

Preparing of
demonstration

MS Office

2010

Team

PC &
Peripherals

8.2

D
emonstration

MS Office

2010

Team

PC &Peripherals

8.3

Reviewing of demo

-

Team

PC &Peripherals


8.4

Approving of demo

-

-

-

Table 15:

Reso
urce Allocation for preparing demo



5.2.3

Budget
&Schedule

allocation:

Work activities are stated

in the section 5.2.1 and taken as a base of budget allocation. We determined
the salary of each team member as 10$/hour. We assumed that supervisor has no salary since he took
the role of customer. Budget and schedule allocation tables for each work activ
ity are shown below:


WBS

Work
Packages

Start Date

(M.D.Y)

End Date

(M.D.Y)

Work
Hour

People
Assigned

Cost

($)

1.1

Defining
problem
statement

10.02.2011

10.02.2011

1

Team

40

1.2


Researching
the problem


10.02.2011

10.02.2011

2

Team

80

1.3

Defining
problem and
our scope

10.02.2011

10.02.2011

2

Team

80




1.4

Determination
of requirements

10.02.2011

10.03.2011

2

team

160


1.5

Documentation

10.03.2011

10.03.2011

2

team

80


1.6

Summarizing
problem
statement

10.03.2011

10.03.2011

1

team

40

TABLE 16:Schedule and Budget Allocation for defining PS


PREPARING IP

WBS

WORK PACKAGES

START
DATE
(M.D.Y)

END
DATE
(M.D.Y)

WORK
HOUR/
DAY

People
ASSIGNE
D

COST
($)

2.1

Project Describing

10.04.2011

10.04.2011

2

Team

80

2.2


Project planning

10.04.2011

10.04.2011

2

Team

80

2.2.1

Staff planning

10.04.2011

10.04.2011

1

Team

40

2.2.2

Resource planning

10.04.2011

10.05.2011

1

Team

15

2.3

Reviewing
planning

10.05.2011

10.05.2011

2

Team

80

2.4

Approving planning

10.05.2011

10.05.2011

2

Supervisor

0

TABLE 17:
schedule and budget al
location for
Preparing IP


WBS

Work Packages

Start Date

(M.D.Y)

End Date

(M.D.Y)

Work
Hour

People
Assigned

Cost

($)

3.1

Defining
responsibilities

10.06.2011

10.07.2011

2

Team

160

3.2


scheduling
&WBS&
determination of
process model

10.07.2011

10.10.2011

3

Team

480

3.3

technical
planning


10.09.2011

10.12.2011

3

Team

480

3.4

documentation of
SPMP


10.10.2011

10.16.2011

5

Team

1400

3.5

building website
of project

10.13.2011

10.16.2011

2

Team

320

3.6

reviewing SPMP

10.16.2011

10.16.2011

3

Team

120

3.7

approving SPMP

-

-

3

Supervisor

0

TABLE 18. schedule and budget allocation for
Preparing SPMP


WBS

Work Packages

Start Date

(M.D.Y)

End Date

(M.D.Y)

Work
Hour

People Assigned

Cost

(YTL)

4.1

Meeting with
Customer

10.21.2011

10.21.2011

2

Team

80

4.2

User Group
determining

10.22.2011

10.25.2011

2

Team

320

4.3

Defining Product
Functions

10.25.2011

10.27.2011

4

Team

480

4.4

Behavioral
Requirements
Specification

10.28.2011

11.02.2011

2

Team

400

4.5

Non
-
Behavioral
Requirements
Specification

11.03.2011

10.05.2011

3

Team

360

4.6

Documentation

11.06.2011

11.12.2011

4

Team

840

4.7

Review of SRS

11.13.2011

11.13.2011

1

Team&Supervisor

40

4.8

Approving of
SRS

-

-

-

supervisor

-

TABLE 19:
schedule and budget allocation for
Preparing SRS





WBS

Work Packages

Start Date

(M.D.Y)

End Date

(M.D.Y)

Work
Hour

People
Assigned

Cost

(YTL)

5.1

SDD Basic
Concepts

11.14.2011

11.15.2011

4

Team

320

5.2

Database Design

11.15.2011

11.19.2011

5

Team

1000

5.3

Interface Design

11.20.2011

12.26.2011

10

Team

2800

5.4

Algorithms
Design

12.27.2011

12.02.2011

12

Team

7200

5.5

Documentation

11.15.2011

12.04.2011

4

Team

3200

5.6

Review of SDD

12.04.2011

12.04.2011

1

Supervisor&
team

40

5.7

Approval
of SDD

-

-

2

Supervisor

0

TABLE 20:
schedule and budget allocation for

Preparing SDD


Coding and testing process of Project are belong to second semester, so there is no budget estimated


for this semester. Budget for documentation and reporting

for PS, IP, SPMP and SRS

is calculated


only.



5.3 CONTROL PLAN


This part contains datum about how our team controls the Project and how
requirements, scheduling,


quality and reporting will be applied.


5.3.1 Requirements Control P
lan


Before
preparing SRS, all requirements will be searched from internet and also some interviews will


be done with customer who is our supervisor in this Project in order to get the nearly realistic data.


Because requirements are very important for imlementing a Project, we have to manage all ideally. If


any requirement needs to be added during the improvement of our Project, we will do the necessary


changes in requirements. These changes will result in

review of SRS. New scheduling and team


member allocation will be done accordingly. Process model of this Project is waterfall, meanly we do


not except any major changes in requirements , only small changes may occur.



5.3.2 Schedule Control Plan


W
e
have shown schedule of our Project

above
. All major and
mino
r
activities have start and end

dates



shown there. In addition, there will be meetings and interviews

with our supervisor, who are


customer also, in order to realize the progress of work done. Lastly we are expecting to finish the


p
roject by the

end of second semester. However , if any unexpected situation occurs about team


members, then our supervisor will be informed and new
plan will be applied in order to follow the


schedule we have done.





5.3.3. Budget Control Plan


Budget in our project is not measured in reality, however it is assumed to be there will be no risk at


budget control plan, assuming that it is like how

it is shown in the budget allocation plan.


5.3.4.
Quality Control Plan



since we have meetings before every and after every documentation, the quality control will be


provided by these meetings. So, if there is anything wrong, it can be easily seen wi
th the help of our


supervisor each team member and t
hen errors will be
corrected
.


5.3.5
. Reporting P
lan


Projects reports will be given as it is early mentioned in the Project deliverables chapter. The reports


will be published at our Project web sit
e, a hardcopy of the report will be given to the supervisor of the


Project and uploading in moodle. After the examination of supervisor, necessary changes to be done


will be started to our team. After corrections and republishing, an upper version of the report will be


given to supervisor. This process will continue until report is approved by committee of instructors.


5.3.6
. Metrics Collection Plan



Metrics collec
tion plan should be done in order to compare the things that we expect and we


have do
ne. This shows me
reliability of our team whether we have done our


responsib
ilities at the submission dates.




5.4. RISK MANAGEMENT PLAN



NAME

RISK

PROBBILI
TY

EFFECT

MITIGATIO
N

CONTINGENCY

Defining
requireme
nts

incorrect&insuffic
ient requirement

high

Cause resign
& re
-
implementati
on

Search in a
detailed
way&underst
and customer
clearly.

Ch
ange
implementation&de
sign

incorrect
requirements.

About
team
members

D
issagreement

medium

Cause failure
in Project

Respect must
be protected

If any seperation
occurs; then
continue to Project
with 3 or less
person


About
team
members

U
navailability

Low

Meetings
cannot be
hold so
reports will
not be on
time

By finding
common
hours or at
weekends we
can meet

Via
the
internet we
can meet at home
s


Reports

Reports may not
be in desired
quality

low

It causes
Project
delays.

By searching
in a detailed
way.

Correcting wrong
information more
study required on
repor
t
s.

Inter
face
design

Th
e wrong core
development
schema

and lack
of requirements

medium

May cause
insufficient
design.

To make a
good

design
have to make
more meeting

Redesign

Database
design

Incorrect design

medium

Project
failure

Ensure that
the
schema
designs
are
correct and
suitable and
also flexible.

Database needs to
be redesigned and
implemented.

















Staff training

Lack of
learning and
resear
c
h

Low

Project failure

Study and
research more
efficient,
spend
more
time about the
less aspect of
our
perspective

Start over
research and
training.

Testing
product

Team
members may
not understand
the source of
error, not have
enough time
to realize all
the tests.

L
ow

product may
not be process
properly

Testing results
should be
considered
and revised
care
fully.

Sufficient time
should be
assigned and all
members
should work on
it again to
satisfy it.

The system
that we record
our documents

May be
broken down

Very low

Project failure

All team
members will
make a back
-
up of her/his
workout

All coding
design will start
over




Web service
application
coding &
desktop app
coding

Coding may
be
unsuccessful

M
edium

Project failure

All team
members will
search about
it&gets the
required
information.

All team
members may
consult an
expert.

TABL
E 21
-
Risk Management




5.5 Project Closeout P
lan


After we develop our project, we will present our project to committee of instructor. Steps of our


project which are SPMP, SRS etc. will be evaluated by our supervisor and committee. When our


project
is ready, we want to use this system for university students which is in same university.














6.TECHNICAL PROCESS PLAN

6.1. Process Model

The process model will be chosen waterfall process model because, project will progress


step by step and project will progress slowly so project will be add info possibly .


Analysis


-
>
design
-
> code
-
>
test have been cyclical approach in waterfall process model


so we will chose this waterfall process model which best suitable model ou
r project. Our


project will start in November, 2011 at the end of December, 2011 and than proje will be


development. Project will be all complete January, 2012.



Figure

1
.

waterfall process model



Activity

Start Date

End Date

Time (date/man)

Defining SP

SEPT.23,2011

Sept.27, 2011


4

Initial planning

SEPT.29,2011

OCT.01,2011


16

Reviewing IP

OCT.03,2011

OCT.05,2011

3

SPMP documenting

OCT.06,2011

OCT.17,2011

45

Reviewing SPMP

OCT.20,2011

DEC.30,2011

7

SRS documenting

NOV.02,2011

NOV.11,2011

48

SDD documenting

NOV.14,2011

DEC.5,2011

42

Coding and Testing

DEC.7,2011

MAY
.19,2012

98

Total Elapsed Time

SEPT.23
,2012

JUNE.
15,2012

263 data/man

Table 22

-

Product Time Schedule

Task

Due Date

Review R.Date

Delivered

Major Milestone

Defining SP

Sept.27, 2011


Yes

Yes

Initial planning

OCT.01,2011

OCT.05,2011

Yes

Yes

Preparing SPMP

OCT.17,2011

DEC.30,2011

Yes

Yes

Preparing SRS

NOV.11,2011

_

No

Yes

Preparing SDD

DEC.5,2011

_

No

Yes

Coding and
Testing

MAR.19,2012


No

Yes

Final
Product

JUNE.13,14,15,2012

_


No

Yes


Table 23

-

Project Delivery Schedule Table


6.2. Methods, Tools, and Techniques


We can finish SPMP after that we will do SRS document. Our teams will decide to project


requirements. We will use MS Office, MS Project, Windows 7, NetBeans, IE, Oracle and



Mozilla Firefox in software tools. We will use our personel computers and cluster in hardware tools.
We will use
communication skills in personal skills.









Figure 2:

Cluster
Figure 3:

Oracle SQL


6.3. Infrastructure

We can finish SPMP after that we will do SRS document. Our teams will decide to project

requirements.We will use


MS Office, MS Project, Windows 7, java EE,


Oracle, c++ QT, Soap/Rest

service, Apache Tomcat


and Mozilla Firefox in software tools. We will use our personel computers

and cluster in hardware tools. We will use
communication ski
lls in personal skills.


6.4. Project Acceptance Plan

Firstly, we will prepare SPMP document after that our supervisor will evaluate and than document will
be turn back for correcting. Secondly, we will prepare new version SPMP and we will derived our
document to supervisor. Finally, this duration will contin
ue until document will be accepted by
supervisor.




















7.SUPPORTING PROCESS PLANS


7.1 Configuration Management Plan


It is done in order to make the necessary changes to the documents and putting them into a suitable


format.


The new
versions of report will been as follows:


1.

The first deliverable named as SPMP V1.0

2.

Major Change for Deliverable named as SPMP V2.0

3.

Minor Change for Deliverable named as SPMP V1.1

7.2. Verification and Validation Plan

This plan is done to control phase of t
he process according to the review reports and
confirm that the project is going correctly. Verification and validation of the project
will be done again by the c
ommittee of instructors. Each step

of

our

project

will be
checked.

7.3 Documentation Schedule Plan

In
project

documentation will adapt

to

IEEE standards.
IEEE templates for SPMP,
SRS, SDD, and STD are taken into consideration. Submission dates and report documents are
given in the early steps of the plan.

7.4 Quality
Assurance Plan:

Team members meeting each week
ends of weeks and
controlling the documents exactly the
requirements and correct plans, and they should follow the schedule strictly and project steps
should be completed in appropriate time. Whole are prepared

according to IEEE standards.
Aftermost, in every step, opinion of project supervisor will be taken.

7.5 Reviews and Audits Plan:

After the each of documentation phases are done , which are included SPMP, SRS, and SDD, all


group members will attended
to this documentation.

In order to reach to super
visor , reports posted


on the web page.


7.6 Problem Resolution Plan


Each of the team members will have information about the problem, regardless of their responsibilities


and take a joint decision
about the solution. Extraordinary meeting will be in crisis situations.


7.7 Subcontractor Management Plan

Not applicable in our Project.


7.8 Process Improvement Plan

Since we started the project, meetings will be made regularly. Supervisor and group meet
ings for


improving

the project process w
ill be clear.
Other necessities of our project

will be taken for


development of the project.













































8.

APPENDENCIES