doggy Client: in the window
SPMP: Build-a-Pet Kiosk
March 25, 2009
Prepared by: Phil Guevara, Edgar Garcia, Tuan Ha P.E.T. Boys Technologies
Doggy in the Window SPMP: Build-A-Pet Kiosk
Revision History
Revision
V1.0 V2.0
Change Description
Rough Draft Revision
Updated By
Phil, Edgar, Tuan Phil, Edgar, Tuan
Date
2009-03-18 2009-03-25
P.E.T Boys Technologies
i
Doggy in the Window SPMP: Build-A-Pet Kiosk
Table of Contents
1.! Introduction ...................................................................................................................... 1! 1.1! Project Scope ..................................................................................................................1! 1.2! Major Software Functions ................................................................................................1! 1.3! Performance/Behavior issues ...........................................................................................1 1.4! Management and technical constraints ............................................................................1 2.! Project Estimates............................................................................................................... 2 2.1! Historical data used for estimates ....................................................................................2! 2.2! Estimation techniques applied and results........................................................................2 2.2.1 !Estimation technique m ........................................................................................2 2.2.2 Estimate for technique m .....................................................................................3 2.3! Reconciled Estimate.........................................................................................................3! 2.4! Project Resources ............................................................................................................3 3.! Risk Management .......................................................................................................... 4! 3.1! Project Risks.................................................................................................................4! 3.2! Risk Table .....................................................................................................................4! 3.3! Overview of Risk Mitigation, Monitoring, Management..........................................6 4.! Project Schedule ............................................................................................................ 5! 4.1! Project Task Set...........................................................................................................5! 4.2! Functional Decomposition ..........................................................................................5! 5.! Staff Organization.......................................................................................................... 6! 5.1! Team Structure ............................................................................................................6! 5.2! Mangement Reporting and Communication.............................................................7! 6.! Tracking and Control Mechanisms .............................................................................. 8! 6.1! Quality assurance and control ...................................................................................8! 6.2! Change Management and Control............................................................................. 8
P.E.T Boys Technologies
ii
Doggy in the Window SPMP: Build-A-Pet Kiosk
1. Introduction
This section provides an overview of the entire problem or product. This document describes the problem, product description, rapid prototype, and acceptance criteria.
1.1 Project scope
This section provides an overview of the software engineering project.
1.2 Major software functions
A functional decomposition of the software (for use during estimation and scheduling) is developed here. Graphical User Interface Application Functions o Dog Program Dog inputs Processing Dog inputs Output Dog Visual o Owner Program Owner inputs Processing Owner inputs Output Owner Profile o Compatibility Program o Management Console Order processing Library updating Reporting Database
1.3 Performance/Behavior issues
Any special requirements for performance or behavior are noted here. Customer designed kiosks. Touch screen friendly.
1.3 Management and technical constraints
Any special constraints that affect the manner in which the project will be conducted (e.g., limited resources or 'drop dead' delivery date) or the technical approach to development are noted here. Customer wants the ability to expand to other types of pets in the future. Customer wants the option to have a future module that can tie the management console to a mobile device. Customer wants the GUI customizable to update the look of the GUI when needed.
P.E.T Boys Technologies
1
Doggy in the Window SPMP: Build-A-Pet Kiosk
2. Project Estimates
This section provides cost, effort and time estimates for the projects
2.1 Historical data used for estimates
Describes the historical data that is relevant to the estimates presented. We have 16 parts to the project and we estimate an average of 22 days for each project milestone. From past projects we have estimated that we will need to charge $150 to perform the project.
2.2 Estimation techniques applied and results
A description of each estimation technique and the resultant estimates are presented here. Graphical User Interface = 24 days Application Functions = 30 days o Dog Program = 16 days Dog inputs = 20 days Processing Dog inputs = 26 days Dog Output Visual = 20 days o Owner Program = 16 days Owner inputs = 20 days Processing Owner inputs = 26 days Output Owner Profile = 20 days o Compatibility Program = 14 days o Management Console = 16 days Order processing = 22 days Library updating = 14 days Reporting = 36 days Database = 30 days
Total = 338 days of programming man hours Total = 2704 programming man hours
2.2.1 Estimation technique m
Tables or equations associated with estimation technique m are presented. Section 2.2.1 is repeated for each of m techniques. 2704 Estimated Man Hours at $150 an hour Man Hours x $150 an Hour
P.E.T Boys Technologies
2
Doggy in the Window SPMP: Build-A-Pet Kiosk
2.2.2 Estimate for technique m
Estimate generated for technique m. 2704 x $150 = $405,600
2.3 Reconciled Estimate
The final cost, effort, time (duration) estimate for the project (at this point in time) is presented here. $450,000 for the project. 15 Months to completion.
2.4 Project Resources
People, hardware, software, tools, and other resources required to build the software are noted here. Architects Programmers Project Manager Graphic Designer Staff Workstations Test Servers Microsoft Windows 2003 Server Microsoft IIS Microsoft Visual Basic.net Conference Line Bridge Office Space Customer Liason
P.E.T Boys Technologies
3
Doggy in the Window SPMP: Build-A-Pet Kiosk
3. Risk Management
This section discusses project risks and the approach to managing them.
3.1 Project Risks
Each project risk is described. The CTC format may be used. Loss of a Key Team Member. Loss of the Head Designer. Catastrophe Financial Fines/Compliance Competition Customer requirements change Change in customer status
3.2 Risk Table
The complete risk table is presented. Name of risk, probability, impact and RM3 pointer are provided. Risk Management will be outsourced by a Software Safe Risk Management Inc.
3.3 Overview of Risk Mitigation, Monitoring, Management
An overview of RM3 is provided here. The Complete RM3 is provided as a separate document or as a set of Risk Information Sheets. Risk Management planning will be outsourced by a 3rd Party Risk Management Service.
P.E.T Boys Technologies
4
Doggy in the Window SPMP: Build-A-Pet Kiosk
4. Project Schedule
This section presents an overview of project tasks and the output of a project scheduling tool.
4.1 Project task set
The process model, framework activities and task set that have been selected for the project are presented in this section.
4.2 Functional decomposition
A functional breakdown to be used for scheduling is presented here. Team 1 Design = 60 days Graphical User Interface = 24 days Team 2 Application Functions = 30 days Dog Program = 16 days Dog inputs = 20 days Processing Dog inputs = 26 days Output Dog Visual = 20 days Owner Program = 16 days Owner inputs = 20 days Processing Owner inputs = 26 days Output Owner Profile = 20 days Compatibility Program = 14 days Team 3 Management Console = 16 days Order processing = 22 days Library updating = 14 days Reporting = 36 days Team 1 Database = 30 days Compile Software Together = 30 days Testing = 90 days
P.E.T Boys Technologies
5
Doggy in the Window SPMP: Build-A-Pet Kiosk
5. Staff Organization
The manner in which staff are organized and the mechanisms for reporting are noted.
5.1 Team structure
The team structure for the project is identified. Roles are defined. The main structure of the programming team will be conducted in a surgeon co-pilot method. Team 1 will be responsible for the Graphical portion, the overall Design and compiling the entire program together will consist of: Graphic Designer Head Software Designer Head Software Designer Assistant Database Programmer Secretary Project Manager Quality Assurance Lead
Team 2 will be responsible for the Dog portion, Owner portion, and Compatibility portion and will consist of: The surgeon The copilot The administrator The editor Two secretaries The program clerk The toolsmith The tester The language lawyer
Team 3 will be responsible for the Management Console portion and will consist of: The surgeon The copilot
P.E.T Boys Technologies
6
Doggy in the Window SPMP: Build-A-Pet Kiosk
The administrator The editor Two secretaries The program clerk The toolsmith The tester The language lawyer
5.2 Management reporting and communication
Mechanisms for progress reporting and inter/intra team communication are identified. The surgeons of Team 2 and 3 will keep a weekly report to the Head Software Designer from Team 1 to report any progress from each team.
P.E.T Boys Technologies
7
Doggy in the Window SPMP: Build-A-Pet Kiosk
6. Tracking and Control Mechanisms
Techniques to be used for project tracking and control identified.
6.1 Quality assurance and control
An overview of SQA activities is provided. Note that an SQA Plan is developed for a moderate to large project and may be a separate document or included as an appendix. Quality Assurance will be conducted by the Quality Assurance Lead. The Quality Assurance Lead will have an outsourced team to do QA on the software.
6.2 Change management and control An overview of SCM activities is provided. Note that an SCM Plan is developed for a moderate to large project and may be a separate document or included as an appendix.
Any type of changes that affect a team's project must be approved by the surgeon's of each team. A formal document must be filled out and sent to the surgeon. Only with an approval can a change be made that affects the team's project. This document must be kept in the designated repository so that the Head Designer may look at any approved changes by the team Surgeon.
P.E.T Boys Technologies
8