LCP_LCA_F07a_T18_v2.0

Document Sample
LCP_LCA_F07a_T18_v2.0 Powered By Docstoc
					Life Cycle Plan (LCP)                                    version 2.0




                Life Cycle Planning (LCP)

                                      EZSIM II


                                      Team 18


                  Arpit Shah                           Project Manager

                 Nirav Shah                Requirement Analyst and Assistant Shaper

                 Chintan Rita                            UML Modeler

                 Amap Bhat                             System Architect

               Harita Bhavsar                        Prototype Developer

                 Nitin Gupta                          Feasibility Analyst

                 Dinesh Iyer                                II V & V




                                                        Date: 11/28/07


LCP_LCA_F07a_T18_v2.0           -1-              Version date: 11/28/07
Life Cycle Plan (LCP)                                          version 2.0




Version History
Date       Author       Version      Changes made                       Rationale
10/17/07   Harita       1.0          Original LCP                       Document for the LCO Draft
           Bhavsar
10/24/07   Harita       1.01         Correction made in Section 1       Document for LCO ARB
           Bhavsar,
           Arpit Shah
10/29/07   Harita       1.10         Changes made in Section 2,3,4      Feedback from LCO ARB
           Bhavsar,
           Amap Bhat
11/28/07   Harita       2.0          Section 4.1.5, 4.3, 4.4 added      Document for LCA Draft
           Bhavsar                   Changes made in section 2,3,4
                                      to focus on the construction
                                      phase
                                     COCOMO estimate changed




LCP_LCA_F07a_T18_v2.0          -2-                     Version date: 11/28/07
Life Cycle Plan (LCP)                                                                                     version 2.0




Table of Contents

VERSION HISTORY ............................................................................................................................. 2

TABLE OF CONTENTS ......................................................................................................................... 3

TABLE OF TABLES .............................................................................................................................. 5

TABLE OF FIGURES ............................................................................................................................ 6

1.     INTRODUCTION ........................................................................................................................ 7

     1.1.      STATUS OF THE LCP DOCUMENT.................................................................................................... 7

     1.2.      ASSUMPTIONS ............................................................................................................................ 7

     1.3.      REFERENCES............................................................................................................................... 7

2.     MILESTONES AND PRODUCTS ................................................................................................... 9

     2.1.      OVERALL STRATEGY ..................................................................................................................... 9

     2.2.      PHASES ..................................................................................................................................... 9

     2.3.      PROJECT DELIVERABLES .............................................................................................................. 13

       2.3.1.          Engineering Stage (includes Inception and Elaboration phase) .................................. 13

       2.3.2.          Production Stage (includes Construction and Transition phase) ................................. 16

3.     RESPONSIBILITIES ................................................................................................................... 18

     3.1.      OVERALL SUMMARY .................................................................................................................. 18

3.2.        BY PHASE/ STAGE ............................................................................................................... 21

4.     APPROACH ............................................................................................................................. 26

     4.1.      MONITORING AND CONTROL....................................................................................................... 26

       4.1.1.          Closed loop feedback control ...................................................................................... 26

       4.1.2.          Reviews ........................................................................................................................ 26

       4.1.3.          Status Reporting .......................................................................................................... 27

       4.1.4.          Risk Identification ........................................................................................................ 28

       4.1.5.          Project Communication ............................................................................................... 29

     4.2.      METHODS TOOLS AND FACILITIES ................................................................................................. 29


LCP_LCA_F07a_T18_v2.0                                   -3-                                 Version date: 11/28/07
Life Cycle Plan (LCP)                                                                              version 2.0



     4.3 CONFIGURATION MANAGEMENT ......................................................................................................... 30

        4.3.1 Product Element Identification ............................................................................................ 30

        4.3.2 Configuration Change Management ................................................................................... 32

        4.3.3 Project Library Management ............................................................................................... 33

        4.3.4 Configuration Status Management ..................................................................................... 35

5.      RESOURCES............................................................................................................................. 35




LCP_LCA_F07a_T18_v2.0                                -4-                              Version date: 11/28/07
Life Cycle Plan (LCP)                                                                     version 2.0




Table of Tables

Table 1: Artifact deliverable in Engineering Stage .................................................................. 14

Table 2: Artifact deliverable in Production Stage.................................................................... 16

Table 3: Stakeholder’s Responsibility during each phase ....................................................... 18

Table 4: Developer’s responsibilities during Inception phase ................................................. 21

Table 5: Developer’s responsibilities during Elaboration phase ............................................. 22

Table 6: Developer’s responsibilities during Construction phase ........................................... 23

Table 7: Developer’s responsibilities during Transition phase................................................ 23

Table 8: Critical stakeholders, their category and organization for Engineering Stage .......... 24

Table 9: Critical stakeholders, their category and organization for Production Stage ........... 25

Table 10: Risk Assessment ....................................................................................................... 28

Table 11: Tools and their usage............................................................................................... 29

Table 12: Product Elements..................................................................................................... 30

Table 13: Personnel Involved in Configuration Management................................................. 35

Table 14: Values for Scale Drivers and their rationale ............................................................ 37

Table 15: COCOMO II Cost Drivers and rationale for their values .......................................... 40




LCP_LCA_F07a_T18_v2.0                           -5-                           Version date: 11/28/07
Life Cycle Plan (LCP)                                                                   version 2.0



Table of Figures
Figure 1: Project Plan Screenshot 1 ......................................................................................... 10

Figure 2: Project Plan Screenshot 2 ......................................................................................... 11

Figure 3: Project Plan Screenshot 3 ......................................................................................... 12

Figure 4: Project Plan Screenshot 4 ......................................................................................... 13

