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 1 2 Status* Released In Change Date 21.10.2009 08.01.2010 Responsible Ismet Serturk BASOGLU Ismet Serturk BASOGLU SPMP 1.0 SPMP 1.1 Version Definition
*: Draft, In Review, Released, Approved, Rejected, In Change
Atlm University COMPE/SE/ISE 491-492
2/36 Team # 13 (Team Lost)
System Project Management Plan Version: Final Copy
Where am I? PROJECT
List of Figures
List of Tables
Table 1. Project Deliverables..9 Table 2. Internal structure.12 Table 3. Project Responsibilities12 Table 4. Product Function I/O Summary13 Table 5. Function Point Metrics.14 Table 6. Complex Adjustment Values..16 Table 7. Project work activity19 Table 8. Resource allocation for Work Activity..20 Table 9. Resource Allocation for customer Meeting20 Table 10. Resource Allocation for preparing SPMP.21 Table 11. Resource Allocation for preparing SRS22 Table 12. Resource Allocation for preparing SDD..22 Table 13. Resource Allocation for preparing STD.23 Table 14. Resource Allocation for Coding23 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 SPMP25 Table 20. Schedule and Budget Allocation for Preparing SRS26 Table 21. Schedule and Budget Allocation for Preparing SDD..26 Table 22. Schedule and Budget Allocation for Preparing STD27 Table 23. Quality Control Plan..28 Table 24. Probability of Risks29 Table 25. Ratio of Probability..29 Table 26. Product Time Schedule32
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......................................................................................................................................6 1.1.1. Purpose, Scope, and Objectives........................................................................................................6 1.1.2. Assumptions and Constraints............................................................................................................6 1.1.3. Project Deliverables..........................................................................................................................7 1.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..................................................................................................................................12 4.2. Internal Structure....................................................................................................................................12 4.3. Project Responsibilities..........................................................................................................................12 5. MANAGERIAL PROCESS PLANS.........................................................................................................13 5.1. Start-up Plan...........................................................................................................................................13 5.1.1. Estimation Plan...............................................................................................................................13 5.1.2. Resource Acquisition Plan..............................................................................................................16 5.1.3. Project Staff Training Plan.............................................................................................................17 5.2. Work Plan...............................................................................................................................................17 5.2.1. Work Activities................................................................................................................................17 5.2.2. Schedule Allocation.........................................................................................................................19 5.2.3. Resource Allocation........................................................................................................................19 5.2.4. Budget Allocation............................................................................................................................24 5.3. Control Plan............................................................................................................................................27 5.3.1. Requirements Control Plan.............................................................................................................27 5.3.2. Schedule Control Plan....................................................................................................................27 5.3.3. Quality Control Plan.......................................................................................................................27 5.3.4. Reporting Plan................................................................................................................................28 5.3.5. Metrics Collection Plan..................................................................................................................28 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........................................................................................28 5.4. Risk Management Plan...........................................................................................................................28 5.4.1. Description of Risks........................................................................................................................29 6. TECHNICAL PROCESS PLANS.............................................................................................................31 6.1. Process Model.........................................................................................................................................31 6.2. Methods, Tools, and Techniques............................................................................................................32 6.3. Infrastructure Plan..................................................................................................................................32 6.4. Product Acceptance Plan........................................................................................................................32 7. SUPPORTING PROCESS PLANS...........................................................................................................34 7.1. Configuration Management Plan............................................................................................................34 7.2. Quality Assurance Plan..........................................................................................................................34 7.3. Documentation Plan...............................................................................................................................35 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................................35
Where am I? PROJECT 7.4. Deployment Plan....................................................................................................................................35 7.5. Review Plan............................................................................................................................................35 8. APPENDICES..............................................................................................................................................36 8.1. Appendix 1 Ganchart...........................................................................................................................36
Where am I? PROJECT
1. Overview
1.1.
1.1.1.
Project Summary
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.
6/36 Team # 13 (Team Lost) System Project Management Plan 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
Description Delivery Date
Work Product Problem Statement Initial Plan
Define the problem (submitted) 30.09.2009 Define the managerial (submitted) technical and01.10.2009 processes 01.10.2009
Reviewed Initial Plan SPMP Document
Revised version(submitted)
Software Project Management 21.10.2009 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
Where am I? PROJECT
and their dates. Reviewed SPMP Document SRS Document Revised version 08.01.2010
Software Requirements16.11.2009 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. Revised version 25.01.2010
Reviewed SRS Document SDD Document
Software Design Description is 30.12.2009 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.
Reviewed SDD Document Presentation
Revised version
22.02.2010
At the end of first and second 26-27-28.01.2010 semester 2 presentations will be done which reflects the work we done during project development. Software Test Documentation15.03.2010 is used to describe plans for
STD Document
Where am I? PROJECT
testing the verification activity Reviewed STD Document Presentation
software. Any and validation 07.06.2010
Revised Version
At the end of first and second15-16-17.06.2010 semester 2 presentations will be done which reflects the work we done during project development. All documents are given with07.06.2010 last versions 18.06.2010 Table 1. Project Deliverables
Final Versions of documents
Project Contest
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.
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
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
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.
Phases
Internal Structure
Responsible Project Manager Web Developer Documentation Tester
Project Management Web Development Documentation Testing & maintenance Table 2. Internal structure
4.3.
Project Responsibilities
Responsibility Project Member, Web Developer Web Developer, Documentation Tester, Documentation E-Mail ismetserturk@hotmail.com efsane_-_1907@hotmail.com demirci_40@hotmail.com
MEMBER NAME Ismet Serturk BASOGLU Efraim KORKMAZ Selcuk DEMIRCI
Table 3. Project Responsibilities
Where am I? PROJECT
5. Managerial Process Plans

