Lifecycle Models V1

8/8/2019 Lifecycle Models V1

http://slidepdf.com/reader/full/lifecycle-models-v1 1/16

Q2 Quest for Quality

Q2 – Lifecycle Models

Page 1 of 16

WARNING: This document is uncontrolled unless viewed electronically from its original location. Where an

Uncontrolled document is used it is the responsibility of the person using it to ensure that it is the latest version.

Contents

1. Overview ....................................................................................................................................2

1.1 Objective ...............................................................................................................................2

1.2 Background ...........................................................................................................................2

1.3 Lifecycle models ...................................................................................................................2

1.4 Document Organization ........................................................................................................3

2. Glossary .....................................................................................................................................3

3. Modified Waterfall Model..........................................................................................................4

3.1 Model Representation ...........................................................................................................4

3.2 Tasks ....................................................................................................................................5

4. Incremental Model............................................................................................................ ........7

4.1 Model Representation ...........................................................................................................7

4.2 Tasks ....................................................................................................................................8

5. Maintenance Model.................................................................................................................11

5.1 Model Representation .........................................................................................................11

5.2 Tasks ..................................................................................................................................12

6. Test Automation ......................................................................................................................13

6.1 Model Representation .........................................................................................................13

6.2 Tasks ..................................................................................................................................15

This Document, constitutes and contains proprietary information of ExcelaCom Technologies and shall not be disclosed in whole or in part by Client to anythird party or to any employees of Client otherthan those who have a need to know such information, and shall not be duplicated or used by Client for any other purpose than to evaluate thisDocument.



Page 2 of 16



1. Overview

1.1 Objective

This document was developed with the objective of setting forth a clear understanding of eventsfor conducting software development activities within the Organization that are well-defined,understood, and implemented across all projects in a systematic and uniform manner. Thisdocument disseminates the software development and maintenance life cycles and processesthat foster the discipline and structure needed to enable projects to consistently and predictablyproduce and deliver high quality products and systems in a uniform way.

1.2 Background

This document was created out of a need to introduce all the lifecycle models that are currently in

practice, for consistency in understanding and usage. It will provide the following information:

• A clear process flow representation of any of the approved lifecycle models that a ProjectManager (PM) may wish to use for his/her project.

• The entry, tasks, verification & validation activities and the exit criteria.

1.3 Lifecycle models

The waterfall model is a popular version of the software development life cycle model for softwareengineering. Often considered the classic approach to the systems development life cycle, thewaterfall model describes a development method that is linear and sequential. Once a phase of development is completed, the development proceeds to the next phase and there is no turning

back. This model could be used by PM’s if the requirement is stable and fully known and nochanges are expected in the normal course of project’s life cycle.

The Incremental model is used for projects wherein one set of requirements is taken up at a timefor development, client feedback is obtained, and once all requirements are completed, theproject is closed. This is similar to keep on adding on what has been done before. This is thesubtle difference. In incremental you don't go back and refactor what you have done before, youonly focus on adding new features and not on improving existing ones.

Eg – Building a house.

If you have the full requirement of the house to be built, and start with building first a couple of rooms, refactor to add new rooms and go on till you complete the entire house, it is iterativemodel. In this case, the user of the house cannot use until the entire house is complete.

If you have a couple of rooms first built and then keep adding rooms (without changing theexisting rooms), then it is incremental model. In this case, the user can exist to stay in the existinghouse and keep doing his changes.

The Maintenance model is used for projects which are in production (live) environment and needsto be taken care in terms of any enhancements that may be required or defects that needs to befixed in the software.

The Test Automation model is used for projects where manual test cases are provided by theclient and the scope of the project involves only scripting the test cases to facilitate automation.



Page 3 of 16



Such projects do not involve the regular software development phases such as Requirements,Design and Construction.

The MVNO Testing model is used for projects where the scope involves only writing and manualexecution of test cases to support Mobile Virtual Network Operations. Such projects do notinvolve the regular software development phases such as Requirements, Design andConstruction.

Note: The PM chooses the appropriate life cycle, documents in the Project Management Planand any tailoring required can be adopted using the “Tailoring Guidelines” document provided.Tailoring is appropriately documented through the QA Engineer.

1.4 Document Organization

