Example of SPMP Document

WHERE AM I? Project

System Project Management Plan

Version: SPMP Final Copy

Prepared by

Team #13

Efraim KORKMAZ – Selcuk DEMIRCI –

Ismet Serturk BASOGLU

January 7th, 2010

Where am I? PROJECT

Preface

In this report, the correct way to get team members has made plans. These reports and team

members, supervisor checks. This report covers a summary including purpose, summary,

objectives, constraints, schedule, budget summary. Moreover, this report contains managerial

process like estimation, staffing resource allocation, quality control and risk management plans.

Version History

Version Status* Date Responsible Version Definition

1 Released 21.10.2009 Ismet Serturk BASOGLU

SPMP 1.0

2 In Change 08.01.2010 Ismet Serturk BASOGLU

SPMP 1.1

*: Draft, In Review, Released, Approved, Rejected, In Change

Atılım University

COMPE/SE/ISE 491-492

2/37

Team # 13 (Team Lost)


Version: Final Copy

Where am I? PROJECT

List of Figures

Figure 1. ganchart........................................................................................................................... 37

List of Tables

Table 1. Project Deliverables……………………………………………………………………..9

Table 2. Internal structure……………………………………………………………………….12

Table 3. Project Responsibilities…………………………………………………………………12

Table 4. Product Function I/O Summary…………………………………………………………13

Table 5. Function Point Metrics………………………………………………………………….14

Table 6. Complex Adjustment Values…………………………………………………………..16

Table 7. Project work activity……………………………………………………………………19

Table 8. Resource allocation for Work Activity………………………………………………..20

Table 9. Resource Allocation for customer Meeting……………………………………………20

Table 10. Resource Allocation for preparing SPMP…………………………………………….21

Table 11. Resource Allocation for preparing SRS………………………………………………22

Table 12. Resource Allocation for preparing SDD……………………………………………..22

Table 13. Resource Allocation for preparing STD……………………………………………….23

Table 14. Resource Allocation for Coding………………………………………………………23

Table 15. Resource Allocation for preparing Testing…………………………………………..24

Table 16. Resource Allocation for preparing User Manual……………………………………….24

Table 17. Resource Allocation for Deployment…………………………………………………..24

Table 18. Schedule and Budget Allocation for Customer Meeting………………………………..25

Table 19. Schedule and Budget Allocation for Preparing SPMP…………………………………25

Table 20. Schedule and Budget Allocation for Preparing SRS……………………………………26

Table 21. Schedule and Budget Allocation for Preparing SDD………………………………..26

Table 22. Schedule and Budget Allocation for Preparing STD…………………………………27

Table 23. Quality Control Plan…………………………………………………………………..28

Table 24. Probability of Risks……………………………………………………………………29

Table 25. Ratio of Probability……………………………………………………………………..29

Table 26. Product Time Schedule…………………………………………………………………32

Atılım University


3/37



Version: Final Copy

Where am I? PROJECT

Table of Contents

PREFACE..........................................................................................................................................................2

LIST OF FIGURES...........................................................................................................................................3

LIST OF TABLES.............................................................................................................................................3

TABLE OF CONTENTS..................................................................................................................................4

1. OVERVIEW..........................................................................................................................................6

1.1. Project Summary.................................................................................................................................61.1.1. Purpose, Scope, and Objectives..................................................................................................61.1.2. Assumptions and Constraints......................................................................................................61.1.3. Project Deliverables....................................................................................................................71.1.4. Schedule and Budget Summary...................................................................................................9

1.2. Evolution of the SPMP........................................................................................................................9

2. REFERENCE MATERIALS.............................................................................................................10

3. DEFINITIONS, ACRONYMS, AND ABBREVIATIONS..............................................................11

4. PROJECT ORGANIZATION...........................................................................................................12

4.1. External Interfaces.............................................................................................................................124.2. Internal Structure...............................................................................................................................124.3. Project Responsibilities.....................................................................................................................12

5. MANAGERIAL PROCESS PLANS.................................................................................................13

5.1. Start-up Plan......................................................................................................................................135.1.1. Estimation Plan.........................................................................................................................135.1.2. Resource Acquisition Plan........................................................................................................165.1.3. Project Staff Training Plan.......................................................................................................17

5.2. Work Plan..........................................................................................................................................175.2.1. Work Activities...........................................................................................................................175.2.2. Schedule Allocation...................................................................................................................205.2.3. Resource Allocation...................................................................................................................205.2.4. Budget Allocation......................................................................................................................24

5.3. Control Plan.......................................................................................................................................275.3.1. Requirements Control Plan.......................................................................................................275.3.2. Schedule Control Plan...............................................................................................................275.3.3. Quality Control Plan.................................................................................................................275.3.4. Reporting Plan..........................................................................................................................285.3.5. Metrics Collection Plan.............................................................................................................29

