Life Cycle Plan (LCP) Version 9.0
Life Cycle Plan (LCP)
California Science Center Volunteer Tracking System
Team #3
Phongphan Danphitsanuphan / Project ManagerCharlie Lormanometee / Project Coordinator / QA
Deepak Pandey / System Analyst / Tester
Pongtip Aroonvatanaporn / System Architect / Programmer
Natachart Laoteppitak / Software Architect / Programmer
Amit Shah / Quality Focal Point Personnel
Jeremy Stoller / Client
Vincent Tsan / Maintainer
May 16 2008
Version History
Date / Author / Version / Changes made / Rationale /10/10/06 / Charlie Lormanometee / 1.0 / · Filled in information in all sections from LCP template in 577a web site / · LCO draft following lean MBASE guideline version 1.7
10/17/06 / Charlie Lormanometee / 1.1 / · Added link for COCOMO model and modified COCOMO model.
· Updated table 2 / · Missing a link for COCOMO and changed development model from early design to post architecture.
· Making table 2 more specific
10/21/06 / Charlie Lormanometee / 1.2 / · Update PCON value and other values
· Update table 2
· Update table 4 / · The team just found out how many people are going to continue in 577b
· The Spring 07 schedule is posted online
11/17/06 / Charlie Lormanometee / 2.0 / · Update table 2
· Update table 4
· Update table 8
· Update section 4.1.2 / · Elaborate more on deliverables in production stage
· Added required qualification
· Make modification on some of the cost drivers
· Added number of review methods
11/22/06 / Charlie Lormanometee / 2.1 / · Added table 5 / · Make clarification on role and skill for existing and new members in 577b
12/2/06 / Charlie Lormanometee / 3.0 / · Modified estimated COCOMO cost driver / · Identify developer discontinuity and recruited new comer
01/31/06 / Charlie Lormanometee / 6.0 / · Updated 2
· Updated 3,4, and 5
· Updated COCOMO KLOC / · Update for RLCA
· New & changed developer
02/15/06 / Charlie Lormanometee / 6.2 / · Updated COCOMO Scale Factor and Cost Drivers
· Added table 7 / · Taking uncertainties in to consideration
· 577b version
04/1/07 / Charlie Lormanometee / 7.0 / · Update section 2.1
· Update COCOMO / · IOC Working Set#1
· Reconstruct COCOMO module according to the plan
04/30/07 / Charlie Lormanometee / 7.3 / · Update delivery date / · Date assigned by Team 0
05/02/07 / Charlie Lormanometee / 8.0 / · Update COCOMO / · COCOMO for TRR
05/16/08 / Supannika Koolmanojwong / 9.0 / · Update all sections / · To comply with ICM guidelines
Table of Contents
Life Cycle Plan (LCP) i
Version History ii
Table of Contents iii
Table of Tables iv
Table of Figures v
1. Introduction 1
1.1 Purpose of the LCP 1
1.2 Status of the LCP 1
1.3 Assumptions 1
2. Milestones and Products 3
2.1 Overall Strategy 3
2.2 Phases 4
2.3 Project Deliverables 5
3. Responsibilities 10
3.1 Overall Summary 10
3.2 By Phase / Stage 12
4. Approach 16
4.1 Monitoring and Control 16
4.2 Methods, Tools and Facilities 18
5. Resources 19
LCP_AsBuilt_S07b_T03_V9.0 iii Version Date: 05/16/08
LCP_LCA_F06a_T03_V2.0.doc Table of Contents
Table of Tables
Table 1: Project Milestones 3
Table 2: Artifact deliverables in Valuation Phase 4
Table 3: Artifact Deliverables in Architecting Phase 5
Table 4: Artifact deliverables in Development Stage 7
Table 5: Artifact Deliverables in Operation Phase 8
Table 6: Stakeholder responsibilities during software life cycle 9
Table 7: Stakeholder responsibilities during each phase 10
Table 8: Role and required skills for 577b members 13
Table 9: Authorized Stakeholder Representatives in CSCI577a 13
Table 10: Authorized Stakeholder Representatives in CSCI577b 13
Table 11: Tools being used in the project 16
Table 12: Rationale for Project Scale Factors 18
Table 13: Rationale for Cost Drivers of Module 1-Volunteer candidate module 18
Table 14: Rationale for Cost Drivers of Module 2-Volunteer portal module 19
Table 15: Rationale for Cost Drivers of Module 3-Supervisor module 20
Table 16: Rationale for Cost Drivers of Module 4-Volunteer Management module 20
Table 17: Rationale for Cost Drivers of Module 5-Personnel Information Management module 21
LCP_AsBuilt_S07b_T03_V9.0 iii Version Date: 05/16/08
LCP_LCA_F06a_T03_V2.0.doc Table of Contents
Table of Figures
Figure 1: COCOMO Estimation Result of 6 modules 24
Figure 2: COCOMO Estimation Result of 5 modules 25
LCP_AsBuilt_S07b_T03_V9.0 iii Version Date: 05/16/08
Life Cycle Plan (LCP) Version 9.0
1. Introduction
1.1 Purpose of the LCP
The purpose of the Life Cycle Plan (LCP) for the California Science Center Volunteer Tracking System is to plan, monitor and control the progress of the project in order to maximize the productivity of people and resources throughout the system’s life cycle for development and after delivery. This LCP document status is in an Operation Commitment Package. There is no major significant difference between the content of the LCP and the WinWin negotiated agreements.
1.2 Status of the LCP
The status of the LCP is currently at the As-Builtoperation commitment package version number 9.0. This is the version that will be delivered to the client. There have been quite significant changes to the project when we moved from the LCA to the Re-baselined LCA phase due to time and personnel constraints as well as teams dependencies (Teams 0,1 and 2). The scope and life cycle plan of the Volunteer Tracking System project has been re-evaluated to accommodate those challenges.
1.3 Assumptions
The assumptions are the following:
1. The duration of the project is 24 weeks, which is 12 weeks in Fall 2006 and 12 weeks in Spring 2007.
2. Each development team member must follow the project schedule.
3. The core requirements will be stable. System capability requirements are
· The system shall provide online application form for volunteer candidate.
· The system shall volunteer clock in/out, volunteer comment log, and volunteer time card view capabilities.
· The system shall provide job request capability for supervisor.
· The system shall provide volunteer list, job assignment, requested task list.
· The system shall provide Person Information Management module, which is a sharing module among team 1, 2, and 3 about personnel information.
4. The development team collaborates with team 1 and team 2 to discuss about shared module implementation in CSC.
5. Team 0, or integration team, has been formed to resolve issues among team 1, 2, and 3.
6. Client, maintainer and Team 0-3 will collaborate with the development team throughout the software development life cycle
7. All project artifacts must follow the LeanICM Guideline.
2. Milestones and Products
2.1 Overall Strategy
Overall strategy for developing the California Science Center (CSC) Volunteer Tracking System is scheduled using the Independent Variable (SAIV) strategy since the project duration has been defined to fit the class schedule. With this strategy, the team is going to prioritize all capabilities and develop them in increments. In the first increment, the team will develop all the essential, or must-have, capabilities, and in the next increments, the team will develop lower-priority features based on time limitation. The schedule for this project is 24 weeks, which is divided into 2 12-week periods: Fall semester (CSCI577a) and Spring semester (CSCI577b). The process model implemented in this project is the Incremental Commitment Model, which will mainly emphasize on stakeholders’ commitment and risk analysis.
The project type is a custom development project as we need to develop a system in which complies with the CSC intranet infrastructure and architecture as well as the CSC template for user interface.
The process model includes the following key milestones:
· Architecture Commitment Review (ACR)
· Development Commitment Review (DCR)
· Rebaselined Development Commitment Review (RDCR)
· Core Capability Drive-through (CCD)
· Transition Readiness Review (TRR)
· Operations Commitment Review (OCR)
The development period can be categorized as follows:
· Valuation and Architecting phases
Duration: Fall 2006 in CSCI577a subject and beginning of Spring 2008
Concept: Conducting WinWin negotiation process. Identifying project operational concept, system and software requirement, system and software architecture, and life-cycle plan. Prioritizing the capabilities. Conducting investment and feasibility analysis. Implementing software prototype.
o Valuation phase
Deliverables: WikiWinWin negotiation report, Initial prototype, Architecting Commitment Package
Milestone: Architecting Commitment Review
Strategy: At least one Incremental Commitment Cycle
o Architecting phase
Deliverables: Updated Wiki WinWin negotiation report, Updated prototype, Development Commitment Package
Milestone: Development Commitment Review
Strategy: At least one Incremental Commitment Cycle
o Rebaselined Architecting phase
Deliverables: Rebaselined WinWin negotiation report, Updated Prototype, Rebaselined Development Commitment Package
Milestone: Rebaselined Development Commitment Review
Strategy: At least one short Incremental Commitment Cycle
· Development and Operation phases
Duration: Spring 2007 in CSCI577b subject
Concept: There are 2 increments in the Development phase. All core capabilities are developed in the first increment and deployed in the second increment, while the lower priority capabilities will be developed in the second increment. Furthermore, the development team has to prepare for transitioning, testing, and installing the system. In the operation phase, the development team delivers the system and ensures the quality of work product.
o Development phase - Increment 1
Deliverables: Executable core capabilities, Operations Commitment Package, Construction Set
Ending Milestone: Core Capability Drive-through
Strategy: One Incremental Commitment Cycle
o Development phase - Increment 2
Deliverables: Executable system, Construction Set, Support and Transition Set
Milestone: Transition Readiness Review
Strategy: One Incremental Commitment Cycle
o Operation phase
Deliverables: System Installation, Operations Commitment Package, Support and Transition Set
Milestone: Operations Commitment Review
Strategy: One Incremental Commitment Cycle
2.2 Phases
Following is the list of major milestones of the project
Table 1: Project Milestones
Milestone / DateArchitecture Commitment Review / 10/16/2006
Development Commitment Review / 11/27/2006
Rebaselined Development Commitment Review / 02/07/2007
Core Capability Drive through / 02/28/2007
Transition Readiness Review / 04/10/2007
Operations Commitment Review / 04/24/2007
Project Release / 05/05/2007
For the most recent project schedule, it can be found in at:
http://greenbay.usc.edu/csci577/spring2007/projects/team3/PR/index.html
2.3 Project Deliverables
2.3.1 Valuation Phase
Table 2: Artifact deliverables in Valuation Phase
Artifact / Due date / Format / MediumOperational Concept Description (OCD) Early Section / 09/18/2006 / .doc, .pdf / Soft copy
Evaluation of OCD Early Section / 09/27/2006 / .xls / Soft copy
Initial Prototype / 09/29/2006 / .doc, .pdf / Soft copy
Wiki WinWin Report / 10/02/2006 / .doc, .pdf / Soft copy
Evaluation of Initial Prototype / 10/04/2006 / .xls / Soft copy
Core Architecting Commitment Package
· Operational Concept Description
· System and Software Requirements Definition
· Supporting Information Document / 10/04/2006 / .doc, .pdf / Soft copy
Evaluation of Core Architecting Commitment Package / 10/09/2006 / .doc / Soft copy
Draft Architecting Commitment Package
· Operational Concept Description
· System and Software Requirements Definition
· System and Software Architecture Description
· UML Model
· Life Cycle Plan
· Feasibility Rationale Description
· Supporting Information Document / 10/11/2006 / .doc, .pdf, .zip / Soft copy
Respond to Evaluation of Core Architecting Commitment Package / 10/16/2006 / .xls, .doc / Soft copy
Evaluation of Draft Architecting Commitment Package / 10/16/2006 / .xls / Soft copy
Architecting Commitment Package
· Operational Concept Description
· System and Software Requirements Definition
· System and Software Architecture Description
· UML Model
· Life Cycle Plan
· Feasibility Rationale Description
· Supporting Information Document / 10/23/2006 / .doc, .pdf, .zip / Soft copy
Quality Management Plan – I / 10/23/2006 / .doc, .pdf / Soft copy
Response to Draft Architecting Commitment Package Evaluation / 10/25/2006 / .xls, .doc / Soft copy
Evaluation of Architecting Commitment Package / 10/30/2006 / .xls / Soft copy
Response to Architecting Commitment Package Evaluation / 11/06/2006 / .xls, .doc / Soft Copy
Project Effort / Every Monday / Text / ER system
Project Plan / Every Wednesday / .mpp, .pdf / Soft copy
Progress Report / Every Wednesday / .xls / Soft copy
Risk Analysis / Every Wednesday / Text / DART system
Client’s Meeting Notes / After the meeting / .doc, .pdf / Soft copy
All of the artifacts in Valuation phase can be found on the team website.
http://greenbay.usc.edu/csci577/spring2007/projects/team3/LCO/index.html
2.3.2 Architecting Phase
Table 3: Artifact Deliverables in Architecting Phase
Artifact / Due date / Format / MediumUpdated Wiki Win-Win Report / 11/08/2006 / .doc, .pdf / Soft copy
Quality Management Plan –II / 11/10/2006 / .doc, .pdf / Soft copy
Draft Development Commitment Package
· Operational Concept Description
· System and Software Requirements Definition
· System and Software Architecture Description
· UML Model
· Life Cycle Plan
· Feasibility Rationale Description
· Supporting Information Document / 11/20/2006 / .doc, .pdf, .zip / Soft copy
Evaluation of Draft Development Commitment Package / 11/27/2006 / .xsl / Soft copy
Development Commitment Package
· Operational Concept Description
· System and Software Requirements Definition
· System and Software Architecture Description
· UML Model
· Life Cycle Plan
· Feasibility Rationale Description
· Supporting Information Document / 12/04/2006 / .doc, .pdf, .zip / Soft copy
Respond to Draft Development Commitment Package Evaluation / 12/04/2006 / .xls, .doc / Soft copy
Rebaselined Development Commitment Package
· Operational Concept Description
· System and Software Requirements Definition
· System and Software Architecture Description
· UML Model
· Life Cycle Plan
· Feasibility Rationale Description
· Supporting Information Document / 02/02/2007 / .doc, .pdf, .zip / Soft copy
Respond to Rebaselined Development Commitment Package
Evaluation / 02/07/2007 / .xls, .doc / Soft copy
Evaluation of Rebaselined Development Commitment Package / 02/09/2007 / .xsl / Soft copy
Project Effort / Every Monday / Text / ER system
Project Plan / Every Wednesday / .mpp, .pdf / Soft copy
Progress Report / Every Wednesday / .xls / Soft copy
Risk Analysis / Every Wednesday / Text / DART system
All of the artifacts in Architecting phase can be found on the team website.