This document is arranged to provide an easy understanding of the lifecycle and the associatedactivities. A process is a set of tasks that have definite entry criteria, verification and validationactivities and exit criteria. This document is divided into the following two distinct components:

Component Description

Model Representation The process flow depicting the major activities in the life cyclemodel.

Tasks The tasks associated for the major activities with the associatedentry criteria, verification and validation activities and exit criteria

2. Glossary

Below is a glossary of terms and acronyms that are frequently used in this document.

Acronym / Term Definition

IT Information Technology

FRS Functional Requirements Specification

PIN Project Initiation note

PM Project Manager

PMP Project Management Plan

SM Senior Management

SOW Statement of Work

BRD/PRS/SRS Software Requirement Specification



Page 4 of 16



3. Modified Waterfall Model

3.1 Model Representation

SOWwithZeroLevel

Estimate

Project Planning

Requirements

Project Initiation

First Level Estimate

Design

Coding

Testing

Release

SecondLevel Estimate

(Revisit if reqd )

Feedback from any of the

phases to improve or fix theissues



Page 5 of 16



3.2 Tasks

Phase Task / Activity Entry Criteria

Verification &

Validation

Exit Criteria /

Output

SOWSOWpreparation

Proposal fromClient with zerolevel estimates

Review of SOW

SOW approved bySM and signed off with Client

Project Initiation

1. Preparationof PIN2. Invitestakeholders3. Conduct kick-off meeting

Approved SOW

ProjectInitiationMeeting withrepresentationfromstakeholders

1. Project initiationmeeting conducted.2. Projectdependenciesagreed upon bygroups.3. Meeting minutescirculated.

Project PlanningPreparation of PMP, & ProjectPlan

PINReview of PMP andProject Plan

Project plan, allsub-plans, Lifecycle model andtailoring guidelinesreviewed by QAand approved bySM

Requirements

BRD/PRS/SRDPreparation

BRD/PRS/SRDReview of BRD/PRS/SRS

BRD/PRS/SRDApproved by Clientand/or SM

System TestPlanning BRD/PRS/SRD

Review of

System TestPlan & Cases

System Test Plan

and Casesapproved by PM

First levelEstimation

EstimationPreparation

SOW

BRD/PRS/SRD

Review of Estimation

Estimationapproved by SM

Design

DesignPreparation

BRD/PRS/SRDReview of Designdocuments

Design documentsapproved by PM

Integration TestPlanning

Designdocuments

Review of IntegrationTest Plan &

Cases

Integration TestPlan and Casesapproved by PM

Second levelEstimation

EstimationPreparation /Revisit

DesignDocuments



DevelopmentCodepreparation

Designdocuments

Review of Code

Code approved byPM



Page 6 of 16



Unit TestPlanning

Designdocuments

Review of UnitTest Plan &

Cases

Unit Test Plan andCases approved by

PM

Testing

Preparation of UTCs

Unit Testing

UTCs

Code

Review of UTCs

Execution of Unit TestCases

Unit Test LogsUnit Test Results /Defect ReportUnit Tested Codeapproved by PM

Preparation of ITCs

Integration

Testing

ITCs

Unit TestedCode

Review of ITCs

Execution of IntegrationTest Cases

Integration TestLogsIntegration TestResults / DefectReport

Integration TestedCode approved byPM

Release

System TestingIntegrationTested Code (of all releases)

Execution of System TestCases

1.System TestResults / DefectReport2.System TestedCode approved byPM

Final ReleaseSystem TestedCode

Final Releaseaudit

Final Release Note



Page 7 of 16



4. Incremental Model


Yes

No

Increment

(1 to n)

Project Planning

First level estimate

Project Initiation

Requirements

Design

Coding

Testing

Release

SOW with zero level

estimate

Project Closure

Client Feedback Second level estimate



Page 8 of 16



4.2 Tasks

Phase

Task /

Activity Entry Criteria

Verification &

Validation

Exit Criteria /

Output

SOWSOWpreparation

Proposal fromClient with zerolevel estimates

Review of SOWSOW approved bySM and signed off with Client

Project Initiation

1.Preparationof PIN2. Invitestakeholder s3. Conductkick-off

meeting

Approved SOW &Estimation

Project InitiationMeeting withrepresentationfromstakeholders