5.4. Risk Management Plan......................................................................................................................295.4.1. Description of Risks...................................................................................................................30

6. TECHNICAL PROCESS PLANS.....................................................................................................32

6.1. Process Model...................................................................................................................................326.2. Methods, Tools, and Techniques.......................................................................................................336.3. Infrastructure Plan.............................................................................................................................336.4. Product Acceptance Plan...................................................................................................................34

7. SUPPORTING PROCESS PLANS...................................................................................................35

7.1. Configuration Management Plan.......................................................................................................357.2. Quality Assurance Plan.....................................................................................................................357.3. Documentation Plan..........................................................................................................................367.4. Deployment Plan...............................................................................................................................367.5. Review Plan.......................................................................................................................................36

8. APPENDICES.....................................................................................................................................37

Atılım University


4/37



Version: Final Copy

Where am I? PROJECT

8.1. Appendix 1 – Ganchart......................................................................................................................37

Atılım University


5/37



Version: Final Copy

Where am I? PROJECT

1. Overview

1.1. Project Summary

1.1.1. Purpose, Scope, and Objectives

1.1.1.1 Purpose:

Our main purpose of our project is with the help of GPS is to determine our position, save

our location, coordinate, path throught and search any location on a digital map.

1.1.1.2 Scope:

The main goal and scope of our project is with the help of GPS is to mark and save where

we are, to save the way we go and search cities, countries, streets etc... with the enter name or

coordinate.

1.1.1.3 Objectives:

Our objectives are ;

When user want save something like location or path throught, user will press save

button and save this location or path throught from system database.

When user want delete or show saved objects like locations or path thoughts, user

will press delete or show button and delete or show these objects from system

database.

When user want to go somewhere and if user do not know this place, user will

press search button and enter locations’ name or coordinate and find this location

with the help of GPS program.

When user want where he or she is, they open GPS program in his or her mobile

phone and start send coordinateness’ from host. And computer Take these

coordinates from host, and show where he or she is with markers.

1.1.2. Assumptions and Constraints

1.1.2.1 Assumptions:

We assumed that the following points exist:

Be present at the computer with the GPS map to establish a connection, we will do

some operations like save path throught on a map.

Due to external factors, program will not work nicely.

Atılım University


6/37



Version: Final Copy

Where am I? PROJECT

Due to system failures, some functions may not work properly.

Connection between GPS and Computer, may not work properly.

Maybe, Program will bought by few users.

Maybe, our project will not finish at the proper time.

1.1.2.2 Constraints:

Our project constraints are:

To avoid a more expensive product

Density of the other courses in the university

Lack of experience of the members of the project.

Be limited to the project calendar.

Not to find enough time.

Lack of adequate communication between team members.

1.1.3. Project Deliverables

Work Product Description Delivery Date

Problem Statement Define the problem (submitted) 30.09.2009

Initial Plan Define the technical and managerial processes (submitted)

01.10.2009

Reviewed Initial Plan Revised version(submitted) 01.10.2009

SPMP Document Software Project Management Plans is used to define the scope, purpose and objectives of the project, to specify roles and responsibilities of team members, the customer company if it exists. Many plans are considered in order to define the assumptions and constraints of the project. It defines which process model is chosen for the project life cycle. It is used to document agreed deliverables

21.10.2009

Atılım University


7/37



Version: Final Copy

Where am I? PROJECT

and their dates.

Reviewed SPMP Document Revised version 08.01.2010

SRS Document Software Requirements Specification is used to describe the behavior of the software of the system to be developed. It documents the functional and nonfunctional requirements of the system. It includes a set of use cases which describes the user-system interactions.

16.11.2009

Reviewed SRS Document Revised version 25.01.2010

SDD Document Software Design Description is

used for complete description of

design of the software of the

system to be developed. It

documents all the information

about the design.

It specifies the form of the

document used to specify system

architecture and application

design in a software related

project.

30.12.2009

Reviewed SDD Document Revised version 22.02.2010

Presentation At the end of first and second semester 2 presentations will be done which reflects the work we done during project development.

26-27-28.01.2010

STD Document Software Test Documentation 15.03.2010

Atılım University


8/37



Version: Final Copy

Where am I? PROJECT

is used to describe plans for testing the software. Any verification and validation activity

Reviewed STD Document Revised Version 07.06.2010

Presentation At the end of first and second semester 2 presentations will be done which reflects the work we done during project development.

15-16-17.06.2010

Final Versions of documents All documents are given with last versions

07.06.2010

Project Contest 18.06.2010

Table 1. Project Deliverables

There will be four major deliverables in the project which are SPMP, SRS, SDD, and STD.

All these documents will be prepared according to the IEEE standards.

These deliverables can be downloaded from our website. Each and every updates of those

deliverables will be announced from the website as well.

1.1.4. Schedule and Budget Summary

