1 file · web viewtable 15: capabilities implemented, tested, and results 11 table of figures. no...

Life Cycle Plan (LCP)

<Renge App>

<Team 01>

Name Role Email AddressChien-Hao Huang Tester [email protected]

Yuzhen Wang Project Manager [email protected] Quan Front-end developer [email protected]

duCHENG-JU LIN Front-end developer [email protected]

duZhanhong Wu Front-end developer zhanhonw@usc.

eduTsung-Han Wu Back-end developer tsunghaw@usc.

eduSean Back-end developer [email protected]

mailto:[email protected]








10/17/2018

Version HistoryDate Author Version Changes made Rationale

08/20/05 PP 1.0Initial version of TCP To comply with Instructional

ICSM-TCP Template

Table of ContentsLife Cycle Plan (LCP)............................................................................................................................................................ iVersion History..................................................................................................................................................................... iiTable of Contents................................................................................................................................................................. iiiTable of Tables..................................................................................................................................................................... ivTable of Figures..................................................................................................................................................................... v

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............................................................................................................................................2

3. Responsibilities....................................................................................................................................................5

3.1 Project-specific stakeholder’s responsibilities..................................................................................................5

3.2 Responsibilities by Phase....................................................................................................................................5

3.3 Skills..................................................................................................................................................................... 6

4. Approach............................................................................................................................................................. 7

4.1 Monitoring and Control.....................................................................................................................................7

4.2 Methods, Tools and Facilities............................................................................................................................7

5. Resources............................................................................................................................................................. 86. Iteration Plan...................................................................................................................................................................10

6.1 Plan............................................................................................................................................................................ 10

6.1.1 Capabilities to be implemented.............................................................................................................................10

6.1.2 Capabilities to be tested.........................................................................................................................................10

6.1.3 Capabilities not to be tested..................................................................................................................................11

6.1.4 CCD Preparation Plans.........................................................................................................................................116.2 Iteration Assessment................................................................................................................................................11

6.2.1 Capabilities Implemented, Tested, and Results...................................................................................................11

6.2.2 Core Capabilities Drive-Through Results............................................................................................................116.3 Adherence to Plan.................................................................................................................................................... 12

Table of TablesTable 1: Artifacts Deliverables in Exploration Phase....................................................................................................2Table 2: Artifact deliverable in Exploration Phase........................................................................................................3Table 3: Artifact deliverable in Valuation Phase...........................................................................................................3Table 4: Artifact deliverable in Foundations Phase.......................................................................................................3Table 5: Artifact deliverable in Development Phase......................................................................................................4Table 6: Stakeholder's Responsibilities in each phase...................................................................................................5Table 7: COCOMOII Scale Driver.................................................................................................................................8Table 8: COCOMOII Cost Driver..................................................................................................................................8Table 9: Application Count: Screens..............................................................................................................................9Table 10: Application Count: Reports............................................................................................................................9Table 11: Application Count: 3GL components.............................................................................................................9Table 12: Application Point Parameters........................................................................................................................9Table 13: Construction iteration capabilities to be implemented................................................................................10Table 14: Construction iteration capabilities to be tested............................................................................................10Table 15: Capabilities implemented, tested, and results..............................................................................................11

Table of FiguresNo table of figures entries found.

1.Introduction

1.1 Purpose of the LCP LCP Guide construction and transition efforts, and the subsequent client evolution effort and can help make the best use of people and resources throughout the life cycle. We can plan to overcome the difficulties likely to arise at the time of development. It also served as the basis for controlling the project’s progress in achieving the software product objectives and as a plan for ensuring the timely execution of the project. Ensure that the quality elements of the Feasibility Rationale including business-case analysis and resource level feasibility are met.

1.2 Status of the LCP Current version of LCP is 1.0. It is an initial LCP at Foundation Phase of ICSM to find goals. It is going to be updated as the time goes on, new phases take place and project’s progress is evaluated.