1. Project initiationmeeting conducted.2. Projectdependenciesagreed upon bygroups.3. Meeting minutescirculated.

ProjectPlanning

Preparationof ProjectDevelopment Plan, &Project Plan

PIN

Review of ProjectDevelopmentPlan andProject Plan

Project plan, all sub-plans, Life cyclemodel and tailoringguidelines reviewedby QA and approvedby SM

Increment 1

Requirements

BRD/PRS/SRDPreparation

BRD/PRS/SRDReview of BRD/PRS/SRD

BRD/PRS/SRDApproved by Clientand/or SM

System TestPlanning

BRD/PRS/SRDReview of System TestPlan & Cases

System Test Planand Casesapproved by PM



SOW

BRD/PRS/SRD



Design

DesignPreparation

BRD/PRS/SRDReview of Designdocuments


IntegrationTestPlanning

Design documents

Review of Integration

Test Plan &Cases



EstimationPreparation/ Revisit

Design DocumentsReview of Estimation


DevelopmentCodepreparation

Design documentsReview of Code

Code approved byPM



Page 9 of 16



Unit TestPlanning

Design documentsReview of UnitTest Plan &

Cases


PM

Testing

Preparationof UTCs

Unit Testing

UTCs

Code

Review of UTCs



Preparationof ITCs

Integration

Testing

ITCs

Unit Tested Code

Review of ITCs

Execution of Integration

Test Cases



ReleaseIncrementalRelease

Integration TestedCode

Release audit Release Note

Increment n

Requirements

BRD/PRS/SRSPreparation

User / businessrequirements

Review of BRD/PRS/SRD

BRD/PRS/BRD/PRS/SRS Approvedby Client and/or SM

System TestPlanning BRD/PRS/SRD

Review of

System TestPlan & Cases

System Test Plan

and Casesapproved by PM



SOW

BRD/PRS/SRD



Design

DesignPreparation

BRD/PRS/BRD/PRS/SRS

Review of Designdocuments


IntegrationTestPlanning

Design documents

Review of IntegrationTest Plan &

Cases



EstimationPreparation/ Revisit

Design DocumentsReview of Estimation


Development Codepreparation

Design documents Review of Code

Code approved byPM



Page 10 of 16



Unit TestPlanning

Design documentsReview of UnitTest Plan &

Cases


PM

Testing

Preparationof UTCs

Unit Testing

UTCs

Code

Review of UTCs



Preparationof ITCs

Integration

Testing

ITCs

Unit Tested Code

Review of ITCs

Execution of Integration

Test Cases



ReleaseIncrementalRelease

Integration TestedCode


Final Release

SystemTesting

Integration TestedCode (of allreleases)

Execution of System TestCases

1.System TestResults / DefectReport2.System TestedCode approved byPM

FinalRelease

System TestedCode

Final Releaseaudit

Final Release Note



Page 11 of 16



5. Maintenance Model


Project Initiation

Maintenance

Tracker

Defect Fixing

Defect

(impact analysis )

Effort Analysis

Unit Testing

Enhancemen

