You are on page 1of 39

SOFTWARE PROJECT MANAGEMENT PLAN

For

PAOS

TEAM 9

Customer:
Çizgi BĠLĠġĠM

Team Members:
H. Yağız YANIKOĞLU
Oğuzhan TÜMER
M. Mustafa ÖZTÜRK
Meriç ALEV

24.11.2010
SIGNATURE PAGE

Project Consultant Signature

Duygu ALBAYRAK

Project Coordinator Signature

Ġlker KOYUNCU (Çizgi Bilişim)

Team Members Signature

H. Yağız YANIKOĞLU

Oğuzhan TÜMER

M. Mustafa ÖZTÜRK

Meriç ALEV

2
CHANGE HISTORY TABLE

Date Version File Name Document Status


Format
13.11.2010 V 1.0 Team9_SPMPv1.0.doc Word Document Completed
20.11.2010 V 1.1 Team9_SPMPv1.1.doc Word Document Completed
24.11.2010 V 1.2 Team9_SPMPv1.2.doc Word Document Completed

3
TABLE OF CONTENTS

1 OVERVIEW ........................................................................................................................................ 8
1.1 PROJECT SUMMARY ..................................................................................................................... 8
1.1.1 Purpose, Scope and Objectives ............................................................................................... 8
1.1.2 Assumptions and Constraints ................................................................................................. 9
1.1.3 Project Deliverables ..............................................................................................................10
1.1.4 Schedule and Budget Summary..............................................................................................11
1.2 EVOLUTION OF THE PLAN............................................................................................................11
2 REFERENCES ...................................................................................................................................11
3 DEFINITIONS ...................................................................................................................................11
4 PROJECT ORGANIZATIONS........................................................................................................12
4.1 EXTERNAL INTERFACE ................................................................................................................12
4.2 INTERNAL STRUCTURE ................................................................................................................12
4.3 ROLES AND RESPONSIBILITIES ....................................................................................................12
5 MANAGERIAL PROCESS PLAN .........................................................................................................13
5.1 START-UP PLAN ...................................................................................................................................13
5.1.1 Estimation Plan ...........................................................................................................................13
5.1.2 Staffing Plan................................................................................................................................20
5.1.3 Resource acquisition plan ...........................................................................................................20
5.1.4 Project Staff Training Plan .........................................................................................................22
5.2 WORK PLAN ........................................................................................................................................23
5.2.1 Work Activities ............................................................................................................................23
5.2.2 Schedule Allocation.....................................................................................................................26
5.2.3 Resource Allocation ....................................................................................................................27
5.2.4 Budget Allocation........................................................................................................................28
5.3 CONTROL PLAN ...........................................................................................................................30
5.3.1 Requirements Control Plan ...................................................................................................30
5.3.2 Schedule Control Plan ...........................................................................................................31
5.3.3 Budget Control Plan ..............................................................................................................31
5.3.4 Quality Control Plan .............................................................................................................31
5.3.5 Reporting Plan.......................................................................................................................31
5.3.6 Metrics Collection Plan .........................................................................................................32
5.4 RISK MANAGEMENT PLAN ..........................................................................................................32
5.5 CLOSEOUT PLAN .........................................................................................................................32
6. TECHNICAL PROCESS PLANS..........................................................................................................33
6.1 PROCESS MODEL .................................................................................................................................33
6.2 METHODS, TOOLS, AND TECHNIQUES ..................................................................................................33
6.3 INFRASTRUCTURE PLAN ......................................................................................................................35
6.4 PRODUCT ACCEPTANCE PLAN .............................................................................................................36
7 SUPPORTING PROCESS PLANS.........................................................................................................36
7.1 CONFIGURATION MANAGEMENT PLAN ................................................................................................36
7.2 VERIFICATION AND VALIDATION PLAN ...............................................................................................37
7.3 DOCUMENTATION PLAN ......................................................................................................................37
7.4 QUALITY ASSURANCE PLAN ................................................................................................................38
7.5 REVIEWS AND AUDITS PLAN ................................................................................................................38
7.6 PROBLEM RESOLUTION PLAN ...............................................................................................................39
7.7 SUBCONTRACTOR MANAGEMENT PLANS..............................................................................................39

4
7.8 PROCESS IMPROVEMENT PLAN ............................................................................................................39
8 ADDITIONAL PLANS ............................................................................................................................39

5
LIST OF TABLES

TABLE 1 DEFINITIONS ....................................................................................................................................11


TABLE 2 COCOMO FUNCTION POINT CALCULATION ......................................................................................15
TABLE 3 COCOMO FUNCTION POINT CALCULATION ......................................................................................15
TABLE 4 COST CALCULATION ........................................................................................................................17
TABLE 5 OBJECT POINT CALCULATION ..........................................................................................................18
TABLE 6 STAFFING PLAN ...............................................................................................................................20
TABLE 7 WORK ACTIVITIES ...........................................................................................................................25
TABLE 8 SCHEDULE ALLOCATION ..................................................................................................................27
TABLE 9 RESOURCE ALLOCATION..................................................................................................................28
TABLE 10 SOFTWARE BUDGET ALLOCATION .................................................................................................30
TABLE 11 HARDWARE BUDGET ALLOCATION ................................................................................................30