We estimate schedule allocation in section 5.2.4 combining with budget allocation.

1.2. Evolution of the SPMP

After this report, students and advisors with the new additions are possible.

Atılım University


9/37



Version: Final Copy

Where am I? PROJECT

2. Reference Materials

IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans

Pressman, Roger S., Software Engineering, 4th edition, McGraw-Hill, 1997

Fairley, R. E., Work breakdown Structure, Software Engineering Project Management, IEEE CS Press, 1997

Atılım University


10/37



Version: Final Copy

Where am I? PROJECT

3. Definitions, Acronyms, and Abbreviations

CMMI: Capability Maturity Model Integration

SPMP: Software Project Management Plan

SRS: Software Requirements Specification

JVM: Java Virtual Machine

V&V: Verification and Validation

XML: Extensible Markup Language

HW: Hardware

SW: Software

LOC: Line of Code

KLOC: Kilo Line of Code

IEEE: Institute of Electrical and Electronical Engineers

JRE: Java Runtime Environment

COCOMO: Constructive Cost Model

IDE: Integrated Development Environment

RAM: Read Only Memory

XML: Extensible Markup Language

SDD: Software Design Description

STD: Software Test Documentation

WBS: Work Breakdown Structure

PC: Personal Computer

Atılım University


11/37



Version: Final Copy

Where am I? PROJECT

4. Project Organization

4.1. External Interfaces

This project is a senior project. Therefore, project will controlled by supervisor and quality group

in each step. Supervisor will determine mistakes on project before implementation. After GPS team

correct mistakes, documents are delivered as a new version.

4.2. Internal Structure

Phases Responsible

Project Management Project Manager

Web Development Web Developer

Documentation Documentation

Testing & maintenance Tester

Table 2. Internal structure

4.3. Project Responsibilities

MEMBER NAME Responsibility E-Mail

Ismet Serturk BASOGLU Project Member, Web Developer [email protected]

Efraim KORKMAZ Web Developer, Documentation [email protected]

Selcuk DEMIRCI Tester, Documentation [email protected]

Table 3. Project Responsibilities

Atılım University


12/37



Version: Final Copy

mailto:[email protected]



Where am I? PROJECT

5. Managerial Process Plans

5.1. Start-up Plan

This section contains our project’s estimation plan, staffing plan, resource acquisition plan,

and training plan. In the following subsections, all these plans will exist with their explanations in

the details.

5.1.1. Estimation Plan

The beginning of a project, it is difficult to predict. This report is the first design of SPMP,

we can not expect an adequate data. Using the following function points, we will predict our

estimation plan.

Inputs Outputs Inquiries

Enter the GPS Program Save something like

maps, path throught Delete objects like

saved maps and path throught

Load objects like saved maps and path throught by press load button

Search something like cities, countries etc.. with enter location name or location coordinate

User will ask where I am

Error Message (if user Search Wrong place or Press Load if system will not have saved Objects.)

Load Objects Show by after Press Load Button

Searched cities, countries etc… shown by after Press Search Button

Shown where user is after user ask where I am

User will look, system has saved Objects for Delete or Load some objects

User will do Search User will as where I am

Table 4. Product Function I/O Summary

Number of inputs: 6

Number of outputs: 4

Number of inquiries: 3

Number of files: There exist no files.

Number of external interface: 6 (Microsoft Visual C# 2008 or C# or Microsoft Visual Basic 2008,

GPS Track Maker, OS, Printing)

Measurement Count ( C) Weighting Factor(W) W*C

Atılım University


13/37



Version: Final Copy

Where am I? PROJECT

Parameter

Inputs 6 3 18

Outputs 4 4 16

Inquiries 3 3 9

Files 0 7 0

External Interfaces 6 5 30

TOTAL 73

Table 5. Function Point Metrics

Atılım University


14/37



Version: Final Copy

Where am I? PROJECT

# Influence Factors Weight

(Fi)

Comments

1 Does the system require reliable backup

and recovery? 5

There is no back-up facility

provided by the system

2 Are data communications required?

5

Online data collection for batch

process

3 Are there distributed processing

functions? 1

Data transfer on-line in one direction

4 Is performance critical?

4

Online response time is not critical

5 Will the system run in an existing,

heavily utilized operational

environment?

1

Not directly related but will run in

the same memory space with other

operational programs.

6 Does the system require on-line entry? 5 Transaction is online

7 Does the on-line data entry require the

input transaction to be built over

multiple screens or operations?

4

8 Are the master files updated on-line? 1 Master files updated online

9 Are the inputs, outputs, files or inquiries

complex? 2

Only security issues are complex,

others are middle

10 Is the internal processing complex?

5

Authentication mechanism and

flexibility make the system complex

11 Is the code designed to be reusable?

4

The code can be adopted to other

systems

12 Are conversion and installation included

in the design? 4

Only for mobile application

13 Is the system designed for multiple