1.3 Assumptions The duration of the project is 24 weeks, which are 12 weeks in Fall 2006 and 12 weeks in

Spring 2007. >> The team of this the project includes project managers, developers and tester from the

class in Fall 2018. It continues by other student from the same class in Spring 2018. The overall target of core functions will be the same as time goes on.

2.Milestones and Products

2.1 Overall StrategyRange is an IOS application, we use COT to evaluate progress and analysis risk weekly. The project is based on Swift on front-end and node.js for back-end. It will need to use JSON data to communicate with other parts too.

Exploration phaseDuration: 08/20/18- 9/15/18Concept: Identifying the meaning and basic function of this application. Analysis the architecture and requirements will be needed in the future. Plan the overall life softerware cycle plam.Deliverables: Risk Deflect report, WinBook, Overall system architecture.Milestone: List of requirements(Use cases).

Strategy: Risk analysis, Win-Win negotiations

Valuation phaseDuration: 09/07/18- 10/02/18 Concept: Identifying core functionality and key requirements, overall risks, mock UI prototype and demo the prototype to see the project feasibility.Deliverables: UI-UX prototype, Initial architecture design, Prototype PresentationMilestone: Prototype Presentation Strategy: Risk Analysis, Win-Win negotiations, Prototyping

Foundation phaseDuration: 09/20/18-Now Concept: Implement map and location as well as profile page. Realizing back-end data base communicating with front-end. Learning technologies and languages used in project by team members.Deliverables: Working initial system Milestone: End of CSCI 577aStrategy: Risk analysis, development

2.2 Project DeliverablesBelow is all deliverables on each phase

2.2.1 Exploration Phase

Table 1: Artifact deliverable in Exploration Phase

Artifact Due date Format MediumLife Cycle Plan Early Section 10/18/2018 .doc WordTeam Website 09/13/2018 .html Website hosted

onlineWin-Win Book 09/13/2018 .html Online WebsiteJira tickets and report Every Monday .html Online Website

2.2.2 Valuation PhaseTable 2: Artifact deliverable in Valuation Phase

Artifact Due date Format MediumPrototype presentation 09/27/2018 .ppt In-class presentation

UI-UX Design 09/27/2018 .bmpl BalsamiqUse case based effort

estimation10/08/2018 .doc Online Website

Use case analysis 09/24/2018 .doc Online Website

2.2.3 Foundations PhaseTable 3 Artifact deliverable in Foundations Phase

Artifact Due date Format MediumJira tickets and report Every Monday .html Online Website

ARB Presentation 10/19/2018 .ppt In-class presentationPrototypes 10/13/2018 .swift Team Website, GitHub

Software architecture 10/13/2018 .vpp Team WebsiteDraft Development

Commitment Package Operational

Concept Description (OCD)