6
LIST OF FIGURES

FIGURE 1 EXTERNAL INTERFACE....................................................................................................................12


FIGURE 2 INTERNAL STRUCTURE ...................................................................................................................12
FIGURE 3 ESTIMATION PLAN ..........................................................................................................................14
FIGURE 4 OBJECT POINT CALCULATION .........................................................................................................18

7
1 Overview
1.1 Project Summary

1.1.1 Purpose, Scope and Objectives

Purpose

After the widespread use of the Internet, online shopping has become popular all around
the world. As time passes by, the usage of online shopping will increase.
People get accustomed to use online shopping system because of its advantages:
 For seller, online shopping system is cheaper and more effective than regular
shopping.
 Seller can introduce his/her products to the whole world via the Internet.
 Customer can do shopping on the computer. In this way, customer saves time.

Our system, PAOS, is integrated with Pre-Accounting and Online Shopping systems
rather than the existing Online Shopping systems. Once a day, Online Shopping part
sends the information of sold products within the day to Pre-Accounting part. When this
information arrives, system user can create and print invoices of sold products. If the user
wants to calculate endorsement, the system shows daily, monthly or annually
endorsement of the company. All these operations can be performed for 2 types of trades:
B2B and B2C (explained in detail later). There is no such system that provides our
solution to the market for now.
PAOS’ purposes are:
 To combine Pre-Accounting and Online Shopping systems
 To provide opportunity for B2B and B2C trades.
 To create an Admin Panel to let the admin change features of the systems
discretionary.

8
Scope

There are 3 different types of users in PAOS.


 B2B users
 B2C users
 System Administrators: can interfere in the systems when needed.

PAOS contains 2 types of trades:


1. B2B (Business to Business): In this concept, dealers buy from each others or from
distributors with a reduced price compared to regular customers.
2. B2C (Business to Customer): This concept consists of regular customers who do
shopping on the Internet.

Objectives

 To complete the project by the project due date


 Complete the project within the given budget.
 To prepare all deliverables of the project.
 To fulfill all requirements of this project which are:
o Online Shopping System based on B2B and B2C platforms
o Pre-Accounting System
o Admin Panel

1.1.2 Assumptions and Constraints

The project will be planned with the following constraints:

 Project members will satisfy Çizgi BiliĢim’s requirements successfully although


some of them have not worked in a large scaled project as PAOS.
 In coding part, project members will fulfill the requirements although some of
them have not passed 256 courses yet.

9
 Project members will pass 459 courses in order to sustain development of the
system.
 User’s internet connection should be more than 512 kbps.
 User should use Internet Explorer 6 or newer.
 None of the main parts of PAOS will be changed with new requirements except
minor requirements.

The project will be planned with the following constraints:

 PAOS is going to be developed for Çizgi BiliĢim.


 Hosting, Domain and Server costs will be paid by Çizgi BiliĢim.
 The usage rights of deliverables belong to Çizgi BiliĢim.
 Deliverables must be submitted in exact dates.
 All of the project members work part-time.
 PAOS will be based on JAVA and PHP programming languages and MySQL
database platform.
 TortoiseSVN will be used as Configuration Management Tool.
 PAOS works on a system which consists of:
o Pentium4 1.5 GHZ processor or better
o 1 GB RAM
o 512 kbps Internet Connection or better.
o IE 6.0 or better.

1.1.3 Project Deliverables

 Initial Plan of PAOS has already been delivered.


 SRS of PAOS has already been delivered
 SPMP of PAOS 2010.11.24
 SDD of PAOS 2010.12.11
 The Prototype of PAOS 2010.12.25
 Completion of Pre-Accounting part 2011.02.01
 Completion of PAOS 2011.05.30

10
1.1.4 Schedule and Budget Summary

The project has the following high-level schedule:


 Delivery of Pre-Accounting part: February 1, 2011
 Delivery of PAOS (consists of Pre-Accounting Part, Admin Panel, Online
Shopping Part): May 30, 2011

Çizgi BiliĢim will provide the entire project related hardware and software which are
servers, domain and hosting services and the programming tools.

1.2 Evolution of the Plan


The plan is considered to be a dynamic document and will be updated on an unscheduled
basis as necessary. Notification of scheduled and unscheduled updates to the plan will be
communicated via e-mail to all project participants.

2 References
 Team-9 Initial Plan v2.0
 Team-9 SRS v3.0
 IEEE Standard for Software Project Management Plans 1058-1998

3 Definitions
SRS Software Requirement Specification
SPMP Software Project Management Plan
SDD Software Design Document
PAOS Pre-Accounting and Online Shopping System
B2B Business to Business
B2C Business to Customer
Online-POS Online Point of Sale

Table 1 Definitions

11
4 Project Organizations
4.1 External Interface

Figure 1 External Interface

4.2 Internal Structure

Figure 2 Internal Structure

4.3 Roles and Responsibilities

Project Manager (H. Yağız Yanıkoğlu):


 Is responsible for the successful planning, execution, monitoring, control and
closure of the project.
o Is also responsible for coding/testing processes when needed.
Software Engineer (Oğuzhan Tümer):

12
 A skilled professional focused on the design and creation of the project.