Figure 5: Configuration Change Management ....................................................................... 32

Figure 6 : Directory Structure of the Configuration Items ...................................................... 34

Figure 7: Estimation Overview for EZSIM II without use of GME ............................................ 36

Figure 8: Scale Factors for EZSIM II ......................................................................................... 36

Figure 9: Cost Drivers for Meta model module ....................................................................... 38

Figure 10: Cost Drivers for Interpreter module....................................................................... 39

Figure 11: Schedule variable for EZSIM II ................................................................................ 39

Figure 12: Snapshot of Project ................................................................................................ 42




LCP_LCA_F07a_T18_v2.0                          -6-                           Version date: 11/28/07
Life Cycle Plan (LCP)                                     version 2.0




    1. Introduction


    1.1.     Status of the LCP Document


The purpose of Life Cycle Plan Document is to provide in depth view of the
process that will be followed during the course of development of EZSIM II. After
LCO ARB, the win win conditions for EZSIM II have been renegotiated. The
content of this document are in congruence with the renegotiated win win
requirements .No major risks other than that of mentioned DART are identified
and referenced in this document. The version of this document is 2.0 modified for
LCA Draft and it covers sections such as project milestones, stakeholder
responsibilities, risks analysis and control/monitoring mechanisms, effort and
schedule estimate, specified in Lean MBASE Guidelines version 1.9. This
document mainly focuses on Construction phase and Transition phase of EZSIM II
to be conducted during spring’08.




    1.2.    Assumptions


In order to follow the process depicted in LCP, following assumptions are made
for EZSIM II.

       Schedule for the project is for 24 weeks(12 weeks in 577a and 12 weeks
        in 577b)

       There can not be major changes in the requirements renegotiated after
        LCO ARB.

       No monetary investments are required for the development of EZSIM II.

       Client will hire third party maintainer for maintenance and support after
        the project has been delivered to them.

       Client and IIV & V person will review each step during the progress of the
        EZSIM II and provide feedback for required modifications.

       Source code of EZSIM in C is available to developer team for their
        understanding of flow.




    1.3.    References


LCP_LCA_F07a_T18_v2.0          -7-                Version date: 11/28/07
Life Cycle Plan (LCP)                                 version 2.0



LeanMBASE Version 1.9 Templates for LCP

http://greenbay.usc.edu/csci577/fall2007/site/guidelines/LeanMBASE_v1.9_temp
lates_for_LCP.doc

Fall 2006 team websites:

http://greenbay.usc.edu/csci577/fall2006/projects/team15

http://greenbay.usc.edu/csci577/fall2006/projects/team03

Team 18 Project Website

http://greenbay.usc.edu/csci577/fall2007/projects/team18

Win Win Report

http://greenbay.usc.edu/csci577/fall2007/projects/team18/team18a/lco/WWW_L
CO_T18_V1.0.doc




LCP_LCA_F07a_T18_v2.0       -8-               Version date: 11/28/07
Life Cycle Plan (LCP)                                    version 2.0




    2. Milestones and Products


    2.1.    Overall Strategy


Overall strategy being used for this project is Schedule as Independent Variable
(SAIV).When using this paradigm software development is downsized and minor
features are dropped in order to meet the schedule. The reason for following
SAIV for EZSIM II is to stick to given time schedule and produce all the
deliverables in given deadline is one of the most important criteria for successful
completion of EZSIM II. With this strategy, team will build all the essential
capabilities first and then add other low priority requirements as time permits.
The time schedule for this project is of 24 weeks which can be divided into two
parts: 12 weeks during 577a and 12 weeks during 577b.

The developer team has agreed upon using RUP (Rational Unified Process) model
as the process model for the life cycle of the project. RUP is iterative software
development process model based on spiral model. Using this model we will
increasingly implement detailed elaboration of EZSIM II’s definition, which aptly
suits the requirements of the project.

The development approach to be used for EZSIM II is COTS based development.
Developer team will be using GME (Generic Modeling Environment) for the
development of front end of EZSIM II which will be integrated with EZSIM I which
will act as simulation engine.




    2.2.    Phases


Following link contains the detailed project plan for EZSIM II including
Construction and Transition phase of 577b.

http://greenbay.usc.edu/csci577/fall2007/projects/team18/team18a/lca/MSP_LC
A_F07a_T18.mpp



Following are the screenshots showing details of Construction and Transition
phase of EZSIM II



LCP_LCA_F07a_T18_v2.0          -9-               Version date: 11/28/07
Life Cycle Plan (LCP)                                         version 2.0




                        Figure 1: Project Plan Screenshot 1




LCP_LCA_F07a_T18_v2.0       - 10 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                         version 2.0



                        Figure 2: Project Plan Screenshot 2




LCP_LCA_F07a_T18_v2.0       - 11 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                         version 2.0




                        Figure 3: Project Plan Screenshot 3




LCP_LCA_F07a_T18_v2.0       - 12 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                           version 2.0




                          Figure 4: Project Plan Screenshot 4




    2.3.    Project Deliverables


The artifacts to be delivered at the end of engineering stage and production stage
are listed below. Along with the artifact name, their due dates, their format and
delivery medium is also specified.



    2.3.1. Engineering Stage (includes Inception and Elaboration phase)



LCP_LCA_F07a_T18_v2.0         - 13 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                            version 2.0



                        Table 1: Artifact deliverable in Engineering Stage
Artifacts                        Due Date              Delivery              Format
                                                       Medium

Progress Report                  Weekly                Soft copy             .xls format

Weekly MS project plan           Weekly                Soft copy             .mpp format

Effort Report                    Every Monday          Soft copy             On 577a course
                                 before midnight                             website

LCO Milestones