installations in different organizations? 0

There is no need to installation in

different organization

14 Is the application designed to facilitate Design and interfaces make the

Atılım University


15/37



Version: Final Copy

Where am I? PROJECT

change and ease of use by the user? 4 system flexible

ΣFi 45

Table 6. Complex Adjustment Values

Function Point= Count-Total*[0.65+0.01*sum(Fi)]

Function Point= 73*[0.65+0.01* 45]

Function Point= 80, 30

COCOMO

LOC=FP*Language factor

We use Visual C# or C# or Visual Basic. These programs average Language factor is 58. When

we put it to the equation we get:

LOC=80.30*58=4657.40

KLOC=4657.40/1000=4, 6574

By using cocomo equations, we found the following results;

E=ab(KLOC)bb (Effort)

D=cb (E) d

b (Duration)

Our Project is semi-detached so we use 3,0 for ab ; 1,12 for bb ; 2,5 for cb and 0,35 for d

b So:

E=3,0*(4,6574)1,12 = 16,805 person-month

D=2,5*(16,805)0,35= 6.711 months

E/D ratio gives the recommended number of people. For Our Project it is:

E/D=16,805/6,711=2.504 ≈3 as our group consist of three people we fulfill necessary human

resources.

5.1.2. Resource Acquisition Plan

Our entire Project, we will use team members computers. The worst computer has

following hardwares:

P IV – 3.0 GHZ

1.5 GB RAM (min)

120 GB hard disk space

Ethernet card

Atılım University


16/37



Version: Final Copy

Where am I? PROJECT

512 MB Graffic Card

In addition to these HW requirements also the following SW requiremnets should be

satisfied:

Visual C#

Visual Basic

C#

GPS Track Maker

MS Office

MS Project

Internet Explorer

5.1.3. Project Staff Training Plan

GPS team members will learn that don’t know topics and develop them. They will

continuously search about this project. When they meet, they transfer knowledge from member to

another. The team members don’t have enough knowledge and experience in Visual C#, Visual

Basic, C# and GPS Track Maker. Thus, they will gain knowledge about these programs.

5.2. Work Plan

5.2.1. Work Activities

In the following table you can see the work activities of the Our Project:

1 CUSTOMER MEETING

1.1 Contact with customer

1.2 Problem Description

1.3 Requirements Gathering

2 PREPARING SPMP

2.1 Work Products & Activities Decomposition

2.2 Product Size Estimation

2.3 Process Model

2.4 Resource Allocation

2.5 Schedule Allocation

2.6 Risk Management Plan

Atılım University


17/37



Version: Final Copy

Where am I? PROJECT

2.7 Technical Process Plans

2.8 Supporting Process Plans

2.9 Documentation

2.10 Review of SPMP

2.11 Revised SPMP

2.12 Approval of SPMP

3 PREPARING SRS

3.1 Contact with Customer

3.2 Formal Identification of User Group

3.3 Product Functions

3.4 Behavioral Requirements Specification

3.5 Non-Behavioral Requirements Specification

3.6 Documentation

3.7 Review of SRS

3.8 Revised SRS

3.9 Approval of SRS

4 PREPARING SDD

4.1 SDD Basic Concepts

4.2 Database Design

4.3 Interface Design

4.4 Algorithms Design

4.5 Documentation

4.6 Review of SDD

4.7 Revised SDD

4.8 Approval of SDD

5 PREPARING STD

5.1 V&V Management

5.2 V&V Acquisition

Atılım University


18/37



Version: Final Copy

Where am I? PROJECT

5.3 V&V Supply

5.4 V&V Development

5.5 V&V Operation

5.6 V&V Maintenance

5.7 Documentation

5.8 Review of STD

5.9 Revised STD

5.10 Approval of STD

6 CODING

6.1 GPS Track Maker Management

6.1.1 GPS Track Maker Parsing

6.1.2 GPS Track Maker Creation

6.2 CODE REVIEW

6.2.1 Authorization

6.2.2 User interface design

6.2.3 Report Preparation

7 TESTING

7.1 GPS Test

7.2 Location Test

7.3 System Test

8 USER MANUAL

8.1 GPS User Manual

8.2 Track Maker User Manual

9 DEPLOYMENT

9.1 Approval of the product

Table 7. Project work activity

Atılım University


19/37



Version: Final Copy

Where am I? PROJECT

5.2.2. Schedule Allocation

We estimate schedule allocation in section 5.2.4 combining with budget allocation.

5.2.3. Resource Allocation

Tables related to resource allocation are stated below:

WORK ACTIVITY

REQUIRED SKILL BASED ON

Customer Meeting Human RelationsFace to face, E-

mail

Preparing SPMPKnowledge of IEEE Std and Estimation Techniques, Planning

And CoordinationIEEE Std. 1058-

1998

Preparing SRS SW EngineeringIEEE Std. 830-