o Is also responsible for coding/testing processes when needed.
Software Developer/Tester (Meriç Alev):
 Is responsible for coding, database design and testing the project.
o Is also responsible for planning and design of the project.
Software Developer/Tester (M. Mustafa Öztürk):
 Is responsible for coding, database design and testing the project.
o Is also responsible for planning and design of the project.
Consultant (Duygu Albayrak):
 To observe and give feedback to the project group and to establish relation
between the customer and the project group.
Customer (Ġlker Koyuncu):
 To clarify requirements. Customer has relations with consultant (Duygu
Albayrak) and with the project group.

5 Managerial Process Plan


5.1 Start-up Plan
5.1.1 Estimation Plan

13
Figure 3 Estimation Plan

COCOMO Function Point Calculation

Information Item Elements Total


Customer Information Inputs Name, Surname, Username, 8
Password, E-Mail, Address,
Phone, Birth date.
Authentication Inputs Username, Password 2
Search Engine Inputs Product Name 1
Product Information Inputs Product Id, Product Name, 7
Product Price, Stock for OS,
Stock for Branch, Tax Ratio,
Product Image.
Category Inputs Category ID, Category Name, 3
Category Priority

14
Invoice Inputs Invoice ID 1
Endorsement Inputs Endorsement ID, Product sold 4
date, Endorsement begin date,
Endorsement end date
Checkout Shopping Cart Inputs IBAN no, Bank Name, Security 4
Code, Expiration date
Comment Product Inputs Comment 1
Survey System Inputs Vote 1
Mail System Inputs e-mail addresses, subject, 3
Message.
Configure POS Inputs Active / De-active 1
Configure Bank Account Inputs Bank Name, IBAN, Branch 3
Design Page Layout Inputs Size, Font, Design template 3
Manage Survey Inputs Survey Question and 4 options 5
Manage News Inputs News text field 1
Image Files Thumb nail, real dimension 2
CSS Files Main.css, admin.css, style.css 3
Registration Query 1
Login Query 1
Search Product Query 1
Checkout Shopping cart Query 1
Edit User Info Query 1
Comment Product Query 1
Vote Survey Query 1
Manage Category Query 1
Manage Product Query 1
Manage Customer Account 1
Query
Create Invoice Query 1
Calculate Endorsement Query 1
General Management Query 6
User/Dealer Management Query 2
Configuration Query 3
Table 2 Cocomo Function Point Calculation

Items Simple Average Complex Total


External Inputs (EI) 40x3=120 5x4=20 0x6=0 140
External Outputs (EO) 0x4=0 0x5=0 0x7=0 0
External Inquiries (EQ) 18x3=54 5x4=20 0x6=0 74
External Interface Files (EIF) 5x5=25 0x7=0 0x10=0 25
Internal Logical Files (ILF) 0x7=28 0x10=0 0x15=0 0
Total Unadjusted Function Point (UFP) = 239

Table 3 Cocomo Function Point Calculation

15
Unadjusted function point (UFP) = 239

The project size is measured as 239 function points.


124 function points is PHP.
115 function points is Java.

LOC = UFP * LFAC (Java is predefined as 30)


LOC= (115*30) + (124*15) =3450+1860=5310

KLOC = LOC / 1000


=5310/ 1000
= 5.310

Effort Applied = 2.4 * 7.171.05


= 13.8535313 Person Months

Average Staffing = 13.8535313 / 4  3.5 months


= 3.46338283 FSP (Full-Time Software Personnel)

Product Design Effort = 0.16 * 3.46338283


= 0.554141253 FSP

Product Design Schedule = 0.19 * 3.46338283


= 0.658042738 FSP

16
Resource Item Duration Price Cost
(month)
Software Personnel 4 5 3.000 TL(monthly) 60.000TL
IBM X series 2 - 5.200 TL(item) 10.400 TL
Servers
SSL Certification 1 12 170$ (yearly) 2040$
Online POS 1 12 150TL 150TL
Adobe Master 1 - 1500$ 1500$
Collection CS4
Computer as 1 5 1200TL
Software repository
Total Cost: 76.800 TL
Table 4 Cost Calculation

17
COCOMO Object Point Calculation

Figure 4 Object Point Calculation

Screens / Simple Medium Difficult Reports Total


Reports screen*1 screen*2 screen*3
Online
Shopping 12 10 21 0 107
Pre-
Accounting 5 3 7 4(simple) 32
Admin Panel 17 12 15 6(simple) 94
Object Point = 233
Table 5 Object Point Calculation
We will not make 3GL component.

NOP = OP*((100-15)/100)
NOP = 233*((100-15)/100)

18
NOP = 198.05
Effort= NOP/PROD
Our team members’ experience is nominal so divide NOP to 13,
Effort=198.05/13
Effort =15.2346154 Person Month
Average Staffing=15.2346154 / 4 (team members)
Average Staffing =3.80865385 FSP

19
5.1.2 Staffing Plan

Based on initial estimates, the project will require the human resources shown in the table
below.

Human Resource Work(hours) Working Period Project Phase Affordable Hourly


Type Rate
Project Manager 500 27.09.2010- All 30-60 TL
30.05.2011
Software Engineer 500 27.09.2010- Requirements 10-40 TL
30.05.2011 Design
Implementation
Testing
Installation