OCD Early Section                9/24/2007             Soft copy             .doc, .pdf

Prototype                        10/05/2007            Soft copy             .doc, .pdf

Evaluation of Early OCD          10/05/2007            Soft copy             .doc, .pdf

Wiki WinWin Report               10/08/2007            Soft copy             .doc, .pdf

LCO Core - OCD                   10/10/2007            Soft copy             .doc, .pdf

LCO Core - SSRD                  10/10/2007            Soft copy             .doc, .pdf

LCO Core - SID                   10/10/2007            Soft copy             .doc, .pdf

LCO Draft - OCD                  10/17/2007            Soft copy             .doc, .pdf

LCO Draft - SSRD                 10/17/2007            Soft copy             .doc, .pdf

LCO Draft - SSAD                 10/19/2007            Soft copy             .doc, .pdf

LCO Draft - LCP                  10/17/2007            Soft copy             .doc, .pdf

LCO Draft - FRD                  10/17/2007            Soft copy             .doc, .pdf

LCO Draft - SID                  10/17/2007            Soft copy             .doc, .pdf

LCO Draft - UML Model            10/17/2007            Soft copy             .emx
File

LCO Package – OCD                10/29/2007            Soft copy             .doc, .pdf

LCO Package – SSRD               10/29/2007            Soft copy             .doc, .pdf

LCO Package - SSAD               10/29/2007            Soft copy             .doc, .pdf

LCO Package – LCP                10/29/2007            Soft copy             .doc, .pdf



LCP_LCA_F07a_T18_v2.0               - 14 -                Version date: 11/28/07
Life Cycle Plan (LCP)                         version 2.0



LCO Package – FRD       10/29/2007   Soft copy          .doc, .pdf

LCO Package - SID       10/29/2007   Soft copy          .doc, .pdf

LCA Milestones

LCA Draft – OCD         11/28/2007   Soft copy          .doc, .pdf

LCA Draft – SSRD        11/28/2007   Soft copy          .doc, .pdf

LCA Draft – SSAD        11/28/2007   Soft copy          .doc, .pdf

LCA Draft – LCP         11/28/2007   Soft copy          .doc, .pdf

LCA Draft - FRD         11/28/2007   Soft copy          .doc, .pdf

LCA Draft - SID         11/28/2007   Soft copy          .doc, .pdf

LCA Package – OCD       12/10/2007   Soft copy          .doc, .pdf

LCA Package- SSRD       12/10/2007   Soft copy          .doc, .pdf

LCA Package – SSAD      12/10/2007   Soft copy          .doc, .pdf

LCA Package - LCP       12/10/2007   Soft copy          .doc, .pdf

LCA Package – FRD       12/10/2007   Soft copy          .doc, .pdf

LCA Package - SID       12/10/2007   Soft copy          .doc, .pdf




LCP_LCA_F07a_T18_v2.0      - 15 -      Version date: 11/28/07
Life Cycle Plan (LCP)                                             version 2.0




    2.3.2. Production Stage (includes Construction and Transition phase)


                        Table 2: Artifact deliverable in Production Stage


Artifacts                       Due Date               Delivery             Format
                                                       Medium

Progress Report                 Weekly                 Soft copy            .xls format

Weekly MS project plan          Weekly                 Soft copy            .mpp format

Effort Report                   Every Monday           Soft copy            On 577a course
                                before midnight                             website

RLCA

RLCA Draft – OCD                2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – SSRD               2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – SSAD               2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – RSA                2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – LCP                2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – FRD                2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – SID                2/6/08*                Softcopy             .doc, .pdf

RLCA Draft – Quality            2/6/08*                Softcopy             .doc, .pdf
management plan

RLCA Draft – Iteration          2/6/08*                Softcopy             .doc, .pdf
Plan

RLCA Draft – Test Plan          2/8/08*                Softcopy             .doc, .pdf
and cases

RLCA Draft – Peer               2/8/08*                Softcopy             .doc, .pdf
review plan

RLCA Package                    2/13/08*               Softcopy             .zip file

IOC Working set #1              4/2/08*                Softcopy             .doc, .pdf


LCP_LCA_F07a_T18_v2.0               - 16 -                Version date: 11/28/07
Life Cycle Plan (LCP)                                     version 2.0



CCD Report                4/2/08*              Softcopy            .doc, .pdf

IOC Working set #2        4/2/08*              Softcopy            .doc, .pdf

Transition Phase

Transition Plan           4/21/08*             Softcopy,           .doc, .pdf
                                               Hardcopy

User Manual               4/21/08*             Softcopy,           .doc, .pdf
                                               Hardcopy

Support Plan              4/21/08*             Softcopy,           .doc, .pdf
                                               Hardcopy

Training material         4/21/08*             Softcopy,           .doc, .pdf
                                               Hardcopy

Regression test           6/5/08*              Softcopy,           .doc, .pdf
packages                                       Hardcopy

Packaged Tools and        6/5/08*              Softcopy,           .doc, .pdf
Packages                                       Hardcopy



*Due dates for the submission of artifacts in Construction and Transition phase
are subject to change as per the schedule defined for 577b for spring’08.




LCP_LCA_F07a_T18_v2.0         - 17 -             Version date: 11/28/07
Life Cycle Plan (LCP)                                                version 2.0




    3. Responsibilities

    3.1.    Overall summary


This section gives overview of what are the responsibilities of critical stakeholders
of EZSIM II during all the 4 phases (Inception, Elaboration, Construction, and
Transition) for the successful completion of project.



                 Table 3: Stakeholder’s Responsibility during each phase


                        Inception            Elaboration       Construction        Transition

End User-          Provide                   Review            Review              Participate in
                   success critical          prototypes        implemented         training