5.1. Start-up Plan
This section contains our projects 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 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 Outputs 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 Inquiries 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)
Where am I? PROJECT
Measurement Parameter Inputs Outputs Inquiries Files External Interfaces TOTAL
Count ( C) 6 4 3 0 6
Weighting Factor(W) 3 4 3 7 5
W*C 18 16 9 0 30 73
Table 5. Function Point Metrics
Where am I? PROJECT
# 1
Influence Factors Does the system require reliable backup and recovery?
Weight (Fi)
Comments There is no back-up facility provided
by the system Online data collection for batch
Are data communications required? 5
process Data transfer on-line in one direction
Are
there
distributed
processing 1
functions? 4 Is performance critical?
Online response time is not critical 4
Will the system run in an existing, heavily environment? utilized operational 1 5
Not directly related but will run in the same memory space with other operational programs. Transaction is online
6 7
Does the system require on-line entry? Does the on-line data entry require the input transaction to be built over multiple screens or operations?
4 1 Master files updated online Only security issues are complex, 2 others are middle Authentication 5 mechanism and
8 9
Are the master files updated on-line? Are the inputs, outputs, files or inquiries complex?
1 0 1 1 1 2 1 3 1 4
Is the internal processing complex?
flexibility make the system complex The code can be adopted to other
Is the code designed to be reusable? 4 Are conversion and installation included in the design? Is the system designed for multiple installations in different organizations? Is the application designed to facilitate change and ease of use by the user? Fi 4 45 0 4
systems Only for mobile application
There is no need to installation in different organization Design and interfaces make the system flexible
Table 6. Complex Adjustment Values Function Point= Count-Total*[0.65+0.01*sum(Fi)]
Where am I? PROJECT
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) db (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 db 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 512 MB Graffic Card In addition to these HW requirements also the following SW requiremnets should be satisfied: Visual C# Visual Basic
Where am I? PROJECT
C# GPS Track Maker MS Office MS Project Internet Explorer
5.1.3.
Project Staff Training Plan
GPS team members will learn that dont 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 dont 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.
5.2.1.
Work Plan
Work Activities
In the following table you can see the work activities of the Our Project:
1 1.1 1.2 1.3 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 CUSTOMER MEETING Contact with customer Problem Description Requirements Gathering PREPARING SPMP Work Products & Activities Decomposition Product Size Estimation Process Model Resource Allocation Schedule Allocation Risk Management Plan Technical Process Plans Supporting Process Plans Documentation Review of SPMP
Where am I? PROJECT
2.11 2.12 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 5 5.1 5.2 5.3 5.4 5.5 5.6
Revised SPMP Approval of SPMP PREPARING SRS Contact with Customer Formal Identification of User Group Product Functions Behavioral Requirements Specification Non-Behavioral Requirements Specification Documentation Review of SRS Revised SRS Approval of SRS PREPARING SDD SDD Basic Concepts Database Design Interface Design Algorithms Design Documentation Review of SDD Revised SDD Approval of SDD PREPARING STD V&V Management V&V Acquisition V&V Supply V&V Development V&V Operation V&V Maintenance
Where am I? PROJECT
5.7 5.8 5.9 5.10 6 6.1 6.1.1 6.1.2 6.2 6.2.1 6.2.2 6.2.3 7 7.1 7.2 7.3 8 8.1 8.2 9 9.1
Documentation Review of STD Revised STD Approval of STD CODING GPS Track Maker Management GPS Track Maker Parsing GPS Track Maker Creation CODE REVIEW Authorization User interface design Report Preparation TESTING GPS Test Location Test System Test USER MANUAL GPS User Manual Track Maker User Manual DEPLOYMENT Approval of the product
Table 7. Project work activity
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:

Atlm University COMPE/SE/ISE 491-492 19/36 Team # 13 (Team Lost) System Project Management Plan Version: Final Copy
Where am I? PROJECT
WORK ACTIVITY Customer Meeting Preparing SPMP Preparing SRS Preparing SDD Preparing STD Coding Testing User Manual Deployment
REQUIRED SKILL Human Relations Knowledge of IEEE Std and Estimation Techniques, Planning And Coordination SW Engineering SW Engineering SW Engineering Knowledge of Java and GPS Track Maker Knowledge Of Control Engineering and Testing Techniques Knowledge of User Manual Standard Knowledge of Review Techniques
BASED ON Face to face, Email IEEE Std. 10581998 IEEE Std. 8301998 IEEE Std. 10581998 IEEE Std. 10161998 IEEE Standards IEEE Standards IEEE Std. 10631987 IS 502 Standards
Table 8. Resource allocation for Work Activity
CUSTOMER MEETING
WBS 1.1 1.2 WORK PACKAGES Contact with customer Problem Description SW TOOLS Ms Office, Java 1.3 Requirements Gathering Ms Office, Java Team PC and peripherals HUMAN RESOURCES Team Team HW RESOURCES PC and peripherals
Table 9. Resource Allocation for customer Meeting
PREPARING SPMP
WBS 2.1 2.2 WORK PACKAGES Work Products & Activities Decomposition Product Size Estimation SW TOOLS MS Office, MS Project MS Office HUMAN RESOURCES Team Team HW RESOURCES PC and Peripherals PC and
Where am I? PROJECT
Peripherals 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 Process Model Resource Allocation Schedule Allocation Risk Management Plan Technical Process Plans Supporting Process Plans Documentation Review of SPMP Revised SPMP Approval of SPMP MS Office MS Office MS Office MS Office MS Office MS Office MS Office MS Office Team Team Team Team Team Team Team Supervisor and Customer Team PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals -
Table 10. Resource Allocation for preparing SPMP
PREPARING SRS
WBS 3.1 3.2 3.3 3.4 3.5 3.6 3.7 WORK PACKAGES Contact with Customer Formal Identification of User Group Product Functions Behavioral Requirements Specification Non-Behavioral Requirements Specification Documentation Review of SRS SW TOOLS Ms Office Ms Office Ms Office, Visual C# Ms Office Ms Office, Visual C# HUMAN RESOURCES Team Team Team Team Team Team Supervisor and HW RESOURCES PC & Peripherals PC & Peripherals PC & Peripherals PC & Peripherals PC & Peripherals PC & Peripherals
Where am I? PROJECT
Customer 3.8 3.9 Revised SRS Approval of SRS Ms Office, Visual C# Team PC & Peripherals PC & Peripherals
Table 11. Resource Allocation for preparing SRS
PREPARING SDD WBS

4.1 4.2 4.3 4.4 4.5.
WORK PACKAGES
SDD Basic Concepts Database Design Interface Design Algorithms Design Documentation Review of SDD Revised SDD Approval of SDD
SW TOOLS
MS Office MS Office MS Office MS Office MS Office, Visual C# MS Office, Visual C# -
HUMAN RESOURCES
Team Team Team Team Team
HW RESOURCES
PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals PC and Peripherals -
4.6 4.7
Team
4.8
Table 12. Resource Allocation for preparing SDD
PREPARING STD WBS

5.1 5.2 5.3 5.4
WORK PACKAGES
V&V Management V&V Acquisition V&V Supply V&V Development
SW TOOLS
MS Office MS Office, Visual C# MS Office MS Office
22/36
HUMAN RESOURCES
Team Team Team Team
HW RESOURCES
PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals
Team # 13 (Team Lost)
Where am I? PROJECT
5.5 5.6 5.7 5.8 5.9 5.10
V&V Operation V&V Maintenance Documentation Review of STD Revised STD Approval of STD
MS Office MS Office MS Office MS Office -
Team Team Team Team -
PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals
Table 13. Resource Allocation for preparing STD
CODING
WBS 6.1 6.1.1 6.1.2 6.2 6.2.1 6.2.2 6.2.3 WORK PACKAGES GPS Track Maker Management GPS Track Maker Parsing GPS Track Maker Creation CODE REVIEW Authorization User interface design Report Preparation Visual C# Visual C# MS Office SW TOOLS MS Office, GPS Track Maker Management GPS Track Maker GPS Track Maker HUMAN RESOURCES Team Team Team Team Team Team Team HW RESOURCES PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals PC &Peripherals
Table 14. Resource Allocation for Coding
TESTING
WBS 7.1 7.2 7.3 WORK PACKAGES GPS Test Location Test System Test SW TOOLS GPS Track Maker GPS Track Maker GPS Track Maker HUMAN RESOURCES Team Team Team HW RESOURCES PC &Peripherals PC &Peripherals PC &Peripherals
Where am I? PROJECT
Table 15. Resource Allocation for preparing Testing
USER MANUAL
WBS 8.1 8.2 WORK PACKAGES GPS User Manual Track Maker User Manual SW TOOLS MS Office MS Office HUMAN RESOURCES Team Team HW RESOURCES PC &Peripherals PC &Peripherals
Table 16. Resource Allocation for preparing User Manual
DEPLOYMENT
WBS 9.1 WORK PACKAGES Approval of the product SW TOOLS HUMAN RESOURCES Team HW RESOURCES 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) 1.1 1.2 1.3 Contact with customer Problem Description Requirements Gathering 16.10.2009 16.10.2009 16.10.2009 End Date (D.M.Y) 16.10.2009 16.10.2009 16.10.2009 Work Hour 1 2 2 People Assigned Team Team Team Cost (YTL) 45 90 90
Table 18. Schedule and Budget Allocation for Customer Meeting
Preparing SPMP
WBS Work Packages Start Date (D.M.Y) End Date (D.M.Y) Work Hour People Assigned Cost (YTL)
Where am I? PROJECT
2.1
Work Products & Activities Decomposition Product Size Estimation Process Model Resource Allocation Schedule Allocation Risk Management Plan Technical Process Plans Supporting Process Plans Documentation Review of SPMP Revised SPMP Approval of SPMP
17.10.2009
18.10.2009
Team
225
2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12
18.10.2009 19.10.2009 19.10.2009 20.10.2009 20.10.2009 20.10.2009 20.10.2009 21.10.2009 06.01.2010 06.01.2010 06.01.2010
18.10.2009 19.10.2009 19.10.2009 20.10.2009 20.10.2009 20.10.2009 20.10.2009 21.10.2009 08.01.2010 08.01.2010 08.01.2010
5 4 2 2 3 3 2 10 1 6 -
Team Team Team Team Team Team Team Team Supervisor Team -
225 180 90 90 135 135 90 450 20 270 0
Table 19. Schedule and Budget Allocation for Preparing SPMP
Preparing SRS
WBS Work Packages Start Date (D.M.Y) 3.1 3.2 Contact with Customer Formal Identification of User Group Product Functions Behavioral Requirements Specification Non-Behavioral Requirements Specification Documentation Review of SRS 10.11.2009 10.11.2009 End Date (D.M.Y) 10.11.2009 10.11.2009 Work Hour 1 2 People Assigned Team Team Cost (YTL) 45 90
3.3 3.4
11.11.2009 13.11.2009
12.11.2009 14.11.2009
10 5
Team Team
450 225
3.5
15.11.2009
16.11.2009
Team
135
3.6 3.7
17.11.2009 25.01.2010
18.11.2009 25.01.2010
25/36
6 1
Team Supervisor
270 20
Team # 13 (Team Lost)
Where am I? PROJECT
3.8 3.9
Revised SRS Approval of SRS
25.01.2010 25.01.2010
25.01.2010 25.01.2010
6 -
Team -
270 0
Table 20. Schedule and Budget Allocation for Preparing SRS
Preparing SDD
WBS Work Packages Start Date (D.M.Y) 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 SDD Basic Concepts Database Design Interface Design Algorithms Design Documentation Review of SDD Revised SDD Approval of SDD 10.12.2009 11.12.2009 13.12.2009 14.12.2009 30.12.2009 22.02.2010 22.02.2010 22.02.2010 End Date (D.M.Y) 10.12.2009 12.12.2009 13.12.2009 15.12.2009 30.12.2009 22.02.2010 22.02.2010 22.02.2010 Work Hour 4 5 10 12 8 1 8 People Assigned Team Team Team Team Team Supervisor Team Cost (YTL) 180 225 450 540 360 20 360 0
Table 21. Schedule and Budget Allocation for Preparing SDD
Preparing STD
WBS Work Packages Start Date (D.M.Y) 5.1 5.2 5.3 5.4 5.5 5.6 5.7 V&V Management V&V Acquisition V&V Supply V&V Development V&V Operation V&V Maintenance Documentation 09.03.2010 09.03.2010 10.03.2010 11.03.2010 12.03.2010 13.03.2010 15.03.2010 End Date (D.M.Y) 09.03.2010 09.03.2010 10.03.2010 11.03.2010 12.03.2010 13.03.2010 15.03.2010 Work Hour 4 3 3 4 3 3 8 People Assigned Team Team Team Team Team Team Team Cost (YTL) 180 135 135 180 135 135 360
Where am I? PROJECT
5.8 5.9 5.10
Review of STD Revised STD Approval of STD
24.03.2010 24.06.2010 24.06.2010
24.03.2010 24.03.2010 24.03.2010
1 8 -
Supervisor Team -
20 360 0
Table 22. Schedule and Budget Allocation for Preparing STD
5.3.
5.3.1.
Control Plan
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 Suitable to Items Standards