Software 500 27.09.2010- Requirements 10-40 TL


Developer/Tester 30.05.2011 Design
Implementation
Testing
Installation

Software 500 27.09.2010- Requirements 10-40 TL


Developer/Tester 30.05.2011 Design
Implementation
Testing
Installation

Table 6 Staffing Plan

5.1.3 Resource acquisition plan

The project manager shall be responsible for acquiring all non-human resources required
by the project. The non-human resources in our project are:
 IBM X series Servers
 SSL Certification
 Online POS
 Adobe Master Collection CS4
 Computer as Software repository

20
IBM X series Servers

Required Date: 07.12.2010


Requested Date: 01.11.2010
Servers should be kept in data center of the Çizgi BiliĢim and server will be supplied by
Çizgi BiliĢim. Servers will be managed by Mustafa Öztürk. Database and source code
will be run different servers to make our system more secure.

SSL Certification

Required Date: 01.04.2011


Requested Date: 01.11.2010
SSL (Secure Sockets Layer) is the standard security technology for establishing an
encrypted link between a web server and a browser. It will be provided by Çizgi BiliĢim
and installed to server by Yağız Yanıkoğlu (Project Manager). We need this certificate to
establish trust between customer and company.

Online POS

Required Date: 01.03.2011


Requested Date: 01.11.2010
Online POS is the most important necessity of the online shopping site because it is the
easiest way to purchase goods. At the beginning of the system we need only one Online
POS to demonstrate that system is working correctly. However, if customer wants to put
more than one banks’ online POS, our system will support it. Online POS will be
provided by Çizgi BiliĢim and it will be integrated to our system by Oğuzhan Tümer
(Software Engineer).

Adobe Master Collection CS4

Required Date: 07.12.2011


Requested Date: 01.11.2010
Project team need to use adobe master collection cs4 in order to make online shopping
design better. It will be provided by Çizgi BiliĢim. Adobe macromedia, flash, photo-shop
will be the most used tools.

Computer as Software repository

Required Date: 01.12.2011


Requested Date: 01.11.2010

21
Software repository storage space is provided in Çizgi BiliĢim and is managed by Meriç
Alev(Software Developer/Tester). All source code and database will be kept in this
repository and every week he will take backup of this computer.

5.1.4 Project Staff Training Plan

This project contain pre-accounting, therefore, there will be basic accounting workflow
training to teach team members process of accounting. This training will be provided by
Çizgi BiliĢim.

PAOS will be written in %70 PHP and %30 Java. However some of the group members
do not know PHP. During the implementation there will be PHP training. The group
members who know PHP will give lecture to members who do not know. During this
project, always there will be exchange of information.

22
5.2 Work Plan
5.2.1 Work Activities
ID Task Name Resource Name Duration Predecessors Successor
1 Pre Accounting and Online 240 days
Shopping System
2 Software Lifecycle Model Project Manager 2 days
Process
3 Select project model Project Manager 2 days 2 4,5,6
4 Map activities to the Project Manager 2 days 2,3 6
PAOS
5 Identify staffing Project Manager 2 days 4 6
requirements
6 Allocate identified Project Manager 5 days 4 7,8
activities to staff
7 Identify tool requirements Project Manager 10 days 8,9
8 Acquire required tools Project Manager 5 days 7 9
9 Create communication Project Manager 1 day 7 10,11
plan
10 Establish documentation Project Manager, 1 day 7 11,12,
repository Software
repository
11 Create baseline Work Project Manager, 10 days 3,4,6,7,8,9 12
Breakdown Structure Software engineer,
(WBS) Software
Developer and
Tester
12 Create SPMP Document Project Manager, 10 days
Software engineer,
Software
Developer and
Tester
13 Project Monitoring & 100 days 11 14
Control
14 SPMP Scheduled Updates 100 days 11 12
15 All project deliverables 11,21,25,30 16
have been delivered
16 Software Quality Software engineer 50 days 13 16
Management
17 System Software 10 days
Allocation(Analyze Developer and
functions) Tester
18 Define and develop Project Manager 5 days 16 18
software requirements

23
19 Define interface Project Manager 2 days 18 20
requirements
20 Prioritize and integrate Project Manager 2 days 19 21
requirements
21 SRS completed 2,3,4,5,6,7,8 22
9,10,11,16,17
18,19,20
22 Perform architectural Project Manager, 10 days 21 23
design Software engineer,
Software
Developer and
Tester
23 Design the database Project Manager, 14 days 22 24
Software engineer,
Software
Developer and
Tester
24 Design interfaces Software 7 days 23 25
Developer and
Tester
25 SDD Completed 22,23,24 26
26 Plan verification and Project Manager, 50 days 25 27
validation Software engineer,
Software
Developer and
Tester
27 Execute verification and Project Manager, 50 days 26 28
validation tasks Software engineer,
Software
Developer and
Tester
28 Develop test requirements Software 20 days 27 29
Developer and
Tester
29 Execute the tests Software 5 days 28 30
Developer and
Tester
30 V&V completed 26,27,28,29 32
31 Training Project Manager, All time
Software engineer,
Software
Developer and
Tester
32 Implementation Project Manager, 180 days 12,21,25,30 33
Software engineer,
Software

