Cycle Life Plan (LCP)
Theater Script Online Database
Team No 16
Jae Young Bang Gary Lam Shi Heng Guan Young Chan Noh Ka Ho Au Nory Kealii Nishimura Julie Sanchez
Non-technical Lead/Builder Tester/Technical Lead Planning and Control Engineer System Architect Builder IIV&V / Quality Lead Client
April 2nd, 2009
Life Cycle Plan (LCP) _ Team 16
Version 9.0
Version History
ii
Life Cycle Plan (LCP) _ Team 16 Date 9/21/08 Author Shi Heng Guan Versio n 1.0 Changes made Original template for use in ICM EPG Rationale
Version 9.0
Initial draft for use with ICM EPG Elaboration of Section 1, 2, 3.3
10/5/08
Shi Heng Guan Shi Heng Guan
2.0
Update Section 3.3
Set the accurate skills everyone need for the system After collecting team view of each responsibility. It was group up to the more convenient ones. The base approach to monitor and review the documentation and project is describe Update details Update tables Estimation of COCOMO v1
10/05/0 8
2.1
Add Responsibility by Phases, Section 3.2
10/11/0 8
Shi Heng Guan
2.2
Describe Approach
10/13/0 8 10/19/0 8
Shi Heng Guan Shi Heng Guan
3.0
Completion of missing section
3.1
Evaluation Corrections on sections 1.3 and 3.3
The status is updated Maintainer roles is added Suggested assumption is added
10/21/0 8 10/27/0 8 10/27/0 8 11/08/0 8 11/13/0 8 11/19/0 8 11/23/0 8 11/24/0 8 11/29/0 8 12/08/0 8
Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan
3.2 3.3 4.0 4.1
Update section 3.3 Update section 3.3 Update section 5 Updated section 5 Error correction and removal
577b roles incorporated Update 577b roles Update COCOMO II Added table 26 for better reference Update section 1.3 List type of users 3.1 Add detail on section 5
4.2 4.3 4.4 5.0 5.1 6.0
Update section 2.3 Update section 5 Update section 5 Review Update section 5 Status update
Add missing development phase deliverable Create new COCOMO estimate Consistence with SSAD Minor corrections Minor changes on naming modules in COCOMO Final check on document
2943238cf290f3387d3c727a2eec9d74506d9339.doc iii
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16 Date 02/06/0 9 02/07/0 9 02/08/0 9 02/18/0 9 02/23/0 9 04/02/0 9 Author Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Shi Heng Guan Versio n 6.1 6.2 7.0 7.1 8.0 9.0 Changes made Update plans Verify content Update section 5 Correction Update status Update section 5 Rationale Update status Correct dates
Version 9.0
Corrected LCP using feedbacks New COCOMO estimate for CCD Correct divergence on dates Final touch for RDCR COCOMO with Code Count calibration
2943238cf290f3387d3c727a2eec9d74506d9339.doc iv
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version 9.0
Table of Contents
Life Cycle Plan (LCP)....................................................................................................................................................i ....................................................................................................................................................................i Version History.............................................................................................................................................................ii Table of Contents..........................................................................................................................................................v Table of Tables.............................................................................................................................................................vi Table of Figures..........................................................................................................................................................vii Introduction..............................................................................................................................................................1 A.1.1 Purpose of the LCP ..................................................................................................................................1 A.1.2 Status of the LCP .....................................................................................................................................1 A.1.3 Assumptions...............................................................................................................................................1 Milestones and Products..........................................................................................................................................2 A.1.4 Overall Strategy........................................................................................................................................2 A.1.5 Phases.........................................................................................................................................................4 A.1.6 Project Deliverables..................................................................................................................................4 Responsibilities.......................................................................................................................................................11 A.1.7 Project-specific stakeholder's responsibilities......................................................................................11 12 A.1.8 Responsibilities by Phase........................................................................................................................12 A.1.9 Skills.........................................................................................................................................................18 Approach.................................................................................................................................................................20 A.1.10 Monitoring and Control.......................................................................................................................20 A.1.11 Methods, Tools and Facilities...............................................................................................................22 22 A.2. Resources.........................................................................................................................................................23
2943238cf290f3387d3c727a2eec9d74506d9339.doc v
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version 9.0
Table of Tables
Table 1: Milestone on Different Phases.......................................................................................................................4 Table 2: Artifact Deliverable in Exploration Phase...................................................................................................4 Table 3: Artifact Deliverable in Valuation Phase......................................................................................................6 Table 4: Artifact deliverable in Foundations Phase part 1/2....................................................................................7 Table 5: Artifact deliverable in Rebaseline (Foundations Phase part 2/2)..............................................................8 Table 6: Artifact deliverable in Development Phase-Construction Iteration.........................................................9 Table 7: Artifact deliverable in Development Phase-Transition Iteration............................................................10 Table 8: Project Specific Stakeholder's Responsibilities.........................................................................................11 Table 9: Project Manager's Responsibilities by Phases..........................................................................................12 Table 10: Operational Concept Engineer's Responsibility by Phases...................................................................13 Table 11: Requirement Engineer's Responsibility by Phases.................................................................................13 Table 12: Planning and Control Engineer's Responsibility by Phases..................................................................14 Table 13: System Architect's Responsibilities by Phases........................................................................................14 Table 14: Prototyper's Responsibility by Phases.....................................................................................................15 Table 15: IIV&V-QFP's Responsibilities by Phases................................................................................................16 Table 16: IIV&V-RE's Responsibilities by Phases..................................................................................................16 Table 17: Authorized Stakeholder Representatives................................................................................................18 Table 18: Required Skills of each member of the Team on 577a...........................................................................18 Table 19: Required Skills of each member of the Team on 577b...........................................................................19 Table 20: Require Skills for maintainer...................................................................................................................19 Table 21: Tools for the Project..................................................................................................................................22 Table 22: COCOMOII Scale Driver.........................................................................................................................23 Table 23: COCOMOII Cost Driver Module 1 - Login............................................................................................24 Table 24: COCOMOII Cost Driver Module 2 Administrator Profile Management.........................................25 Table 25: COCOMOII Cost Driver Module 3 Search Script..............................................................................26 Table 26: COCOMOII Cost Driver Module 4 User Interface (View Script).....................................................27 Table 27: COCOMOII Cost Driver Module 5 Account Creation.......................................................................28 Table 28: COCOMOII Cost Driver Module 6 Script Management...................................................................29 Table 29: SLOC of the System...................................................................................................................................31
vi
Life Cycle Plan
Table of Contents
Table of Figures
Figure 1: ICM Phases and Calendar Distribution ....................................................................................................3 Figure 2: COCOMO Estimate Model.......................................................................................................................32 Figure 3: COCOMO for CCD...................................................................................................................................33 Figure 4: CCD COCOMO Estimation with Unified Code Count..........................................................................34
2943238cf290f3387d3c727a2eec9d74506d9339.docvii
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Introduction
A.1.1 Purpose of the LCP
The purpose of the present Life Cycle Plan (LCP) document is to provide assistance in monitoring and managing the project and its progress. It is extremely important to allocate the correct amount of people and resources into the right area of the project. This document will help setting a plan to walkthrough all the phases of the ICM in the life cycle of developing the system. It will also provide a vision of where each member is now in this development process and what is his/hers next step and the understanding of the entire system.
A.1.2 Status of the LCP
The status of the LCP is currently at the middle of development phase and preparing for transition. This LCP goes in the Initial Operational Capability Set 1. All of the artifacts are completed for planning and updated according to changes. The client ideas of the system are understood and she has provided adequate hardware necessary for setup and client is satisfied so far with prototype. The progress have been checked by the client and approved by the client. Every document will be improved on the present packages to refine requirements, design and issues on the development.
A.1.3 Assumptions
These are our assumptions: The total time of development is 24 weeks split in CS577a and CS577b, 12 weeks each. Everyone will be working at least 12 hours a week on the project. No major changes will be seen after the WikiWinWin Negotiation. Six team members will finish the project on CS577b. A computer unit will be provided to be the server of the system with connection to the web and a scanner; no other hardware interfacing will be involved. All documentation and product will follow the guidelines of ICM EPG. The client will provide us feedback. She also will coordinate with us on the project meetings. The client takes the position of administrator and maintainer of the system. There will be a small amount on the budget for the project. OCR does not directly interact with the system.
2943238cf290f3387d3c727a2eec9d74506d9339.doc 1
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Milestones and Products
A.1.4 Overall Strategy
The overall strategy is based on the time factor, which is unchangeable since it has to adjust in two semesters school time. Therefore, we will prioritize client requirements with the Schedule As Independent Variable (SAIV) method. We set the main requirements of the system as initial operation capabilities and consider the rest to be extra features, given by the priority of each requirement. Since requirements will be changing throughout the process of development, the Incremental Commitment Model (ICM) is the best method that works with changing requirements over time as the client comes up with new win conditions. Major changes on the definition of the system and scope of the system are done during the first semester and mainly during negotiations. Through negotiation and client meetings we will shape a clear idea of the system. During the spring semester minor corrections to the system will be made. Major milestones on our system: Valuation Commitment Review (VCR) Foundations Commitment Review (FCR) Development Commitment Review (DCR) Rebaselined Development Commitment Review (RDCR) Core Capability Drive-through (CCD) Transition Readiness Review (TRR) Operation Commitment Review (OCR) The phases are laid clearly on the following figure:
2943238cf290f3387d3c727a2eec9d74506d9339.doc 2
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16 Figure 1: ICM Phases and Calendar Distribution
Version No 9.0
*The phases, milestones and ideas are taken from the ICM EPG and the example it provides [1]
2943238cf290f3387d3c727a2eec9d74506d9339.doc 3
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
A.1.5 Phases
The list of milestones at the end of each phase according to schedule:
Table 1: Milestone on Different Phases
Milestone Valuation Commitment Review Foundations Commitment Review Development Commitment Review Rebaselined Development Commitment Review (RDCR) Core Capability Drive-through (CCD) Transition Readiness Review (TRR) Operation Commitment Review (OCR) Product Delivery
Date 09/22/2008 10/23/2008 12/01/2008 02/11/2009 03/24/2009 04/15/2009 04/29/2009 05/04/2009
The complete schedule that includes all the tasks is updated on our website. The link provides the index of MS Projects files. Click on the most recent one: http://greenbay.usc.edu/csci577/spring2009/projects/team16/PR/index.html
A.1.6 Project Deliverables
.1.6.1 Exploration Phase
Table 2: Artifact Deliverable in Exploration Phase
Artifact Client Interaction Report Valuation Commitment Package: Operational Concept Description (OCD) Life Cycle Plan (LCP) Feasibility Evidence Description (FED) Evaluation of VC Package Individual Effort Report Progress Report MS Project Risk Analysis
Due date 9/17/2008 9/22/2008
Format .doc and .pdf .doc and .pdf
Medium Soft copy Soft copy
09/29/2008 Every Monday Every Wednesday Every Wednesday Every Wednesday
.doc, .xls Text .xls .mpp Text
Soft copy ER System Soft copy Soft copy DART system
2943238cf290f3387d3c727a2eec9d74506d9339.doc 4
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Client Meeting Notes
After Meetings
.doc, .pdf
Soft copy
2943238cf290f3387d3c727a2eec9d74506d9339.doc 5
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
.1.6.2 Valuation Phase
Table 3: Artifact Deliverable in Valuation Phase
Artifact Initial Prototype Core Foundations Commitment (FC) Package: OCD LCP FED System and Software Requirements Definition (SSRD) Supporting Information Document (SID) Evaluation of Initial Prototype WikiWinWin Report Draft FC Package: OCD LCP FED SSRD SID UML Model System and Software Architecture Description (SSAD) Evaluation of Core FC Package Response to Evaluation of Core FC Package Evaluation of Draft FC Package FC Package: OCD LCP FED SSRD SID UML Model SSAD Quality Management Plan #1 Response to Evaluation of Draft FC Package Evaluation of FC Package
Due date 09/29/2008 10/05/2008
Format .doc, .pdf .doc, .pdf
Medium Soft copy Soft copy
10/05/2008 10/08/2008 10/13/2008
.doc, .xls .doc, .pdf .doc, .pdf, .ras
Soft copy Soft copy Soft copy
10/13/2008 10/17/2008 10/20/2008 10/27/2008
.doc, .pdf .doc, .xls .doc, .xls .doc, .pdf, .ras
Soft copy Soft copy Soft copy Soft copy
10/27/2008 10/29/2008 11/03/2008
.doc, .pdf .doc, .xls .doc, .xls
Soft copy Soft copy Soft copy
2943238cf290f3387d3c727a2eec9d74506d9339.doc 6
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Response to Foundations Commitment Package Evaluation Individual Effort Report Progress Report MS Project Risk Analysis Client Meeting Notes
11/10/2008 Every Monday Every Wednesday Every Wednesday Every Wednesday After Meetings
.doc, .xls text .xls .mpp text .doc, .pdf
Soft copy ER System Soft copy Soft copy DART system Soft copy
.1.6.3 Foundations Phase
Table 4: Artifact deliverable in Foundations Phase part 1/2
Artifact Update WikiWinWin Report COTS Integration Analysis Quality Management Plan (QMP) #2 Draft Development Commitment (DC) Package: OCD LCP FED SSRD SID UML Model SSAD QMP Acceptance Test Plan and Cases (ATPC) Transition Plan (TP) Iteration Plan (IP) Evaluation of Draft DC Package Response to Draft DC Package Evaluation DC Package: OCD LCP FED SSRD SID UML Model SSAD
Due date 11/10/2008 11/14/2008 11/17/2008 11/24/2008
Format .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf, .ras
Medium Soft copy Soft copy Soft copy Soft copy
12/1/2008 12/10/2008 12/8/2008
.doc, .xls .doc, .xls .doc, .pdf, .ras
Soft copy Soft copy Soft copy
2943238cf290f3387d3c727a2eec9d74506d9339.doc 7
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
QMP ATPC TP IP Evaluation of DC Package Project Archiving Individual Effort Report Progress Report MS Project Risk Analysis Client Meeting Notes
12/15/2008 12/15/2008 Every Monday Every Wednesday Every Wednesday Every Wednesday After Meetings
.doc, .pdf .doc, .pdf text .xls .mpp text .doc, .pdf
Soft copy Soft copy ER System Soft copy Soft copy DART system Soft copy
*The tables' dates are taken from assignment page [2] The deliverables for 577b, which corresponds to spring 2009, are the following: Table 5: Artifact deliverable in Rebaseline (Foundations Phase part 2/2)
Artifact Prototype (part of OCD) Draft Development Commitment Package (Draft Rebaselined DC Package): Elaborated and updated fall Development Commitment Package Development Commitment Package (DC Package): Elaborated and updated Draft Development Commitment Package Evaluation of Draft Rebaselined Development Commitment (RDC) Package Response Evaluation of Draft RDC Evaluation of RDC Package Evaluation of RDC Package Individual Effort Report Progress Report MS Project Risk Analysis Client Meeting Notes
Due date 02/09/2009 02/09/2009
Format .doc, .pdf .doc, .pdf, .ras
Medium Soft copy Soft copy
02/20/2009
.doc, .pdf, .ras
Soft copy
02/18/2009 02/25/2009 03/02/2009 03/09/2009 Every Monday Every Wednesday Every Wednesday Every Wednesday Every Wednesday
.doc, .xls .doc, .xls .doc, .xls .doc, .xls text .xls .mpp text .doc, .pdf
Soft copy Soft copy Soft copy Soft copy ER System Soft copy Soft copy DART system Soft copy
2943238cf290f3387d3c727a2eec9d74506d9339.doc 8
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
.1.6.4 Development Phase
This section will be updated when more precise information is obtained.
Table 6: Artifact deliverable in Development Phase-Construction Iteration
Artifact Initial Operational Capability (IOC) Working Set #1: Quality Management Plan (QMP) Iteration Plan (IP) Top-level Test Plan and Cases (TPC) Core Capability Drivethrough (CCD) report IOC Working Set #2: Updated QMP Updated IP Updated TPC Transition Preparation Plan (TP) IOC Working Set #3: Updated IOC Working set #2 TP Test Procedures and Result (TPR) Iteration Assessment Report (IAR) Draft Transition Package Transition Plan (TP) User Manual (UM) Support Plan (SP) Training Materials Regression Test Package (RTP) Individual Effort Report
Due date 03/10/2009
Format .doc, .pdf
Medium Soft copy
04/03/2009 04/03/2009
.doc, .pdf .doc, .pdf
Soft copy Soft copy
04/17/2009
.doc, .pdf
Soft copy
04/13/2009
.doc, .pdf
Soft copy
Every Monday
text
ER System
2943238cf290f3387d3c727a2eec9d74506d9339.doc 9
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Progress Report MS Project Risk Analysis Client Meeting Notes
Every Wednesday Every Wednesday Every Wednesday Every Wednesday
.xls .mpp text .doc, .pdf
Soft copy Soft copy DART system Soft copy
Table 7: Artifact deliverable in Development Phase-Transition Iteration
Artifact Support and Transition Set Updated Draft Transition Package Operations Commitment Package Project Archiving: Source Code Files Executable Components Release Description Individual Effort Report Progress Report MS Project Risk Analysis Client Meeting Notes
Due date 04/20/2009 4/27/2009 5/01/2009
Format .doc, .pdf .doc, .pdf .doc, .pdf, .zip
Medium Soft copy Soft copy Soft copy
Every Monday Every Wednesday Every Wednesday Every Wednesday Every Wednesday
text .xls .mpp text .doc, .pdf
ER System Soft copy Soft copy DART system Soft copy
2943238cf290f3387d3c727a2eec9d74506d9339.doc10
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Responsibilities
A.1.7 Project-specific stakeholder's responsibilities
Table 8: Project Specific Stakeholder's Responsibilities
Role All Stakeholders
Responsibilities Contribute to the WikiWinWin negotiations Attend weekly meeting and commitment review Be responsible for assigned tasks and assist with secondary responsibilities Provide win conditions Test prototype and provide feedback
Users: Staff/Actors Administrator Client
Prepare for meetings with development team Inform about current system Coordinate with development team and users Provide information and feedback, review and test the product Test and deploy the product. Define system hardware Be able to take charge after transition phase Receive training for the new system Record and converge all stakeholders' win conditions Gather information regarding current system and provide initial architecture Initiate and complete WikiWinWin negotiation. Produce new architecture for system Build prototype and produce project plan. Build system according to design Report progress to client Meet exit criteria on project documentations Do testing before giving it to client Give training for client/maintainer Verify and validate the project Review and provide feedback to the development team Check quality of the system
Developer
IIV&V
2943238cf290f3387d3c727a2eec9d74506d9339.doc11
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Maintainer
Receive training for the new system Provide maintenance of the system Update all software that needs upgrade.
A.1.8 Responsibilities by Phase
The following tables will show more specific details of each member of the development team
Table 9: Project Manager's Responsibilities by Phases
Stakeholder: Role Primary/ Secondary Exploration
Jae Young Bang: Project Manager/ Operational Concept Engineer 577b: Project Manager/ Builder Primary Responsibility Secondary Responsibility Set up an efficient Analyze current system communication route with client and IIV&Vs Arrange responsibility to development team members Set up team meetings and client meetings Monitor project weekly progress Coordinate with all stakeholders Manage project Arrange WikiWinWin negotiations sessions Review artifacts Manage project Coordinate with all stakeholders Prepare team for development phase Evaluate and organize team Coordinate with all stakeholders Manage project Coordinate with all stakeholders Prepare for transition Manage project Coordinate with all stakeholders Verify system final deliverable Define Operational Concepts
Valuation
Foundations
Review artifacts Assess Operational Concepts
Rebaseline DevelopmentConstruction
Analyze prototype and UML Create front end user interface Assist with programming the modules Provide training
DevelopmentTransition
2943238cf290f3387d3c727a2eec9d74506d9339.doc12
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16 Table 10: Operational Concept Engineer's Responsibility by Phases
Version No 9.0
Stakeholder: Role Primary/ Secondary
Exploration
Sandeep Mikkilineni: Operational Concept Engineer / LCP/ Learning Facilitator 577b: N/A Primary Responsibility Secondary Responsibility Analyze current system and its Analyze core capabilities environment
Form a shared vision for concept system
Valuation
Identify and establish operational concepts Set project scope Assist prototyper on the prototype for the proposed system Assess the OCD Refine OCD and prepare for development phase Ensure that project matches operational concept
Assist on estimation of cost Facilitate team learning of the project
Foundations
Assist updating Life Cycle Plan Review artifacts
Table 11: Requirement Engineer's Responsibility by Phases
Stakeholder: Role Primary/ Secondary Exploration
Gary Lam: Requirements Engineer / Feasibility Analyst/ 577b: Tester Primary Responsibility Secondary Responsibility Analyze current system Explore risks that may exist in creating the new system Analyze main capabilities Provide ways to mitigate risk Analyze final WIOA Negotiation agreements Prioritize Requirements Convert Agreements on negotiation to requirements Generate requirements definitions Assess requirement definition Ensure that the prototype covers all requirements. Identify missing requirements Remove requirements that are no longer deemed necessary. Generate testing plans Look at return on investment and continue to assess old risks along with any new risks Assess and address any risks that still exist and mitigate them
Valuation
Foundations
Rebaseline
Review requirement specifications Assess and address any risks that still exist and mitigate them Review requirements and prioritize them
2943238cf290f3387d3c727a2eec9d74506d9339.doc13
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
DevelopmentConstruction
DevelopmentTransition
Prepare testing environment Perform module testing Review consistency between developed modules and documents Perform final test
Correct any documentation according to client needs
Help produce support documentation
Table 12: Planning and Control Engineer's Responsibility by Phases
Stakeholder: Role Primary/ Secondary Exploration
Shi Heng Guan: LCP/ Software Architect/ Assistant Shaper 577b: LCP/ Tester Primary Responsibility Secondary Responsibility Understand deliverable artifacts Coordinate with clients and team members Identify responsibilities and skills Draft project plan Coordinate with development team Assist Project Manager in generating project life cycle plan Estimate cost of software with COCOMO II Review milestone and products Optimize life cycle plan Refine cost estimation Review milestone and products Provide a more detail planning per iteration Generate detailed planning for transition Perform final testing Provide support for transition Converge Win Conditions Assist drafting UML models of the system Resolve Conflict on WIOA Negotiation
Valuation
Foundations
Rebaseline DevelopmentConstruction DevelopmentTransition
Plan for testing Coordinate with team members Assist on testing criteria Assist on testing Setup system
Table 13: System Architect's Responsibilities by Phases
Stakeholder: Role Primary/ Secondary Exploration
Young Chan Noh: System Architect / Prototyper 577b: Designer/Builder (577b) Primary Responsibility Secondary Responsibility Analyze current system Set up DART Record and organize risk Explore platforms, databases, languages, and servers to be used. Identify possible COTS products
2943238cf290f3387d3c727a2eec9d74506d9339.doc14
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Valuation
Propose system architecture Determine useful COTS for the system Define Technology independent Architecture Draft UML design for the system Define system architecture Define Architecture Style, Patterns and Frameworks Optimize UML design Revise prototype Update system architecture Design modules Integrate modules Prepare for system release Provide support for transition
Assist in creation of initial prototype
Foundations
Improve prototype
Rebaseline DevelopmentTransition
DevelopmentConstruction
Review Prototype Perform integration testing Setup system
Table 14: Prototyper's Responsibility by Phases
Stakeholder: Role Primary/ Secondary Exploration
Valuation
Ka Ho Au: Prototyper / Requirement Engineer 577b: Programmer Primary Responsibility Secondary Responsibility Establish new operational Analyze core capabilities concepts Brainstorm requirements Explore ways to design the user interface and acquire required capabilities of product Establish new operational Assist generation of concepts requirements definitions Develop low-fidelity prototype Optimize Prototype Revise prototype Keep the UML model consistent with the prototype Ensure prototype captures all the requirements Improve Prototype and correct according to changes in requirements Develop modules Integrate modules Perform final testing Provide support for transition Review requirement specification
Foundations
Rebaseline DevelopmentConstruction DevelopmentTransition
Review system architecture Perform integration testing Setup system
2943238cf290f3387d3c727a2eec9d74506d9339.doc15
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Table 15: IIV&V-QFP's Responsibilities by Phases
Stakeholder: Role Primary/ Secondary Exploration
Nory Nishimura: Integrated & Independent Validation and Verification/ Quality Focal Point/ Quality Focal Point 577b: IV&V/ Tester Primary Responsibility Secondary Responsibility Analyze project business cases Give input to the project with an emphasis on quality Assess possible risks Verify and validate all project artifacts Generate first quality management plan Identify configuration management Generate defect/issue logs Refine quality management plan Identify configuration management strategy Assess quality management strategy Review all documentation Assist preparing final documentations Prepare for final release
Valuation
Foundations
Verify and validate project artifacts
Rebaseline DevelopmentConstruction DevelopmentTransition
Update QMP Verify and validate project artifacts Perform testing Prepare for system release Provide support for transition
Table 16: IIV&V-RE's Responsibilities by Phases
Stakeholder: Role Primary/ Secondary
Exploration Valuation
John Reynolds: Integrated & Independent Validation and Verification/ Requirement Engineer/ Shaper 577b: N/A Primary Responsibility Secondary Responsibility Understand current system Understand what client desires in system Shape WikiWinWin negotiation Define requirements Verify and validate project artifacts Generate Requirement definitions Generate WikiWinWin report Verify and validate project Prepare acceptance test cases
Foundations
2943238cf290f3387d3c727a2eec9d74506d9339.doc16
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
artifacts Update WikiWinWin report
2943238cf290f3387d3c727a2eec9d74506d9339.doc17
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Table 17: Authorized Stakeholder Representatives
Stakeholders Jae Young Bang Gary Lam Young Chan Noh Ka Ho Au Shi Heng Guan Nory Kealii Nishimura Julie Sanchez
Category Developers
Organization University of Southern California (USC)
Client/ Administrator/ Maintainer
JulesTBear's Online Scripto-Rama
A.1.9 Skills
Table 18: Required Skills of each member of the Team on 577a
Team members Jae Young Bang Shi Heng Guan
Role primary/secondary Project Manager/Operational Concept Engineer Planning and Control Engineer/ System Architect/ Assistant Shaper Operational Concept Engineer/ Planning and Control Engineer, Learning Facilitator Requirements Engineer/ Feasibility Analyst/ Website Administrator System Architect/ Prototyper/ DART manager Prototyper/ Requirement Engineer IIV&V / QFP IIV&V/ SRE / Shaper
Sandeep Mikkilineni
Skills Project Management, configuration management Project coordination, MS Project, COCOMO, WikiWinWin-J, UML, JAVA, RSM, JSP Project coordination, MS Project, COCOMO, Motivation for learning WikiWinWin-J, Analysis of Requirements, configuration management, Analysis and Management of Risk UML, JAVA, MySQL, Apache, RSM, DART management, JSP UML, JAVA, MySQL, Apache, WikiWinWin-J, RSM, JSP, OCR integration Quality Management, Agile Artifact Review WikiWinWin-J, Agile Artifact Review
Gary Lam
Young Chan Noh Ka Ho Au Nory Kealii Nishimura John Christopher Reynolds
2943238cf290f3387d3c727a2eec9d74506d9339.doc18
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16 Table 19: Required Skills of each member of the Team on 577b
Version No 9.0
Team members Jae Young Bang
Role primary/secondary Project Manager/ Builder
Gary Lam Young Chan Noh Ka Ho Au Nory Kealii Nishimura Shi Heng Guan
Tester System Architect/ Builder Builder IIV&V / QFP/Tester LCP/ Tester
Skills Project Management, configuration management, UML, JAVA, MySQL, Apache, JSP UML, JAVA, MySQL, Apache, JSP UML, JAVA, MySQL, Apache, RSM, DART management, JSP UML, JAVA, MySQL, Apache, JSP Quality Management, Agile Artifact Review Project coordination, MS Project, JAVA, MySQL, Apache, JSP, OCR, COCOMO II
* The client confirmed that she would take the position of maintainer on the system. We take this into consideration so that we may provide a system to maintainers with less technical knowledge. There may still be a case where a major breakdown occurs or a repair of the system is required. Here are the skills for an ideal maintainer of the system in case the client hires one.
Table 20: Require Skills for maintainer
Role Maintainer
Skills Knowledge on database administration using MySQL. Programming language JAVA, JSP and Apache Tomcat, OCR operations
2943238cf290f3387d3c727a2eec9d74506d9339.doc19
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
Approach
A.1.10Monitoring and Control
The purpose of monitoring and control for the Theater Script Online Database (TSOD) is to acknowledge the current status of each part of the project and track development team productivity. It helps accelerate the process of artifacts that are behind schedule and keep all activities and documents up to date according to plan. The way to monitor our work is to use the following tools so we can check weekly each person's work and group work: Weekly Client Meeting Report This document provides record of client opinion or feedback of our progress in the system and in different artifacts. Weekly Progress Report Shows an overview of the project being developed and the contribution of each member. It also provides a list of high level of problems encountered. Weekly Effort Report Every member of the development team records the time each one spends on the different areas of the project. It gives a clear view of the area of concentration and if any area is overlooked. Project Plan It give an organized view of each person's task and responsibility and the amount of time to be dedicated to each one. Risk management and mitigation (DART) Identifies all the risks and prioritize the top ones that need to be reduced or managed. Software Cost Estimation (USC COCOMO tool) It gives the approximation of the effort and the man-hours of the project and helps put in perspective the scope of the project. Regular Team meeting A minimum of one group meeting per week is done so that we may update each other on the status of our work and look to cooperate on common tasks.
2943238cf290f3387d3c727a2eec9d74506d9339.doc20
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
.1.10.1 Closed Loop Feedback Control
In the closed loop feedback we monitor our work through our Progress Report and the Project Plan and be consistent with both artifacts. We update our status in our weekly developer meetings. If any mismatch is found between plan and production we analyze the issue and resolve the problem as soon as possible. By looking on at how critical the problem is we can categorize it into something we must address now or later.
.1.10.2 Reviews
The reviews for the life cycle plan of the system is done through the phases mostly at the end yet there are others in between. They are listed here: Review Board When we finish a phase, a review board session is conducted to see if the group can proceed to the next phase. All stakeholders are involved. The Architecture Review Boards (ARB) for this semester are the following: o Foundation Commitment Review o Development Commitment Review o Rebaselined Development Commitment Review o Transition Readiness Review Core Capability Drive-through (CCD) Show the client the core capabilities of the system. Client interaction with the system will provide feedback to see if our system is consistent with her view of the system. It will be brought to her each time a new prototype is done. Configuration Management This allows us to have a clear and unified convention for versioning and updating the artifacts. It also allows tracing back too the documents. It uses Fagan's inspection to detect any defects of the peer work. Peer Review Team members will help each other in checking other's artifacts and provide suggestions and corrections. TAs Review The feedback provided by our TAs on our documents provide suggestions on improving deficiencies. Agile Artifact Review Review done by IIV&V students.
2943238cf290f3387d3c727a2eec9d74506d9339.doc21
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
.1.10.3 Project plan
The Project Manager elaborates a progress report weekly where he highlights each member task. The team can acknowledge the status of the project and the progress on it. Possible risks are identified and defects are discovered on the process. Moreover, the Project Plan is use to reassure the schedule of the project. The progress report and project plan are at the following link: http://greenbay.usc.edu/csci577/spring2009/projects/team16/PR/index.html
A.1.11Methods, Tools and Facilities
Table 21: Tools for the Project
Tools Microsoft Word 2007 Microsoft Project 2007 Microsoft PowerPoint 2007 Internet Explorer and Mozilla Firefox WikiWinWin-J Rationale Software Modeler Adobe Acrobat Reader iCard System and ER DART OCR Google Custom Search MySQL Tomcat Apache NetBeans 6.1 Bugzilla ABBYY PDF
Usage Used to generate all the artifacts of the project Used to create the weekly project plans Used to produce the presentations for the review Used to download documentations and help from ICM EPG. It is also the test environment for the system Used for the WikiWinWin negotiations Produce the UML models Use to read pdf files Submit effort report Manage risk Convert image into text Search within the script Database creation To produce web server IDE for the project To debug bugs on the project To convert PDF into DOC
Provider USC USC USC Free software USC USC Freeware USC USC On the scanner software Google freeware Opensource Opensource Opensource Opensource COTS
2943238cf290f3387d3c727a2eec9d74506d9339.doc22
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
A.2.
Resources
Using the COCOMO II 2000.3 tool we show the estimated cost for the project development in terms of the time and the number of people it needs. Here are the numbers we have for our team using what we have been given. They can be used to see if it fits according to the factors we set, or if we need to reduce the scope of the project. Even though there are more than 10 weeks for this class, it takes time to form groups during our first time. Rebaseline and transition will take a couple of weeks, as well, leaving us with 10 weeks. Spring 2009 577b Effort: (in assumption that everyone is still on the team) 6 team members at 12 hrs/week for 10 weeks Spring schedule will be: 720 hours Our project is separated into the following modules: Login: access or use system Administrator Profile Management: The administrator's capabilities to grant access to user to view specific script and for the administrator to register or change information. Search Script: The search inside the script that produces the pages where the keyword appears User Interface (View Scripts): Every visual and inputs for the user to interact with the system including view the scripts. Account Creation: the visitor register into the system and wait for permission Script Management: interface with the OCR, upload and edit the scripts. *Calibration will be done after better understanding of Code Count. The scale drivers for the module are the same so they will remain as one, yet the cost driver will vary. These are the tables for each module.
Table 22: COCOMOII Scale Driver
Scale Factor PREC
Value NOMINAL
FLEX RESL
HIGH HIGH
Rationale On the surface, this project appears to be fairly similar to basic database search / web interface applications. However, this specific implementation doesn't appear to have been done yet. There is good flexibility from the client and they are all based on schedule so capabilities can be eliminated The architecture clearly defines all the risks involved and is managed on a weekly-basis using DART.
2943238cf290f3387d3c727a2eec9d74506d9339.doc23
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
TEAM PMAT
NOMINAL NOMINAL
We are from different backgrounds and we have not worked together before yet the client is easy to reach The project has to be developed in fast pace and be matured quickly. However, ICM is a new approach to develop the system so the process maturity will be nominal
Table 23: COCOMOII Cost Driver Module 1 - Login
Cost Driver RELY DATA DOCU CPLX RUSE TIME STOR PVOL
Value LOW LOW NOMINAL LOW LOW NOMINAL NOMINAL LOW
Rationale If user cannot login, the administrator can always revert to the old system of manually retrieving and copying scripts for the users. There is no monetary loss. The amount of users data require for testing will not be small. However, it is small part of the database size. The amount of documentation will be suitable for its life-cycle needs, as this project seems to be fairly straightforward. It is a component most have done for a previous project. It won't be reused It requires less than 50% of execution time. There is few data to be stored for each user so it is less than 50%. Software will not get updated in a short amount of time. Even if it does it is always comparable to previous versions and will not alter the login. Analysts have had experience in the industry. Since our team consists of members from different backgrounds and different countries, not all are familiar with the procedures we plan to use. In addition, our coding styles will be different, as well as our methods of attack. This is a challenge that we will have to get through. More than 75% of the team will continue. Most of the team members have experience constructing a login and some even have experience with industry standards.
ACAP PCAP
NOM NOM
PCON APEX
HIGH HIGH
2943238cf290f3387d3c727a2eec9d74506d9339.doc24
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
LTEX
NOMINAL
Everyone in the team has had some coding experience and although it is not specifically JAVA or JSP, I believe that all high level coding languages are similar enough where one could just pick up another high-level language and learn it quickly. We will be using NetBeans, which comes with a small learning curve. The web server Apache Tomcat and database is MySQL. They are commonly use platforms and most of not all have experience with them for more than 1 year. Besides it is on Windows a common OS that everyone has use more than a year. NetBeans can be used to edit, debug, and test our code Seven of eight members of the team are in Los Angeles County and the client is located on campus. Our schedule will follow the schedule given in class. We will have 24 weeks spanning two semesters
PLEX
NOMINAL
TOOL SITE SCED
HIGH HIGH NOMINAL
Table 24: COCOMOII Cost Driver Module 2 Administrator Profile Management
Cost Driver RELY DATA DOCU CPLX RUSE TIME STOR PVOL ACAP PCAP
Value NOMINAL NOMINAL NOMINAL NOMINAL LOW NOMINAL LOW LOW NOM NOM
Rationale The administrator needs to be able to work reliably on the system. We require some data for testing different part of system the administrator control will have all the different parts except a search will be a good amount but still below 100, D/P<100. The amount of documentation will be suitable for its life-cycle needs, as this project seems to be fairly straightforward. So far the controls just involve uploading the scripts and activating user accounts It won't be reused Those are simple operations that might not take so long This module is more about functionality so it does not require much storage. Administration control will not have evolution Analysts have had experience in the industry. Since our team consists of members from different backgrounds and different countries, not all are familiar with the procedures
2943238cf290f3387d3c727a2eec9d74506d9339.doc25
Version Date: 04/02/09
Life Cycle Plan (LCP) _ Team 16
Version No 9.0
we plan to use. In addition, our coding styles will be different, as well as our method of attack. This is a challenge that we will have to get through. PCON APEX LTEX HIGH NOMINAL NOMINAL More than 75% of the team will continue. Those are web admin capabilities that most of us have developed Everyone in the team has had some coding experience and although it is not specifically JAVA or JSP, I believe that all high level coding languages are similar enough where one could just pick up another high-level language and learn it quickly. We will be using NetBeans, which comes with a small learning curve. The web server Apache Tomcat and database is MySQL. They are commonly use platforms and most of not all have experience with them for more than 1 year. Besides it is on Windows a common OS that everyone has use more than a year. NetBeans can be used to edit, debug, and test our code Seven of eight members of the team are in Los Angeles County and the clie...