1998

Preparing SDD SW EngineeringIEEE Std. 1058-

1998

Preparing STD SW EngineeringIEEE Std. 1016-

1998

Coding Knowledge of Java and GPS Track Maker IEEE Standards

Testing Knowledge Of Control Engineering and Testing Techniques IEEE Standards

User Manual Knowledge of User Manual StandardIEEE Std. 1063-

1987

Deployment Knowledge of Review Techniques IS 502 Standards

Table 8. Resource allocation for Work Activity

CUSTOMER MEETING

WBS WORK PACKAGES SW TOOLS HUMAN RESOURCES HW RESOURCES

1.1 Contact with customer - Team -

1.2 Problem Description Ms Office,

Java

Team PC and peripherals

1.3 Requirements Gathering Ms Office,

Java

Team PC and peripherals

Table 9. Resource Allocation for customer Meeting

Atılım University


20/37



Version: Final Copy

Where am I? PROJECT

PREPARING SPMP

WBS WORK PACKAGES SW TOOLS HUMAN RESOURCES

HW RESOURCES

2.1 Work Products & Activities Decomposition

MS Office, MS Project

Team PC and Peripherals

2.2 Product Size Estimation MS Office Team PC and Peripherals

2.3 Process Model MS Office Team PC and Peripherals

2.4 Resource Allocation MS Office Team PC and Peripherals

2.5 Schedule Allocation MS Office Team PC and Peripherals

2.6 Risk Management Plan MS Office Team PC and Peripherals

2.7 Technical Process Plans MS Office Team PC and Peripherals

2.8 Supporting Process Plans MS Office Team PC and Peripherals

2.9 Documentation MS Office Team PC and Peripherals

2.10 Review of SPMP - Supervisor and Customer

-

2.11 Revised SPMP MS Office Team PC and Peripherals

2.12 Approval of SPMP - - -

Table 10. Resource Allocation for preparing SPMP

PREPARING SRS


HW RESOURCES

3.1 Contact with Customer - Team -

3.2 Formal Identification of User Group

Ms Office Team PC & Peripherals

3.3 Product Functions Ms Office Team PC & Peripherals

Atılım University


21/37



Version: Final Copy

Where am I? PROJECT


Ms Office, Visual C#

Team PC & Peripherals


Ms Office Team PC & Peripherals

3.6 Documentation Ms Office, Visual C#


3.7 Review of SRS - Supervisor and Customer

PC & Peripherals

3.8 Revised SRS Ms Office, Visual C#


3.9 Approval of SRS - - PC & Peripherals

Table 11. Resource Allocation for preparing SRS

PREPARING SDD

WBS WORK PACKAGES

SW TOOLS HUMAN RESOURCES

HW RESOURCES

4.1 SDD Basic Concepts MS Office TeamPC and Peripherals

4.2 Database Design MS Office TeamPC and Peripherals

4.3 Interface Design MS Office TeamPC and Peripherals

4.4 Algorithms Design MS Office TeamPC and Peripherals

4.5. Documentation MS Office, Visual C#

TeamPC and Peripherals

4.6 Review of SDD - --

4.7Revised SDD

MS Office, Visual C#

TeamPC and Peripherals

4.8 Approval of SDD - - -

Table 12. Resource Allocation for preparing SDD

Atılım University


22/37



Version: Final Copy

Where am I? PROJECT

PREPARING STD

WBS WORK PACKAGES

SW TOOLS HUMAN RESOURCES

HW RESOURCES

5.1 V&V Management MS Office Team PC &Peripherals

5.2V&V Acquisition

MS Office, Visual C#

Team PC &Peripherals

5.3 V&V Supply MS Office Team PC &Peripherals

5.4 V&V Development MS Office Team PC &Peripherals

5.5 V&V Operation MS Office Team PC &Peripherals

5.6 V&V Maintenance MS Office Team PC &Peripherals

5.7 Documentation MS Office Team PC &Peripherals

5.8 Review of STD - - PC &Peripherals

5.9 Revised STD MS Office Team PC &Peripherals

5.10 Approval of STD - - PC &Peripherals

Table 13. Resource Allocation for preparing STD

CODING


HW RESOURCES

6.1 GPS Track Maker Management

MS Office, GPS Track Maker Management

Team PC &Peripherals

6.1.1 GPS Track Maker Parsing

GPS Track Maker Team PC &Peripherals

6.1.2 GPS Track Maker Creation

GPS Track Maker Team PC &Peripherals

6.2 CODE REVIEW Team PC &Peripherals

6.2.1 Authorization Visual C# Team PC &Peripherals

6.2.2 User interface design Visual C# Team PC &Peripherals

6.2.3 Report Preparation MS Office Team PC &Peripherals

Table 14. Resource Allocation for Coding

Atılım University


23/37



Version: Final Copy

Where am I? PROJECT