24
Developer and
Tester
33 Maintenance Project Manager, 60 days 12,21,25,30,32
Software engineer,
Software
Developer and
Tester
Table 7 Work Activities

25
5.2.2 Schedule Allocation

Task Name Work Duration Start Finish


Pre Accounting and Online 500 hrs 240 days 27.09.2010 30.05.2011
Shopping System
Software Lifecycle Model 10 hrs 2 days 01.10.2010 03.10.2010
Process
Select project model 10 hrs 2 days 05.10.2010 07.10.2010
Software Quality 30 hrs 50 days 08.10.2010 10.12.2010
Management
System 30 hr 10 days 01.10.2010 12.10.2010
Allocation(Analyze
functions)
Define and develop 10 hrs 5 days 01.10.2010 06.10.2010
software requirements
Define interface 5 hrs 2 days 15.10.2010 17.10.2010
requirements
Prioritize and integrate 5 hrs 2 days 22.10.2010 24.10.2010
requirements
SRS completed 50 hrs 19 days 01.10.2010 06.11.2010
SRS deliverables have
been delivered
Map activities to the 10 hrs 2 days 08.11.2010 10.11.2010
PAOS
Identify staffing 5 hrs 2 days 11.11.2010 13.11.2010
requirements
Allocate identified 10 hrs 5 days 14.11.2010 19.11.2010
activities to staff
Identify tool requirements 10 hrs 5 days 18.11.2010 23.11.2010
Acquire required tools 10 hrs 7 days 01.12.2010 07.12.2010
Create communication 1 hrs 1 day 24.11.2010 24.11.2010
plan
Establish documentation 4 hrs 1 day 07.12.2010 07.12.2010
repository
Create baseline Work 20 hrs 10 days 15.11.2010 25.11.2010
Breakdown Structure
(WBS)
Create SPMP Document 50 hrs 10 days 13.11.2010 23.11.2010
Project Monitoring & 50 hrs 150 days 27.09.2010 29.05.2011
Control
SPMP Scheduled Updates 30 hrs 150 days 27.09.2010 29.05.2011
Perform architectural 50 hrs 10 days 16.11.2010 26.11.2010
design
Design the database 60 hrs 14 days 20.11.2010 04.12.2010
Design interfaces 30 hrs 7 days 04.12.2010 11.12.2010

26
SDD Completed 16.11.2010 11.12.2010
Prototype 40 hrs 10 days 15.12.2010 25.12.2010
Training All time 27.09.2010 30.05.2011
Implementation 500 hrs 180 days 01.12.2010 30.05.2011
Plan verification and 150 hrs 50 days 20.12.2010 15.02.2011
validation
Execute verification and 50 hrs 50 days 20.12.2010 15.02.2011
validation tasks
Develop test requirements 100 hrs 50 days 20.12.2010 15.02.2011
Execute the tests 20 hrs 50 days 20.12.2010 15.02.2011
V&V completed 50 days 20.12.2010 15.02.2011
Maintenance 150 hrs 60 days 01.06.2011 01.08.2011
Table 8 Schedule Allocation

5.2.3 Resource Allocation


Task Name Work Duration Start Finish
Servers setup and
installation 20 hrs 5 days 20.12.2010 25.12.2010
SSL Certification 5 hrs 1 day 01.04.2011 01.04.2011
Online POS integration 15 hrs 3 days 01.03.2011 04.03.2011
Adobe Master Collection
CS4 installation 2 hrs 1 day 07.12.2010 07.12.2010
Prepare Repository 5 hrs 1 day 01.12.2010 01.12.2010
Pre Accounting and Online 500 hrs 240 days 27.09.2010 30.05.2011
Shopping System
Software Lifecycle Model 10 hrs 2 days 01.10.2010 03.10.2010
Process
Select project model 10 hrs 2 days 05.10.2010 07.10.2010
Software Quality 30 hrs 50 days 08.10.2010 10.12.2010
Management
System 30 hr 10 days 01.10.2010 12.10.2010
Allocation(Analyze
functions)
Define and develop 10 hrs 5 days 01.10.2010 06.10.2010
software requirements
Define interface 5 hrs 2 days 15.10.2010 17.10.2010
requirements
Prioritize and integrate 5 hrs 2 days 22.10.2010 24.10.2010
requirements
SRS completed 50 hrs 19 days 01.10.2010 06.11.2010
SRS deliverables have
been delivered
Map activities to the 10 hrs 2 days 08.11.2010 10.11.2010
PAOS
27
Identify staffing 5 hrs 2 days 11.11.2010 13.11.2010
requirements
Allocate identified 10 hrs 5 days 14.11.2010 19.11.2010
activities to staff
Identify tool requirements 10 hrs 5 days 18.11.2010 23.11.2010
Acquire required tools 10 hrs 7 days 01.12.2010 07.12.2010
Create communication 1 hrs 1 day 24.11.2010 24.11.2010
plan
Establish documentation 4 hrs 1 day 07.12.2010 07.12.2010
repository
Create baseline Work 20 hrs 10 days 15.11.2010 25.11.2010
Breakdown Structure
(WBS)
Create SPMP Document 50 hrs 10 days 13.11.2010 23.11.2010
Project Monitoring & 50 hrs 150 days 27.09.2010 29.05.2011
Control
SPMP Scheduled Updates 30 hrs 150 days 27.09.2010 29.05.2011
Perform architectural 50 hrs 10 days 16.11.2010 26.11.2010
design
Design the database 60 hrs 14 days 20.11.2010 04.12.2010
Design interfaces 30 hrs 7 days 04.12.2010 11.12.2010
SDD Completed 16.11.2010 11.12.2010
Prototype 40 hrs 10 days 15.12.2010 25.12.2010
Training All time 27.09.2010 30.05.2011
Implementation 500 hrs 180 days 01.12.2010 30.05.2011
Plan verification and 150 hrs 50 days 20.12.2010 15.02.2011
validation
Execute verification and 50 hrs 50 days 20.12.2010 15.02.2011
validation tasks
Develop test requirements 100 hrs 50 days 20.12.2010 15.02.2011
Execute the tests 20 hrs 50 days 20.12.2010 15.02.2011
V&V completed 50 days 20.12.2010 15.02.2011
Maintenance 150 hrs 60 days 01.06.2011 01.08.2011
Table 9 Resource Allocation

