48 Pages

LCP_LCO_F04a_T07_V01.0

Course: CSCI 577, Fall 2009
School: USC
Rating:
 
 
 
 
 

Word Count: 5765

Document Preview

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 October 11, 2004 Life Cycle Plan Version 1.0 Version History Date 10/05/04 Author Fenny Muliawan Version 1.0 Changes made Initial draft LCP_LCO_F04a_T07_V01.0.doc ii Version Date: 10/11/2004 Life Cycle...

Register Now

Unformatted Document Excerpt

Coursehero >> California >> USC >> CSCI 577

Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.

Course Hero has millions of student submitted documents similar to the one below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
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 October 11, 2004 Life Cycle Plan Version 1.0 Version History Date 10/05/04 Author Fenny Muliawan Version 1.0 Changes made Initial draft LCP_LCO_F04a_T07_V01.0.doc ii Version Date: 10/11/2004 Life Cycle Plan Version 1.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 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..................................................................................................................................10 Responsibilities.........................................................................................................................................17 Stakeholder Responsibilities.....................................................................................................................17 Development Responsibilities ..................................................................................................................19 Approach ..................................................................................................................................................21 Monitoring and Control ............................................................................................................................21 Unable to communicate directly with client ................................................................................. 23 LCO, LCO-ARB ........................................................................................................................... 23 Client and developer ..................................................................................................................... 23 Using email and telephone to communicate with client. .............................................................. 23 4.2 4.3 4.4 Methods, Tools and Facilities...................................................................................................................26 Configuration Management......................................................................................................................27 Quality Management ................................................................................................................................29 LCP_LCO_F04a_T07_V01.0.doc iii Version Date: 10/11/2004 Life Cycle Plan 5. 5.1 5.2 6. 6.1 6.2 Version 1.0 Resources..................................................................................................................................................30 Work Breakdown Structure ......................................................................................................................30 Budgets.....................................................................................................................................................32 Appendices ...............................................................................................................................................33 Gantt Chart ...............................................................................................................................................33 Pert Chart..................................................................................................................................................37 LCP_LCO_F04a_T07_V01.0.doc iv Version Date: 10/11/2004 Life Cycle Plan Version 1.0 Table of Tables Table 1: Change Summary ............................................................................................................................................3 Table 2: Engineering Stage Deliverable 1 ..................................................................................................................10 Table 3: Engineering Stage Deliverable 2 ..................................................................................................................11 Table 4: Engineering Stage Deliverable 3 ..................................................................................................................11 Table 5: Engineering Stage Deliverable 4 ..................................................................................................................11 Table 6: Engineering Stage Deliverable 5 ..................................................................................................................11 Table 7: Engineering Stage Deliverable 6 ..................................................................................................................11 Table 8: Engineering Stage Deliverable 7 ..................................................................................................................12 Table 9: Engineering Stage Deliverable 8 ..................................................................................................................12 Table 10: Engineering Stage Deliverable 9 ................................................................................................................12 Table 11: Engineering Stage Deliverable 10...............................................................................................................12 Table 12: Engineering Stage Deliverable 11...............................................................................................................13 Table 13: Engineering Stage Deliverable 12...............................................................................................................13 Table 14: Engineering Stage Deliverable 13...............................................................................................................13 Table 15: Engineering Stage Deliverable 14...............................................................................................................13 Table 16: Engineering Stage Deliverable 15...............................................................................................................13 Table 17: < Engineering Stage Deliverable 16...........................................................................................................14 Table 18: Engineering Stage Deliverable 17...............................................................................................................14 Table 19: Production Stage deliverable 1 ...................................................................................................................14 Table 20: Stage deliverable 2 .....................................................................................................................................14 Table 21: Stage deliverable 3 ......................................................................................................................................15 Table 22: Stage deliverable 4 ......................................................................................................................................15 Table 23: Stage deliverable 5 ......................................................................................................................................15 Table 24: Stage deliverable 6 ......................................................................................................................................15 LCP_LCO_F04a_T07_V01.0.doc v Version Date: 10/11/2004 Life Cycle Plan Table of Contents Table 25: Stage deliverable 7 ......................................................................................................................................15 Table 26: Stage deliverable 8 ......................................................................................................................................16 Table 27: Stage deliverable 9 ......................................................................................................................................16 Table 28: Stage deliverable 10 ....................................................................................................................................16 Table 29: Stakeholder Responsibilities........................................................................................................................17 Table 30: Stakeholder representatvies ........................................................................................................................17 Table 31: Engineering stage responsibilities ..............................................................................................................18 Table 32: Production stage responsibilities ................................................................................................................18 Table 33: Support Stage Responsibilities ....................................................................................................................19 Table 34: Development responsibilities ......................................................................................................................19 Table 35: Staffing ........................................................................................................................................................20 Table 36: Top-N Risk Item List (Assuming weekly risk reassessment October 4-10, 2004)........................................22 Table 37: Detailed Risk Management .........................................................................................................................23 Table 38: Product Element identification....................................................................................................................27 Table 39: Assessment Activities...................................................................................................................................29 LCP_LCO_F04a_T07_V01.0.doc vi Version Date: 10/11/2004 Life Cycle Plan Version 1.0 Table of Figures Figure 1: Phase Milestones and Schedules ...................................................................................................................5 Figure 2: Development Organization Chart................................................................................................................20 Figure 3: Configuration Change flowchart.................................................................................................................28 Figure 4: Gantt chart - Milestones and schedule in engineering stage view 1............................................................33 Figure 5: Gantt chart - Milestones and schedule in engineering stage view 2............................................................34 Figure 6: Gantt chart - Milestones and schedule in production stage view 1 .............................................................35 Figure 7: Gantt chart - Milestones and schedule in production stage view 2 .............................................................36 Figure 8: Pert chart - Milestones and schedule in engineering stage view 1..............................................................37 Figure 9: Pert chart - Milestones and schedule in engineering stage view 2..............................................................38 Figure 10: Pert chart - Milestones and schedule in engineering stage view 3............................................................39 Figure 11: Pert chart - Milestones and schedule in production stage view 1 .............................................................40 Figure 12: Pert chart - Milestones and schedule in production stage view 2 .............................................................41 LCP_LCO_F04a_T07_V01.0.doc vii Version Date: 10/11/2004 Life Cycle Plan Version 1.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 and milestones. It will assist the developers and client in putting their best effort in 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 Open source code will be used as a basis for user interface design Log data will be provided by ISD representative People use current USC Digital Archive System The developer team 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 http://seacliff.usc.edu/~team7/LCO/Prototypes/Prorotype_LCO_F04a_T7_v1_0.doc Fall 2004 CS 577a Project #7 SSRD for LCO http://seacliff.usc.edu/~team7/LCO/SSRD_LCO_F04a_T07.doc LCP_LCO_F04a_T07_V01.0.doc 1 Version date 10/11/2004 Life Cycle Plan Version 1.0 Fall 2004 CS 577a Project #7 SSAD for LCO http://seacliff.usc.edu/~team7/LCO/SSAD_LCO_F04a_T07.doc 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_V01.0.doc 2 Version date 10/11/2004 Life Cycle Plan Version 1.0 1.4 Change Summary Table 1: Change Summary Version 1.0 Changes Made Initial draft. LCP_LCO_F04a_T07_V01.0.doc 3 Version date 10/11/2004 Life Cycle Plan Version 1.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 of 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 Milestone: LCO Package October 25, 2004 b. Elaboration Phase 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 Not Applicable for this project 2.2 Phase Milestones and Schedules The following are the milestones needed to be achieved: LCO (Life Cycle Objectives) LCA (Life Cycle Architecture) RLCA ARB RLCA Package IOC Working Set #1 Core Capability - ARB TTR Package 10/20/2004 12/03/2004 02/16/2005 (anticipated) 02/21/2005 (anticipated) 03/27/2005 (anticipated) 03/27/2005 (anticipated) 04/08/2005 (anticipated) LCP_LCO_F04a_T07_V01.0.doc 4 Version date 10/11/2004 Life Cycle Plan TTR Review IOC Working Set RRR (Release Readiness Review) Version 1.0 04/11/2005 (anticipated) 04/25/2005 (anticipated) 05/04/2005 (anticipated) The following figure shows the milestones of the project date that the document needed to be completed: Figure 1: Phase Milestones and Schedules RLCA 04/21/2005 LCA ARB: 11/22/2004 WinWin, Prototype, early OCD: 9/22/2004 LCO ARB: 10/1/2004 Elaborati on. Iteration #2 CCR ARB 03/27/2005 TRR 04/04/2005 Construc tion Iteration #1 Construc tion Iteration #2 Transition Phase TBD Inception Iteration Preliminary Iteration Elaborati on Iteration #1 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. 9/10/2004 Team formed Six students from cs577A class form a team to work together for the project. LCP_LCO_F04a_T07_V01.0.doc 5 Version date 10/11/2004 Life Cycle Plan Version 1.0 9/13/2004 Client visit during class Client visits the developer team during class session and describe the background of the project 9/15/2004 First official client meeting First meeting with client is held. Client presents brief description about the project and requirement. 9/16/2004 Client meeting 2 Developer team and client hold a meeting to get detailed description about the project. 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. 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 LCP_LCO_F04a_T07_V01.0.doc 6 Version date 10/11/2004 Life Cycle Plan Version 1.0 Developer team and client hold a third meeting to brainstorm and negotiate the win situation for both parties. 9/25/2004 Win-win negotiation final session Developer team and client hold a final meeting to brainstorm and negotiate the win situation for both parties. 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 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. 10/1/2004 LCO Core OCD modified version (if available), SSAD and SSRD early version. 10/8/2004 Developer team meeting 3 The developer team meets to discuss LCO Core document review. 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 10/11/2004 LCO draft OCD, SSAD, SSRD modified version (if available) LCP_LCO_F04a_T07_V01.0.doc 7 Version date 10/11/2004 Life Cycle Plan LCP, FRP early version. 10/22/2004 LCO ARB Review of LCO document 1022/2004 Developer team meeting4 The developer team meets to discuss final LCO document. 10/25/2004 LCO Package Final version of OCD, SSAD, SSRD, LCP and FRP. 10/30/2004 Developer team meeting 5 The developer team meets to discuss LCA document. 11/07/2004 Developer team meeting 6 The developer team meets to discuss LCA draft. 11/22/2004 LCA draft Life Cycle Architecture document Version 1.0 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. LCP_LCO_F04a_T07_V01.0.doc 8 Version date 10/11/2004 Life Cycle Plan Version 1.0 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/25/2005 Client meeting 1 Possible meeting with client 01/28/2005 LCA Documents Reviewed. The developer team reviews the artifacts from the LCA Package and evaluates them. 02/10/2005 Client meeting 2 Possible second meeting with client 02/16/2005 LCA ARB LCA documents draft is ready. 02/21/2005 RLCA ARB The team will produce an updated the LCA documents, if applicable. 02/22/2005 Client meeting 3 Possible third meeting with client 02/25/2005 Core Capability Development Begins All team members will be working in parallel, on a different architectural component of the system, which form the core components of the final system. 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/27/2005 LCP_LCO_F04a_T07_V01.0.doc 9 Version date 10/11/2004 Life Cycle Plan Core Capability ARB Core Capability features developed The system will be available to be tested with limited capabilities 03/28/2005 Client meeting 4 Possible fourth meeting with client 03/28/2005 Further Features Development Begin Developers will continue develop full capabilities of the system. Version 1.0 04/08/2005 System Inspection & Preparation for TRR The system with full the capabilities mentioned in the SSRD will be ready to be tested and reviewed 04/11/2005 Transition Readiness review (IOC) The final system is reviewed 04/11/2005 IOC working set IOC working set is ready 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 Date Format Exit criteria OCD early version 9/22/2004 Hardcopy document MBASE Guidelines version 2.4.1 LCP_LCO_F04a_T07_V01.0.doc 10 Version date 10/11/2004 Life Cycle Plan Version 1.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 Table 7: Engineering Stage Deliverable 6 Artifact LCO Core SSRD LCP_LCO_F04a_T07_V01.0.doc 11 Version date 10/11/2004 Life Cycle Plan Version 1.0 Date Format Exit criteria 10/1/2004 Electronic document MBASE Guidelines version 2.4.1 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 Exit criteria LCO Draft LCP 10/11/2004 Electronic document MBASE Guidelines version 2.4.1 LCP_LCO_F04a_T07_V01.0.doc 12 Version date 10/11/2004 Life Cycle Plan 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 Version 1.0 Table 13: Engineering Stage Deliverable 12 Artifact Date Format Exit criteria LCO Final Package 10/25/2004 Electronic document 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 Date Format LCA draft SSAD 11/22/2004 Electronic document LCP_LCO_F04a_T07_V01.0.doc 13 Version date 10/11/2004 Life Cycle Plan Version 1.0 Exit criteria MBASE Guidelines version 2.4.1 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 Table 19: Production Stage deliverable 1 MBASE Guidelines version 2.4.1 Exit criteria Production Stage Deliverable Table 20: 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_V01.0.doc 14 Version date 10/11/2004 Life Cycle Plan Table 21: Stage deliverable 3 Artifact Date Format Exit criteria RLCA - SSRD 02/16/2005 Electronic document MBASE Guidelines version 2.4.1 Version 1.0 Table 22: Stage deliverable 4 Artifact Date Format Exit criteria RLCA - LCP 02/16/2005 Electronic document MBASE Guidelines version 2.4.1 Table 23: Stage deliverable 5 Artifact Date Format Exit criteria RLCA - FRD 02/16/2005 Electronic document MBASE Guidelines version 2.4.1 Table 24: Stage deliverable 6 Artifact Date Format Exit criteria Core Capability ARB 03/27/2005 Electronic document MBASE Guidelines version 2.4.1 Table 25: Stage deliverable 7 Artifact Date IOC Working Set #1 03/27/2005 LCP_LCO_F04a_T07_V01.0.doc 15 Version date 10/11/2004 Life Cycle Plan Version 1.0 Format Exit criteria Electronic document System implements core capability. Table 26: Stage deliverable 8 Artifact Date Format Exit criteria TTR Package 04/08/2005 Electronic document MBASE Guidelines version 2.4.1 Table 27: Stage deliverable 9 Artifact Date Format Exit criteria TTR Review 04/11/2005 Electronic document MBASE Guidelines version 2.4.1 Table 28: Stage deliverable 10 Artifact Date Format Exit criteria Final IOC Working Set 04/25/2005 System System implements all capabilities. LCP_LCO_F04a_T07_V01.0.doc 16 Version date 10/11/2004 Life Cycle Plan Version 1.0 3. Responsibilities 3.1 Stakeholder Responsibilities Table 29: Stakeholder Responsibilities Name Jewel Ward Role Product Customer Responsibility Provide information necessary for the development of the system. Johan Bollen Shing-Cheung Chan Fenny Muliawan Hsiao-Han Huang Hui-Hsien Chi Maxim Krivokon Pei Li Kristine Guevara Jeff Pearson TBD Product Customer Developer Developer Developer Developer Developer Developer IV & V OCD LCP, Prototype SSAD Team leader, FRD, UML SSRD, Prototype SSAD, UML Ensure that developers correctly execute the initiative Data suppliers Maintainers Provides log data to be used as analysis Maintain the system 3.1.1 Stakeholder Representatives Table 30: Stakeholder representatives Stakeholders USC Digital Resources librarian Old Dominion University Research Professor CS577A Developer team Authorized Representative Jewel Ward Johan Bollen Hui-Hsien Chi Shing-Cheung Chan Fenny Muliawan Hsiao-Han Huang LCP_LCO_F04a_T07_V01.0.doc 17 Version date 10/11/2004 Life Cycle Plan Maxim Krivokon Pei-Han Li Kristin Guevara Version 1.0 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 WinWin negotiation Prepare OCD, SSAD, SSRD document Create and provide prototype for the client Elaboration User is acted by client Review the prototype design and make suggestion Provide log data Make changes on the prototype/document according to the client's suggestion Developers 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 product Support users, administrators and maintainers Review system performance Developer Refine design Implement and integrate product Perform and support test Plan training Improve prototype development Provide development support in transitioning the product Provide training materials for system maintainer and users LCP_LCO_F04a_T07_V01.0.doc 18 Version date 10/11/2004 Life Cycle Plan Version 1.0 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 Updating the system Provide feedback and report about system bugs. User 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_V01.0.doc 19 Version date 10/11/2004 Life Cycle Plan Version 1.0 3.2.1 Development Organization Charts Figure 2: Development Organization Chart Project Manager Chi, Hui-Hsien Concept Engineer Chan, ShingCheung System Architect Huang, Hsiao-Han System Analyst Krivokon, Maxim Prototype Designer Muliawan, Fenny 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 18 15 15 15 15 Elaboration 18 15 15 15 15 Construction Transition TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD 3.2.3 Training The following training is conducted by development team: COCOMO UML Rose modeling LCP_LCO_F04a_T07_V01.0.doc 20 Version date 10/11/2004 Life Cycle Plan Easy WinWin Microsoft project Version 1.0 4. Approach 4.1 Monitoring and Control The following describes how our team monitors and controls the flow of the project. Client meeting 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 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 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. 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. 2. LCA ARB1 Review of LCA package. LCP_LCO_F04a_T07_V01.0.doc 21 Version date 10/11/2004 Life Cycle Plan Version 1.0 3. RLCA ARB2 Review of RLCA artifacts 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 man 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 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. 4.1.4 Risk Monitoring and Control Table 36: Top-N Risk Item List (Assuming weekly risk reassessment October 4-10, 2004) Risk Item Current Client unavailable for 1.5 months H3 viewer library/tool difficult to tailor 1 2 Weekly Ranking Previous 1 n/a # of weeks 2 1 Using email and telephone to communicate with client. By the end of this semester we should demonstrate a prototype incorporating some of the above features in the tool. That way we can evaluate efforts necessary to implement them all, and make a decision on this Version date 10/11/2004 Risk Resolution Strategy LCP_LCO_F04a_T07_V01.0.doc 22 Life Cycle Plan COTS Viewer portability problem 3 n/a 1 Version 1.0 Demonstrate a prototype compliable at least on two platforms of choice (picked by the client). Suggested Windows, Linux (FreeBSD) Read document to get familiar with the open source. Reuse existing visualization libraries/tools. The emphasis of our project is on datamining, therefore the visualization effort should be minimized Prepare the documents of the project and give new teammates training that help them quickly get familiar with the system. Unfamiliar open source library Complex GUI 4 5 n/a 2 1 1 Personnel Loss 6 4 3 Table 37: Detailed Risk Management RiSK-01 Client unavailable for 1.5 months Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources: Unable to communicate directly with client LCO, LCO-ARB Client and developer Using email and telephone to communicate with client. No budget RISK-02 H3 viewer library/tool difficult to tailor LCP_LCO_F04a_T07_V01.0.doc 23 Version date 10/11/2004 Life Cycle Plan Version 1.0 Objectives: Coding will be difficult Deliverables and Milestones: Responsibilities and Organization: RLCA, IOC Working Set, Core Capability, TTR Developer team By the end of this semester we should demonstrate a prototype incorporating some of the above features in the tool. That way we can evaluate efforts necessary to implement them all, and make a decision on this COTS Approach: Resources: No budget RISK-03 Viewer portability problem Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources: Coding will be difficult RLCA, IOC Working Set, Core Capability, TTR Developer team Developer team No budget RISK-04 Unfamiliar open source library Objectives: Deliverables and Milestones: Responsibilities and Organization: Coding will be difficult RLCA, IOC Working Set, Core Capability, TTR Developer team LCP_LCO_F04a_T07_V01.0.doc 24 Version date 10/11/2004 Life Cycle Plan Version 1.0 Approach: Resources: Read document to get familiar with the open source No budget RISK-05 Complex GUI Objectives: Deliverables and Milestones: Responsibilities and Organization: Approach: Resources: Coding will be difficult RLCA, IOC Working Set, Core Capability, TTR Developer team Reuse existing visualization libraries/tools. The emphasis of our project is on data-mining, therefore the visualization effort should be minimized No budget RISK-06 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 LCP_LCO_F04a_T07_V01.0.doc 25 Version date 10/11/2004 Life Cycle Plan Version 1.0 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 ...

Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more. Course Hero has millions of course specific materials providing students with the best way to expand their education.