Life Cycle Plan (LCP_

Feasibility Evidence Description (FED)

Prototype (PRO) System and

Software

10/22/2018 .doc, .pdf Soft Copy

Architecture Description (SSAD)

Test Plan and Cases (TPC)

Risk and Defect Reports Bi-weekly .xlsx Team WebsiteProject Plan Bi-weekly on

Wednesday.mpp Soft copy

Progress Report Bi-weekly on Wednesday

.xls Soft copy

Technical Debt Report Bi-weekly on Friday

.xls Soft Copy

3.Responsibilities

3.1 Project-specific stakeholder’s responsibilitiesName: JadebRole: ClientExploration Define current system and show business workflow. Establish win

conditions and state minimum marketable features.Valuation Finalize win conditions and determine business value as well as relative

penalty for each condition. Give feedback for the progress of group. Give group access to hosting package. Gain shared vision with team members.

Foundations Attend architectural review board for development commitment review. Give key feedback on prototypes and current progress of inventory system.

Development- Construction Iteration

Give information on features and how they can be improved if time permits. Test out the inventory system and give feedback.

Development- Transition Iteration

Attend training sessions, and learn complete functions of the system. Give feedback on user manual. Understand what sort of maintenance is needed.

Name: ElliottRole: CTOExploration Define current system and show business workflow. Establish win

conditions and state minimum marketable features.Valuation Finalize win conditions and determine business value as well as relative

penalty for each condition. Give feedback for the progress of group. Give group access to hosting package. Gain shared vision with team members.

Foundations Meet with team to understand how system works. Give feedback on usability of system.

Development- Construction Iteration

Fill out the spreadsheet of items available in storage. Attend meetings with team to understand features of system. Give feedback regarding usability and ease of use.


Attend training sessions to understand all the features and have a good understanding of the domain model of COSMIC. Learn the basic functions of phpMyAdmin in the case an item has a malfunction and needs manual fixing. Give final feedback on inventory system.

3.2 Responsibilities by PhaseTable 1: Stakeholder's Responsibilities in each phase

Team Member / Role

Primary / Secondary ResponsibilityExploration Valuation Foundations Development-

Construction Iteration


Name:Elliott、JadebRole:Client、Maintainer

Primary ResponsibilityExplain what kind of application they want to build

Primary ResponsibilityProvide the design sketch of Renge and list of requirements.Participate prototype presentation and give feedback on developing system

Primary ResponsibilityAttend ARB’s presentation, provide more detail requirements and check the development.

Name:SeanRole:Back-end developer

Primary ResponsibilityGather requirementsSecondary ResponsibilityInteract with the clientGather project requirementsFill in the Winbook

Primary ResponsibilityGather the requirementsAnalyze risksFigure out top risks of the projectSuggest risks mitigation strategySecondary ResponsibilityPrototype project’s features according to the plan

Primary ResponsibilityWork with other Back-end team mates to finish all front-end tasks and discussion with clients about task detail and feasibility

Name:JonathanRole:Back-end developer

Primary ResponsibilityEvaluate overall system requirementsMake initial system architecture assumptionSecondary ResponsibilityArrange team meetingsArrange negotiation

Primary ResponsibilityEvaluate specific system requirementsMake initial system architectureMake initial use casesSecondary ResponsibilityArrange team meetingsArrange

Primary ResponsibilityWork with other Back-end team mates to finish all front-end tasks and discussion with clients about task detail and feasibility

sessions with the client

negotiation sessions with the client

Name:YufeiRole:Front-end developer

Primary ResponsibilityPlan the project’s life cycleAnalyze the requirementsShare responsibilities between team members

Primary ResponsibilityPlan the project’s life cycleAnalyze the requirementsShare responsibilities between team membersEstimate time and costs for each taskSecondary ResponsibilityPrototype project’s features according to the plan

Primary ResponsibilityWork with other front-end team mates to finish all front-end tasks and discussion with clients about task detail and feasibility

Name:BillyRole:Front-end developer

Primary ResponsibilityGather the requirementsAnalyze risks

Primary ResponsibilityUpdate initial system’s prototype designMake UI mockupsMake prototyping plan of most important modulesSecondary ResponsibilityPrototype project’s features according to the plan


Name:JustinRole:Front-end developer

Primary ResponsibilityVerify and validate work products and requirementsSecondary ResponsibilityGet an overall system overviewMake initial operational

Primary ResponsibilityVerify and validate work products and requirementsNegotiate with team about issues in project developmentSecondary Responsibility


concept assumptions

Develop operational concept

Name:GinaRole:Project Manager

Primary ResponsibilityAnalyze scope of the projectArrange team meetingsArrange negotiation sessions with the clientKeep track of project progressSecondary ResponsibilityInteract with the clientGather project requirementsFill in the Winbook

rimary ResponsibilityAnalyze scope of the projectArrange team meetingsArrange negotiation sessions with the clientKeep track of project progressSecondary ResponsibilityInteract with the clientGather project requirementsMake sure, that project progress meets the requirementsUpdate the Winbook

Primary ResponsibilityAnalyze scope of the projectArrange team meetingsArrange negotiation sessions with the clientKeep track of project progressSecondary ResponsibilityInteract with the clientGather project requirementsMake sure, that project progress meets the requirements

Name:WillRole:Tester

Primary ResponsibilityHelp understand the concept of the whole application and raise question and point improperly function for clients

Primary ResponsibilityPrototype project’s features according to the planSecondary ResponsibilityVerify and validate work products and requirementsNegotiate with team about issues in project development

Primary ResponsibilityHelp other developers which has shortage of member while load are heavy

3.3 Skills<< Identify current and required skills for each role. Please note that if some of your team member does not continue in 577b, you should identify the required role(s) and skills of the new team member. Example of skills can be found at ICSM EPG> Task: Identify Responsibilities and Skills. >> >>

Team members Role SkillsGina Project Manager, Life Cycle

PlannerCurrent skills: Leadership, scheduling, technical writing, CSS, HTML, JavaScript, Java

Required skills: Project management and planning, Microsoft Project Planning, Testing

Billy Prototyper, Front-end developer

Current skills: Leadership, technical writing, Aerodynamics engineering, CSS, HTML, JavaScript, Java, Python, MATLAB

Required skills: operational concept design, web development, code implementation, prototyping, training

Jonathan Back-end developer Current skills: Leadership, technical writing, CSS, HTML, JavaScript, Java, Node.js, C++, Json

Required skills: back-end skills like PHP and mySQL, front-end skills (Angular JS & Bootstrap)

Sean Feasibility Analyst, back-end developer

Current Skills: Leadership, C/C++, Java, C#, python,

Required skills: feasibility analysis skills, web development, back-end technologies (PHP and MySQL), risk mitigation

Yufei Software Architect, Front-end developer

Current skills: Leadership, Software Engineering, CSS, HTML, JavaScript, Java, swift

Required skills: UML modeling, physical and logical architecture modeling, web development, code

implementation, back-end technologies (PHP and MySQL)

Will Quality Focal Point, Tester Current Skills: Leadership, Software Development, Java, C#, HTML, CSS, JavaScript

Required skills: Testing and verification, Quality Management, Peer Review, Jira validation, Developing Test Cases

Justin Requirements Engineer, Tester as well as front-end developer

Current Skills: Leadership, Software Development, C++, Python, Java, IOS Development, html, CSS, JavaScript, Json,swift

Required Skills: Testing and verification, Peer Review, understanding requirements and win-conditions

4.Approach

4.1 Monitoring and ControlIn order to monitor and control this project better and reasonablely, below are the tools and approaches we use:

GitHub Repository – Used for code collaboration, allowing members of the team to add their content and push it to branches.

Jira Tickets – Team members and project manager use Jira to assign and record tasks on tickets to log work and monitor assignments.

Progress Report – Bi-weekly assignment to record and update progress on the project with a to-do list and completed list.

Risk and Defect Report – Bi-weekly assignment to record and update risk exposure as well as defects that are both avoidable and unavoidable.

Win-Win Book- Used to capture, categorize, and prioritize win-conditions and requirements for the inventory system.

4.1.1 Closed Loop Feedback Control

We have two social media to communicate with each other in our team. Slack is used to discuss the product requirement and technical tasks with clients and CTO(client side). WeChat is used mostly to discuss the technical difficulties among our developers. When it is necessary, we will schedule a meeting to discuss the difficulties together.

4.1.2 Reviews

The following listed are review methods used to control project: Peer Review Test Cases Architecture Review Board Review Boards Teaching Assistant & Professor Feedback Client Feedback

4.2 Methods, Tools and Facilities

Tools Usage ProviderJira Used to create tickets and log work. Also used to assign tasks. AtlassianWinBook Categorize and prioritize win conditions USCCOINCOMO II

Allows for resource estimation using COCOMO II model USC

Microsoft Project Plan

Allows for creation of Gantt Chart and project plan Microsoft

GitHub Used for code collaboration between members GitHubMySQL Database service used to store items and user information. OracleSwift Front-end coding laguageMicrosoft Excel

Used for creating spreadsheet used for import into system Microsoft

GoDaddy Hosting package for web application GoDaddyWeChat Collaborate and update team members through group chat WeChatSlack Collaborate and update with clietns and CTO through group

chatSlack

Google Drive Google Drive is used to share files between team members (especially files that are being updated constantly)

Google

Balsamiq Tool to create prototype mockups Balsamiq

5.ResourcesEstimated Effort: 7 team members at 10 hrs/week for 12 weeks

Total effort: 1840 hours

Project Duration: 12 weeks

Component Modules: user-interface module, Nutrition module, NCS functions module, Server-side module

Programming Language used: Node.js Swift

Table 2: COCOMOII Scale Driver

Scale Driver Value RationalePREC High There are similarities between this app and other existing apps;

however, the Renge app does offer several new featuresFLEX High There is already existing code for the system developed by the

client; new code will need to conformRESL Nominal Several major risks have been identified, and mitigation

techniques are in planning. It will be presented in the following parts.

TEAM High Team interactions are generally productive and cooperative. However, some scheduling and communication obstacles have arisen because of the inclusion of an off-campus team member.

PMAT Nominal Most of us have understanding about how IOS application works.

Table 3: COCOMOII Cost Driver for Module 1:User Interface

Cost Driver Value RationaleRELY High User interface is integral part of the systemDATA High Renge is a geo-application, it means lot of geometric date

need to be storedDOCU Nominal Documentation will be developed for each phase of

development, but nothing special to handle. CPLX Nominal Common knowledge would be enough to use this interfaceRUSE Low This module is developed specially for the project, so

reusability is low.TIME Nominal User registration needs to be done in a timely manner.STOR High Each user’s location information and chatting history would

need to be storedPVOL Low No frequent changes will be made to the app, therefore

volatility low.ACAP Nominal Team members have some analyst capabilities, but not all of

us are good at it.APEX High Using a mobile app is familiar to team members.PCAP Nominal Some of us have IOS application experience beforePLEX Low Some team members are familiar with the platform used for

our project.LTEX Nominal Most team members are familiar with Swift and Node.js for

back-end part is not hard to learn.PCON High Very few team members are going to continue with CSCI

577b next semester.TOOL Nominal Basic software tools are used and are moderately integrated.SITE High One DEN students on the team, communication with whom

is done using slack and hangout.

Table 9: COCOMOII Cost Driver for Module 2:NCS Functions

Cost Driver Value RationaleRELY High Facebook API and google map API are important integration

of this systemDATA High User’s personal information and map location data need to be

storedDOCU Nominal Documentation will be developed for each phase of

development, but nothing special to handle. CPLX Nominal Enough source code for this two API to use in our appRUSE High This module is not developed specially for the project, so

reusability is high.TIME High Even source code is available, we have to conform it with

current app.STOR High Each user’s location information and chatting history would








Table 10: COCOMOII Cost Driver for Module 3: server-side

Cost Driver Value RationaleRELY High Back-end part is integration of this system.DATA High Renge is a geo-application, it means lot of geometric date

need to be storedDOCU Nominal Documentation will be developed for each phase of

development, but nothing special to handle. CPLX Nominal Common knowledge would be enough to use this interfaceRUSE Low This module is not developed specially for the project, so

reusability is low.TIME High Design request handle and process all requirement and

operate this system.STOR High Each user’s location information and chatting history would








SreenShot of the COCOMOII estimate:

RESULT ANALYSIS:

Estimated Most-likely Effort by COCOMOII: 9.5 Person-MonthEffort per person: 10 hrs/week

Total time available per person:Monthly efforts: 10 hours per week * 7 members * 4 weeks = 280 hrs/month

Time required as per COCOMOII:Total time(months): (9.5 person-month * 152 hrs per person-month) / 280 = 5.15 months

Thus, as per COCOMOII, most-likely time required to complete the project is 5.15 months. So it is kind of unlikely to finish this project for this semester. We would need to pass this project for the student continuing in next semester to work on it.

6. Iteration Plan6.1 Plan

The first iteration will be the first construction phase of the highest priority capabilities. These include many of the capabilities already prototyped, but need final implementation.

The second iteration will be the second construction phase of capabilities that will improve the system, but are secondary. These features will only be constructed and implemented if time permits.

6.1.1 Capabilities to be implementedTable 4: Construction iteration capabilities to be implemented

ID Capability Description Priority Iteration

C1 chat User can chat with their friends Highest 1st

Construction Phase

C2 Find friends User can find all his/her friends around him/her

Highest 1st Construction Phase

C3 Reject friend request

User can reject other user’s friend request

Highest 1st

Construction Phase

C4 Current event information

User can see information about current event

Highest 1st

Construction Phase

C5 Recommendation about interest

User can receive recommendation about their interest person

Highest 1st

Construction Phase

C6 Create account User can create account and update personal information

Highest 1st

Construction Phase

C7 Block/unblock user

User can block/unblock other user’s message

highest 1st

Construction Phase

C8 Import information from

Facebook

User can import information from Facebook

High 2nd

Construction Phase

C9 Future event Information

User can receive information about future event

High 2nd

Construction Phase

C10 See route User can see route from himself/herself to his/her friends

High 2nd

Construction Phase

6.1.2 Capabilities to be testedTable 5: Construction iteration capabilities to be tested

ID Capability Description Priority Iteration

C1 chat User can chat with their friends Highest 1st

Construction Phase

C2 Find friends User can find all his/her friends around him/her

Highest 1st Construction Phase

C3 Reject friend request

User can reject other user’s friend request

Highest 1st

Construction Phase

C4 Current event information

User can see information about current event

Highest 1st

Construction Phase

C5 Recommendation about interest

User can receive recommendation about their interest person

Highest 1st

Construction Phase

C6 Create account User can create account and update personal information

Highest 1st

Construction

Phase

C7 Block/unblock user

User can block/unblock other user’s message

highest 1st

Construction Phase

C8 Import information from

Facebook

User can import information from Facebook

High 2nd

Construction Phase

C9 Future event Information

User can receive information about future event

High 2nd

Construction Phase

C10 See route User can see route from himself/herself to his/her friends

High 2nd

Construction Phase

6.1.3 Capabilities not to be tested

All capabilities implemented will be tested during all iterations. Because it all need to make sure performing well to apply and then release to market.

6.1.4 CCD Preparation Plans

For the Core Capability Drive-through, the key stake holders involved include:- Jade – Client & Director of Renge Program- Elliott- CTO & Client of Renge Program- Development Team Members- Professors & Teaching Assistants

The purpose of the core capability drive-through is to give the client a hands-on experience utilizing the inventory management system. They will test the functions that have already been put in place, and give us feedback regarding the system. They will provide information on ways to make the product more intuitive and improve overall usability and user experience. Feedback forms will be provided for the client and teaching staff to give recommendations and thoughts on project.

6.2 Iteration Assessment

6.2.1 Capabilities Implemented, Tested, and Results

Currently all tests are TBD since we have not provide capabilities that are implemented well enough to be tested yet.

Table 6: Capabilities implemented, tested, and results

ID Capability Test Case Test Results If fail, why?C1 Friend request sent TC-01 TBD TBDC2 Friend block TC-02 TBD TBDC3 Friend unblock TC-03 TBD TBDC4 Route TC-04 TBD TBDC5 Chat with friends TC-05 TBD TBD

6.2c.2 Core Capabilities Drive-Through Results

CCD Presentation will come soon.

6.3 Adherence to PlanAdherence to iteration plan will be documented following development and testing throughout the Construction phase.

1 file · web viewtable 15: capabilities implemented, tested, and results 11 table of figures. no...

Documents