5.2.4 Budget Allocation

Software Budget Allocation

Task Name Work Duration


Pre Accounting and Online 500 hrs 60.000 TL
Shopping System
Software Lifecycle Model 10 hrs 300 TL
Process

28
Select project model 10 hrs 300 TL
Software Quality 30 hrs 900 TL
Management
System 30 hr 900 TL
Allocation(Analyze
functions)
Define and develop 10 hrs 300 TL
software requirements
Define interface 5 hrs 150 TL
requirements
Prioritize and integrate 5 hrs 150 TL
requirements
SRS completed 50 hrs 1500 TL
SRS deliverables have
been delivered
Map activities to the 10 hrs 300 TL
PAOS
Identify staffing 5 hrs 150 TL
requirements
Allocate identified 10 hrs 300 TL
activities to staff
Identify tool requirements 10 hrs 300 TL
Acquire required tools 10 hrs 300 TL
Create communication 1 hrs 30 TL
plan
Establish documentation 4 hrs 120 TL
repository
Create baseline Work 20 hrs 600 TL
Breakdown Structure
(WBS)
Create SPMP Document 50 hrs 1500 TL
Project Monitoring & 50 hrs 1500 TL
Control
SPMP Scheduled Updates 30 hrs 900 TL
Perform architectural 50 hrs 1500 TL
design
Design the database 60 hrs 1800 TL
Design interfaces 30 hrs 900 TL
SDD Completed
Prototype 40 hrs 1200 TL
Training ----
Implementation 500 hrs 15.000 TL
Plan verification and 150 hrs 4500 TL
validation
Execute verification and 50 hrs 1500 TL

29
validation tasks
Develop test requirements 100 hrs 3000 TL
Execute the tests 20 hrs 600 TL
V&V completed -----
Maintenance 150 hrs 4500 TL
Table 10 Software Budget Allocation

Hardware Budget Allocation

Name Quantity Duration Price Total Price


(months)
IBM X series 2 - 5.200 TL(item) 10.400 TL
Servers
SSL Certification 1 12 170$ (yearly) 3000 TL
Online POS 1 12 150TL 150 TL
Adobe Master 1 - 1500$ 2000 TL
Collection CS4
Computer as 1 5 1200TL 1200 TL
Software repository
Table 11 Hardware Budget Allocation

5.3 Control Plan


5.3.1 Requirements Control Plan

All of the requirements have been specified in the Software Requirements Specification.
When changes are to be made in the requirements after the SRS has been released, the
changes shall be brought to the attention of the Team 9 and discussed.
Any changes that are to be made will be with the prior approval of the Team 9 and only
if feasible and permissible within the constraints of the project mentioned in section
1.1.2. Once the changes have been made to the SRS document, an updated version of the
SRS shall be released.

30
5.3.2 Schedule Control Plan

If the work scheduled in section 1.1.4 is gets behind, Team 9 is ready to spend extra time
on the project to make up for the lost time and deliver the final project on time.

5.3.3 Budget Control Plan

The cost of work completed, measured in team member man hours, will be compared to
the budgeted cost to determine whether the actual cost remains consistent with the
planned cost. Examination of the actual cost will occur after the implementation of each
iteration.

5.3.4 Quality Control Plan


This subsection will describe the mechanisms to be used for measuring and controlling
quality of work processes and products.

Audits
Audits of work processes will not be conducted on a schedule. However, they may be
requested by one of the following:
• H. Yağız Yanıkoğlu (Team 9 Project Manager)
• Ġlker Koyuncu (Çizgi BiliĢim)
• Duygu Albayrak (Consultant)

Reviews
Regularly scheduled reviews of work products will take place.

Defect/issue tracking
Defects and other issues will be tracked with “Bugzilla” for Online Shopping part and
Admin Panel.

5.3.5 Reporting Plan

Each of preliminary versions of all the documents and updates and status reports will be
sent and discussed with the advisor and upon approval the approved document will be
circulated to the other members of Team 9.

31
5.3.6 Metrics Collection Plan