Software Requirements Specification (SRS) SRS Review SRS Approval Software Design Description (SDD) SDD Review X X X
Needs Revisons
Explation
Major revisions
Revisions are made and plan is approved. X Major revisions
Where am I? PROJECT
SDD Approval Software Test Documentation (STD) STD Review STD Approval Project Plan Project Plan Review Approval of Project Plan Design Design Review Design Approval Coding Test Implementation Product Review Product Approval
X X X X X
Revisions are made and plan is approved. Major revisions
Revisions are made and plan is approved.
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 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
Where am I? PROJECT
RISKS
PROBABILITY
IMPACT 1(low) 5(high)
REFERENCES
Quality of product documentation and coding are not suitable Disagree between team members Unavailability of team members Timing Problem Health problem Mistake in coding System may be work not
%35
5.4.1.1
%8 %8 %15 %35 %15 %15
2 2 4 1 4 4
5.4.1.2 5.4.1.3
Table 24. Probability of Risks
Probability > % 80 %80 - %61 %60 %41 %40 %21 < % 20
Uncertainty Statement Almost certainly Probable, probably Doubtable Unlikely Highly unlikely Table 25. Ratio of Probability
5.4.1.
Description of Risks Quality of product documentation and coding are not suitable
5.4.1.1.
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
Where am I? PROJECT
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.
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.
Time Activity Start Date End Date (date/man) Defining PS Initial Planning Reviewing IP SPMP Documenting Reviewing SPMP SRS Documenting SDD Documenting Coding and Testing Total Elapsed Time Oct. 16, 2009 Oct. 17, 2009 Oct. 22, 2009 Oct. 07, 2009 Nov. 10, 2009 Nov. 10, 2009 Dec. 01, 2009 Jan. 01, 2010 Oct. 16, 2009 Oct. 20, 2009 Oct. 20, 2009 Oct. 23, 2009 Oct. 21, 2009 Jan. 08, 2009 Nov. 18, 2009 Dec.30, 2009 June 10, 2010 June 19, 2010 4 21 6 44 6 42 44 100 267 date/man
Table 26. Product Time Schedule
TASK SPMP SRS
DUE TO
Oct.21, 2009 Nov.18, 2009
REVEW DATE DELIVERED