Represented        win conditions            and make          requirements.       sessions
by Jared           for EZSIM II.             sure that         Provide             organized by
Fortune(PhD        Negotiate                 prototype is      feedback about      developers.
Student)           conflicting win           according to      the                 Check the
                   conditions.               specified         implemented         review about
                   Provide review            requirements.     features.           user manual.
                   of LCO Package            Provide           Check the           Review the
                   documents.                corrections       correctness of      system as a
                   Participate in            for prototype     test case           whole and
                   Win Win                   if any. Review    results. Review     provide
                   Session and               LCA Package       RLCA Package        feedback
                   LCO ARB.                  documents         documents.          about
                                             and provide       Attend RLCA         system’s
                                             feedback.         ARB.                success and
                                             Attend LCA                            developers’
                                             ARB. Help                             efforts.
                                             providing test
                                             case data.

Client -           Provide basic             Monitor the       Review RLCA         Provide
                   understanding             progress of       Package. Make       support to
Dr. Ray            of current                project at        certain that        plan training
Madachy,           simulation                milestones of     progress of         session for
                   software                  this phase.       project is          the developed
Dr. Behrokh
                   EZPRO. Provide            Review            following right     system.
Khoshnevis
                   success critical          prototypes        track. Provide      Review the
                   win conditions            and provide       feedback on         system

LCP_LCA_F07a_T18_v2.0               - 18 -                    Version date: 11/28/07
Life Cycle Plan (LCP)                                              version 2.0



                   for EZSIM II          rectification if    RLCA Package.       performance
                   and negotiate         not according       Review test         once it is
                   them if any of        to specified        cases and test      deployed.
                   them clashed          requirements.       case results.       Provide
                   with win              Review              Attend RLCA         feedback
                   conditions of         documents for       ARB.                about success
                   other                 LCA package.                            of EZSIM II.
                   stakeholders.         Participate in
                   Actively              LAC ARB.
                   participate in        Provide data
                   Win Win               required for
                   sessions and          preparing test
                   LCO ARB.              cases. Provide
                   Review                required
                   documents of          information
                   LCO package           and support
                   and provide           for LCA
                   feedback on           milestone.
                   them.

Developers -       Grasp the             Prepare             Start               Deploy the
Team18             understanding         detailed            implementing        system to
                   of client’s           design for          high priority       user Plan
                   current               ESZIM II.           requirements        training
                   simulation            Determine top       of system. Plan     session for
                   software              n risks for the     tests during        users. Provide
                   EZPRO.                software and        and after           user manuals,
                   Understand            mitigation          implementation      support files
                   client’s              strategy for        of                  and test
                   requirements.         them .Prepare       requirements.       results for
                   Negotiate own         documents for       Integrate all       future use.
                   win conditions        LCA Package         the modules.
                   with that of          and                 Accommodate
                   other                 participate in      corrections
                   stakeholders          LCA ARB.            provided by
                   clashing win          Prepare             client on RLCA
                   conditions.           detailed            Package.
                   Prepare               prototype for       Check the
                   documents             EZSIM II            efficiency of
                   such as OCD,          keeping             the software.
                   SSRD, SSAD,           investigation
                   LCP, FRD, and         of top risks in
                   SID for LCO           consideration
                   Package.              and get
                   Prepare               feedback from


LCP_LCA_F07a_T18_v2.0           - 19 -                      Version date: 11/28/07
Life Cycle Plan (LCP)                                             version 2.0



                   Prototype and          client.
                   get client’s           Prepare test
                   feedback.              cases using
                   Participate in         information
                   Win Win                provided by
                   sessions and           client.
                   LCO ARB.

IIV & V –          Provide an             Provide an        Provide an          Review the
Dinesh Iyer        independent            independent       independent         functioning of
                   review and             review and        review and          system in
                   evaluation of          evaluation of     evaluation of       operational
                   LCO Package            LCA Package       RLCA Package        environment.
                   artifacts. Make        artifacts.        artifacts.          Make sure
                   sure that all          Suggest           Determine that      support
                   the artifacts of       correction in     construction is     documents
                   LCO Package            system design     following the       are in
                   are in                 if any. Make      development         accordance
                   consistency            sure all          process             with Lean
                   with Lean              artifacts are     decided during      MBase version
                   MBase version          in consistency    engineering         1.9
                   1.9 guidelines.        with Lean         stage. Make         guidelines.
                   Attend Win Win         MBase version     sure all the        Provide an
                   sessions and           1.9               artifacts are in    independent
                   LCO ARB.               guidelines.       consistency         review of
                                          Attend LCA        with Lean           developers.
                                          ARB.              MBase version
                                                            1.9 guidelines.
                                                            Attend RLCA
                                                            ARB.

Maintainer-        N/A                    N/A               N/A                 Understand
TBD by                                                                          how system
client                                                                          works.
                                                                                Participate in
                                                                                training
                                                                                sessions
                                                                                arranged by
                                                                                Developer
                                                                                team. Provide
                                                                                support to
                                                                                end user and
                                                                                client
                                                                                whenever a
                                                                                bug is found


LCP_LCA_F07a_T18_v2.0            - 20 -                    Version date: 11/28/07
Life Cycle Plan (LCP)                                            version 2.0



                                                                               or error arises
                                                                               in the
                                                                               developed
                                                                               system.




    3.2. By Phase/ Stage

               Table 2: Developer’s responsibilities during Inception phase


Name                Role                    Primary Responsibility     Secondary Responsibility

Arpitkumar          Project Manager         Formalize interface        Contribute towards
Shah                                        specifications. Identify   system requirements
                                            Business process           specification and
                                            Develop Detailed risk      operational concept
                                            analysis and
                                            mitigation plan.