TESTING


7.1 GPS Test GPS Track Maker Team PC &Peripherals

7.2 Location Test GPS Track Maker Team PC &Peripherals

7.3 System Test GPS Track Maker Team PC &Peripherals

Table 15. Resource Allocation for preparing Testing

USER MANUAL


8.1 GPS User Manual MS Office Team PC &Peripherals

8.2 Track Maker User Manual

MS Office Team PC &Peripherals

Table 16. Resource Allocation for preparing User Manual

DEPLOYMENT


9.1Approval of the product

- Team PC &Peripherals

Table 17. Resource Allocation for Deployment

5.2.4. Budget 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 15 YTL/hour and assumed that supervisor has 20

YTL/hour salary. Budget and schedule allocation tables for each work activity are shown below:

Customer Meeting

WBS Work Packages Start Date

(D.M.Y)

End Date

(D.M.Y)

Work Hour

People Assigned

Cost

(YTL)

1.1 Contact with customer

16.10.2009 16.10.2009 1 Team 45

1.2 Problem 16.10.2009 16.10.2009 2 Team 90

Atılım University


24/37



Version: Final Copy

Where am I? PROJECT

Description

1.3 Requirements Gathering

16.10.2009 16.10.2009 2 Team 90

Table 18. Schedule and Budget Allocation for Customer Meeting

Preparing SPMP


(D.M.Y)

End Date

(D.M.Y)

Work Hour

People Assigned

Cost

(YTL)

2.1 Work Products & Activities

Decomposition

17.10.2009 18.10.2009 5 Team 225

2.2 Product Size Estimation

18.10.2009 18.10.2009 5 Team 225

2.3 Process Model 19.10.2009 19.10.2009 4 Team 180

2.4 Resource Allocation

19.10.2009 19.10.2009 2 Team 90

2.5 Schedule Allocation

20.10.2009 20.10.2009 2 Team 90

2.6 Risk Management Plan

20.10.2009 20.10.2009 3 Team 135

2.7 Technical Process Plans

20.10.2009 20.10.2009 3 Team 135

2.8 Supporting Process Plans

20.10.2009 20.10.2009 2 Team 90

2.9 Documentation 21.10.2009 21.10.2009 10 Team 450

2.10 Review of SPMP 06.01.2010 08.01.2010 1 Supervisor 20

2.11 Revised SPMP 06.01.2010 08.01.2010 6 Team 270

2.12 Approval of SPMP

06.01.2010 08.01.2010 - - 0

Table 19. Schedule and Budget Allocation for Preparing SPMP

Preparing SRS


(D.M.Y)

End Date

(D.M.Y)

Work Hour

People Assigned

Cost

(YTL)

3.1 Contact with Customer

10.11.2009 10.11.2009 1 Team 45

3.2 Formal 10.11.2009 10.11.2009 2 Team 90

Atılım University


25/37



Version: Final Copy

Where am I? PROJECT

Identification of User Group

3.3 Product Functions 11.11.2009 12.11.2009 10 Team 450


13.11.2009 14.11.2009 5 Team 225


15.11.2009 16.11.2009 3 Team 135


3.7 Review of SRS 25.01.2010 25.01.2010 1 Supervisor 20

3.8 Revised SRS 25.01.2010 25.01.2010 6 Team 270

3.9 Approval of SRS 25.01.2010 25.01.2010 - - 0

Table 20. Schedule and Budget Allocation for Preparing SRS

Preparing SDD


(D.M.Y)

End Date

(D.M.Y)

Work Hour

People Assigned

Cost

(YTL)

4.1 SDD Basic Concepts

10.12.2009 10.12.2009 4 Team 180

4.2 Database Design 11.12.2009 12.12.2009 5 Team 225

4.3 Interface Design 13.12.2009 13.12.2009 10 Team 450

4.4 Algorithms Design

14.12.2009 15.12.2009 12 Team 540


4.6 Review of SDD 22.02.2010 22.02.2010 1 Supervisor 20

4.7 Revised SDD 22.02.2010 22.02.2010 8 Team 360

4.8 Approval of SDD 22.02.2010 22.02.2010 - - 0

Table 21. Schedule and Budget Allocation for Preparing SDD

Preparing STD


(D.M.Y)

End Date

(D.M.Y)

Work Hour

People Assigned

Cost

(YTL)

Atılım University


26/37



Version: Final Copy

Where am I? PROJECT

5.1 V&V Management 09.03.2010 09.03.2010 4 Team 180

5.2 V&V Acquisition 09.03.2010 09.03.2010 3 Team 135

5.3 V&V Supply 10.03.2010 10.03.2010 3 Team 135

5.4 V&V Development 11.03.2010 11.03.2010 4 Team 180

5.5 V&V Operation 12.03.2010 12.03.2010 3 Team 135

5.6 V&V Maintenance 13.03.2010 13.03.2010 3 Team 135


