Life Cycle Plan (LCP)

Transcription

1 Using Social Media/Mobile Devices to Bridge the Achievement Gap Team 2 Ying Yang, Project Manager/Life Cycle Planner Tianyin Zhou, Life Cycle Planner/Prototyper Ying Li, Operational Concept Engineer/Requirement Engineer Wei Tan, System Architect/Prototyper Iris Buri, Feasibility Analyst/Requirement Engineer Charles Muckenthaler: IIV & V 10/14/11

2 Version 1.2 Version History Date Author Version Changes made Rationale 9/30/11 Tianyin Zhou 1.0 Created the LCP The initial draft of LCP 10/7/11 Ying Yang 1.1 Add new information to section 1 and modified section /14 Tianyin Zhou 1.2 Add new information to Section 1.3, 2.2.2, 3.1, 3.2, 4,5 Specify purpose of LCP and modify roles and skills LCP_FCP_F11a_T02_V1.2.doc Version Date: 10/14/11

3 Version 1.2 Table of Contents Life Cycle Plan (LCP)...i Version History... ii Table of Contents... iii Table of Tables...iv Table of Figures... v 1. Introduction Purpose of the LCP Status of the LCP Assumptions Milestones and Products Overall Strategy Project Deliverables Responsibilities Project-specific stakeholder s responsibilities Responsibilities by Phase Skills Approach Monitoring and Control Methods, Tools and Facilities Resources LCP_FCP_F11a_T02_V1.2.doc iii Version Date: 10/14/11

4 Version 1.2 Table of Tables Table 1: Artifacts Deliverables in Exploration Phase... 3 Table 2: Artifact deliverable in Exploration Phase... Error! Bookmark not defined. Table 3: Artifact deliverable in Valuation Phase... 4 Table 4: Artifact deliverable in Foundations Phase... 5 Table 5: Artifact deliverable in Development Phase... 6 Table 6: Stakeholder's Responsibilities in each phase... 7 Table 7: COCOMOII Scale Driver Table 8: COCOMOII Cost Driver LCP_FCP_F11a_T02_V1.2.doc Version Date: 10/14/11

5 Version 1.2 Table of Figures No table of figures entries found. LCP_FCP_F11a_T02_V1.2.doc Version Date: 10/14/11

6 1. Introduction 1.1 Purpose of the LCP Life Cycle Plan is an artifact that records the plans and processes for the project. It addresses the answers to common questions. The questions included: why? Whereas? What? When? Who? Where? How and how much? Doing LCP will benefits the whole project. As the project goes, LCP keeps the project going forward and makes sure the artifacts are documented in each phase. 1.2 Status of the LCP All information in this version is currently at FCP. The changes from last version are: Add new assumptions to section 1.3 Finish the Valuation Phase table Add information to Section 3, Add information to Section 4, Approach Add information to Section 5, Resource 1.3 Assumptions The duration of the project is 12 weeks, which is the 12 weeks of fall semester Clients will stay in contact and are willing to meet for at least 4 times. Clients will provide certain funds for selecting NDIs. Team meets 3 times a week and is high-coherent. The ICM-Sw Guidelines will be followed by all out team members. Client has clearly state the requirements of the project. LCP_FCP_F11a_T02_V1.2.doc 1 Version Date: 10/14/11

7 2. Milestones and Products 2.1 Overall Strategy By using Koolman Process Decision Driver, we figured out that our project should follow NDI- Intensive Process. Figure 1 shows the reasoning behind this decision: Figure 1: Case Process Selection Result LCP_FCP_F11a_T02_V1.2.doc 2 Version Date: 10/14/11