Nirav Shah          Requirement             Build system               Aide prototype
                    Analyst                 requirements               developer
                                            specification

Chintan Rita        UML Modeler             Construct accurate         contribute towards
                                            operational concept.       system requirements
                                            Prepare UML Diagrams       specification
                                            for system

Amap Bhat           System                  Prepare architectural      Contribute towards
                    Architecture            sketches and plan.         system requirements
                                                                       specification and
                                                                       operation concept.

Harita Bhavsar      Prototype               Build user interface       Contribute towards
                    Developer               prototype (GUI             system requirements
                                            screenshots based on       specification.
                                            UML diagrams)

Nitin Gupta         Feasibility             Collaborate between        Contribute towards
                    Analyst                 system architecture        system requirements
                                            and plan’s sketches        specification and
                                            and prototype              operational concept


LCP_LCA_F07a_T18_v2.0              - 21 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                            version 2.0



                                            development



              Table 5: Developer’s responsibilities during Elaboration phase



Name                Role                    Primary                    Secondary
                                            Responsibility             Responsibility

Arpit Shah          Project Manager         Prepare test plan          Aide system architect
                                                                       for ARB review

Nirav Shah          Requirement             Refine interface           Aide system architect
                    Analyst                 specifications, get        for ARB review
                                            feedback from clients

Chintan Rita        UML Modeler             Review design and          Collaborating with other
                                            aide in ARB review         team members for
                                            preparations               building a better
                                                                       prototype

Amap Bhat           System                  Perform 2nd iterative      Collaborate with other
                    Architecture            refinement of              team members for
                                            architecture and           feedback on system
                                            present them to ARB        architecture build during
                                                                       inception phase

Harita Bhavsar      Prototype               Refine and\or rebuild      Collaborating with other
                    Developer               prototype to               team members for
                                            investigate risks, after   building a better
                                            getting feedback from      prototype
                                            clients and team
                                            members during
                                            inception phase

Nitin Gupta         Feasibility             Review design and          Collaborating with other
                    Analyst                 help and risk and GUI      team members for
                                            prototype being            building a better
                                            developed                  prototype




LCP_LCA_F07a_T18_v2.0              - 22 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                           version 2.0



             Table 6: Developer’s responsibilities during Construction phase


Name                Role                  Primary                     Secondary
                                          Responsibility              Responsibility

TBD                 Project               Refine design based         Help with performing
                    Manager-              on prototypes and           reviews
                    Programmer 1          tailor it to fit client
                                          vision of the product


TBD                 Programmer 2          Implement Meta              Implement design and
                                          Model for the system        build wrappers

TBD                 Programmer 3,         Integrate Meta model        Help in preparing
                    Tester 1              with interpreter and        various test cases.
                                          write the code to
                                          integrate EZSIM I with
                                          developed code

TBD                 Technical Writer,     Write various technical     Perform quality
                    Quality Manager       manuals and help            management as the
                                          manual.                     project proceeds.

TBD                 Tester 2              Perform tests using         Integrate product
                                          test data and               modules
                                          simulation test run
                                          environment

Harita Bhavsar      Configuration         Perform and setup           Aide tests
                    Manager               reviews of
                                          implemented modules



               Table 7: Developer’s responsibilities during Transition phase


Name                Role                  Primary                     Secondary
                                          Responsibility              Responsibility

TBD                 Project               Prepare Help files,         Help in deployment of
                    Manager-              user manual                 system.
                    Programmer 1




LCP_LCA_F07a_T18_v2.0            - 23 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                                version 2.0



TBD                    Programmer 2            Provide training to end      Prepare Help files, User
                                               user.                        manual.

TBD                    Programmer 3,           Prepare transition           Prepare regression test
                       Tester 1                documents                    packages

TBD                    Technical Writer,       Prepare support              Aid in providing training
                       Quality Manager         documents, training
                                               manuals

TBD                    Tester 2                Prepare regression           Provide training to end
                                               test packages.               user.

Harita Bhavsar         Configuration           Provide deployment           Prepare transition
                       Manager                 support                      documents



Note: For the Construction phase and Transition phase, Developer team is required to have
the knowledge of GME (Generic Modeling Environment).



  Table 8: Critical stakeholders, their category and organization for Engineering Stage


Stakeholder                Category                   Organization

Jared Fortune              End User                   University of Southern California

Dr. Ray Madachy, Dr.       Client                     University of Southern California
Behrokh Khoshnevis

Arpit Shah                 Developer                  Computer Science Department, University of
                                                      Southern California

Nirav Shah                 Developer                  Computer Science Department, University of
                                                      Southern California

Chintan Rita               Developer                  Computer Science Department, University of
                                                      Southern California

Amap Bhat                  Developer                  Computer Science Department, University of
                                                      Southern California

Harita Bhavsar             Developer                  Computer Science Department, University of
                                                      Southern California




LCP_LCA_F07a_T18_v2.0                 - 24 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                         version 2.0



Nitin Gupta             Developer               Computer Science Department, University of
                                                Southern California

Dinesh Iyer             IIV & V                 Computer Science Department, University of
                                                Southern California

Maintainer              TBD                     TBD




   Table 9: Critical stakeholders, their category and organization for Production Stage


Stakeholder             Category                Organization

Jared Fortune           End User                University of Southern California

Dr. Ray Madachy,        Client                  University of Southern California
Dr. Behrokh
Khoshnevis

TBD                     Project Manager-        Computer Science Department, University
                        Programmer 1            of Southern California

TBD                     Programmer 2            Computer Science Department, University
                                                of Southern California

