Cycle Life Plan (LCP)
Data Mining of Digital Library Usage Data
Team 7 Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UML
November 21, 2004
Life Cycle Plan
Version 3.0
Version History
Date 10/05/04 10/18/04 Author Fenny Muliawan Fenny Muliawan Fenny Muliawan Version 1.0 1.1 Changes made Initial draft Some grammar mistakes were fixed. Modify Configuration Change Flowchart [figure 3] More elaboration on [section 3.2.3] Modify document based on ARB review Updated Project milestones Engineering phase[Section 2.2.1] Added Risk monitoring and control [Section 4.1.5] Added Configuration Status Management [Section 4.3.4] Added Budgets [Section 5.2] Incorporate various LCO ARB review document Project website links added to various different sections Plan modified and updated [section 2.2.1] [section 2.2.2] Gantt Chart and Pert Chart updated [Section 6] Updated responsibilities [section 3]
10/23/04
2.0
11/15/04 11/21/04
Fenny Muliawan Fenny Muliawan
2.2 3.0
LCP_LCO_F04a_T07_V03.0.doc
ii
Version Date: 11/21/2004
Life Cycle Plan
Version 3.0
Table of Contents
Life Cycle Plan (LCP) ................................................................................................................................................i
Version History............................................................................................................................... ii Table of Contents........................................................................................................................... iii Table of Tables ............................................................................................................................... v Table of Figures ............................................................................................................................ vii
1. 1.1 1.2 1.3 1.4 2. 2.1 2.2 2.3 3. 3.1 3.2 4. 4.1 4.2 4.3 4.4 5. 5.1 5.2 Introduction ................................................................................................................................................1 Purpose of the Life Cycle Plan Document..................................................................................................1 Assumptions ...............................................................................................................................................1 References ..................................................................................................................................................1 Change Summary .......................................................................................................................................3 Milestones and Products.............................................................................................................................4 Overall Life Cycle Strategy ........................................................................................................................4 Phase Milestones and Schedules ................................................................................................................4 Project Deliverables..................................................................................................................................14 Responsibilities.........................................................................................................................................21 Stakeholder Responsibilities.....................................................................................................................21 Development Responsibilities ..................................................................................................................24 Approach ..................................................................................................................................................26 Monitoring and Control ............................................................................................................................26 Methods, Tools and Facilities...................................................................................................................31 Configuration Management ......................................................................................................................32 Quality Management ................................................................................................................................35 Resources..................................................................................................................................................37 Work Breakdown Structure ......................................................................................................................37 Budgets .....................................................................................................................................................39
LCP_LCO_F04a_T07_V03.0.doc
iii
Version Date: 11/21/2004
Life Cycle Plan
6. 6.1 6.2 6.3
Version 3.0
Appendices ...............................................................................................................................................40 Gantt Chart ...............................................................................................................................................40 Pert Chart..................................................................................................................................................45 COCOMO result.......................................................................................................................................51
LCP_LCO_F04a_T07_V03.0.doc
iv
Version Date: 11/21/2004
Life Cycle Plan
Version 3.0
Table of Tables
Table 1: Change Summary ............................................................................................................................................3 Table 2: Engineering Stage Deliverable 1 ..................................................................................................................14 Table 3: Engineering Stage Deliverable 2 ..................................................................................................................15 Table 4: Engineering Stage Deliverable 3 ..................................................................................................................15 Table 5: Engineering Stage Deliverable 4 ..................................................................................................................15 Table 6: Engineering Stage Deliverable 5 ..................................................................................................................15 Table 7: Engineering Stage Deliverable 6 ..................................................................................................................16 Table 8: Engineering Stage Deliverable 7 ..................................................................................................................16 Table 9: Engineering Stage Deliverable 8 ..................................................................................................................16 Table 10: Engineering Stage Deliverable 9.................................................................................................................16 Table 11: Engineering Stage Deliverable 10...............................................................................................................16 Table 12: Engineering Stage Deliverable 11...............................................................................................................17 Table 13: Engineering Stage Deliverable 12...............................................................................................................17 Table 14: Engineering Stage Deliverable 13...............................................................................................................17 Table 15: Engineering Stage Deliverable 14...............................................................................................................17 Table 16: Engineering Stage Deliverable 15...............................................................................................................17 Table 17: Engineering Stage Deliverable 16...............................................................................................................18 Table 18: Engineering Stage Deliverable 17...............................................................................................................18 Table 19: Production Stage deliverable 1 ...................................................................................................................18 Table 20: Production Stage deliverable 2 ..................................................................................................................18 Table 21: Production Stage deliverable 3 ...................................................................................................................19 Table 22: Production Stage deliverable 4 ...................................................................................................................19 Table 23: Production Stage deliverable 5 ...................................................................................................................19 Table 24: Production Stage deliverable 6 ...................................................................................................................19
LCP_LCO_F04a_T07_V03.0.doc
v
Version Date: 11/21/2004
Life Cycle Plan
Table of Contents
Table 25: Production Stage deliverable 7 ...................................................................................................................19 Table 26: Production Stage deliverable 8 ...................................................................................................................20 Table 27: Production Stage deliverable 9 ...................................................................................................................20 Table 28: Production Stage deliverable 10 .................................................................................................................20 Table 29: Stakeholder Responsibilities........................................................................................................................21 Table 30: Stakeholder representatives ........................................................................................................................21 Table 31: Engineering stage responsibilities ..............................................................................................................22 Table 32: Production stage responsibilities ................................................................................................................23 Table 33: Support Stage Responsibilities ....................................................................................................................23 Table 34: Development responsibilities ......................................................................................................................24 Table 35: Staffing ........................................................................................................................................................25 Table 36: Top-N Risk Item List (Assuming weekly risk reassessment October 4-10, 2004)........................................28 Table 37: Detailed Risk Management .........................................................................................................................28 Table 38: Product Element identification....................................................................................................................33 Table 39: Assessment Activities...................................................................................................................................35 Table 40: Time Cost for both Developers and Client ..................................................................................................40 Table 41: COCOMO Scale Factors.............................................................................................................................51 Table 42: COCOMO Product Factors ........................................................................................................................51 Table 43: COCOMO Platform Factors .......................................................................................................................52 Table 44: COCOMO Personnel Factors .....................................................................................................................52 Table 45: COCOMO Project Factors .........................................................................................................................52
LCP_LCO_F04a_T07_V03.0.doc
vi
Version Date: 11/21/2004
Life Cycle Plan
Version 3.0
Table of Figures
Figure 1: Phase Milestones and Schedules ...................................................................................................................5 Figure 2: Development Organization Chart................................................................................................................25 Figure 3: Configuration Change flowchart.................................................................................................................34 Figure 4: Gantt chart - Milestones and schedule in engineering stage view 1............................................................41 Figure 5: Gantt chart - Milestones and schedule in engineering stage view 2............................................................42 Figure 6: Gantt chart - Milestones and schedule in production stage view 1 .............................................................43 Figure 7: Gantt chart - Milestones and schedule in production stage view 2 .............................................................44 Figure 8: Pert chart - Milestones and schedule in engineering stage view 1..............................................................45 Figure 9: Pert chart - Milestones and schedule in engineering stage view 2..............................................................46 Figure 10: Pert chart - Milestones and schedule in engineering stage view 3............................................................47 Figure 11: Pert chart - Milestones and schedule in production stage view 1 .............................................................48 Figure 12: Pert chart - Milestones and schedule in production stage view 2 .............................................................49 Figure 13: COCOMO result........................................................................................................................................53
LCP_LCO_F04a_T07_V03.0.doc
vii
Version Date: 11/21/2004
Life Cycle Plan
Version 3.0
1. Introduction
1.1 Purpose of the Life Cycle Plan Document
The purpose of the Life Cycle Plan document is to serve as the basis for monitoring and controlling the progress of the Data Mining of Digital Library Usage Data project throughout its life cycle. This document provides a detailed description of the project's objectives, which is to analyze digital archive usage logs and create relationships and display them in the three-dimension view. It also describe some milestones of this project. It will assist the developers and client in putting their best effort into the development of the project.
1.2 Assumptions
The following are the conditions that are assumed to be true for this project: No major changes will be made for the requirements. The open source code that we will be using as a basis for user interface design is stable. i.e.: this is the final version Log data will be provided by ISD representative. The format will not change in the future. People are using current USC Digital Archive System. The project will continue on to cs577b.
1.3 References
"Data Mining of Digital Library Usage Data" Project Description http://sunset.usc.edu/classes/cs577a_2004/projects/description/project7.htm MBASE Guidelines version 2.4.1 http://sunset.usc.edu/classes/cs577a_2004/guidelines/MBASE_Guidelines_v2.4.1.pdf MBASE Version 2.4.1 Templates for LCP (version 1a) http://sunset.usc.edu/classes/cs577a_2004/guidelines/MBASEtemplates/LCP_Templatev 1a.doc MBASE Electronic Process Guide http://cse.usc.edu/research/MBASE/EPG Fall 2004 CS 577a Project #7 Prototype for LCO LCP_LCO_F04a_T07_V03.0.doc 1 Version date 11/21/2004
Life Cycle Plan http://seacliff.usc.edu/~team7/LCO/LCO.html Fall 2004 CS 577a Project #7 SSRD for LCO http://seacliff.usc.edu/~team7/LCO/LCO.html Fall 2004 CS 577a Project #7 SSAD for LCO http://seacliff.usc.edu/~team7/LCO/LCO.html
Version 3.0
Fall 2003 CS 577a Project #5 LCP portion of LCO http://ebase.usc.edu:8080/Document%20Library/CSCI577%20Projects/cs577a_2003/tea m05a/LCO/LCP_LCO_F03a_T05.doc Fall 2003 CS 577a Project #8 LCP portion of LCO http://ebase.usc.edu:8080/usercontrol/csci577/cs577a_2003/team08a/default.aspx Fall 2003 CS 577a Project #26 LCP portion of LCO http://ebase.usc.edu:8080/Document%20Library/CSCI577%20Projects/cs577a_2003/tea m26a/LCO/LCP_LCO_F03a_T26.doc Fall 2004 CS 577a OCD early section assignment http://cse.usc.edu/classes/cs577a_2004/assignments/Team/Exit_Criteria_for_Early_Secti ons_OCD_MBASE_2.4_V3.doc Fall 2004 CS 577a Prototype assignment http://cse.usc.edu/classes/cs577a_2004/assignments/Team/prototype.html Fall 2004 CS 577a Easy WinWin assignment http://cse.usc.edu/classes/cs577a_2004/assignments/Team/EasyWinWin.doc Fall 2004 CS 577a LCO Core assignment http://cse.usc.edu/classes/cs577a_2004/assignments/Team/Exit_Criteria_for_LCO_Core_ V1.doc Fall 2004 CS 577a LCO Draft assignment http://cse.usc.edu/classes/cs577a_2004/assignments/Team/LCO%20Draft.doc USC Information Services Division http://www.usc.edu/isd/about/about.html Dr. Bollen, Johan presentations http://www.cs.odu.edu~jbollen/presentations/facstaff_02_28_03.pdf http://www.cs.odu.edu/~jbollen/presentations/ecdl02.pdf http://www.cs.odu.edu/~jbollen/presentations/aisti04.pdf
LCP_LCO_F04a_T07_V03.0.doc
2
Version date 11/21/2004
Life Cycle Plan
Version 3.0
1.4 Change Summary
Table 1: Change Summary
Version 1.0 1.1 Changes Made Initial draft. Some grammar mistakes were fixed. Modify Configuration Change Flowchart [figure 3] More elaboration on [section 3.2.3] 2.0 Updated Project milestones Engineering phase[Section 2.2.1] Added Risk monitoring and control [Section 4.1.5] Added Configuration Status Management [Section 4.3.4] Added Budgets [Section 5.2] 2.1 3.0 Incorporate various LCO ARB review document Project website links added to various different sections Plan modified and updated [section 2.2.1] [section 2.2.2] Gantt Chart and Pert Chart updated [Section 6] Updated responsibilities [section 3]
LCP_LCO_F04a_T07_V03.0.doc
3
Version date 11/21/2004
Life Cycle Plan
Version 3.0
2. Milestones and Products
This section describes the project functions that will be performed during the project life cycle.
2.1 Overall Life Cycle Strategy
The process of defining and developing the Data Mining of Digital Library Usage Data is approached using the win-win spiral model, which is divided into three major stages: Engineering, Production and Support stage. The following are the phases and milestones of each stage: 1. Engineering Stage a. Inception Phase Initial Prototype, WinWin spiral cycle results in LCO artifacts. This cycle needs to be completed by ARB review before moving on to the next cycle. Milestone: LCO Package October 25, 2004 b. Elaboration Phase Life Cycle Architecture is another WinWin spiral cycle. It also needs to be accomplished by ARB review. Milestone: LCA Package December 6, 2004 2. Production Stage: The two phases of production stage will be completed in the spring semester. a. Construction Phase This phase covers the development and testing of the proposed system. It consists of a short Win-win spiral cycle to incorporate changes. It will result in a Transition Readiness Review (TRR). b. Transition Phase The transition phase results in the production of the transition plan and ends with a Release Readiness Review (RRR). 3. Support Stage Support stage is undefined at this point.
2.2 Phase Milestones and Schedules
The following are the milestones needed to be achieved: LCO ARB Review LCO (Life Cycle Objectives) LCA ARB Review LCA (Life Cycle Architecture) 10/20/2004 10/25/2004 12/01/2004 12/06/2004
LCP_LCO_F04a_T07_V03.0.doc
4
Version date 11/21/2004
Life Cycle Plan RLCA(Re-baseline Life Cycle Architecture) ARB RLCA Package IOC(Initial Operation Capability) Working Set #1 Core Capability - ARB TTR (Transition Readiness Review) Package TTR Review IOC Working Set RRR (Release Readiness Review)
Version 3.0 02/16/2005 (anticipated) 02/21/2005 (anticipated) 03/27/2005 (anticipated) 03/27/2005 (anticipated) 04/08/2005 (anticipated) 04/11/2005 (anticipated) 04/25/2005 (anticipated) 05/04/2005 (anticipated)
The following figure shows the milestones of the project dates by which the documents need to be completed: Figure 1: Phase Milestones and Schedules
RLCA 04/21/2005 LCA ARB: 12/1/2004
CCR ARB 03/27/2005
TRR 04/04/2005
WinWin, Prototype, early OCD: 9/22/2004
LCO ARB: 10/20/200
Inception Iteration
Preliminary Iteration
Elaborati on Iteration #1
Elaborati on. Iteration #2
Construc tion Iteration #1
Construc tion Iteration #2 Transition Phase
TBD
TBD
Release Phase
Engineering
Production
Support
2.2.1
Engineering Stage (Inception and Elaboration Phases)
This section identifies the activities, milestones in the inception and elaboration phase of the project. Gantt chart for this stage is provided in [Section 6.1.1] of this document. Pert chart for this stage is provided in [Section 6.2.1] of this document.
LCP_LCO_F04a_T07_V03.0.doc
5
Version date 11/21/2004
Life Cycle Plan
Version 3.0
9/10/2004 Team formed Six students (Shing-Cheung Chan, Maxim Krivokon, Hsiao-Han Huang, Pei-Han Li, Fenny Muliawan, Hui-Hsien Chi) from cs577A class form a team to work together for the project. At this point, we also submit our four preferences of the project to cs577a TAs. 9/13/2004 Client visit during class Client (Jewel Ward) visits the developer team during class session and describes the background of the project 9/15/2004 First official client meeting First meeting with client and Dr. Bollen is held. Dr. Bollen presents brief description about the project. 9/16/2004 Client meeting 2 Developer team and client hold a meeting to get detailed description about the project and overview of project requirements. 9/16/2004 Developer team meeting 1 Developer team holds a meeting to discuss the level of understanding of the project within the team 9/18/2004 Developer team meeting 2 Developer team holds a meeting to discuss about Operational Concept Description document. 9/20/2004 Win-win negotiation session 1 Developer team and client hold the first win-win meeting to brainstorm and negotiate the win situation for both parties. 9/20/2004 OCD early section peer review Review of Early OCD is conducted by some developers 9/22/2004 OCD Draft Early Operational Concept Description document is to be submitted in hardcopy format during class. It contains the top level system objectives and scope.
LCP_LCO_F04a_T07_V03.0.doc
6
Version date 11/21/2004
Life Cycle Plan
Version 3.0
9/22/2004 Win-win negotiation session2 Developer team and client hold a second meeting to brainstorm and negotiate the win situation for both parties. 9/24/2004 Win-win negotiation session3 Developer team and client hold a third meeting to decide the win conditions of this project for both parties. 9/25/2004 Win-win negotiation final session Developer team and client hold a final meeting to vote for the win conditions base on business importance and easy of implementation and check the completeness of the negotiation topics. Developer team discusses the prototype design after the Win-win negotiation. 9/27/2004 Prototype early version Early prototype design of the user interface model is to be submitted in class in hardcopy format. 9/29/2004 Easy Win-win Document Final win-win negotiation result in document format. The results contain the win criteria for both the developers and client. 9/29/2004 Client meeting Developer team meets with client to gain information about the organization/ project structure for the purpose of OCD documenting. We also discuss further about prototype design of the user interface. Also, client provides a user ID and password to access DA database. 10/1/2004 LCO Core OCD modified version (if available), SSAD and SSRD early version. SSRD provides the top level functions and interface of the system. SSAD provides the top level definition of the physical and logical architecture of the system. The LCO Core is to be published on team web-site. 10/8/2004 Developer team meeting 3 The developer team meets to discuss LCO Core document review.
LCP_LCO_F04a_T07_V03.0.doc
7
Version date 11/21/2004
Life Cycle Plan 10/8/2004 LCO OCD peer review LCO-OCD peer review is conducted by two members of the team 10/8/2004 LCO SSRD peer review LCO-SSRD peer review is conducted by two members of the team 10/8/2004 LCO SSAD peer review LCO-SSAD peer review is conducted by two members of the team
Version 3.0
10/11/2004 LCO draft OCD, SSAD, SSRD modified version (if available) LCP, FRD early version. LCP provides the responsibilities of key stakeholders during the development of the system. It provides the life cycle plan of the project. FRD ensures that consistency is maintained among all documents. The LCO draft is to be published on team web-site, and quality reviews need to be submitted in class in hardcopy format. Responsibility: OCD: Shing-Cheung Chan SSRD: Maxim Krivokon SSAD: Pei-Han Li, Hsiao-Han Huang LCP: Fenny Muliawan FRD: Hui-Hsien Chi 10/20/2004 LCO ARB Review of LCO document done by cs577a professor (Dr. Boehm), substitute client and one of the cs577a TA (Gustavo). 10/22/2004 Developer team meeting4 The developer team meets to discuss final LCO document based on the suggestion of improvement from LCO ARB, and conduct a meeting with team mentor to clarify the confusing aspect of the documents. 10/25/2004 LCO Package Final LCO package is ready. It contains OCD, SSAD, SSRD, LCP and FRP. LCO package is to be submitted in class in hardcopy, and also published on team website.
LCP_LCO_F04a_T07_V03.0.doc
8
Version date 11/21/2004
Life Cycle Plan 10/30/2004 Developer team meeting 5 The developer team meets to discuss LCA document. 11/05/2004 Developer team meeting 6 The developer team meets to discuss LCA draft.
Version 3.0
11/11 - 11/15/2004 IV&V Problem for LCO package problem Problem list of LCO package problem sent by IV&V are reviewed and any changes needed according to the problem list are made to the document. 11/15/2004 Developer team meeting 7 The developer teem meets to plan the schedule for the upcoming milestone. 11/15 11/22/2004 LCA draft Life Cycle Architecture draft Responsibility: OCD: Shing-Cheung Chan SSRD: Maxim Krivokon SSAD: Pei-Han Li, Hsiao-Han Huang LCP: Fenny Muliawan FRD: Hui-Hsien Chi 11/17 Author is to send the artifact he/she responsible with to the corresponding reviewer. Reviewers: OCD: Hsiao-Han Huang SSRD: Fenny Muliawan SSAD: Shing-Cheung Chan LCP: Pei-Han Li FRD: Maxim Krivokon UML & prototype: Hui-Hsien Chi 11/18-11/19 Artifact is reviewed and suggestions are sent to the author by 11/19 midnight. 11/19-11/21 Author make any changes necessary to the artifact according to review. The final version of the artifact (LCA draft), along with the quality report, are sent to the project manager by 11/21 midnight to be posted to the team website (http://seacliff.usc.edu/~team7). 11/22 - The LCA draft is sent to the client, Jewel Ward to be reviewed. 11/24/2004 Developer team meeting 8
LCP_LCO_F04a_T07_V03.0.doc
9
Version date 11/21/2004
Life Cycle Plan
Version 3.0
First LCA draft presentation practice for LCA-ARB. Suggestions on the presentation are addressed to the presenter. Lawford Anderson, a professor chair from Department of Earth Sciences, is expected to be present to give some comment and suggestion on the quality of the presentation. 11/29/2004 Developer team meeting 9 Second LCA ARB presentation practice (after suggestions from the first practice are incorporated). 11/30 or 12/1/2004 LCA ARB The LCA draft is presented to Prof. Boehm, Jewel Ward, and cs577 TAs by the developers. The professor is expected to give some comments to improve the document. 12/1/2004 Developer team meeting 10 Developer team meets to discuss the ARB comment that's been given during the ARB meeting. 12/2/2004 Meeting with mentor The developers conduct a meeting with mentor to clarify any comment given during the presentation. 12/2 12/6//2004 LCA Package Author modifies the artifact he/she is responsible according to comment/suggestion given during the presentation. Responsibility: OCD: Shing-Cheung Chan SSRD: Maxim Krivokon SSAD: Pei-Han Li, Hsiao-Han Huang LCP: Fenny Muliawan FRD: Hui-Hsien Chi 12/3 - Artifacts are sent to the reviewer to be reviewed. Reviewers: OCD: Fenny Muliawan SSRD: Hsiao-Han Huang SSAD: Hui-Hsien Chi LCP: Maxim Krivokon FRD: Pei-Han Li UML and Prototype: Shing-Cheung Chan 12/4 Artifact is reviewed and suggestions are sent to the author by 12/4 midnight.
LCP_LCO_F04a_T07_V03.0.doc
10
Version date 11/21/2004
Life Cycle Plan
Version 3.0
12/4 - 12/6 - Author make any changes necessary to the artifact according to review. The final version of each artifact is sent to the project manager by 12/5 midnight to be posted to the team website (http://seacliff.usc.edu/~team7).
2.2.2
Production Stage (Construction and Transition Phases)
This section identifies the specific activities, milestones, and priorities for implementation of the system requirements in a feasible timely manner to achieve initial operational capability (IOC). The main focus is on the schedule for which the system components will be implemented. The activities account for the execution and further development of IOC plans (iterations, quality, test, inspection, transition, etc.) and the creation of major client deliverables such as user manuals, test, inspection, iteration reports, release notes, final architecture documents). The dates used for this stage is a rough estimation based on previous year work. Gantt chart for this stage is provided in [Section 6.1.2] of this document. Pert chart for this stage is provided in [Section 6.2.2] of this document. 01/10/2005 Spring Semester Starts, Re-Baseline Phase On this day, the next semester is supposed to start. 01/21/2005 New Team Formed. New team might be formed, depending on the number of members of the team will continue on taking cs577b. 01/22/2005 Team meeting 1 Developers meet to discuss and review about the project. Some team members might leave and new personnel(s) come and join the team. Roles are assigned to every individual. 01/25/2005 Client meeting 1 Possible meeting with client to ensure that each member of the team thoroughly understands the project. 01/26 - 01/28/2005 LCA Documents Reviewed. The developer team reviews the artifacts from the LCA Package and evaluates them. 01/28 01/31/2005 LCP_LCO_F04a_T07_V03.0.doc 11 Version date 11/21/2004
Life Cycle Plan Requirement The development team updates the SSRD if necessary.
Version 3.0
01/31 02/04/2005 Architecture Development team determine the implementation detail of the system, and updates SSAD if necessary 02/06/2005 Client meeting 2 Possible second meeting with client to better understand the needed information for RLCA draft. 02/07/2005 Team meeting 2 The developer team conducts a meeting to make sure that each team member has all the information needed for RLCA 02/08 02/14/2004 RLCA draft preparation LCA document produced in the previous semester is updated and modified if necessary. 02/15/2004 RLCA review Development team conducts a review of all the RLCA document. 02/16/2005 RLCA draft online RLCA documents draft is ready and posted online on the team website (http://seacliff.usc.edu/~team7. 02/21/2005 RLCA ARB Team present progress of the project to Prof. Boehm, Jewel Ward, and possibly some other digital library related personnel. 02/22/2005 Client meeting 3 Possible third meeting with client to discuss the core capability development. 02/23 02/25/2005 Core Capability Development Begins All team members will begin working in parallel, on a different architectural component of the system, which form the core components of the final system. The team will be split into two groups. One of which will implement the
LCP_LCO_F04a_T07_V03.0.doc
12
Version date 11/21/2004
Life Cycle Plan
Version 3.0
algorithm to generate relationship and the other will tailor the H3viewer framework. Start to implement the following classes: 1. File input output for importing file from/to database. This will be done using C++ 2. Log data analysis (analyzing item relationships based on user input). This will be done using C++ 3. Produce the graphical user interface to show the item relationship. This will be done using H3viewer and C++ 03/01 03/08/2004 Component development Each team member will work on developing the component of the system according to his/her specific role. Further activity includes implementing the following classes: 1. Format conversion to convert original log data format to match the table schema defined in database. 2. Data storage to store data to log analysis database In addition to these, the previous class implementation is reviewed and continue to be developed. 03/10/2005 Component Integration and Testing. The individual components are integrated together to form the system with initial operational capabilities. Test data will be gathered from client 03/27/2005 Core Capability Inspection & Preparation for Core capability ARB The system will be ready with the initial operational capabilities. The system will be inspected to prepare for the Core Capability ARB. 03/2782005 Core Capability ARB Core Capability features developed and presented to Dr. Boehm, Jewel Ward and possibly some Digital Archive related personnel. The system will be available to be tested with limited capabilities 03/28/2005 Client meeting 4 Possible fourth meeting with client 03/28 04/06/2005 Further Features Development Begin
LCP_LCO_F04a_T07_V03.0.doc
13
Version date 11/21/2004
Life Cycle Plan
Version 3.0
Developers will continue develop full capabilities of the system. All the integrated components are checked and continue to be developed. 04/01/2004 Client Meeting Possible meeting with client to ensure that the development of the system satisfy the requirement. At this point, client gives comment and suggestion. 04/05 04/08/2005 System Inspection & Preparation for TRR The system with the full capabilities mentioned in the SSRD will be ready to be tested and reviewed 04/11/2005 Transition Readiness review (TRR) The final system is reviewed 04/11 04/15/2004 Prepare IOC working set Update/ modify the system according to the review TRR review 04/16/2005 IOC working set IOC working set is ready 05/01/2004 Training Development team gives training to the client/ on user how to use the Digital Archive Usage Data system.
2.2.3
Support Stage
Support stage is undefined at this point.
2.3 Project Deliverables
2.3.1 Engineering Stage
Table 2: Engineering Stage Deliverable 1 Artifact OCD early version 14 Version date 11/21/2004
LCP_LCO_F04a_T07_V03.0.doc
Life Cycle Plan Date Format Exit criteria 9/22/2004 Hardcopy document MBASE Guidelines version 2.4.1
Version 3.0
Table 3: Engineering Stage Deliverable 2 Artifact Date Format Exit criteria Prototype early version 9/27/2004 Hardcopy document MBASE Guidelines version 2.4.1
Table 4: Engineering Stage Deliverable 3 Artifact Date Format Exit criteria LCO Core - OCD 10/1/2004 Electronic document MBASE Guidelines version 2.4.1
Table 5: Engineering Stage Deliverable 4 Artifact Date Format Exit criteria LCO Core - SSRD 10/1/2004 Electronic document MBASE Guidelines version 2.4.1
Table 6: Engineering Stage Deliverable 5
Artifact Date Format Exit criteria
LCO Core - SSAD 10/1/2004 Electronic document MBASE Guidelines version 2.4.1
LCP_LCO_F04a_T07_V03.0.doc
15
Version date 11/21/2004
Life Cycle Plan Table 7: Engineering Stage Deliverable 6 Artifact Date Format Exit criteria LCO Core SSRD 10/1/2004 Electronic document MBASE Guidelines version 2.4.1
Version 3.0
Table 8: Engineering Stage Deliverable 7 Artifact Date Format Exit criteria LCO Draft OCD 10/11/2004 Electronic document MBASE Guidelines version 2.4.1
Table 9: Engineering Stage Deliverable 8 Artifact Date Format Exit criteria LCO Draft SSRD 10/11/2004 Electronic document MBASE Guidelines version 2.4.1
Table 10: Engineering Stage Deliverable 9 Artifact Date Format Exit criteria LCO Draft SSAD 10/11/2004 Electronic document MBASE Guidelines version 2.4.1
Table 11: Engineering Stage Deliverable 10 Artifact Date Format LCO Draft LCP 10/11/2004 Electronic document
LCP_LCO_F04a_T07_V03.0.doc
16
Version date 11/21/2004
Life Cycle Plan Exit criteria MBASE Guidelines version 2.4.1
Version 3.0
Table 12: Engineering Stage Deliverable 11 Artifact Date Format Exit criteria LCO Draft FRP 10/11/2004 Electronic document MBASE Guidelines version 2.4.1
Table 13: Engineering Stage Deliverable 12 Artifact Date Format Exit criteria LCO Final Package 10/25/2004 Electronic document and hardcopy MBASE Guidelines version 2.4.1
Table 14: Engineering Stage Deliverable 13 Artifact Date Format Exit criteria LCA draft OCD 11/22/2004 Electronic document MBASE Guidelines version 2.4.1
Table 15: Engineering Stage Deliverable 14 Artifact Date Format Exit criteria LCA draft SSRD 11/22/2004 Electronic document MBASE Guidelines version 2.4.1
Table 16: Engineering Stage Deliverable 15 Artifact LCA draft SSAD 17 Version date 11/21/2004
LCP_LCO_F04a_T07_V03.0.doc
Life Cycle Plan Date Format Exit criteria 11/22/2004 Electronic document MBASE Guidelines version 2.4.1
Version 3.0
Table 17: Engineering Stage Deliverable 16 Artifact Date Format Exit criteria LCA draft Rose Model 11/22/2004 Electronic document MBASE Guidelines version 2.4.1
Table 18: Engineering Stage Deliverable 17 Artifact Date Format Exit criteria LCA Packages 12/6/2004 Electronic document MBASE Guidelines version 2.4.1
2.3.2
Artifact Date Format
Production Stage
RLCA OCD 02/16/2005 Electronic document MBASE Guidelines version 2.4.1
Table 19: Production Stage deliverable 1
Exit criteria
Table 20: Production Stage deliverable 2 Artifact Date Format Exit criteria RLCA SSAD 02/16/2005 Electronic document MBASE Guidelines version 2.4.1
LCP_LCO_F04a_T07_V03.0.doc
18
Version date 11/21/2004
Life Cycle Plan Table 21: Production Stage deliverable 3 Artifact Date Format Exit criteria RLCA SSRD 02/16/2005 Electronic document MBASE Guidelines version 2.4.1
Version 3.0
Table 22: Production Stage deliverable 4 Artifact Date Format Exit criteria RLCA LCP 02/16/2005 Electronic document MBASE Guidelines version 2.4.1
Table 23: Production Stage deliverable 5 Artifact Date Format Exit criteria RLCA FRD 02/16/2005 Electronic document MBASE Guidelines version 2.4.1
Table 24: Production Stage deliverable 6 Artifact Date Format Exit criteria Core Capability ARB 03/27/2005 Electronic document MBASE Guidelines version 2.4.1
Table 25: Production Stage deliverable 7 Artifact Date IOC Working Set #1 03/27/2005
LCP_LCO_F04a_T07_V03.0.doc
19
Version date 11/21/2004
Life Cycle Plan Format Exit criteria Electronic document System implements core capability.
Version 3.0
Table 26: Production Stage deliverable 8 Artifact Date Format Exit criteria TTR Package 04/08/2005 Electronic document MBASE Guidelines version 2.4.1
Table 27: Production Stage deliverable 9 Artifact Date Format Exit criteria TTR Review 04/11/2005 Electronic document MBASE Guidelines version 2.4.1
Table 28: Production Stage deliverable 10 Artifact Date Format Exit criteria Final IOC Working Set 04/25/2005 System System implements all capabilities.
LCP_LCO_F04a_T07_V03.0.doc
20
Version date 11/21/2004
Life Cycle Plan
Version 3.0
3. Responsibilities
3.1 Stakeholder Responsibilities
Table 29: Stakeholder Responsibilities
Name Role Responsibility
Jewel Ward Johan Bollen Shing-Cheung Chan Fenny Muliawan Hui-Hsien Chi Maxim Krivokon Pei-Han Li Kristine Guevara
Client Client Developer Developer Developer Developer Developer IV & V
Provide information necessary for the development of the system. OCD LCP, Prototype SSAD Team leader, FRD, UML SSRD, Prototype SSAD, UML Ensure that developers correctly execute the initiative Provides log data to be used as analysis Maintain database (update whenever it is necessary) Maintain the system, update whenever necessary.
Hsiao-Han Huang Developer
Jeff Pearson TBD TBD
Data suppliers Database Administrator Maintainer
3.1.1
Stakeholder Representatives
Table 30: Stakeholder representatives Stakeholders USC Digital Resources librarian Authorized Representative Jewel Ward Jeff Pearson
LCP_LCO_F04a_T07_V03.0.doc
21
Version date 11/21/2004
Life Cycle Plan
Version 3.0 Maintainer (TBD) Database Administrator (TBD) Johan Bollen Hui-Hsien Chi Shing-Cheung Chan Fenny Muliawan Hsiao-Han Huang Maxim Krivokon Pei-Han Li Kristine Guevara
Old Dominion University Assistant Professor CS577A Developer team
IV&V
3.1.2
Engineering Stage Responsibilities
Table 31: Engineering stage responsibilities Stakeholder User Client Inception User is acted by client Participate in Winwin negotiation Provide feedback and suggestion on documents such as prototype and LCO Core Provide system requirements Participate in LCO ARB and provide some comment/ suggestions Participate in WinWin negotiation Prepare OCD, SSAD, SSRD, LCP, FRD documents Create and provide prototype for the client especially in the GUI environment showing the user relationship within digital archives Present the top level contact of the LCO documents in LCO ARB n/a n/a Evaluate, validate verify all documents Elaboration User is acted by client Review the prototype design and make suggestion Provide log data for analysis Participate in LCA ARB and provide some comment/ suggestions Make changes on the prototype/document according to the client's suggestion Present the top level contact of the LCA documents in LCA ARB Update prototype whenever necessary n/a n/a Evaluate, validate verify all documents
Developers
Maintainer Database Administrator IV & V
LCP_LCO_F04a_T07_V03.0.doc
22
Version date 11/21/2004
Life Cycle Plan
Version 3.0
3.1.3
Production Stage Responsibilities
Table 32: Production stage responsibilities Stakeholders User Client Construction stage User is acted by client Provide test data Review system performance Transition stage User is acted by client Provide support in transitioning the digital archive usage relationship system to an individual system or a server. Support users, administrators and maintainers Review system performance Developer Refine design Implement and integrate digital archive usage data Perform and support test Plan training to the librarian/users Improve prototype development Data Supplier Maintainer Database Administrator IV & V Provide data to be used for testing n/a n/a Evaluate, validate verify all documents Provide data to be used for the system n/a n/a Evaluate, validate verify all documents Provide development support in transitioning the product Provide training materials for system maintainer and users
3.1.4
Support Stage Responsibilities
Table 33: Support Stage Responsibilities Stake Holder Developer Customer Responsibility None Decide on which evolutionary features are to be implemented or enhanced in the future
LCP_LCO_F04a_T07_V03.0.doc
23
Version date 11/21/2004
Life Cycle Plan Stake Holder User Database administrator Maintainers IV & V Responsibility Updating the system Provide feedback and report about system bugs. Maintain the database. Update it whenever necessary. Maintain the work of the system. Fix any bugs found. Update the system if necessary. Evaluate, validate verify all documents
Version 3.0
3.2 Development Responsibilities
Table 34: Development responsibilities Team Member Chi, Hui-Hsien Chan, Shing-Cheung Krivokon, Maxim Huang, Hsiao-Han Muliawan, Fenny Li, Pei-Han Inception FRD, UML OCD SSRD, Prototype SSAD Prototype, LCP SSAD, UML Elaboration FRD, UML OCD SSRD, Prototype SSAD Prototype, LCP SSAD, UML Construction TBD TBD TBD TBD TBD TBD Transition TBD TBD TBD TBD TBD TBD
LCP_LCO_F04a_T07_V03.0.doc
24
Version date 11/21/2004
Life Cycle Plan
Version 3.0
3.2.1
Development Organization Charts
Figure 2: Development Organization Chart
Chi, Hui-Hsien
Project Manager
Chan, ShingCheung
Concept Engineer
Huang, Hsiao-Han
System Architect
System Analyst
Krivokon, Maxim
Muliawan, Fenny
Prototype Designer
UML Designer
Li, Pei-Han
3.2.2
Staffing
Table 35: Staffing Role Project Manager System Analyst System Architect Designer Developer Effort hour/week/person Inception 20 19 19 19 19 Elaboration 20 19 19 19 19 Construction Transition TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
3.2.3
Training
The following training is conducted by development team through cs577a class: COCOMO learnt how to calculate person-month and effort
LCP_LCO_F04a_T07_V03.0.doc
25
Version date 11/21/2004
Life Cycle Plan
Version 3.0
UML Rose modeling learn how to model the UML graph using Rational Rose software Easy WinWin Learn to determine win-win criteria for both client and developers using Easy WinWin tool. Microsoft Project Learn how to keep track the schedule of a project
In addition to this, one team member is responsible to do a thorough evaluation/study of the COTS product (H3viewer) and thoroughly understand it. He then presents the overview detail to the other developers. All the team members is responsible to do his/her own extended research on it. The developers also individually study the algorithm provided by Dr. Johan Bollen that will be used as the basis of the analysis of the system.
4. Approach
4.1 Monitoring and Control
The following describes how our project manager monitors and controls the flow of the project. Client meeting (http://seacliff.usc.edu/~team7/CMN/CMN.html) Developer team and client hold a meeting whenever it is necessary Weekly meeting Our team holds a meeting at least once a week to ensure that everyone is on the same page. Progress reports (http://seacliff.usc.edu/~team7/PR/PR.html) This is done on a weekly basis. Each person takes turn to do this. Individual effort report Each person submits an effort report weekly. Weekly email / remainder email Weekly email is sent out to ensure that each team member is doing what each person is supposed to be doing DART Possible risks are listed and available for developers and client to be voted to determine which ones are more important and need to be handled first.
4.1.1
Closed Loop Feedback Control
Project manager assigns an individual to keep track of the progress of the project weekly. The assigned individual is responsible to record the meeting agenda of every meeting, generate meeting minutes, create and submit the progress report.
LCP_LCO_F04a_T07_V03.0.doc
26
Version date 11/21/2004
Life Cycle Plan
Version 3.0
Project manager upload all the artifacts to the team website whenever a version of an artifact is completed. All other team members check whether it satisfies the requirement or not. If it does not, he/she will report the defects/ issue to the project manager.
4.1.2
Reviews
The following are the major review conducted for this project. 1. LCO ARB Review of LCO artifacts that include OCD, SSAD, SSRD, LCP and FRD. LCO draft is presented to Prof Boehm, Jewel Ward and cs577 TAs by the developer team. The main focus of this LCO ARB is OCD and Prototype. Through ARB, developers and client ensures that they have common understanding about the requirement and risks of the project. The professor provides some suggestion for improvement for the LCO package. The developers made any changes necessary to the artifacts based on the professor's suggestion. 2. LCA ARB1 Review of LCA draft that includes OCD, SSAD, SSRD, LCP and FRD. LCA draft is presented to Prof Boehm, Jewel Ward and cs577 TAs by the developer team. The main focus of LCA ARB is SSAD and LCP. Through LCA ARB, developers show the client that architecture of the system has been planned and that they have scheduled upcoming tasks. The professor provides some suggestion for improvement for the LCA package. The developers made any changes necessary to the artifacts based on the professor's suggestion. 3. RLCA ARB2 Review of RLCA artifacts to Prof Boehm, Jewel Ward and TAs 4. TRR(Transition Readiness Review) Verify that the system is ready to be used and transition plan is ready. 5. RRR(Release Readiness Review) Verify the successful completion of TTR In addition to the reviews mentioned above, agile review is conducted after an artifact is due to be submitted. Project manager assigns individual(s) to be responsible reviewing certain document(s).
4.1.3
Status Reporting
Each developer submits an effort report on a weekly basis, specifying how many hours he/she contributed for a particular part of the project. Risks are updated on a weekly basis using DART system. An individual appointed by the team leader summarizes the effort LCP_LCO_F04a_T07_V03.0.doc 27 Version date 11/21/2004
Life Cycle Plan
Version 3.0
data and submit it along with the risks summary in the progress report. In addition to this, the progress report also contain the number of issue exists during that particular week. Thus, the weekly progress report contains information on the progress of the project. The documents are available on the team website (http://seacliff.usc.edu/~team7/PR/PR.html).
4.1.4
Risk Monitoring and Control
The following table contains risks that may apply to our project. A more detailed description of each risk can be found in FRD sec.4 Table 36: Top-N Risk Item List (Assuming weekly risk reassessment October 4-10, 2004) Risk Item Current Scalability of visualization clustering algorithm Inappropriately Modify open source component New Usage Log Algorithm Temporary disconnection with client Personnel Loss 1 Weekly Ranking Previous n/a # of weeks 1 Test the system with large data Risk Resolution Strategy
2
n/a
1
Thoroughly study the open source component Frequent communication with Dr. Bollen Email and Phone
3 4
2 4
4 4
5
2
5
Prepare easy-to-understand document for future developer members Training and user manual
User misuse of the proposed system
6
n/a
1
Table 37: Detailed Risk Management RISK-01 Scalability of visualization clustering algorithm
LCP_LCO_F04a_T07_V03.0.doc
28
Version date 11/21/2004
Life Cycle Plan
Version 3.0 The system must be able to handle large amount of data logs. RLCA, IOC Working Set, Core Capability, TTR Developer team Use large data to test visualization clustering algorithm Developers time, no budget
Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources:
RISK-02 Inappropriately modify open source component Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources: Some of the open source component might not be successfully modified to tailor the requirements IOC Working Set, Core Capability, TRR Developer team Thoroughly study the open source component Developers time, no budget
RISK-03 New usage log algorithm Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Few references can be found for the usage analysis algorithm provided by Dr. Bollen. RLCA, IOC Working Set, Core Capability, TTR Developer team Clear communication with Dr.Bollen and thoroughly study his research papers.
LCP_LCO_F04a_T07_V03.0.doc
29
Version date 11/21/2004
Life Cycle Plan Resources:
Version 3.0
Developers time, No budget
RISK-04 Temporary disconnection with client Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources: Client and developer Using email and telephone to communicate with client. No budget, No developers time unable to communicate directly to the client
RISK-05 Personnel Loss Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources: Some developers may leave after December 2004 RLCA, IOC Working Set, Core Capability, TTR Developer team Prepare the documents of the project and give new teammates training that help them quickly get familiar with the system. No budget, developers time
RISK-06 User misuse of the proposed system Objectives: Deliverables and Milestones: User might misunderstood some function of the system IOC Working Set, Core Capability, TRR
LCP_LCO_F04a_T07_V03.0.doc
30
Version date 11/21/2004
Life Cycle Plan Responsibilities and Organization: Approach: Resources:
Version 3.0
Developer team Provide training and develop user manual Some time after the final deliverable is released
4.1.5
Project Communication
The following methods are used by stakeholders to communicate: Client meeting Developer team and client meet whenever it is necessary (once a week). Exception: October and early November. Client will not be in town due to work demand. Communication will take place via email and telephone. Developers weekly meeting Developer team holds a weekly meeting to ensure the project is going on as it is supposed to. Email Email is used to communicate the document progress. Each time an artifact is finish documented, it is sent out via email to all the stakeholders (developers, client and IV&V) to be reviewed. Phone Phone is used whenever necessary.
4.2 Methods, Tools and Facilities
Engineering Stage 1. Easy WinWin tool Negotiation of the win-win criteria for the client and developers. This tool is used during the Inception phase to develop the win criteria for both parties. 2. Microsoft word Documenting artifacts of LCO, LCA, Prototype, etc Used throughout the project cycle for documenting artifacts. 3. Microsoft excel Progress report Used every week to develop summary of weekly progress report to be submitted for cs577 class. 4. Rational Rose UML diagram LCP_LCO_F04a_T07_V03.0.doc 31 Version date 11/21/2004
Life Cycle Plan
Version 3.0
5.
6. 7.
8. 9.
Used throughout the life cycle of the project to model the architecture of the system/organization. USC COCOMO Cost estimation Used early in the project cycle to determine the cost (budget/schedule for both client and developers) associated with this project. Microsoft Project Project tracking and planning Used during the inception phase to plan the activities to do. Microsoft PowerPoint ARB presentation Used before the LCO and LCA ARB milestones to develop slides for presentation. Effort Report System Documenting the man hour each developer contributes for the project. Used weekly to keep track of the man hour contributed to this project. DART List the risk items related to this project Used every week to determine the risks, along with the importance associated with this project.
Production Stage 1. Microsoft word Documenting artifacts of RLCA, Prototype, etc 2. Microsoft project Project tracking and planning 3. Microsoft PowerPoint ARB presentation 4. Rational Rose UML diagram 5. c/c++ Coding the user interface 6. mySQL Database storage for digital image relationship results 7. H3viewer Open source for displaying hyperbolic view of the image relationship. Support Stage Support stage is undefined at this point.
4.3 Configuration Management
LCP_LCO_F04a_T07_V03.0.doc
32
Version date 11/21/2004
Life Cycle Plan
Version 3.0
4.3.1
Product Element Identification
The following table indicates the product elements that are considered as strong baselines. Table 38: Product Element identification Document OCD SSRD SSAD LCP FRD Prototype Quality Assurance Plan Test Plan Test Data Operation Manual and Documentation Transition Plan Release plan Inception X X X X X X Life Cycle Phase Elaboration Construction Transition X X X X X X X X X X X X X X X X X X X X X X X X Support
X
X
Whenever an artifact is updated, the version number is also updated. The version change to the next number if the artifact is one of the milestones from cs577a class. If an artifact is updated based on team discussion or request by client, the ver...