1€¦ · Web viewFarica Mascarenhas IV&V ... Tools Usage Provider Microsoft Word 2012 Constructs documents for all artifacts USC Microsoft Project 2003 Creates Gantt

Life Cycle Plan (LCP)

Mission Science iRobots

Team 07

Ashwini Ramesha OCE, Requirements EngineerChen Li Requirements Engineer, Feasibility AnalystFarica Mascarenhas IV&V, Quality AnalystJiashuo Li Prototyper, Software ArchitectRitika Khurana Project ManagerSiddhesh Rumde Life Cycle Planner, Requirements EngineerSowmya Sampath Software Architect, PrototyperYun Shao Feasibility Analyst, OCE

09/20/2014

ii

Version HistoryDate Author Version Changes made Rationale

09/20/14 FM 1.0 Original for CSCI577; Tailored

from ICSM OCD Template To fit CS577 course content

iii

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

1. Introduction.................................................................................................................................................1

2. Milestones and Products.............................................................................................................................2

3. Responsibilities............................................................................................................................................3

3.1 Responsibilities by Phase............................................................................................................................3

3.2 Skills..............................................................................................................................................................3

4. Approach......................................................................................................................................................4

4.1 Monitoring and Control..............................................................................................................................4

4.2 Methods, Tools and Facilities.....................................................................................................................4

5. Resources......................................................................................................................................................56. 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

iv

Table of TablesTable 1: Stakeholder's responsibilities...........................................................................................................................3Table 2: Stakeholder's responsibilities...........................................................................................................................3Table 3: Stakeholder's responsibilities...........................................................................................................................3Table 4: Stakeholder's responsibilities...........................................................................................................................4Table 5: Stakeholder's responsibilities...........................................................................................................................4Table 6: Stakeholder's responsibilities...........................................................................................................................4Table 7: Stakeholder's responsibilities...........................................................................................................................5Table 8: Stakeholder's responsibilities...........................................................................................................................5Table 9: Stakeholder's responsibilities...........................................................................................................................5Table 10: Team Members Role and Skills......................................................................................................................6Table 11: Required tools.................................................................................................................................................7Table 12: Module lists and SLOC...................................................................................................................................8Table 13: COCOMOII Scale Drivers.............................................................................................................................8Table 14: COCOMOII Cost Drivers of Module 1..........................................................................................................9Table 15: Construction iteration capabilities to be implemented................................................................................12Table 16: Construction iteration capabilities to be tested............................................................................................12Table 17: Capabilities implemented, tested, and results..............................................................................................13

v

Table of FiguresFigure 1: COCOMO Estimation Result........................................................................................................................10

vi

1.Introduction

This document is organized to answer the most common questions about a project or activity: Why? Whereas? What? When? Who? Where? How? How much?

This is the first version of the LCP document. Any changes in the upcoming weeks will be recorded in this document.

1

2.Milestones and Products

<< Identify the life cycle phases and its dates, deliverables, milestone and strategy of each phase. For example:>>

Exploration phaseDuration: 09/17/14 – Concept: Analyze current system, assess and plan to mitigate risks, identify other success-critical stakeholders, identify responsibilities and skills, develop project plan, record project individual effort and project progressDeliverables: Valuation Commitment PackageMilestone: Valuation Commitment ReviewStrategy: One Incremental Commitment Cycle

Valuation PhaseDuration: Concept: Identify operational concept, system and software requirement, system and software architecture, and life-cycle plan. Conduct on-campus win-win negotiation participation and off campus follow upDeliverables: Foundations Commitment Package Milestone: Foundations Commitment ReviewStrategy: One Incremental Commitment Cycle

Foundations phaseDuration: Concept: Assess project status, plan and manage project, manage project quality, prototype and develop software architectureDeliverables: Development Commitment Package Milestone: Development Commitment Review Strategy: One Incremental Commitment Cycle

Development phaseDuration: Concept: Plan for test and implement the software prototypeDeliverables: Operation Commitment Package Milestone: Operation Commitment Review Strategy: One Incremental Commitment Cycle

<<Note: Schedule of the class and its milestone can be found in the first lecture of the class.>>

2

3.Responsibilities

3.1 Responsibilities by Phase<< Identify responsibilities of each team member including client, user, and maintainer in each phase. Please note that a document name such as OCD, WinWin Agreements or Prototype is not a responsibility. Examples of responsibilities are identify project risk, develop prototype, acquire NDI, and etc.>>

Table 1: Stakeholder's responsibilities

Name: Dr. Gray DarinRole: ClientExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration

<<responsibilities>>

Development- Transition Iteration



Name: Ritika KhuranaRole: Project ManagerExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Ashwini Ramesha

3

Role: OCEExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Chen LiRole: Requirements EngineerExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Sowmya SampathRole: Software ArchitectExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Siddhesh RumdeRole: Life Cycle Planner

4

Exploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Jiashuo LiRole: PrototyperExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Yun ShaoRole: Feasibility AnalystExploration <<responsibilities>>Valuation <<responsibilities>>Foundations <<responsibilities>>Development- Construction Iteration