8 Exploration phase Duration: 09/21/11-9/21/11 Concept: Meanwhile team members and clients analyze current system, assess and plans to mitigate riskes, identify responsibilities and skills Deliverables: Valuation Commitment Package Milestone: Valuation Commitment Review Strategy: One Incremental Commitment Cycle Valuation phase Duration: 09/22/11-10/07/11 Concept: Meanwhile team members identify OC&P, define operational concept, negotiate win conditions, explore alternatives, plan and manage project, acquire NDI or NCS Components, Define Architecture and prototyping. Deliverables: Valuation Commitment Package Milestone: Valuation Commitment Review Strategy: One Incremental Commitment Cycle Foundation phase Duration: 10/08/11-11/10/11 Concept: Meanwhile team members assess project status, prototyping, plan and manage project, manage project quality and analyze NDI interoperability. Deliverables: Valuation Commitment Package Milestone: Valuation Commitment Review Strategy: One Incremental Commitment Cycle 2.2 Project Deliverables << Identify project deliverables in each phase and its due date, format, and medium>> Exploration Phase << The following is an example of deliverables in Exploration phase.>> Table 1: Artifacts Deliverables in Exploration Phase Artifact Due date Format Medium Client Interaction Report 9/17/2006.doc,.pdf Soft copy Valuation Commitment Package Operational Concept Description (OCD) Early Section Life Cycle Plan (LCP) Early Section 09/18/2006.doc,.pdf Soft copy LCP_FCP_F11a_T02_V1.2.doc 3 Version Date: 10/14/11

9 Feasibility Evidence Description (FED) Early Section Evaluation of Valuation 09/27/2006.xls Soft copy Commitment Package Project Effort Every Monday Text ER system Project Plan Every Wednesday.mpp,.pdf Soft copy Progress Report Every Wednesday.xls Soft copy Risk Analysis Every Wednesday Text DART system Valuation Phase Table 2: Artifact deliverable in Valuation Phase Artifact Due date Format Medium Initial Prototype 9/28.doc,.pdf Soft copy Wikiwinwin Report 10/5.html Soft copy Wikiwinwin Report Discussion 10/6.doc Soft copy Core Foundations Commitment Package 10/7.doc,.pdf Soft copy Operational Concept Description(OCD) Prototypes (PRO) Updated prototypes System and Software Requirement Definition (SSRD) System and Architecture Description (SSAD) early section Life Cycle Plan (LCP) updated Feasibility Evidence Description (FED) updated Supporting Information Document(SID) Evaluation of Core Foundations Soft copy Commitment Package Draft Foundations Commitment Package Operational Concept Description (OCD) Prototypes (PRO) Updated System and Software Requirement Definition (SSRD) System Software Architecture (SSAD) early section Life Cycle Plan (LCP) Updated Feasibility Evidence Description (FED) updated 10/14 Soft copy LCP_FCP_F11a_T02_V1.2.doc 4 Version Date: 10/14/11

10 Prototypes(PRO) Foundations Phase Table 3: Artifact deliverable in Foundations Phase Artifact Due date Format Medium <artifact name> <due date> <format type:.doc,.pdf> <Medium type: hard copy, soft copy> LCP_FCP_F11a_T02_V1.2.doc 5 Version Date: 10/14/11

11 2.2.4 Development Phase Table 4: Artifact deliverable in Development Phase Artifact Due date Format Medium <artifact name> <due date> <format type:.doc,.pdf> <Medium type: hard copy, soft copy> LCP_FCP_F11a_T02_V1.2.doc 6 Version Date: 10/14/11

12 3. Responsibilities 3.1 Project-specific stakeholder s responsibilities Role All stakeholders Client Developer/Builder IIV & V Communicate with each other Show commitment to the project Be reachable and willing to answer questions Clearly state the win conditions Track the progress of the system, give feedback to the developers builders Provide the platform in which their required website can be deployed Collect the win conditions from the stakeholders Figure out the requirement specification, operational concepts and initial architecture Initiate the Win-Win negotiation and try to reach to goal in which all stakeholder will win Develop prototypes, identify project risks, analyze project feasibility and mitigate risks Keep the client updated with the project progress Participate in the win-win negotiation Ensure the quality of the project Review the proceeding of the project and provide suggestion 3.2 Responsibilities by Phase Table 5: Stakeholder's Responsibilities in each phase Team Member / Role Name: Ying Yang Role: : Project Manager : Life Cycle Planner / Exploration Valuation Foundations Development- Construction Iteration 1.Project Plan 2.Progress Report 1.Record project progress 2.Project Plan 1.Record project progress 2.Project Plan Development- Transition Iteration LCP_FCP_F11a_T02_V1.2.doc 7 Version Date: 10/14/11