5.8 Review of STD 24.03.2010 24.03.2010 1 Supervisor 20

5.9 Revised STD 24.06.2010 24.03.2010 8 Team 360

5.10 Approval of STD 24.06.2010 24.03.2010 - - 0

Table 22. Schedule and Budget Allocation for Preparing STD

5.3. Control Plan

5.3.1. Requirements Control Plan

Changes are to be made in the requirements, after the completion of the SPMP step. Team

members have a meeting for revision. Document will be examined for the major/minor revision.

Resource allocation, Schedule allocation and estimation plan will be reconsidered and updated.

Budget is not important due to this project is a senior Project. Document will be updated as a new

version of all projects.

5.3.2. Schedule Control Plan

The Project consists of certain time interval. Project group members constantly

conversation in messanger, meeting one or two days in a week, and they effort to finish the Project.

The results of the meeting between team members will be discussed with supervisor and keep on

regular basis.

5.3.3. Quality Control Plan

Supervisor, who is Atilla BOSTAN, will control all working (documents, coding, demo, etc.)

by GPS Team. If supervisor is not give approval to the working , GPS team will not do next step.

Work Products and Items

Suitable to

Standards

Needs Revisons Explation

Atılım University


27/37



Version: Final Copy

Where am I? PROJECT

Software Requirements Specification (SRS)

X Major revisions

SRS Review X

SRS Approval X Revisions are made and plan is approved.

Software Design Description (SDD)

X Major revisions

SDD Review X

SDD Approval X Revisions are made and plan is approved.

Software Test Documentation (STD)

X X Major revisions

STD Review X

STD Approval X Revisions are made and plan is approved.

Project Plan

Project Plan Review

Approval of Project Plan

Design

Design Review

Design Approval

Coding

Test

Implementation

Product Review

Product Approval

Table 23. Quality Control Plan

5.3.4. Reporting Plan

Each of versions of all the documents and updates and status reports will be sent and

discussed with the supervisor and upon approval the approved document will be circulated to the

Atılım University


28/37



Version: Final Copy

Where am I? PROJECT

other members of the committee. The report on the status of the project will be sent to the members

and interview about mistakes or lacks of reports.

5.3.5. Metrics Collection Plan

In our project, each of metrics are saved system database. If we will encounter any problem, we

will use these saved metrics with connect system database.

5.4. Risk Management Plan

RISKS PROBABILITY IMPACT

1(low) – 5(high)

REFERENCES

Quality of product documentation and coding are not suitable

%35 3 5.4.1.1

Disagree between team members

%8 2 5.4.1.2

Unavailability of team members

%8 2 5.4.1.3

Timing Problem %15 4

Health problem %35 1

Mistake in coding %15 4

System may be not work

%15 4

Table 24. Probability of Risks

Probability Uncertainty Statement

> % 80 Almost certainly

%80 - %61 Probable, probably

%60 – %41 Doubtable

%40 – %21 Unlikely

< % 20 Highly unlikely

Atılım University


29/37



Version: Final Copy

Where am I? PROJECT

Table 25. Ratio of Probability

5.4.1. Description of Risks

5.4.1.1. Quality of product documentation and coding are not suitable

GPS team prepares the project planning, software documentation and coding with less

experience. Thus, The GPS Team must, try to prepare every documents of project in high

priority and control all steps of documentation.

5.4.1.2. Disagree Between Team Members

The GPS Team must behave respectfully and be careful not disagree with each other. If

The GPS Team has this problem, they must solve the problem between team members in early time

and prevention disagreement things before the conflict.

5.4.1.3. Unavailability of Team Members

The GPS Team must use all common free time to work on project. Before The GPS Team

start does project, they have to adjust date before starting the project. If The GPS Team has a

problem about meeting, Team must use all communication (telephone, msn, e-mail …) , and may

be prevent problem of time.

5.4.1.4. Timing Problem

The GPS Team must split the project and prepare the working program in weekly and

check each team members program every week and control how project is run.

5.4.1.5. Health Problem

The GPS Team must take care of their health. If team have health problem, they must do

work overtime or adjust new part-time labors and work another team member to instead of ill team

member.

5.4.1.6. Mistake in Coding

If The GPS Team does not want any mistake in coding, Team must do control the coding

and test every week or control and test small part and back up codes every week.

5.4.1.7. System may be not Work

The GPS Team must do not notice the mistake in design or coding. If Team does not want

any problem, they must do control the design again and again and contact with instructor when

coding and designing.

Atılım University


30/37



Version: Final Copy

Where am I? PROJECT

Atılım University


31/37



Version: Final Copy

Where am I? PROJECT

6. Technical Process Plans

6.1. Process Model

We in our project, we used Waterfall Process Model. The initialization of the

project will start in October 2009, at the end of January 2010; a prototype of the project

