Life Cycle Plan (LCP) Team-04 Version 2.0
Life Cycle Plan (LCP)
Combat Conflict
Team 04
Christopher Hanford - UML Modeler, Prototyper
Jai Khanna- Prototyper, Software Developer
Lisa Scaria- Operational Concepts Engineer, Lifecycle Planner
Mansi Negi - Prototyper, Software Developer
Nicholas Funk - Prototyper, Software Developer
Rijuta Kapoor - Requirement Engineer, Feasiblity Analyst
Tony Chun- Project Manager, Prototyper
Tyler Bard- Quality Focal Point
12/04/15
3
Life Cycle Plan (LCP) Team-04 Version 2.0
Version History
Date / Author / Version / Changes made / Rationale /10/19/15 / Lisa Scaria / 1.0 / Original template for use with LeanMBASE v1.0 / Initial draft for use with LeanMBASE v1.0
12/1/15 / Lisa Scaria / 2.0 / Added section 6 which details the transition iteration details. / Finishing up the document.
Table of Contents
Life Cycle Plan (LCP) i
Version History iii
Table of Contents iv
Table of Tables vi
Table of Figures vii
1. Introduction 1
1.1 Purpose of the LCP 1
1.2 Status of the LCP 1
1.3 Assumptions 1
2. Milestones and Products 2
2.1 Overall Strategy 2
2.2 Project Deliverables 3
3. Responsibilities 6
3.1 Project-specific stakeholder’s responsibilities 6
3.2 Responsibilities by Phase 6
3.3 Skills 8
4. Approach 10
4.1 Monitoring and Control 10
4.2 Methods, Tools and Facilities 10
5. Resources 12
6. Iteration Plan 17
6.1 Plan 17
6.1.1 Capabilities to be implemented 17
6.1.2 Capabilities to be tested 18
6.1.3 Capabilities not to be tested 18
6.1.4 CCD Preparation Plans 18
6.2 Iteration Assessment 19
6.2.1 Capabilities Implemented, Tested, and Results 19
6.2.2 Core Capabilities Drive-Through Results 20
6.3 Adherence to Plan ...... 20
3
1 Table of Contents
Table of Tables
Table 1: Artifacts Deliverables in Exploration Phase 2
Table 2: Artifact deliverable in Valuation Phase 3
Table 3: Artifact deliverable in Foundations Phase 3
Table 4: Artifact deliverable in Development Phase 4
Table 5: Stakeholder's Responsibilities in each phase 5
Table 6: Team Members: Individual Skills 5
Table 7: Web Tools to be Used 5
Table 8: COCOMOII Scale Driver 8
Table 9: COCOMOII Insert PHPCost Driver 8
Table 10: COCOMOII WP Buisness Intelligence Stats Plugin Cost Driver 8
Table11: COCOMOII Wordpress Cost Driver 8
Table 12:Consturction iteration capabilities to be implemented ...... 17
Table 13: Construction iteration capabilities to be tested...... 18
Table 14: Capabilities implemented, tested, and results...... 19
3
1 Table of Contents
Table of Figures
No table of figures entries found.
3
Life Cycle Plan (LCP) Template Version no 2.0
1. Introduction
1.1 Purpose of the LCP
The purpose of this Life Cycle Plan is to show the different stages of the Combat Conflict project, the artifacts which are to be delivered at each stage, which team members are responsible for what and what our team hopes to accomplish by the end of this class. At each stage, this LCP will become updated with requirement changes which are encountered after every iteration of prototyping and negotiating this software system.
1.2 Status of the LCP
The status of the LCP is currently at version 1.0, the first iteration. The project has just finished the exploration and valuation phase and is currently in the developmental phase since we are a one semester team. The major changes from the exploration/ valuation phase are:
- An overall design for the project has been discussed and agreed upon between the client and the team.
- There is an understanding of the minimum marketable features as well as features which the client would like to include given more time.
- Team member roles have been assigned.
- Gained access to the web based server in order to begin prototyping.
- Began implementing prototype using Wordpress
1.3 Assumptions
· The duration of the project is 12 weeks in Fall 2015 as all of the team members are only taking CSCI 577a.
· The team consists of six on campus members and two off campus members.
· The software will be hosted on the Oceans web server provided by the client.
· The software must meet all software guidelines given by USC's Marshall School of Business as their students are the initial end users.
2. Milestones and Products
2.1 Overall Strategy
The Combat Conflict Project is following the Architected Agile process.
Exploration phase
Duration: 9/09/15 - 09/25/15
Concept: Identify the basic requirements of the project through client meetings. Decide what the design of the game should be and look into what ideas may be feasible as a one semester project. Decide team roles depending on strengths of each member.
Deliverables: Client Interaction Report, Team Website, Win Conditions
Milestone: N/A
Strategy: Once Incremental Commitment Cycle
Valuation phase
Duration: 9/25/15 - 10/2/15
Concept: Have a clear understanding of scope of project as well as minimum marketable features which are necessary for the system. Begin to look at possible COTS products which could be implemented for the system as well as possible systems which could be built from scratch. Gain access to the clients web server and begin to test and prototype biggest risk features.
Deliverables:FC Package
Milestone: Top Risk Prototype presentation
Strategy: One Incremental Commitment Cycle
Foundations phase
Duration: 10/2/15 - 10/19/15
Concept: Narrow down COTS options and begin to create a prototype which can be shown to the client to gather feedback. Possibly have some veterans who will use the Combat Conflict system use the beta version and respond to what features could be improved. If a feature is not able to be met, renegotiate with client to see how this problem can be tackled.
Deliverables: DC Package
Milestone: DC Review
Strategy: One Incremental Commitment Cycle
Development phase
Duration: 10/20/15 - 11/30/15
Concept: Finish prototype and begin testing and quality control. Go through review iterations with client and IV&V team member and ensure minimum marketable features have been met. Begin documenting and training maintainers who must run the system after CSCI 577a
Deliverables:Final Deliverables, Project Release, Close out Report
Milestone: OCR
Strategy: Once Incremental Commitment Cycle
2.2 Project Deliverables
2.2.1 Exploration Phase
Table 1: Artifacts Deliverables in Exploration Phase
Artifact / Due date / Format / MediumTeam Website / 9/16/2015 / website / Online
Win Conditions Report / 09/28/2006 / .doc, .pdf / Soft copy, Team Website
Client Interaction Report / 09/28/15 / .doc, .pdf / Soft copy, Team Website
Progress Report / Bi Weekly / .xlsx / Soft copy, Team Website
Project Plan / Bi Weekly / .mpp, / Soft copy, Team Website
Progress Report / BiWeekly / .xls / Soft copy, Team Website
Jira Individual Tasks / Every Monday / Jira site
2.2.2 Valuation Phase
Table 2: Artifact Deliverable in Valuation Phase
Artifact / Due date / Format / MediumTop Risk Prototype / 10/2/15 / Ppt / Hard copy, in class presentation
Progress Report / Bi Weekly / .xlsx / Soft copy, Team Website
Project Plan / Bi Weekly / .mpp, / Soft copy, Team Website
Progress Report / BiWeekly / .xls / Soft copy, Team Website
Jira Individual Tasks / Every Monday / Jira site
2.2.3 Foundations Phase
Table 3: Artifact Deliverable in Foundations Phase
Artifact / Due date / Format / MediumInitial Prototype / 10/14/15 / Ppt/website / Website
FC package:
Operational Concepts Document
Prototype Document
Software Architecture Document
Life Cycle Plan
Feasibility Evidence Document / 10/19/15 / Doc, pdf / Soft copy, team website
Project Plan / Bi Weekly / .mpp, / Soft copy, Team Website
Progress Report / BiWeekly / .xls / Soft copy, Team Website
Jira Individual Tasks / Every Monday / Jira site
Progress Report / Bi Weekly / .xlsx / Soft copy, Team Website
Development Phase
Table 4: Artifact deliverable in Development Phase
Artifact / Due date / Format / MediumPrototype progress / 11/06/15 / Ppt/website / Web
OC package:
Operational Concepts Document
Prototype Document
Software Architecture Document
Life Cycle Plan
Feasibility Evidence Document / 12/07/15 / Doc, pdf / Soft copy, team website
Project Plan / Bi Weekly / .mpp, / Soft copy, Team Website
Progress Report / BiWeekly / .xls / Soft copy, Team Website
Jira Individual Tasks / Every Monday / Jira site
Progress Report / Bi Weekly / .xlsx / Soft copy, Team Website
Project Release / 12/07/15 / Web / Webbased service
Client Evaluation Report / 12/07/15 / Doc, pdf / Soft copy
Close Out Report / 12/07/15 / Doc, pdf / Soft copy, team website
Team Critique / 12/07/15 / Doc, pdf / Soft copy, team website
3. Responsibilities
3.1 Project-specific stakeholder’s responsibilities
Other than the typical stakeholders, of client, user, maintainer, developer and IIV&V we do not have an project-specific stakeholders for this project.
3.2 Responsibilities by Phase
Table 5: Stakeholder's Responsibilities in each phase
Team Member / Role / Primary / Secondary ResponsibilityExploration / Valuation / Foundations / Development- Construction Iteration / Development- Transition Iteration
Name:
Christopher Hanford - UML Modeler/Prototyper / Primary Responsibility:
Participate in win win negotiation and commitment review
Secondary Responsibility
Think of and analyze win conditions for project. / Primary Responsibility
COTS Evaluation / Primary Responsibility
Creating Use case and system diagrams .
Secondary Responsibility
Development / Primary Responsibility
Prototyping & Development
Secondary Responsibility
Plan for testing / Primary Responsibility
Help transition product to maintainers, train them.
Name:
Jai Khanna - Prototyper/Software Architect / Primary Responsibility
Assess client points and submit details after Win Win meeting
Secondary Responsibility
Think of and analyze win conditions for project. / Primary Responsibility
COTS Evaluation / Primary Responsibility
Prototyping and Development / Primary Responsibility
Help with system iterations after feedback from client
Secondary Responsibility
Documentation for protoype. / Primary Responsibility
Documentation for maintainers.
Name:
Lisa Scaria - Life Cycle Planner/ Feasibliity / Primary Responsibility
Coordinate Meetings and emails with client
Secondary Responsibility
Create project plan for semester. / Primary Responsibility
Attend client meetings and relay information /questions from prototypers
Secondary
Responsibility
Update project plan / Primary Responsibility
Work on and refine life cycle plan and update as needed.
Secondary Responsibility
Meetings with client. / Primary Responsibility
Keep lifecycle plan as well as bi weekly project reports updated with scope of project / Primary Responsibility
Submit final versions of life cycle plan which has been updated with scope of project.
Help with documentation for maintainers and client.
Name:
Mansi Negi - Prototyper/Software Developer / Primary Responsibility
Assess client points and submit details after Win Win meeting
Secondary Responsibility
Think of and analyze win conditions for project. / Primary Responsibility
COTS Evaluation / Primary Responsibility
Prototyping and Development / Primary Responsibility
Help with system iterations after feedback from client
Secondary Responsibility
Documentation for protoype. / Primary Responsibility
Documentation for maintainers.
Name:
Nicholas Funk - Protoyper/ Software Developer / Primary Responsibility
Assess client points and submit details after Win Win meeting
Secondary Responsibility
Think of and analyze win conditions for project. / Primary Responsibility
NDI Candidate Review
Secondary Responsibility
Feasibility Evidence Description Document / Primary Responsibility
Prototyping & Development / Primary Responsibility
Prototyping & Development
Secondary Responsibility
Plan for testing / Primary Responsibility
Help transition product to maintainers, train them.
Name:
Rijuta Kapoor- Requirements. Operational Concepts / Primary Responsibility
Collect all stakeholders' win conditions
Secondary Responsibility
Think of and analyze win conditions for project. / Primary Responsibility
Attend client meetings and relay information /questions from prototypers / Primary Responsibility
Work on and refine operational concepts and update use cases as needed
Secondary Responsibility
Meetings with client. / Primary Responsibility
Meet and coordinate with client about changing requirements / Primary Responsibility
Help with documentation for maintainers and client.
Facilitate, system implementation with client.
Name:
Tony Chun - Project Manager/ Prototyper / Primary Responsibility
Identify project risks and negotiate design with client
Secondary Responsibility
Create Team Website / Primary Responsibility
Handle relaying findings about solution to clients as well as validating the technical parameters with the professors and TAs.
Secondary Responsibility
Contribute to the technical details of the prototype. / Primary Responsibility
Create and validate that the set technical details of the project are reasonable to complete by the due date.
Secondary Responsibility
Negotiate with client if any issues come up which causes changes in requirements / Primary Responsibility
Keep track of prototype progress and assign tasks. / Primary Responsibility
Help with system transition between maintainers and developers.
Name:
Tyler Bard - Quality Focal Point / Primary Responsibility
Submit win conditions / Primary Responsibility
Give input to prototypers when assessing COTS products / Primary Responsibility
Review and provide feedback for the prototypers. / Primary Responsibility
Plan and conduct testing / Primary Responsibility
Ensure quality of the product
Name:
Stephanie Westmeyer - Client / Primary Responsibility
Participate in win conditions negotiations, and explain desired system to the 577a team. / Primary Responsibility
Provide details of desired system, attend negotiation meetings to discuss terms / Primary Responsibility
Provide questions and scenarios to be inserted into prototype.
Provide possible users to test with / Primary Responsibility
Assess prototype and give feedback through review meetings / Primary Responsibility
Interact with maintainers and team to ensure smooth transition of system.
Maintainers: / Primary Responsibility / Primary Responsibility / Primary Responsibility / Primary Responsibility / Primary Responsibility
Use documentation and meet with prototypers to learn system.
Users: / Primary Responsibility / Primary Responsibility / Primary Responsibility
Use the first iteration of the prototype and give feedback about usability / Primary Responsibility
Use and provide feedback for the system / Primary Responsibility
Use the system as a learning tool to enhance their combat conflict skills
3.3 Skills
Table 6: Team Members: Individual Skills
Team members / Role / SkillsChristopher Hanford / UML Modeler, Prototyper / Current skills: Programming, Web development, Creating UML diagrams.
Required skills: Web development, database management
Jai Khanna / Prototyper, Software developer / Current skills: Programming, Web development
Required skills: Web development, database management
Lisa Scaria / Lifecycle Planner, Operational Concepts Engineer / Current skills: Programming
Required skills: Client negotiation , Lifecycle planning
Mansi Negi / Prototyper, Software Developer / Current skills:
Programming,
Web development
Required skills:
Web development, Database management
Nicholas Funk / Prototyper, Software Developer / Current skills: Programming, Web CMS platforms
Required skills: Requirements Analysis, PHP language skills
Rijuta Kapoor / Requirements Engineer, Feasibility Analyst / Current skills: Programming
Required skills: Client negotiation , Requirements Analysis
Tony Chun / Project Manager, Prototyper / Current skills: Programming
Required skills: Management, Technical Leadership
Tyler Bard / Quality Focal Point / Current skills: Software Testing
Required skills: Web Development, PHP language skills
4. Approach