(impact analysiCall

Analysis

Code Enhancem

Functional / Integration

Testing

Effort Analysis

Project Planning

SOW with zero level

estimate



Page 12 of 16



5.2 Tasks

Phase

Task /

Activity Entry Criteria

Verification &

Validation

Exit Criteria /

Output

SOWSOWpreparation

Proposal fromClient with zerolevel estimate

Review of SOW

SOW approvedby SM andsigned off withClient

Project Initiation

1.Preparation of PIN2. Invitestakeholders3.Conductkick-off meeting

Approved SOW

Project InitiationMeeting withrepresentation fromstakeholders

1. Projectinitiationmeetingconducted.2. Projectdependenciesagreed upon by

groups.3. Meetingminutescirculated.

Project Planning

Preparation of ProjectDevelopmentPlan, &ProjectPlan

PINReview of ProjectDevelopment Planand Project Plan

Project plan, allsub-plans, Lifecycle modeland tailoringguidelinesreviewed byQA andapproved by

SM

Maintenance Tracker

Track alltheissuesraisedthroughcalls andIssueTrackingTool

Calls received

Issues logged inIssue TrackingTool

Review of MaintenanceTracker in weeklyimplementationchecks and other audits

MaintenanceTracker

Defect Call

Defect Impactanalysis

Issue Tracking

Tool /MaintenanceTracker

Review of impact

analysis bystakeholders inIssue Tracking Tool

Impact analysisin IssueTracking Tool

Effort Analysis

Effortanalysisto fixdefect

MaintenanceTracker

Review of effortanalysis

Effort analysisapproved byPM/Lead



Page 13 of 16



Defect Fixing

Make

necessar ychangesto code

1. BaselinedCode2. MaintenanceTracker

Testing of re-workedcode

Defect log /Defects in

Issue TrackingTool

Tested code

Enhancement Call

EnhancementImpactanalysis

MaintenanceTracker

Review of MaintenanceTracker

MaintenanceTracker approved byPM/Lead

Effort Analysis Effortanalysisfor enhancement

MaintenanceTracker

Review of effortanalysis

Effort analysisapproved byPM/Lead

Code Enhancement

Makenecessar ychangesto code

1. BaselinedCode2. MaintenanceTracker

Testing of re-workedcode

Defect log /Defects inIssue TrackingTool

Tested code

Unit Testing

Preparation of UTCs

UnitTesting

UTCs

Re-worked Code

Review of UTCs

Execution of UnitTest Cases

Unit Test LogsUnit TestResults /

Defect ReportUnit TestedCode

Functional /Integration Testing

Preparation of FTCs/ITCs

Functional /Integration Testing

FTCs/ITCs

Unit TestedCode

Review of FTCs/ITCs

Execution of Functional /Integration TestCases

Defect ReportDefects inIssue TrackingTool

Functional /IntegrationTested Code

Release ReleaseFunctional /IntegrationTested Code


6. Test Automation




Page 14 of 16



SOW with zero level

estimate

Project Planning

First level estimate

Project Initiation

Manual execution of

test cases

Test Case Scripting

Compilation,

Debugging &

Execution

Yes

No

Changes /

Updates

Change / Update

Release

Yes

No

All test cases

completed?

Project Closure

Validation by on-site

Client’s manual testcases



Page 15 of 16



6.2 Tasks

Phase Task / ActivityEntry

CriteriaVerification& Validation

Exit Criteria / Output

SOWSOWpreparation

Proposalfrom Clientwith zerolevelestimate

Review of SOW

SOW approved by SM and signedoff with Client

ProjectInitiation

1. Preparationof PIN2. Invitestakeholders3. Conduct

kick-off meeting

ApprovedSOW

ProjectInitiationMeeting withrepresentation from

stakeholders

1. Project initiation meetingconducted.2. Project dependencies agreedupon by groups.

3. Meeting minutes circulated.

ProjectPlanning

Preparation of ProjectDevelopmentPlan, & ProjectPlan

PIN

Review of ProjectDevelopment Plan andProject Plan

Project plan, all sub-plans, Lifecycle model and tailoring guidelinesreviewed by QA and approved bySM

Manualexecution of TestCases

Execute testcases manually

Client’smanualtest cases

Review of test caseexecutionreport

Test case execution reportApproved by PM

Firstlevelestimate

Estimationpreparation

Client’srequirements

Analysis andsplit up of Estimation

Estimation Approved by SM

TestCaseScripting

Write testscripts for thetest scenarios

Test caseexecutionreport

Review of Test Scripts

Test Scripts Approved by PM

TestingExecution of Automated testscripts

ApprovedTestscripts

Testing Defect log and Test results

Validation by on-

site

Run theautomated test

scripts

Successfulrun of

automatedtest scripts

Reviewreport of

executedtest cases

Successful run of automated test

scripts (on-site)

Release Release

Successfulrun of automatedtest scripts

Releaseaudit

Release Note



P f



Document InformationAuthor Excelacom Technologies Private Limited

Reviewer Ramya Raghupathy

Approval Joseph Daniel Suresh

Status Issued

Creation Date 13-Feb-08

Review Date 17-Jun-08

Approval Date 14-Jul-08

Issued Date 14-Jul-08

Document Control

Version Section Change Request # Description Date

1.0 Allnecessar ysections

To comply with ISO9001:2000, CMMI L5 andSAS 70

14-Jul-08

1.1 Refer JIRA ID 4153 17-Aug-09