None.

5.4 Risk Management Plan


This section will observe the project risks that may arise in the future, and also specify
the techniques used to manage these project risks.

Risk Probability Effect Strategy


Lack of information High Tolerable Do search about the problem that
during development occurred in the system via the Internet.
of the software Read related e-books etc.
Failure of one team High Serious Share the team member’s work among
member in 459 the project team.
courses
Change of the Low Serious Always be in contact with the customer
Requirements in order to review the system according
to the requirements.
Passing deadlines Low Serious Conform to the plan of project to deliver
the requirements in exact dates.
Stolen of the user Moderate Serious Get a SSL Certificate to make the system
information reliable. Make provision against hacking
techniques such as SQL injection.
Server breakdown High Serious Keep waiting a second server to keep the
system work. Block all the incoming
attacks to the system.
Loss of time during Moderate Serious Prepare the SQL queries to make the
data transfer system work fast.
Bankrupt of Çizgi Low Serious Try to find another firm that accept the
Bilişim project.

5.5 Closeout Plan


This section describes the nature of the activities that will be used to closeout the project
when it is completed.
Upon termination of the entire project for any reason, whether due to the objectives being
met or some other reason, there is a number of closure activities that will be performed
before the project is considered closed. These activities are captured in the following:

32
 Communicate decision
 Identify remaining work
 Deliver released software
 Get customer approvals
 Publish released documentation Michael Gold
 Release or reassign team
 Return or release vendor or customer materials

6. Technical Process Plans


6.1 Process Model
The main aim of software process model is perform activities such as determine the
requirements, design, coding and testing. Process models increase the repeatability,
manageability and measurability. The project team will use the waterfall model because
the amount of resources required to implement this model is very minimal. The most
important aspect of the waterfall model is that none of the stages can be started off with
before the preceding stage is complete. This feature allows us to complete every stage
successfully.

6.2 Methods, Tools, and Techniques

Development methodology
The project shall use the waterfall development methodology to deliver the software
products. The decision to the use waterfall methodology is due to the following
characteristic of the project
 The product definition is stable.
 Requirements and implementation of PAOS are both well-understood

Programming language
Java and PHP programming languages are chosen in the project. Java will use on pre-
accounting part and PHP will used Admin Panel and Online Shopping part of PAOS.

33
The main reasons of choosing PHP and java
 Both of them are free
 There are many support groups, forms and teams supporting PHP
 Both of them are runs on different operating systems,

Tools

Eclipse Galileo: Eclipse is an open source community, whose projects are focused on
building an open development platform comprised of extensible frameworks, tools and
runtimes for building, deploying and managing software across the lifecycle.

Adobe Dreamweaver: Adobe Dreamweaver enhanced coding functions make it a breeze


to navigate through complex site pages at design time. Improved layout tools expedite
workflows from comp conception to client approval. Innovations like these and more
throughout Dreamweaver help teams and individual developers alike reach the next
levels in performance and functionality.

MySQL: The MySQL database has become the world's most popular open source
database because of its consistent fast performance, high reliability and ease of use.
MySQL is the world's most popular open source database; it's also become the database
of choice for a new generation of applications built on the LAMP stack (Linux, Apache,
MySQL, PHP / Perl / Python.) MySQL runs on more than 20 platforms including Linux,
Windows, Mac OS, Solaris, HP-UX, IBM AIX, giving you the kind of flexibility that
puts you in control.

Bugzilla: The Bugzilla prevent SQL Injection, and has a very careful system in place to
prevent Cross-Site Scripting. Bugzilla’s history of patching security vulnerabilities is
excellent, and the system is designed at every stage with security in mind. Also, email
addresses of users are not available to log out users, to make life harder to spammers.
And if someone tries to abuse your account by guessing your password, this account will
be automatically locked after a few attempts to prevent brute force.

34
Document distribution
All documents that distributed electronically will be created in the Microsoft Word

6.3 Infrastructure Plan

Software Infrastructure
 PAOS will be mainly written in two languages which are PHP and Java. Pre-
accounting part will be written in Java and Online Shopping and Admin Panel
part will be written in PHP.
 We will use centralized database because database will be used by both java and
PHP part. If we separate the database it will reduce our system efficiency. That’s
why we decided to use repository architectural pattern for our system. All sub-
systems are used same database so sub-systems do not interact directly, only
through the repository.
 We will use MySql version 5.1.3 as database because it is free and both PHP and
Java is working efficient with MySql.
 To develop PHP source code we will use macromedia dreamweaver 8 (Adobe
Master Collection CS4) and to run it we will use XAMPP version 1.7.2.
 To develop JAVA source code we will use eclipse Galileo and JBuilder.
 We will use one of the bank Online-POS framework but our customer has not
decided it yet which bank it should be.
 All Interface design will be design by using Adobe Master Collection CS4 tools
like Adobe illustrator, Adobe Photoshop.
 We will test our Java source code with JUnit framework.
 We have used Jude and Microsoft Visio to design our system.
 We will setup FileZilla server to our both servers and FileZilla Client to all team
members computer to deploy our source code to servers.

35
Hardware Infrastructure
 We will use 2 servers one for web server second for database server. Both of these