Below is a small sample set of documents:

USC - CSCI - 577
Life Cycle Plan (LCP)Data Mining of Digital Library Usage DataTeam 7 Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UMLNovember 21, 2004Life Cycle PlanVersion 3
USC - CSCI - 577
Operational Concept Description (OCD)Data Mining of Digital Library Usage DataTeam #7Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UML&lt;October 25, 2004&gt;OCD_LCO
USC - CSCI - 577
Feasibility Rationale Description (FRD)Data Mining of Digital Library Usage DataTeam #7Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UML&lt;October 25, 2004&gt;FRD_L
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Data Mining of Digital Library Usage DataTeam #7Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UML&lt;October 11, 2
USC - CSCI - 577
Operational Concept Description (OCD)Data Mining of Digital Library Usage DataTeam #7Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UML&lt;November 22, 2004&gt;OCD_LC
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Data Mining of Digital Library Usage DataTeam #7Hui-Hsien Chi FRD Shing-Cheung Chan OCD Maxim Krivokon SSRD Hsiao-Han Huang SSAD Fenny Muliawan LCP/Prototype Pei-Han Li - UML&lt;October 24, 2
USC - CSCI - 577
PROTOTYPEVersion 1.1Data Mining of Digital Library Usage DataTeam 7 Shing-Cheung Chan Maxim Krivokon Hui-Hsien Chi Hsiao-Han Huang Maxim Krivokon Pei-Han Li Fenny Muliawan1. Prototyping1.1 ObjectivesThe purpose of our prototype is to help vi
USC - CSCI - 577
PROTOTYPEVersion 1.2Data Mining of Digital Library Usage DataTeam 7 Shing-Cheung Chan Maxim Krivokon Hui-Hsien Chi Hsiao-Han Huang Maxim Krivokon Pei-Han Li Fenny Muliawan1. Prototyping1.1 ObjectivesThe purpose of our prototype is to demonst
USC - CSCI - 577
USC - CSCI - 577
System and Software Architecture Description (SSAD)NFS DatabaseTeam No 11TEAM MEMBERS:PROJECT MANAGER: Muhammad Amer PROTOTYPE: Muhammad Zaki ARCHITECT: Salman Rafique PLAN: Jacob Everist REQUIREMENT: Ran Wang CONCEPT: Limei Wang11/21/04SS
USC - CSCI - 577
TEAM #14Period: 09/20/04 09/26/04WEEKLY STATUS REPORTTeam #14 Project: STS Database Evaluation Week #2 Progress The following 5 tasks were accomplished in the week ending 09/26/04 Meeting with our client - Dr. Richard Hurvitz to show him a to
USC - CSCI - 577
TEAM #13Period: 11/25/04-12/1/04Progress: -During this past week we focused on the presentation for the LCA ARB. The ARB included some major revisions on our documents plus the addition of three more documents: the Test Plan, the Iteration Plan a
USC - CSCI - 577
Easy Win-Win Negotiation ReportAda to AADL TranslatorTeam 18December 05, 2004Easy Win-Win Negotiation Report _ContentsParticipants Version History Agenda 4. Review and Expand Negotiation Topics 8. Classify Win Conditions By Priority 11. Neg
USC - CSCI - 577
Oct. 19, 2004 Internal Meeting by Jacob Everist Present: Limei Wang, Ran Wang, Jacob Everist, Mohammed Ali Amer, Zaki Murtaza, Salman Rafique Wednesday 4pm-6pm at Salman's apartment 1. Reviewed OCD document for Nicosia's IV&amp;V concerns 2. Reviewed SSA
USC - CSCI - 577
Win conditions:MLR - may be later IWH - imp with hurdles LHF - low hanging fruit1. Project Requirements 1.1 [W3] [IWH] Design and Analysis MUST be completed within 10 calendar weeks in order to meet course deadlines. 1.2 [W4] [MLR] Use of Third pa
USC - CSCI - 577
TEAM #14Period: 12/01/04-12/8/04WEEKLY STATUS REPORT Team #14 Project: STS Database Evaluation Week #12 Progress The following 4 tasks were accomplished in the week ending 11/30/04 As per plan we prepared the final slides for the LCA ARB We incor
USC - CSCI - 577
1. Data Migration a. Current Hypercard database can be exported to a flat text file (tab delimited) b. We only have to do this one time to import the data into the RDBMS 2. Deployment a. Leverage client's existing hardware Mac G4, 60gig HD b. Try to
USC - CSCI - 577
Online Bibliographies on Chinese Religions in Western LanguagesVersion 2.3Life Cycle Plan (LCP)Online Bibliographies of Chinese Religion in Western LanguagesTeam 3 Stephan Pak: Project Manager Atul Vij: Requirements Rukmani khajuria: Operatio
USC - ITP - 320
Logistics Overview 2nd Annual Curriculum ConferenceHeather Czech (heather.czech@SAP-age.de) SAP America March 17, 1999R SAP AGTopicsl Logistics Applications l Logistics Business Processes l ReportingR SAP AGThe R/3 Integration ModelSD
N.C. State - P - 254
Dietaryfibre in apple cultivars and pectins. However, lignin is not included in the NSP fraction. Also the recovery of monosaccharides from polysaccharidesare usually less than 100% due to loss during hydrolysis. NSP can be considered to be a very co
N.C. State - ARE - 309
ARE 309Exam IInstructions: When you complete your exam please fold it in half along the long axis and place your name on the outside. Your name should appear nowhere else on your paper. You may not use notes or any other outside assistance on thi
N.C. State - ARE - 309
ARE 309Exam I IMonday, March 26, 2001Instructions: You may not use notes or any other outside assistance on this examination, except for one 3x5 card of handwritten notes. Put all answers on the scantron sheet. Keep the exam booklet. 1. CERCLA
N.C. State - ARE - 309
EXAMINATION IIMarch 2003Distance EducationARE 309Instructions: You may use one 3x5 card of notes, handwritten, front and back. No other notes or books are permitted. All answers must be placed on the scantron sheet using a number 2 pencil. If
USC - FBE - 552
Windows of ReleaseThis is an International BusinessuThe film business has always been international In silent era we imported from FranceuUS Industry has a big advantage leading BO share in most markets big domestic market no subtitles
USC - FBE - 552
SportsWhere have you gone Joe DiMaggioPerfect Competition?uProfessional Sports Poses a Few Interesting Problems Are the Teams in the League a Single Entity, or Are They Competitors, or Some Combination? What Is the Relation of Professional S
USC - FBE - 552
Incentive Contracts in EntertainmentIs it Gross to Get Net?SummaryuOverview of Incentive Contracts in General What Do Incentive Contracts in the Motion Picture Business Look Like How Can We Explain Incentive Contracts in the Motion Picture Bus
USC - FBE - 552
THE NEW YORK TIMES, November 27, 1977Somebody Must Put a Lid on BudgetsBy VINCENT CANBYFor weeks before the first public showings of Steven Spielberg new science-fiction s spectacle, Close Encounters of the Third Kind, the common stock of Columb
USC - FBE - 552
T he m oti pi r stu d i on ctu e oHi y &amp; Econ i stor om csA b r ef d escri onof the pr i pti ocessu n n ed fora b ou t a cen r cha g tu yu3 sta g es i pr u cti n od on P od u cti r onvG etti g from i i a li ea to the m a ster pr n n nti d
USC - FBE - 552
Macro-ViewRecreation Expenditure DataThe data is in the appendix to Vogel that I asked you to look at. u Try to get a feel for what has been happening to leisure expenditures over timeu relative to all consumption within various classes2In
USC - FBE - 552
USC - FBE - 552
New York Times Dec. 29, 1997Managing a Megaplex Takes Mega-EffortBy CONSTANCE L. HAYSSOUTHFIELD, Mich. - If there is ever a film version of Phil Urrutia going about his job, it s might come out as a cross between Caddyshack and one of any of the
USC - FBE - 552
May 25, 1998Let Make a Deal: The New Fall Schedule sNew York TimesBy BILL CARTERComing soon to a television channel near you: the best shows the networks can find - as long as the deal is right. The new fall television season was announced last
USC - CHEM - 322
USC - CHEM - 322
USC - CHEM - 322
USC - AME - 514
Mesoscale Power Generation by a Catalytic Combustor using Electrosprayed Liquid Hydrocarbons Dimitrios C. Kyritsis+, Ismael Guerrero-Arias+, Subir Roychoudhury and Alessandro Gomez+* Yale Center for Combustion Studies Department of Mechanical Enginee
CSU Bakersfield - ECON - 312
ECON 312Dr. GrammyGrowth and Structural Change1. Measuring Production and Growth!Gross National Product (GNP): Total market value of all final goods produced by citizens of the country Gross Domestic Product (GDP): Total market value of all f
CSU Bakersfield - ECON - 312
California State University, Bakersfield Economies of the Middle East &amp; North Africa (ECON 312)Dr. Abbas P. Grammy Phone: (661) 664-2466 Fax: (661) 664-2049 E-mail: agrammy@csub.edu Website: www.csub.edu/~agrammy Office: BPA Offices- Room 261 Office
CSU Bakersfield - ECON - 202
California State University, Bakersfield Essentials of Macroeconomics (AECO 202)Abbas Grammy, Ph.D., CU-Boulder Department of Applied Economics Office: BDC Room 232 E-mail: agrammy@csub.edu Telephone: 661-654-2466 Professor of Economics School of Bu
CSU Bakersfield - ECON - 420
California State University, Bakersfield Department of Economics Introduction to Econometrics (ECON 420)Instructor Information Abbas Grammy, Ph.D., University of Colorado, Boulder, May 1982 Professor of Economics School of Business and Public Admini
CSU Bakersfield - ECON - 302
California State University, Bakersfield Intermediate Macroeconomics (ECON 302)Abbas P. Grammy Phone: (661) 664-2466 Fax: (661) 664-2049 Office: BPA Offices Room 261 Office hours: MWF 1-2 p.m. E-mail: agrammy@csub.eduCourse Description Keynesian a
CSU Bakersfield - ECON - 309
California State University, Bakersfield Economy and Society (Economics 309)Dr. Abbas Grammy Office: BPA Building, Room 261 Phone: 664-2466 Fax: 664-2049 E-mail: agrammy@csub.edu Website : www.csub.edu/~agrammy Course Description: Application of eco
CSU Bakersfield - ADM - 520
California State University, Bakersfield Master of Science in Administration Quantitative Decision Making (ADM 520 online; 5 quarter units)Instructor Information Abbas Grammy, Ph.D., University of Colorado, Boulder, May 1982 Professor of Economics S
CSU Bakersfield - ECON - 312
Dr. GrammyEcon 312International and Intra-Regional TradeTheory of International Trade External trade is said to be the engine of development. Trade generates foreign exchange to finance industrialization. Historically, the Middle East has been k
CSU Bakersfield - ECON - 410
California State University, Bakersfield International Economic Development (ECON 410)Instructor Information Abbas Grammy, Ph.D., University of Colorado, Boulder Professor of Economics School of Business and Public Administration Office: BDC 249 (en
CSU Bakersfield - ECON - 312
Dr. GrammyDr. GrammyHuman Capital FormationEducation Human capital formation is central to economic development. It has been the major factor in explaining rapid and sustained output growth. Human capital formation improves the quality and produ
CSU Bakersfield - ECON - 312
Dr. GrammyEcon 312Role of the StateThe role of government has often been poorly defined in the ME &amp; NA, partly because it has tendency to change systematically every time political leaders and decision makers change as they often do with the use
CSU Bakersfield - ECON - 312
Oil and DevelopmentThe Oil Rush: Of the world proven petroleum reserves, the ME &amp; NA account for nearly 70 percent. The leading nations in the region are Saudi Arabia, Iraq, Kuwait, UAE, and Iran. Oil exports vary across countries, depending on prod
CSU Bakersfield - ECON - 312
Dr. GrammyEconomics 312Introduction to Economic DevelopmentEconomic Development Definition: Growth plus Change ! Growth: a long-term and sustained increase in the level of per capita real income ! Change: an overall improvement in institutions a
CSU Bakersfield - ECON - 312
Dr. GrammyEcon 312Regional CharacteristicsRegional Identification: Geography: The ME &amp; NA consists of 22 nations: 18 Arab and 4 non-Arab countries. They are Algeria, Bahrain, Cyprus, Egypt, Iran, Iraq, Israel, Jordan, Kuwait, Lebanon, Libya, Mor
CSU Bakersfield - ECON - 312
Dr. GrammyEcon 312Urbanization and Rural-Urban MigrationEconomic development will take place as a result of structural transformation from a rural-based agrarian to an urban-based industrial economy. Urbanization rate and GDP per capita are posi
CSU Bakersfield - ECON - 312
Dr. GrammyEcon 312Population GrowthThe Demographic Transition: Demographic transition is as a shift from a stable population with high birth and death rates to low birth and death rates. The transition phase consists of four stages. Stage I: hig
USC - CSCI - 577
Life Cycle Plan (LCP)Version 3.0Life Cycle Plan (LCP)Team # 11 Web-based Service for TPC FoundationBrijen Ved Kevin Sanghavi Natasha Julka Sheena Singh Prathima Naidu Ankitsinh Rana Ely Lerner Pat MeansProject Manager Software Architect Pro
USC - CSCI - 577
Life Cycle Plan (LCP)Version 2.0Life Cycle Plan (LCP)Team # 11 Web-based Service for TPC FoundationBrijen Ved Kevin Sanghavi Natasha Julka Sheena Singh Prathima Naidu Ankitsinh Rana Ely Lerner Pat MeansProject Manager Software Architect Pro
USC - CSCI - 577
Operational Concept Description (OCD)Version 3.1Operational Concept Description (OCD)Team # 11 Web-based Service for TPC FoundationBrijen Ved Kevin Sanghavi Natasha Julka Sheena Singh Prathima Naidu Ankitsinh Rana Ely Lerner Patricia MeansPr
USC - CSCI - 577
COTS Assessment Process (CAP)Version 1.1COTS Assessment Process (CAP)Team # 11 Web-based Service for TPC FoundationBrijen Ved Kevin Sanghavi Natasha Julka Sheena Singh Prathima Naidu Ankitsinh Rana Ely Lerner Pat MeansProject Manager Softwa
CSU Bakersfield - CS - 223
StacksTuesday, September 25, 2007 11:00 PM7.1 Introduction stacks are last-in, first-out (LIFO) can only access top element no traversal operations Standard operations construct empty stack check if stack is empty push - add item to stack pop - r
CSU Bakersfield - CS - 223
Thinking CriticallyThursday, September 13, 2007 1:12 PMOptimization &amp; Algorithm Analysis (Ch 1.2, 10.4) Concerned with: space utilization (eg memory) time efficiency Usually optimize for just one of the two usually a tradeoff between space &amp; time
CSU Bakersfield - CS - 223
Standard Template Library9.3 &quot;Quick Peek&quot; STL history 1990s Alex Stepanov &amp; Meng Lee of HP Labs 1994 ANSI/IS0 standard Components Container class templates Iterators Algorithm templatesWednesday, October 10, 2007 10:09 AMIterators are interface
CSU Bakersfield - CS - 223
Graphs &amp; DigraphsTuesday, November 06, 2007 10:34 PM16.1 Directed Graphs (digraphs) like a tree but w/ no root node &amp; no guarantee of paths between nodes consists of: nodes/vertices - a set of elements directed edges/arcs - a set of connections b