will be developed. And finally at the end of June 2010, our project will be finished. The

schedule plan for the project table will be given in the following table, table 24.

Activity Start Date End DateTime

(date/man)

Defining PS Oct. 16, 2009 Oct. 20, 2009 4

Initial Planning Oct. 17, 2009 Oct. 20, 2009 21

Reviewing IP Oct. 22, 2009 Oct. 23, 2009 6

SPMP Documenting Oct. 07, 2009 Oct. 21, 2009 44

Reviewing SPMP Nov. 10, 2009 Jan. 08, 2009 6

SRS Documenting Nov. 10, 2009 Nov. 18, 2009 42

SDD Documenting Dec. 01, 2009 Dec.30, 2009 44

Coding and Testing Jan. 01, 2010 June 10, 2010 100

Total Elapsed Time Oct. 16, 2009 June 19, 2010 267 date/man

Table 26. Product Time Schedule

Atılım University


32/37



Version: Final Copy

Where am I? PROJECT

TASK DUE TO REVİEW DATE DELIVERED MAJOR Milestone

SPMP Oct.21, 2009 Jan.8, 2010 YES YES

SRS Nov.18, 2009 Jan.26-27-28, 2010 YES YES

SDD Jan.4, 2009 April 5, 2010 YES YES

STD Mar.15, 2010 June 07, 2010 YES YES

Coding & Testing NO YES

User Manual NO YES

Final Product June 07, 2010 NO YES

6.2. Methods, Tools, and Techniques

Tools and techniques used to realize these working and to develop final product are shown

below:

SW TOOLS: Java, MS Office, MS Project, GPS Track Maker 13.5.409, Internet Explorer,

HW TOOLS: PC and Peripherals

PERSONAL SKILLS: Communication skills, XML, Java, SW Engineering Processes, Review

and Testing Techniques, User Manual, Planning and Coordination.

6.3. Infrastructure Plan

This software, internet connection, hardware and operating system are available

from other sources and from the internet is provided by team members..Projects that help

us the GPS Track Maker and JAVA programs can be downloaded from the internet and

available free. Each team member has one PC with the operating system of Windows XP

and Vista. We also use GPS track maker program for transfer data from GPS to computer

and computer to GPS also we are make ourselves develop. Group members identify

themselves as areas of project work as a group and as individuals we project focuses.

These places may be one team member’s house, library, and school’s studying room.

Atılım University


33/37



Version: Final Copy

Where am I? PROJECT

6.4. Product Acceptance Plan

Customer wants a review process will be reviewed and problems will be solved. By

the consultant and the client is missing a delivery point is checked to determine. Then

cover the missing points, a new version is created and delivered to the customer is

presented. This process shall continue until the customer and supervisor satisfaction is

achieved. In this way, the customer really needs to improve the basic product warranties

may be the result. If there are problems to be solved, and the product will deliver the

necessary points will change.

Atılım University


34/37



Version: Final Copy

Where am I? PROJECT

7. Supporting Process Plans

7.1. Configuration Management Plan

This part is very important for future changes for our project. When our project supervisor

or customers comes a request for project change, we will quickly review our previous report and

we will change our report like desired format. As the regeneration of the report, the report names

will also change. Such as;

First Deliverable:

Deliverable Name V1.0, like SPMP V1.0

Major Change for Deliverable:


Minor Change for Deliverable:


7.2. Quality Assurance Plan

Quality Assurance Plan:

All project reports must be made according to the IEEE a standard format

and should be submitted according to this format. Customer meetings are very important, that’s

why these meetings should be well organized. Project members must follow project Schedule very

carefully and projects should be delivered in a time.

Verification and Validation Plan:

Verification Plan

The process of determining to make the right product.

Made full order to produce for needs of customers.

All project’s delivered time and every steps made according to

accuracy of the SW.

Validation Plan

Products are made to ensure that the correct process.

About producing the right product.

Made full order to produce for needs of customers.

Atılım University


35/37



Version: Final Copy

Where am I? PROJECT

7.3. Documentation Plan

All documents will be made according to IEEE standards. For these IEEE templates

considers for SPMP, SRS, SDD, and STD. Each deliverable document will be reviewed by the

supervisor.

7.4. Deployment Plan

After our project is finish, our project resembles a desktop application. Thus, every people use

our project. But, if people use GPS program, their computers or laptops must take signals from

satellite.

7.5. Review Plan

After each phase of Project which are SPMP, SRS, SDD, STD are completed, are reviewed.

There are two types of review.

First review is done by GPS team after the completion of deliverable.

Second review is done by supervisor. Supervisor controls verification of the deliverable and to

cover requirements of the product.

Atılım University


36/37



Version: Final Copy

Where am I? PROJECT

8. Appendices

8.1. Appendix 1 – Ganchart

Atılım University


37/37



Version: Final Copy

Documents

Example of SPMP Document