servers will have Linux OS for security reasons. Servers will stay at the Çizgi
BiliĢim data center.
 We will use a computer as repository. We will set up this PC to CVS and all of
the team member will have an account to reach the repository.

6.4 Product Acceptance Plan

This section will describe the methods of acceptance for each of the project deliverables
identified in section 1.1.3; the headings of this plan relate to the deliverable categories in
that section.

Project documentation

All of the project documents are approved by the project manager and will be reviewed
by both PM and rest of the Team 9 members.
The SPMP will be approved by Çizgi BiliĢim according to their private criteria.

Software Program

Once testing has been completed, if the software program is ready to be executed
successfully; the project manager will hold a review session with Çizgi BiliĢim in order
to report outstanding issues with the software.
Çizgi BiliĢim will deliver a decision to the project manager on whether the issues are
acceptable or not.

7 Supporting Process Plans


7.1 Configuration Management Plan
This part of the document describes the configuration management of the PAOS.
Software configuration management describes the techniques of initiating, analyzing,
evaluating, controlling and tracking changes to products which are prepared during

36
improvement process. It emphasizes the importance of configuration management control
of safety and design patterns.
In PAOS, project manager who is Hüseyin Yağız Yanıkoğlu is the configuration manager
at the same time. Configuration manager is responsible for
 Identifying configuration of PAOS’ SRS and PAOS’ SDD documents,

 Controlling configuration of the product,

 Auditing configuration,

 Accounting configuration status.

Thanks to the configuration management plan, PAOS will be more acceptable and
supportable for changes.
Configuration management tool which will be used by configuration manager is Clear
Case which is configuration management tool by IBM.

7.2 Verification and Validation Plan


Verification and validation ensures that quality of the product is settled the software and
software meets requirements or changes customer’s requirements. Software verification
and validation uses review, inspect, analysis, implement, and testing techniques to meet
requirements of the software product. Verification and validation planning begins the
starting of the project and continues until the end of the project.
The aims of this plan are to develop and meet Quality Assurance of the project and to
meet requirements of the project.
In PAOS, the purpose of the verification and validation plan is to control deliverables,
subsystems, modules, databases and source code of the project stage by stage. The project
manager is responsible for finding an error on the whole system.

7.3 Documentation Plan


Documentation plan shall be subject to analysis, decomposition, estimation, and inclusion
in the PAOS by the external client or the internal client. Deliverables and non-
deliverables are significant for the team members.

37
Deliverables are Software Requirement Specifications, coding standards, Software
Project Management Plan, Software Requirement Specification Revision, Software
Configuration Management Plan, Software Quality Assurance Plan, Software
Verification and Validation Plan and Software Design Documentation.

Non-deliverables are Development Process, Meeting Process, Conflict Resolution


Process, Privileges Information Handling Process, Requirement Change Process, Stand-
up meeting process and Shared Knowledge Process.

In PAOS, project manager is the documentation manager at the same time. All team
members will help the documentation manager.

7.4 Quality Assurance Plan


A quality assurance plan will be used by team members during the implementation of the
PAOS. The Quality Assurance Plan describes the quality approach for completed
software and related work products with the set of quality actions and roles involved in
implementing software quality. Quality assurance plan provides the final phase of the
project is high quality. The quality assurance plan contains a set of documented activities
which provide customers are satisfied with the software product.

All members of the project team are responsible for the quality of the deliverables of the
PAOS and they will find bugs and errors which causes dissatisfaction of the customer.
Quality assurance manager of the team will control this deliverable then quality reviewers
will control his review before PAOS will be submitted.
In PAOS, Quality Assurance plan will be used in all stages of the project. The purpose of
Quality Assurance Plan is to ensure that the product meets customer requests.

7.5 Reviews and audits plan


Reviews and Audits will be used by team members during the implementation of PAOS.
The aim of reviews and audits is to ensure an independent evaluation of conformance of
software and processes to applicable regulations, standards, guidelines, plans, and

38
procedures. Team members will use reviews and audits in order to provide Quality
control.
Besides, team members track the team’s progress to provide PAOS project stays on
budget and schedule, to determine the whole status of the project and to ensure Quality
Assurance Standards of the project.
In PAOS, project manager is responsible for reviews and audits of the project. Reviews
and audits will be signified by project manager due to documentation plan. At the same
time, all team members might be reviewers and auditors of the project if it is required.

7.6 Problem resolution plan


Problem resolution plan is none, because if a problem occurs, this problem will be
resolved between team members, advisor and the customer who is Çizgi BiliĢim.

7.7 Subcontractor management plans


None

7.8 Process Improvement Plan


Software process improvement is a tool which is performed for software procurement,
development, operation, planning about supporting processes, management and auditing.
Software process improvement is beneficial if the project is having problems which have
made apparent the need for change. Therefore, Software process improvement plan is
very important for IT projects. Software process improvement implementation
methodologies are grouped under two stages. Fist of these is model based, the other is
comparison (benchmark) based.

In PAOS, the aim of the Software Process Improvement Plan is to arrange interviews
with the project consultant who is Duygu Albayrak, and the customer who is Çizgi
BiliĢim. The Software Process Improvement Plan will be rewritten in the next phases of
the project.

8 Additional Plans
There are no Additional Plans

39