13 Name: Tianyin Zhou Role: : Life Cycle Planner : Prototyper Name: Ying Li Role: : Operational Concept Engineer : Requirement Engineer Name: Wei Tan Role: : System Architect : Prototyper Name: Iris Dror Role: : Feasibility Analyst : Requirement Engineer 1.Life Cycle Plan 2.Identify responsibilities and skills 1.Life Cycle Plan 2.Identify responsibilities and skills 1.Analyze Current System 2.Operational Concept Description Feasibility Evidence Description 1.Life Cycle Plan 2.Identify life cycle milestones 1.Life Cycle Plan 2.Identify life cycle milestones 1.Develop and assess prototype 1.OCD 2. Identify objectives, constraints and priorities 1.Define and develop out SSRD 1.SSAD 2.Provide Architecture Feasibility Evidence 3.Analysis current software architecture and design new architecture 4.UML 1.Develop and assess prototype 1.Feasibility Evidence Description 2.Assess and Mitigate Risks 3. Analyze business case 1.Life Cycle Plan 2.Identify life cycle milestones 1.Life Cycle Plan 2.Identify life cycle milestones 1.Develop and assess prototype 1.OCD 2. Identify objectives, constraints and priorities 1.Define and develop out SSRD 1.SSAD 2.Provide Architecture Feasibility Evidence 1.Develop and assess prototype 1.Feasibility Evidence Description 2.Assess and Mitigate Risks 3.Analyze business case 1.Define and 1.Define and LCP_FCP_F11a_T02_V1.2.doc 8 Version Date: 10/14/11

14 develop out SSRD develop out SSRD Name: Charles Muckenthaler Role: : IIV & V 1.Tracking System Quality 2.Identify Quality Management Strategy 3. Focuses on Quality Management Plan and tracks their execution. 1.Tracking System Quality 2.Identify Quality Management Strategy Focuses on Quality Management Plan and tracks their execution. 3.3 Skills Team members Role Skills Ying Yang Project Manager /Life Cycle Planner Wei Tan System Architect /Prototyper Tianyin Zhou Life Cycle Planner /Prototyper Ying Li Operational Concept Engineer /Requirements Engineering Iris Dror Feasibility Analyst Perl, C /Requirements Engineer Charles Muckenthaler IIV&V /Shaper Project Managing, C++, SQL C#, ASP.NET, Java COCOT, C++, Python, Pascal, HTML, CSS MySQL, PHP, C/C++ Quality Management, Java LCP_FCP_F11a_T02_V1.2.doc 9 Version Date: 10/14/11

15 4. Approach 4.1 Monitoring and Control We use Progress Report and Project Plans to control our project Closed Loop Feedback Control It is mainly controlled by s Reviews Valuation Commitment Review Foundation Commitment Review 4.2 Methods, Tools and Facilities Tools Usage Provider DART tools Assesses and mitigates risks in the system development life USC cycle Red Ridge 3.0 Provides examples for user interface and system functionality, CSC is helpful in the development of prototype PEAR Creates a framework and distribution system for reusable PHP components Open source LCP_FCP_F11a_T02_V1.2.doc 10 Version Date: 10/14/11

16 5. Resources Figure 1: Screenshot COCOMO result1 LCP_FCP_F11a_T02_V1.2.doc 11 Version Date: 10/14/11

17 Table 6: COCOMOII Scale Driver Driver Value Rationale Short Definition PREC Low Have some experience in database development If the product is similar to several that have been developed before then the precedentedness is high. FLEX High Because LADOT is open to consider all options Extent of constraints the product has to meet. The more flexible the requirements, schedules, interfaces, etc., the higher the rating. RESL Nominal Often The thoroughness of architectural definition and freedom from risk of the software architecture used for the product. TEAM High The clients are very busy and hard to reach. PMAT Nominal This cost driver accounts for the sources of project turbulence and extra effort due to difficulties in synchronizing the project's stakeholders: users, customers, developers, maintainers, interfacers, others. Process Maturity is organized around the Software Engineering Institute's Capability Maturity Model (CMM). The time period for reporting process maturity is at the time the project was underway and the capabilities practiced at the project level. High = L3. Scale Driver Value Rationale <Driver name> <value> <comments> Table 7: COCOMOII Cost Driver Cost Driver Value Rationale <Driver name> <value> <comments> LCP_FCP_F11a_T02_V1.2.doc 12 Version Date: 10/14/11