Jan.8, 2010 Jan.26-27-28, 2010
MAJOR Milestone YES YES
YES YES
Where am I? PROJECT
SDD STD Coding & Testing User Manual Final Product
Jan.4, 2009 Mar.15, 2010
April 5, 2010 June 07, 2010
YES YES NO NO
YES YES YES YES YES
June 07, 2010
NO
6.2.
below:
Methods, Tools, and Techniques
Tools and techniques used to realize these working and to develop final product are shown
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 members house, library, and schools studying room.
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
Where am I? PROJECT
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.
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: Deliverable Name V2.0, like SPMP V2.0 Minor Change for Deliverable: Deliverable Name V1.1, like SPMP V1.1
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, thats 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 projects 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.
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.
Where am I? PROJECT
8. Appendices
8.1. Appendix 1 Ganchart

Example of SPMP Document

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Example of SPMP Document

Transféré par

Droits d'auteur :

Formats disponibles

WHERE AM I?

January 7th, 2010

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

Atlm University COMPE/SE/ISE 491-492

2/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Atlm University COMPE/SE/ISE 491-492

3/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Atlm University COMPE/SE/ISE 491-492

4/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Atlm University COMPE/SE/ISE 491-492

5/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Assumptions and Constraints

Atlm University COMPE/SE/ISE 491-492