TBD                     Programmer 3, Tester    Computer Science Department, University
                        1                       of Southern California

TBD                     Technical Writer,       Computer Science Department, University
                        Quality Manager         of Southern California

TBD                     Tester 2                Computer Science Department, University
                                                of Southern California

Harita Bhavsar          Configuration           Computer Science Department, University
                        Manager                 of Southern California

Maintainer              Project Manager-        TBD
                        Programmer 1




LCP_LCA_F07a_T18_v2.0              - 25 -             Version date: 11/28/07
Life Cycle Plan (LCP)                                     version 2.0



    4. Approach
    4.1.    Monitoring and Control


For the consistent progress of the project we perform the following activities.

       Weekly progress report

       Weekly effort report

       Weekly MS project plan

       Weekly team meeting: The team meets twice a week for the document
        review and for the correction if any to be made to the existing document.
        We also discuss the information to be added to the different documents.
        The team discuss about where will be the project after two weeks.

       Interaction between team and the client: Team and client discuss about
        the current work done by the team and discuss about the change if
        required to any of the work and also discuss about the further activities to
        be done.

       Client meeting notes

       To get the perfect estimation we use COCOMO II.

       Team interacts with the DEN student to be in sync for the proper
        execution of the project.

    4.1.1. Closed loop feedback control


During the team meeting which also includes the IV & V developer and client
some times, we get the feedback from the each and every person associated with
the project and try to resolve the common errors in the current documents. This
helps the team to be consistent and also helps for the project’s smooth progress.
In this meeting we talk about the risk and its mitigation plan. We also discuss the
actions taken to mitigate the previous high risks and the new risk that has
evolved newly. If necessary we also talk about the Project manager is responsible
for carrying out this activity.

    4.1.2. Reviews


       Internal Review: Before streamlining any document each team member
        reviews the document for its correctness and for its format. This review



LCP_LCA_F07a_T18_v2.0          - 26 -              Version date: 11/28/07
Life Cycle Plan (LCP)                                      version 2.0



        makes sure that the document is up to the mark and is what required by
        the 577a course.



       The documents are also reviewed by the DEN student, Dinesh Iyer. This
        ensures the quality of the information present in the document.

        The major documents which have been reviewed till now are:

               Early OCD

               Initial Prototype

               LCO Core documents

               LCO Draft documents



       Architectural Reviews are performed in presence of CSCI 577 faculties,
        Clients, TAs and Development team. Two architectural reviews are
        performed during 577a.These reviews focuses on correctness of artifacts,
        software process being followed , system requirements and system
        design:

        Following reviews are performed during the Inception and Elaboration
        phase in 577a:

               Life Cycle Objective ARB(Architectural Review Board)

               Life Cycle Architecture ARB(Architectural Review Board)

        Following reviews are performed during the Construction and Transition
        phase in 577b:

               Rebase-line Life Cycle Architecture ARB(Feb 12,2008)

               Transition Readiness Review(Apr 15-16, 2008)

               Release Readiness Review(May 5-6, 2008)

    4.1.3. Status Reporting
        For the status of the project we perform the following activities:

           Weekly progress report

           Weekly project plan.

           Client meeting notes


LCP_LCA_F07a_T18_v2.0           - 27 -              Version date: 11/28/07
Life Cycle Plan (LCP)                                           version 2.0



            Team meeting

    4.1.4. Risk Identification


            For the EZSIM II, risk identification is performed on the weekly basis
             using DART tool. This helps to identify Top N risks for the software.
             The mitigation plan these Top N risks is also decided in put in action.
             Following table shows Top-3 risks for the EZSIM II.

         Top-3 Risks:

        Personal Continuity

        Schedule Overrun

        Programming Inexperience



                               Table 10: Risk Assessment


Rank            Risk Item                      Average                        Mitigation Plan

                                           Risk Exposure

                                      P         S          RE
                                      LOSS      LOSS

    1.   Personal Continuity:              9       5       45    As it is known that most of the
         Most of the team                                        team members will not continue
         members are not                                         for 577b, the team has done
         going to continue for                                   documentation very carefully. so
         577b                                                    that the new members who will
                                                                 join the team can easily get
                                                                 familiar with project and get the
                                                                 idea of how to proceed in project
    2.   Schedule Overrun: If              5       7       35
         the project overruns
         the scheduled time, it
         can not be counted as
         success
    3.   Programmer                        5       8       40    This Risk Exposure is Reducible.
         inexperience: The                                       The code for EZSIM 1 is available
         programming team                                        and can be studied along with
         does not have                                           programming practice sessions for
         extensive experience                                    the programming team prior to

LCP_LCA_F07a_T18_v2.0             - 28 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                          version 2.0



           of programming for                                   Construction phase. Moreover, any
           Simulation software.                                 feature that has complex coding
                                                                structure has to be dispensed if it
                                                                is not absolutely necessary and is
                                                                a gold-plating


    4.1.5. Project Communication
Team uses various methods to communicate with other team members, with IIV
& V student, with client and with faculties.

       Meetings: Team holds regular team meetings to get informed with the
        progress of the project. Team also holds client meeting according to
        client’s convenience when some clarification in regards of the project is
        needed.

       E-mails: Team uses e-mails for internal communication , to communicate
        with IIV&V student and client

       Team Website: Team website is used for getting easy access to
        deliverables prepared by team members.




    4.2.     Methods Tools and Facilities


                             Table 11: Tools and their usage


        Tool                                 Usage

LeanMBASE guidelines v 1.9                   Reference material for deliverables

LeanMBASE Templates v 1.9                    Reference material for deliverables

Twiki win win                                Win Win negotiation between client,
                                             developer and 577a staff.

