Cycle Life Plan (LCP)
USC CCR Web Application
Team 7
CS-577b Development Team Andrew Hart Kailash Karol Skanda Ramesh Sutap Chatterjee Clients
Carolina Castillo Sharon Stewart Sinan Liu
Instructors & TA
Mr. A. Winsor Brown Dr. Barry Boehm Mr. Ed Colbert Supannika Koolmanojwong
Version Date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
Version History
LCP_RLCA_S07b_T07_V1.8.doc
ii
Version Date: 2/15/07
Life Cycle Plan (LCP) Date
10/11/06 10/16/06
Version no 1.8 Version
1.0 1.1
Author
SR SR
Changes made
FIRST VERSION OF LCP CHANGES MADE IN SECTION 1.1, 2.2 AND 5
Rationale
1.1 NEW ISSUES WERE ADDED, 2.2 THE ELABORATION PHASE PROJECT PLAN LINK WAS UPDATED 5 THE COST ESTIMATION FOR DIFFERENT MODULES IN THE PROJECT WAS UPDATED.
10/21/06
SR
1.2
CHANGES MADE IN SECTION 1.1, 1.2, 2.1, 2.2, 2.3.2, 4.1.4, 5
1.1 NEW ISSUES WERE ADDED, 1.2 ASSUMPTIONS WERE MODIFIED 2.1, 2.2 FROMATTING ERRORS 2.3.2 MODIFIED THE SCHEDULE FOR PRODUCTION STAGE. 4.1.4 DELETED THE THIS SECTION AS IT WAS NOT REQUIRED AS IT WAS A DUPLIACTE WITH FRD AND QMP 5 THE COST ESTIMATION WAS MODIFIED. CORRECTED THE GRAMMATICAL MISTAKES AS POINTED OUT BY THE IV & V. CORRECTED MISTAKES AS POINTED OUT BY IV & V.
10/25/06
SR
1.3
CHANGES MADE IN TABLE OF TABLES, SECTION 1.1, 1.2, 2.3.1, 4.1.2, CHANGES MADE IN SECTION 1.2, 1.3, 2.3.1, 4.1.4, 4.1.2, 4.2, 5
11/06/06
SR
1.4
11/19/06
SR
1.5
CHANGES MADE IN SECTION 2.2 , 1.1, 4.1, 3.1,2.3.1
CHANGES MADE FOR LCA DRAFT
12/03/06
SR
1.6
CHANGES MADE IN SECTION 1.1, 1.2, 2.2, 3.1, 5 CHANGES MADE IN SECTION 1.1, 1.2, 2.1, 2.2, 3.1, 3.2, 5 CHANGES MADE IN SECTION 2.2, 3.1,3.2, 5
CHANGES MADE FOR LCA PACKAGE BASED ON IV&V EVALUATION AND LCA ARB CHANGES MADE FOR RLCA DRAFT. CHANGES MADE FOR RLCA PACKAGE.
2/1/07
SR
1.7
2/15/07
SR
1.8
LCP_RLCA_S07b_T07_V1.8.doc
iii
Version Date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
Table of Contents
Life Cycle Plan (LCP)......................................................................................................................i Version History................................................................................................................................ii Table of Contents............................................................................................................................iv Table of Tables................................................................................................................................v
A.1. Introduction.........................................................................................................................................................1 A.1.1 Status of the LCP Document.......................................................................................................................1 A.1.2 Assumptions................................................................................................................................................1 A.1.3 References...................................................................................................................................................1 A.2. Milestones and Products.....................................................................................................................................3 A.2.1 Overall Strategy..........................................................................................................................................3 A.2.2 Phases..........................................................................................................................................................4 A.2.3 Project Deliverables....................................................................................................................................4 A.3. Responsibilities...................................................................................................................................................8 A.3.1 Overall Summary........................................................................................................................................8 A.3.2 By Phase / Stage..........................................................................................................................................9 A.4. Approach...........................................................................................................................................................12 A.4.1 Monitoring and Control.............................................................................................................................12 A.4.2 Methods, Tools and Facilities...................................................................................................................14 5. Resources.......................................................................................................................................................16 The link to COCOMO II file is:...............................................................................................................................16 COCOMO II Screen Shot:.......................................................................................................................................21
LCP_RLCA_S07b_T07_V1.8.doc
iv
Version Date: 2/15/07
Life Cycle Plan (LCP)
Version 1.8
Table of Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. Table 1: LCO Artifact deliverable in Engineering Stage (INCEPTION)...........................4 Table 2: LCA Artifact deliverable in Engineering Stage (ELABORATION).....................5 Table 3: Artifact deliverable in Production Stage......................................................6 Table 4: Stakeholder responsibilities during software lifecycle..................................8 Table 5: Stakeholder responsibilities during each phase..........................................10 Table 6: Authorized Stakeholder Representatives...................................................11 Table 7: COCOMOII Scale Driver...........................................................................16 Table 8: COCOMOII Cost Driver for module1.......................................................... 17 Table 9: COCOMOII Cost Driver for module2...........................................................19
LCP_RLCA_S07b_T07_V1.8.doc
v
Version Date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
A.1.
Introduction
The goal of the LCP for the project `USC CCR WEB APPLICATION' is to monitor and control the project's progress and to make the best use of people and resources available with the development team. It also gives the clients evidence that the developers have thought through major life cycle issues in advance.
A.1.1 Status of the LCP Document
During one of the developer/client meetings the clients put forward certain requirements for the prototype which is being developed. This would reduce the time to deliver the project to the client as some sort of conceptual coding is going to be done for the main module which is Data Collection & Analysis. This being one of the fallback options according to the Win Win Report will help us to make the project a success if this module works. The Data Collection and Analysis is the only module which would be proceeding to the construction and transition phase.
A.1.2 Assumptions
The assumptions for the project are: The system once developed will have a part time database maintainer who will be hired by the ER or CCR to maintain the system and keep the data consistent in the system. He would be required to spend about 2hrs/wk of his time. All the 29 program directors have access to the web and have basic computer knowledge and are going to use this website to maintain accurate and consistent data.
A.1.3 References
OCD document: http://greenbay.usc.edu/csci577/fall2006/projects/team7/LCA/OCD_LCA_F06a_ T07_V3.0.doc SSRD document: http://greenbay.usc.edu/csci577/fall2006/projects/team7/LCA/SSRD_LCA_F06a_ T07_V2.6.doc Weekly Progress Report : http://greenbay.usc.edu/csci577/fall2006/projects/team7/PR/Week12_PR_F06a_T 07.xls Client Meeting:
LCP_RLCA_S07b_T07_V1.8.doc
1
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
http://greenbay.usc.edu/csci577/fall2006/projects/team7/CMN/ Previous years projects: http://greenbay.usc.edu/csci577/fall2005/projects/team13/LCA/LCP_LCO_F05a_ T13_v1.1.doc Supporting Information Document: http://greenbay.usc.edu/csci577/fall2006/projects/team7/LCA/SID_LCO_F06a_T 07_V2.8.doc
LCP_RLCA_S07b_T07_V1.8.doc
2
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
A.2.
Milestones and Products
This section has a description of the overall strategy used in the life cycle of the project; it gives a description of the various life cycle stages, phases and milestones achieved. This section in general specifies the different tasks which have to be performed with the help of setting milestones and also specifies the deliverables (work products) which have to be completed.
A.2.1 Overall Strategy
The overall strategy used in our project "USC CCR WEB APPLICATION" is shown in this section and the process model used in this section is that of risk driven Win Win Spiral Model which is supported by the Lean MBASE guidelines. We use Win Win method because these win conditions helps us to identify and resolve risks at an early stage. This model fits into our project as we would be required to be developing several prototypes since it is important to get the system to be exactly what the client wants to be using. The different life cycle stages are Engineering Stage (Inception and Elaboration): Inception Phase (Life Cycle Objective) In the inception phase the Win Win agreements are captured. The following documents are delivered during this phase: 1) Initial Prototype 2) Win-Win negotiation Report 3) LCO Draft 4) LCO Core 5) LCO Package Elaboration Phase (Life Cycle Architecture) In the Elaboration phase the documents presented in inception phase are elaborated further. The following documents are delivered during this phase: 1) Remodeled prototype 2) Architecture elaboration 3) LCA Draft 4) Updated Easy Win Win Report. 5) LCA Package Production Stage (Construction and Transition):
LCP_RLCA_S07b_T07_V1.8.doc
3
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
Construction Phase: This phase takes place in Spring 2007 and includes development of the system and testing of the developed system. Transition Phase: This phase includes reviewing and testing the software in operational environment and is usually done during the later half of 577b class in Spring 2007.
A.2.2 Phases
The major milestones and dates are shown in the Gantt chart in the following link. Note: The plan for 577b is included in the same file. For All phases: LINK: http://greenbay.usc.edu/csci577/spring2007/projects/team7/PR/index.php Click on the link and then open the week #3 project plan file.
A.2.3 Project Deliverables
This section lists the different artifacts which have to be delivered on the respective due dates as shown in the following tables:
.2.3.1 Engineering Stage
Table 2: LCO Artifact deliverable in Engineering Stage (INCEPTION)
LCO Artifacts OCD
LCO Draft due date 10/04/2006
LCO Package due date 10/23/06
Format .doc, .pdf
Media Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website)
Version date: 2/15/07
SSRD
10/04/2006
10/23/06
.doc, .pdf
SSAD
10/11/2006
10/23/06
.doc, .pdf
LCP_RLCA_S07b_T07_V1.8.doc
4
Life Cycle Plan (LCP)
Version no 1.8
LCP
10/11/2006
10/23/06
.doc, .pdf
FRD
10/11/2006
10/23/06
.doc, .pdf
PROTOTYPE
9/29/2006
10/23/06
.doc, .pdf
SID
10/11/2006
10/23/06
.doc, .pdf
UML MODEL FILE EASY WIN WIN REPORT QR REPORTS
10/11/2006 10/02/06
10/23/06 11/08/06
.zip(.emx+.project) .doc, .pdf
Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website)
10/11/2006
10/23/06
doc, .pdf
Table 2: LCA Artifact deliverable in Engineering Stage (ELABORATION)
LCA Artifacts Updated Eassy Win Win Report Elaborated OCD Elaborated SSRD Revised SSAD Revised LCP
LCA draft due date 11/08/06
LCA Package due date NA
Format .doc, .xls
Media Hardcopy (printed) and Softcopy (team website) Softcopy (team website) Softcopy (team website) Softcopy (team website) Softcopy (team website)
11/20/2006 11/20/2006 11/20/2006 11/20/2006
12/04/2006 12/04/2006 12/04/2006 12/04/2006
.doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf
LCP_RLCA_S07b_T07_V1.8.doc
5
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
Revised FRD Updated Prototype Updated SID
11/20/2006 11/20/2006
12/04/2006 12/04/2006
.doc, .pdf .doc, .pdf
Softcopy (team website)) Softcopy (team website) Softcopy (team website) Softcopy (team website) Softcopy (team website) Hardcopy (printed) and Softcopy (team website)
11/20/2006
12/04/2006
.doc, .pdf
Updated UML Model File Easy Win Win Report QR Reports
11/20/2006
12/04/2006
. zip(.emx+.project) .doc, .pdf
11/20/2006
12/04/2006
11/20/2006
12/04/2006
doc, .pdf
.2.3.2 Production Stage
The deliverables in the production stage are listed below according to the schedule mailed by the teaching assistant of this course.
Table 3: Artifact deliverable in Production Stage
Artifact RLCA ARB RLCA Package Core Capability DriveThrough CCD Report IOC Working Set #1 Draft Transition Readiness Review(TRR)
Due date 02/09/2007 02/16/2007 03/05/2007 03/30/2007 04/04/2007 04/11/2007 04/12/2007
Format .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf 6
Medium Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and
Version date: 2/15/07
LCP_RLCA_S07b_T07_V1.8.doc
Life Cycle Plan (LCP)
Version no 1.8
TRR ARB Release Readiness Review Project Release .doc, .pdf 04/18/2007
Softcopy (team website) Hardcopy (printed) and Softcopy (team website) Hardcopy (printed) and Softcopy (team website)
05/02/2007
.doc, .pdf
Apart from the technical documents listed above we have to deliver transition package to the client which include the software packages: Source Code Load Modules Installation Scripts Software Development Files (e.g. test modules) The other client side deliverables include: User Manual Training Plan Transition Plan Support Plan Training materials (including tutorials and sample data) Regression Test Package Tools and Procedures Version Description Document (or Final Release Notes) Facilities, Equipment and Data (these may not be the responsibility of the team)
LCP_RLCA_S07b_T07_V1.8.doc
7
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
A.3.
Responsibilities
A.3.1 Overall Summary
Table 4: Stakeholder responsibilities during software lifecycle
Developers
Inception Prepare the documents which are necessary for LCO & LCA package. This includes meeting the exit criteria for SSAD, SSRD, OCD, LCP, FRD and prototype. The active participation of clients in Win Win negotiations and thus helping the developers come up with the correct win conditions which would help developers to document the LCO and LCA package better. Review and provide feedback for the different milestones.
Elaboration Refine / Elaborate documents from LCO ARB and evolve them to form the LCA Package milestone.
Construction Implement the system which was being proposed in the previous 2 phases and also test the same.
Customers / Clients
Review the documents delivered and monitor the progress in the project. Provide feedback on the documents.
Core Capability drive through Review the prototypes being developed and give feedback to the developers.
Transition The software should be reviewed and tested in the real world and should also provide a user's manual for new users ( i.e., a help option in the website) Check how the software has progressed by monitoring its working regularly. Learn how to use the web based tool effectively.
IV&V
Review and provide feedback for the different milestones.
Review and provide feedback for each document delivered in this phase.
Review and provide feedback for the different milestones.
LCP_RLCA_S07b_T07_V1.8.doc
8
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
A.3.2 By Phase / Stage
Table 5: Stakeholder responsibilities during each phase
Team Member / Role Andrew Hart System Architect and Manager
Eva Lee Project Manager, Prototypist
Inception Primary: Creation and design of the initial System Architecture, via the SSAD Secondary: UML Modeling of the system Primary: Creation of initial prototypes and operational storyboard. Secondary: Creation and documentation of OCD.
Primary / Secondary Responsibility Elaboration Construction Primary: Primary: Maintenance and SSAD its enhancement of documentation the SSAD Secondary: Secondary: Prototype and its Maintenance and incremental Enhancements to development the OCD Primary: Maintenance and Enhancement of prototype. Creation of Functional Prototype Secondary: Enhancements and Updates to the SSRD Primary: Enhancement and updates to the SSRD Secondary: Maintain project schedule provide feasibility By using FRD
Transition Primary: Documentation of transition process Secondary: Supervise installation and deployment
NA
NA
Karim Vidhani Analyst/Tester
Primary: Requirement Creation and documentation of Requirements via the SSRD Secondary: Creation and design of the initial System Architecture, via the SSAD
NA
NA
LCP_RLCA_S07b_T07_V1.8.doc
9
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
Primary: Carlo Stearns Creation and documentation of OCD and Quality the OCD Assurance Person Secondary: Creation and design of the initial System Architecture, via the SSAD Kailash Karol FRD Primary: Creation of FRD analysis Secondary: Creation of initial prototypes and operational storyboard
Primary: Maintenance and Enhancements to the OCD Secondary: Maintenance and enhancements to the LCP and project schedule Primary: Maintenance and enhancements to the LCP and project schedule provide feasibility By using FRD Secondary: enhancement of the initial prototype. Primary: Maintenance and enhancements to the LCP and project schedule Secondary: Maintenance and enhancement of the SSAD Primary: (IV & V ) i.e., verification and validation Secondary: Help out in project plans and progress reports.
NA
NA
Primary: FRD and its documentation Secondary: SSRD and its documentation and prototyping.
Primary: Interface with clients/users to co-ordinate efforts Secondary: Supervise installation and deployment
Skanda Ramesh LCP
Betty Liu (IV&V) Verifications and Validation.
Primary: Creation of LCP and project scheduling Secondary: Creation of initial prototypes and operational storyboard Primary: (IV & V ) i.e., verification and validation Secondary: Help out in project plans and progress reports.
Primary: LCP and its documentation Secondary: OCD and its documentation and protyping.
Primary: Supervise installation and deployment Secondary: Documentation of transition process
NA
NA
LCP_RLCA_S07b_T07_V1.8.doc
10
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
Sutap Chatterjee (V&V) Verifications and Validation.
NA
NA
Primary: Quality Assurance and Testing, QMP. Quality Focal Point person. Secondary: Development of software solution
Primary: Supervise installation and deployment Secondary: Documentation of transition process
Table 6: Authorized Stakeholder Representatives
Stakeholders Sharon Stewart Carolina Castillo Sinan Liu
Category client / customer client / customer Business Analyst
Organization Director, CCR Director, External Relations Marshall School of Business
LCP_RLCA_S07b_T07_V1.8.doc
11
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
A.4.
Approach
A.4.1 Monitoring and Control
Monitoring and control in our project is done by the following methods: We have a Google group [e-mail] we use this group to post our deliverables or questions etc., most of our interaction takes place via email through this group, this is an efficient way of communicating as all of us are updated with what is happening in the project automatically. Weekly effort report is done by individually logging onto the link http://greenbay.usc.edu/iCard/authentication/ulogin.php and then entering our weekly effort in this way we can record, how much of effort we put in that week on our project. This also gives the cumulative effort of the entire team, which is useful to find out whether we are on track or not. The weekly progress report is compiled by one person every week, usually different for every week, but all the members have to fill out individually a weekly progress report and mail it to the group. This then is compiled by one person and then put on the team website. The team also has a website where all its deliverables and a brief description of its project is posted. A MS Project plan is also developed by an individual usually a different person every week, and it is used to monitor the progress in the project and also estimate when a particular deliverable can be completed. It is helpful to judge when a milestone is reached. The team also holds developers meetings regularly to discuss the risks and issues the different developers may have. The team coordinates with each other while developing any deliverables using pair programming methodology; this is done so as to maintain quality. There are also meetings held with the client at least once a week, where certain issues are resolved, also feedback for the different deliverables are given by the client during these meetings. The minutes of the meeting is documented by the facilitator and is sent out to all the stakeholders and these minutes are also updated on the website under client meeting notes. We also have the ARB review and QMIS tool to maintain the quality in the project being developed, there are two major ARB reviews held in the course of 577a where the ARB checks whether we are headed in the right direction. The QMIS tool helps us to keep track of the top risks in our project and hence try to remove them and also helps us to monitor the status of this risk. The Test Plan and the Iteration Plan helps us to plan the testing and development of the system
LCP_RLCA_S07b_T07_V1.8.doc
12
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
The Quality Management Plan helps us to maintain the quality in the project with the help of the QFP person.
.4.1.1 Closed Loop Feedback Control
The weekly progress reports and DART tool helps us to find out the risks which have been persistent. To resolve this risk, this issue is brought up by one of the team members and it is either resolved during the meeting or mitigated by taking steps toward resolving the risk. The MS Project Plan is updated weekly on the website and this is used to check whether everything is on schedule, if not on schedule the project manager with this feedback would try to give high priority to the deliverable which is not on schedule and bring it up in the next meeting.
.4.1.2 Reviews
There are many ways in which reviews are made: Pair review the deliverables have been made using pair development, on completion the pair who developed the document would review the pair development form and write down ` Area's of concern ' , the defects they found and how important they were, and whether they were fixed. This sort of pair review where one person is the driver and the other the observer helps to increase quality in the software product and reduces risks and defects. IV&V review- Every deliverable which is submitted is reviewed in detail by the IV&V and a feedback on different defects or issues is sent back to the team. The team now reviews the defects that were sent by the IV&V and if valid makes the necessary changes. Individual reviews- Every deliverable is read by all the team members as each deliverable is mailed to the team members before it is put up on the website and then each of them give their own feedback on the deliverable, in this way the content of all the deliverables will be consistent and there would be no clashes in ideas. Review in developer meetings- the developers do some sort of review during meetings held where the deliverable to be made is first looked into and then the feedback from different members is got on how to do it, the developers also discuss some major risks or issues which have not been discussed till now or has been there for a long time. LCA and LCO ARB reviews provide the team valuable feedback from clients, professors, and TA. These reviews help the team to correct any faults in the documents, approach, design etc., which is crucial for the success of the project.
.4.1.3 Status Reporting
The status report of all the team member's efforts should be updated in the weekly individual effort report. 13
Version date: 2/15/07
LCP_RLCA_S07b_T07_V1.8.doc
Life Cycle Plan (LCP)
Version no 1.8
Individual weekly progress reports are sent to the Google groups, every week a particular individual takes responsibility and compiles all individual reports received in the groups into a single weekly progress report and then uploads it into the database. The MS Project plan is done by the project manager or one of the team members; this helps us to get a formal representation of what progress has been done in the project and what milestones have been reached.
4.1.4 Project Communication
The techniques and tools my team uses for communication are: We use Win Win tool to capture the win conditions We have a Google group [e-mail] we use this group to post our deliverables or questions etc., most of our interaction takes place via email through this group, this is an efficient way of communicating as all of us are updated with what is happening in the project automatically. We also used audio conferencing while meeting with our clients as some of them are from different programs and were not available to meet personally. We also use discussion rooms where only the developers or sometimes even the client meets personally. We sometimes use telephones to interact with developers. Team website is another way of interacting and communicating as any document to be given to everyone can be just put on the team website. The developers also meet for short periods of time before and after class. We use crawwler.com/citadel for maintaining versioning and code consistency.
A.4.2 Methods, Tools and Facilities
The Easy Win Win negotiation was done using the Easy Win Win tool which is available at http://alanya.usc.edu/AMWebHost/default.asp this tool made it simpler for all the stakeholders to participate in the Win Win negotiation as it documented the win conditions and also gave a chance for all the success critical stakeholders to vote on the win conditions, it also identified risks which needed to be resolved by the success critical stakeholders. The tool MS Project is used to create the weekly project plans and also shows the Gantt chart which shows the amount of work completed. The COCOMO tool is used to estimate the cost of developing the system in terms of money as well as effort put into the system. 14
Version date: 2/15/07
LCP_RLCA_S07b_T07_V1.8.doc
Life Cycle Plan (LCP)
Version no 1.8
IBM Rational Software Architect tool can be used to build UML diagrams and is used to design the architecture of a system. We also use the Lean MBASE guidelines present in the link http://greenbay.usc.edu/csci577/fall2006/site/guidelines/LeanMBASE_Guidelines_V1.7 this link leads to the guidelines which is required to develop a good document.
LCP_RLCA_S07b_T07_V1.8.doc
15
Version date: 2/15/07
Life Cycle Plan (LCP)
Version no 1.8
5. Resources
The link to COCOMO II file is:
http://greenbay.usc.edu/csci577/fall2006/projects/team7/LCA/PMD/index...