Name: Farica MascarenhasRole: IV&VExploration Analyze current system, explore alternatives

5

Valuation Identify configuration management strategy, identify quality management strategy

Foundations Help with prototypingDevelopment- Construction Iteration

Assess Development Iteration


Help with creating user menu and maintenance information

3.2 SkillsTable 10: Team Members Role and Skills

Team members Role SkillsRitika Khurana Project Manager <Current skills:>

< Required skills:>Ashwini Ramesha OCE <Current skills:>

< Required skills:>Chen Li Requirements Engineer <Current skills:>

< Required skills:>Sowmya Sampath Software Architect <Current skills:>

< Required skills:>Siddhesh Rumde Life Cycle Planner <Current skills:>

< Required skills:>Jiashuo Li Prototyper <Current skills:>

< Required skills:>Yun Shao Feasibility Analyst <Current skills:>

< Required skills:>Farica Mascarenhas IV&V Current skills: Shell scripting,

Perl, Java, C++, SQL, AutoShell, HTML, JavaScript

Required skills: .NET

6

4.Approach

4.1 Monitoring and Control

4.1.1 Closed Loop Feedback Control The weekly progress reports identify the activities undertaken and completed in the week.

Project Plan provides the baseline for the activities. Any deviation from this baseline is identified, its severity is analyzed and action, as appropriate, is taken

The progress reports records planned and actual efforts and tasks spent. If the difference is outside acceptable limits, then the Project Manager can initiate action by calling in team meeting and discuss this issue and follow up measures and tasks for next week

The weekly risk analysis ensures that all risks identified have a mitigation plan. This will help to stay on track with the project schedule

4.1.2 Reviews

No other reviews activities are being used to control the project.

4.2 Methods, Tools and FacilitiesTable 11: Required tools

Tools Usage ProviderMicrosoft Word 2012

Constructs documents for all artifacts USC

Microsoft Project 2003

Creates Gantt charts for Progress reports and LCP USC

Microsoft PowerPoint 2012

Creates presentation for client meeting and ARB reviews USC

Mozilla Firefox and Google Chrome

Downloads course material and medium for communication among stakeholders

USC

WikiWinWin tool Facilitates and supports Win-Win negotiation USCSubversion Implements version control system to maintain artifact

integrity and traceabilityOpen Source

Microsoft Visual Studio 2012

Build .NET framework USC

7

5. ResourcesIn this section, we present the project effort and schedule estimation of the project using COCOMO II.

The following conditions were used to estimate the cost of our system, Mission Science iRobot1. This project has no budget for our development efforts. However, the client must provide

some necessary equipment for development and testing, e.g. iRobot Machine2. The duration of the project is 24 weeks, 12 weeks in CS577a and 12 weeks in CS577b3. There are 8 developers4. There is only 1 module

i. Module 1: Drag and drop GUI that implements functions to control the robot5. This GUI will be developed with .NET framework

The following is module listed in the system and its estimated size with Source Lines of Code (SLOC)

Table 12: Module lists and SLOC

No. Module Name Brief Description SLOC REVL1 Drag and Drop GUI Provide fun UI for end-users to control

the robot3,000 0.0%

The following is COCOMOII Scale Drivers and rationales of choosing the values.

Table 13: COCOMOII Scale Drivers

Scale Driver Value RationalePREC HIGH The development team will have considerable knowledge of

project requirements and considerable experience in working with related system. There will be some need for innovative data processing architecture

FLEX HIGH The system will need to considerably conform to pre-established requirements from the client and external interface specifications

RESL NOMINAL Critical risk items, schedule, budget and internal milestone will need to be identified. There will be considerable uncertainty in hardware compatibility

TEAM VERY HIGH

There will be strong consistency of stakeholder objectives and cultures, and strong ability and willingness of stakeholders to accommodate other stakeholder’s objectives. There will be considerable experience of stakeholders in operating as a team

PMAT NOMINAL The development team will follow ICSM-EPG, in which the processes are defined and repeatable but the result may not be consistent, CMM Level 2

8

The following is COCOMOII Cost Drivers of Module 1 and rationales of choosing the values.

Table 14: COCOMOII Cost Drivers of Module 1

Cost Driver Value RationaleRELY NOMINAL This module has low, easily recoverable losses. Hence it’s

nominal.DATA LOW The ratio of bytes in the database to SLOC in the program is less

than 10.DOCU NOMINAL Because the development process follows ICSM, the document

for life-cycle needs is normal.CPLX LOW It contains use of simple graphic user interface (GUI) builders.RUSE NOMINAL It’s intended to be reused across future project.TIME NOMINAL The time expected to program complex instruction set for the

iRobot is reduced by 50%.STOR NOMINAL There is no impact to storage with the new system.PVOL LOW Major change in iRobot machine or the platform computer need

to take place every 12 months; minor change every 1 month.ACAP VERY

HIGHThe analysts have the ability to analyze, design, communicate, and cooperate very well.