COCOMO II v 2000.3                           Cost estimation

IBM Rational Software Modeler (UML           UML Modeling.
2.0)

Microsoft Office 2003                        Documentation, reports and
                                             presentation




LCP_LCA_F07a_T18_v2.0             - 29 -             Version date: 11/28/07
Life Cycle Plan (LCP)                                             version 2.0



Microsoft Project 2003                          Project plan

MS Visio 2003                                   Diagram and charts

Core FTP                                        Uploading document and artifacts to
                                                team website

DART                                            Risk assessment

Adobe Acrobat v 8.0                             Documentation

iCard System                                    Weekly effort report

Internet explorer v 6.0                         Viewing and uploading the data on
                                                team website and to surf internet for
                                                the reference.

GME (Generic Modeling Environment)              To develop the meta model




4.3 Configuration Management
Configuration management is the process of managing change in hardware,
software, firmware, documentation, measurements, etc. As change requires an
initial state and next state, the marking of significant states within a series of
several changes becomes important.

4.3.1 Product Element Identification

See Table for a listing of all product elements that will be tracked through the
configuration management plan and processes.

                               Table 12: Product Elements
                        Artifact                   Owner                   ID

               Operational Concept           Arpit Shah                OCD
               Description (OCD)

                       Prototype            Harita Bhavsar            -

               WikiWinWin Report             Dinesh Iyer               WWW

               System and Software           Nirav Shah                SSRD
               Requirements
               Definition (SSRD)




LCP_LCA_F07a_T18_v2.0               - 30 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                            version 2.0



                        Artifact                  Owner                    ID

               System and Software          Amap Bhatt                SSAD
               Architecture
               Description (SSAD)

                       UML Model           Chintan Rita              UML

               Life Cycle Plan (LCP)        Harita Bhavsar            LCP

               Feasibility Rationale        Nitin Gupta               FRD
               Description (FRD)

               Supporting                   Chintan Rita              SID
               Information Document
               (SID)

               Quality Management           Chintan Rita              QMP
               Plan

               Iteration Plan               Arpit Shah                IP

               Peer Review Plan             Nirav Shah                PRP

               Test Plan and Cases          Dinesh Iyer               TP

               Client Meeting Notes         Nitin Gupta               CMN

               Progress Reports             Amap Bhatt                PR

               IIV&V Review Forms           Dinesh Iyer               IIVV

               Quality Reports              TBD                       QR



The Naming convention for each project artifact is specified in Team Website
Setup Guidelines found at
http://greenbay.usc.edu/csci577/fall2007/site/guidelines/ProjectWebSiteGuidelin
eFall07Updated.pdf

The Naming convention used is:


ConfigurationID_Phase_SemesterYear(a/b)_T(TeamNo)_v(Version).FileExtension


Example:




LCP_LCA_F07a_T18_v2.0              - 31 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                                   version 2.0



The Filename OCD_LCO_F07a_T18_v1.1.doc means the item is OCD prepared
during LCO phase in Fall Semester of 2007 and course CS577a by Team 18 and
Version of the document is 1.1.

4.3.2 Configuration Change Management

                           Figure 5: Configuration Change Management

                                       Originator submitted
                                       a change request



                                 Submitted

                                        Evaluator performed
                                        impact analysis



                                                        CCB decided
                                 Evaluated              not to make
                                                                                 Rejected
                                                        the change

                                        CCB decided to
                                        make the change


                                                            Change was canceled;
                                 Approved                   back out of modifications


            Verification                Modifier has made
            failed                      the change and
                                        requested verification


                                                       Change was canceled;
                             Change Made               back out of modifications          Canceled
            No verification                 Verifier has
            required; Modifier              confirmed the
            has installed                   change
            modified work
            products
                                                                  change was canceled;
                                  Verified                        back out of modifications

                                            Modifier has
                                            installed modified
                                            work products


                                  Closed

LCP_LCA_F07a_T18_v2.0              - 32 -                        Version date: 11/28/07
Life Cycle Plan (LCP)                                     version 2.0



The Configuration Change Management include following the above steps in
Figure. The procedure shown above shows the steps performed when a change is
requested. When a change is requested, it is evaluated by Change Control Board
(CCB) which consists of Configuration Manager (CM), Project Manager (PM), the
development team, the clients and all other key stakeholders. If the change is
found infeasible, then it is not incorporated else if the change is found feasible
then the required change is made to the system. After a change is made, it is
verified. If the verification fails, the change is undone and re-done using different
approach, still if it is not proper the change request is cancelled. If the
verification of a change is successful, then the change is reflected on the system
and that change request is closed due to successful modification.

4.3.3 Project Library Management
The configuration items will be stored in the directory structure as shown in the
figure below. The root directory Team 18 will be made accessible through a
website where all versions of the configuration will be stored in the respective
directory depending on the phase as shown in the figure. The latest versions of
the documents can be known from the latest SID.




LCP_LCA_F07a_T18_v2.0          - 33 -              Version date: 11/28/07
Life Cycle Plan (LCP)                                                  version 2.0



                        Figure 6 : Directory Structure of the Configuration Items




LCP_LCA_F07a_T18_v2.0                  - 34 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                        version 2.0



4.3.4 Configuration Status Management
The personnel represented using project roles involved in configuration
management are:

               Table 13: Personnel Involved in Configuration Management
               Project Role                                 Responsibility

Quality Focal Point                         Configuration Manager

Webmaster of Team Website                   Maintaining the Website

Key Stakeholders                            Change Control Board (CCB)




    5. Resources

The COCOMO II has been used for the schedule and effort estimation of EZSIM
II. The estimated results are given in following link. For EZSIM II, we have
provided two effort and schedule estimations- one without using GME and
another with using GME.