Work Product Problem Statement Initial Plan

Reviewed Initial Plan SPMP Document

Atlm University COMPE/SE/ISE 491-492

7/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Reviewed SRS Document SDD Document

Reviewed SDD Document Presentation

Atlm University COMPE/SE/ISE 491-492

8/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

testing the verification activity Reviewed STD Document Presentation

software. Any and validation 07.06.2010

Final Versions of documents

Schedule and Budget Summary

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

Evolution of the SPMP

Atlm University COMPE/SE/ISE 491-492

9/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Atlm University COMPE/SE/ISE 491-492

10/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

3. Definitions, Acronyms, and Abbreviations

Atlm University COMPE/SE/ISE 491-492

11/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

MEMBER NAME Ismet Serturk BASOGLU Efraim KORKMAZ Selcuk DEMIRCI

Table 3. Project Responsibilities

Atlm University COMPE/SE/ISE 491-492

12/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

5. Managerial Process Plans

Table 4. Product Function I/O Summary

Atlm University COMPE/SE/ISE 491-492

13/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Measurement Parameter Inputs Outputs Inquiries Files External Interfaces TOTAL

Table 5. Function Point Metrics

Atlm University COMPE/SE/ISE 491-492

14/36 Team # 13 (Team Lost)

System Project Management Plan Version: Final Copy

Comments There is no back-up facility provided

by the system Online data collection for batch

Are data communications required? 5

process Data transfer on-line in one direction

functions? 4 Is performance critical?

Table 6. Complex Adjustment Values Function Point= Count-Total[0.65+0.01sum(Fi)]