PCAP VERY HIGH

Developers are capable, efficient and thorough. They are able to communicate and cooperate very well.

PCON NOMINAL We have 8 team members in CSCI 577a and 8 team members in CSCI 577b that are suitable for our project sizing.

APEX NOMINAL The average experience of the team members for this GUI is about one year.

LTEX NOMINAL The development team plans to develop the GUI with .NET framework. The tool for programming is Visual Studio. Therefore, the language and tool experience is nominal because team members have at least a year experience with these languages and tools.

PLEX LOW Although, all developers have experience in graphic user interfaces, this module implements GUI to control a machine for which our developers have less experience.

TOOL LOW The software tools development team plan to use is just simple, frontend, backend CASE, and supporting little integration.

SITE VERY HIGH

In CSCI 577a, 7 of 8 team members are on-campus students. In CSCI 577b, 7 of 8 team members are on-campus students; only one team member is an off-campus student. Additionally, we use wideband electronic communication and occasional videoconference.

SCED NOMINAL The schedule is fixed for 12 weeks in Fall semester and 12 weeks in Spring semester.

9

The following is the result from COCOMOII estimation based on Scale Drivers and Cost Drivers discussed above.

Figure 1: COCOMO Estimation Result

The form of schedule our project uses is the Independent Variable (SAIV) strategy, 24–week schedule drives development of a set of top priority core capabilities. Therefore, the estimates show the effort required for the project.

According to COCOMO II Estimates for CSCI577, one team member effort = 0.8 COCOMO II person months. The pessimistic effort from the COCOMO estimation above is 4.40, so the total team members need for this project = 4.40/0.8 = 5.5

Since we have 8 people from this effort estimate, we would be able to finish the project in time.

10

6. Iteration Plan6.1 Plan<< Provide a high-level overview of the content of the given iteration. Indicate which Life cycle milestones will be addressed. >>

6.1.1 Capabilities to be implemented

<< For the milestone identified above, identify the capabilities that will be implemented in the upcoming iteration. Identify the features, requirements or use–cases that are being developed (implemented, tested, etc.) for this iteration. Each component should be accounted for in at least one iteration. All requirements should be implemented and tested (or re-negotiated) by the completion of all the iterations. Be mindful of implementation dependencies. Document complex dependencies and communicate them to the appropriate development staff. >>

Table 15: Construction iteration capabilities to be implemented

ID Capability Description Priority Iteration

< ID > < Capability > < comments > <value> <value>

6.1.2 Capabilities to be tested

<< For the milestone identified above, identify the capabilities that will be tested in the upcoming iteration.

Identify the software features and combinations of software features to be tested this iteration. This may also include non-functional requirements or extra-functional requirements, such as performance, portability, and so forth.

Additionally you may need to test every requirement listed in the WinWin Agreements DC package, non-requirement component features such as COTS capabilities and quality, API functionality, etc. >>

Table 16: Construction iteration capabilities to be tested

ID Capability Description Priority Iteration

< ID > < Capability > < comments > <value> <value>

11

6.1.3 Capabilities not to be tested

<< Identify notable features, and significant combinations of features, which will not be tested this iteration and why (e.g. a given feature uses a feature which will be implemented in following iteration). >>

6.1.4 CCD Preparation Plans

<< Identify the clients and other users who will be involved in the Core Capability Drive-through, the usage scenarios that it will support, and the specific CCD preparation plans and milestones. These may include

- user context-setting- site preparation dry runs, - feedback forms, and - CCD risk management plans. >>

6.2 Iteration Assessment

6.2.1 Capabilities Implemented, Tested, and Results

<< Describes, in brief, the capabilities that were implemented and the test results. The capabilities implemented and tested do not necessarily need to match the ones listed in section 6.1 because some capabilities may have been pushed to the next iteration. >>

Table 17: Capabilities implemented, tested, and results

ID Capability Test Case Test Results If fail, why?< ID > < Capability > < TC-XX > Pass/Fail < comments >

…

6.2.2 Core Capabilities Drive-Through Results

<< Briefly summarize the feedback you received from your client(s). You need to be specific enough to cover the critical capabilities or scenarios that were discussed, demoed, or shown. Your descriptions MUST, but not limited to, cover the following areas:

Positive feedbacks Improvements needed/suggested Changes to‐be considered (Reprioritized capabilities, requirements, GUI, etc.) Risks (New risks introduced, risks mitigated, etc.)

12

Note: Make sure to be specific to the capabilities shown/demonstrated/driven-through.Simply stating that the clients liked the capabilities is not sufficient. >>

6.3 Adherence to Plan<< Describe how well the iteration ran according to plan. Was it on budget and on time? Is there any uncertainty in the Software Development Status? Provide some insight to avoid mistakes for future iterations. >>

13

Documents

1€¦ · Web viewFarica Mascarenhas IV&V ... Tools Usage Provider Microsoft Word 2012 Constructs documents for all artifacts USC Microsoft Project 2003 Creates Gantt