The link for estimation of required efforts is following:

http://greenbay.usc.edu/csci577/fall2007/projects/team18/team18a/lca/COCOM
O_LCA_F07a_T18_v2.0.est




LCP_LCA_F07a_T18_v2.0          - 35 -               Version date: 11/28/07
Life Cycle Plan (LCP)                                                 version 2.0



                  Figure 7: Estimation Overview for EZSIM II without use of GME




                               Figure 8: Scale Factors for EZSIM II




LCP_LCA_F07a_T18_v2.0              - 36 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                          version 2.0



                   Table 14: Values for Scale Drivers and their rationale


Scale Driver            Value         Rationale

Precedentedness         Low           Many simulation based projects have been
                                      developed in industry but in CS577a few (or
                                      almost none) simulation related projects have
                                      been developed

Development             Nominal       Schedule and requirements allow only occasional
Flexibility                           relaxation

Architecture            Nominal       The architecture being used for the project has
/Risk Resolution                      proven its success but the nature of project
                                      makes it risky to be very sure about architecture
                                      success

Team Cohesion           Very High     Development team members are highly
                                      cooperative with each other and client also spares
                                      time for team meetings when required.

Process Maturity        Very Low      Organization (here Development team) is not
                                      CMM certified company




LCP_LCA_F07a_T18_v2.0               - 37 -              Version date: 11/28/07
Life Cycle Plan (LCP)                                          version 2.0



                        Figure 9: Cost Drivers for Meta model module




LCP_LCA_F07a_T18_v2.0            - 38 -                 Version date: 11/28/07
Life Cycle Plan (LCP)                                            version 2.0



                        Figure 10: Cost Drivers for Interpreter module




                          Figure 11: Schedule variable for EZSIM II




LCP_LCA_F07a_T18_v2.0            - 39 -                  Version date: 11/28/07
Life Cycle Plan (LCP)                                        version 2.0



             Table 15: COCOMO II Cost Drivers and rationale for their values
Driver       Value            Module                        Rationale
                              Name

Product

RELY      Low           All               High reliability is not required since the
                                          effect of losses due to incorrect results from
                                          software is low and easily recoverable.

DATA      Nominal       All               Moderate sized data are needed as input.

DOCU      Nominal       All               Documentation is right sized to life-cycle
                                          needs.

CPLX      High          Interpret         Control operations, data-management
                        Module            operations, and user interface management
                                          operations have high complexity for this
                                          module.

          Nominal       Meta Model        Simple control operations, Computational
                                          operations and user interface management
                                          operations are used for this module. So
                                          their complexity is nominal.

RUSE      Nominal       All               The software is required to be reused across
                                          program only.

Platform

TIME      Nominal       All               The software will not use more than or
                                          equal to 50% of available execution time.

STOR      Nominal       All               The software will not use more than or
                                          equal to 50% of available storage.

PVOL      Low           All               According to clients, the software will be
                                          used for more than 10 coming years (with
                                          out major changes in it after all the
                                          extended features are included in it).

Personnel

ACAP      Nominal       All                Analyst is not highly experienced person
                                          but have academic experience which may
                                          prove sufficient for the project.

PCAP      Nominal       All               Team from a programming perspective has
                                          moderate experience.

PCON      Very Low      All               Most of the students in development team
                                          are not going to continue for 577b. So


LCP_LCA_F07a_T18_v2.0            - 40 -               Version date: 11/28/07
Life Cycle Plan (LCP)                                    version 2.0



                                       annual personnel turnover is very
                                       low(personal turnover more than 48%/year)

APEX      Low           All            Development team doesn’t have experience
                                       more than 6 months in developing these
                                       kind of modules

LTEX      Nominal       All            Development team has academic experience
                                       of programming language that will be used
                                       for the development of the project

PLEX      Nominal       All            Development team has academic experience
                                       of developing windows platform specific
                                       application. This software is window specific
                                       application.

Project

TOOL      Nominal                      Development team would be using IDE for
                                       software development and Modeling tools
                                       for UML.

SITE      Nominal                       Software team mostly communicates
                                       through e-mails and phones. At times they
                                       communicate through WebEx meetings soon


Schedule

SCED      High                         The project needs to be finished on given
                                       deadline. Schedule cannot be stretched.




LCP_LCA_F07a_T18_v2.0         - 41 -              Version date: 11/28/07
Life Cycle Plan (LCP)                                          version 2.0




                              Figure 12: Snapshot of Project




Results of Effort Estimation for Construction phase:

       Using COCOMO II to determine how large team needed for 12 week fix
        schedule :

            o   Assuming 14 hours/week of dedicated efforts per person

            o   Assuming 10 weeks out of 12 weeks fill the construction phase in
                577b (72% of total effort estimate)

            o   Assuming 120 hours/person – month for COCOMO II estimate

       For 577b Construction phase, following are equivalent:

            o   1 577b team member effort = 14*10 = 144 hours

            o   1.67*(estimated COCOMO II person month) = 1.67* 120* 0.72
                =144 hours

       So now one 577b team members effort = 1.67 COCOMO II person months

       6 577b team members effort = 6*1.67 = 10 COCOMO II person months

    Calculation referred from
    http://greenbay.usc.edu/csci577/fall2007/site/coursenotes/ec/charts/ec-
    11.ppt

    Pessimistic effort estimation for team 18 = 9.4 person months (COCOMO
    Screenshots)

    The no. of members required = 9.4/1.67 = 5.6 ~ 6 members


LCP_LCA_F07a_T18_v2.0          - 42 -                  Version date: 11/28/07

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:14
posted:12/31/2011
language:
pages:42