Q2 Quest for Quality

Q2 – Lifecycle Models

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

Page 1 of 16
This Document, constitutes and contains proprietary information of ExcelaCom Technologies and shall not be disclosed in whole or in part by Client to any
third party or to any employees of Client other
than 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 this
Document.
 Q2 Quest for Quality
Q2 – Lifecycle Models

1. Overview
1.1 Objective
This document was developed with the objective of setting forth a clear understanding of events
for conducting software development activities within the Organization that are well-defined,
understood, and implemented across all projects in a systematic and uniform manner. This
document disseminates the software development and maintenance life cycles and processes
that foster the discipline and structure needed to enable projects to consistently and predictably
produce 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 Project
Manager (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 software
engineering. Often considered the classic approach to the systems development life cycle, the
waterfall 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 no
changes 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 time
for development, client feedback is obtained, and once all requirements are completed, the
project is closed. This is similar to keep on adding on what has been done before. This is the
subtle difference. In incremental you don't go back and refactor what you have done before, you
only 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 iterative
model. 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 the
existing rooms), then it is incremental model. In this case, the user can exist to stay in the existing
house and keep doing his changes.
The Maintenance model is used for projects which are in production (live) environment and needs
to be taken care in terms of any enhancements that may be required or defects that needs to be
fixed in the software.
The Test Automation model is used for projects where manual test cases are provided by the
client and the scope of the project involves only scripting the test cases to facilitate automation.

Page 2 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

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 manual
execution of test cases to support Mobile Virtual Network Operations. Such projects do not
involve the regular software development phases such as Requirements, Design and
Construction.
Note: The PM chooses the appropriate life cycle, documents in the Project Management Plan
and 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 associated
activities. A process is a set of tasks that have definite entry criteria, verification and validation
activities 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 cycle
model.

Tasks The tasks associated for the major activities with the associated
entry 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 3 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

3. Modified Waterfall Model

3.1 Model Representation
S
OWw
it
h Z
er
o L
evel
E
st
im ate

P
roj
ectI
nit
iat
ion

P
roje
ctP
la
nnin
g

R
eq
uir
eme
nts

F
ir
stL
ev
elE
st
ima
te
Feedback from any of the
phases to improve or fix the
D
es
ign
issues

S
eco
ndLe
velEstima
te
(R ev
is
itifr
eqd )

C
od
in
g

T
es
tin
g

R
ele
ase

Page 4 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

3.2 Tasks
Verification & Exit Criteria /
Phase Task / Activity Entry Criteria
Validation Output
Proposal from SOW approved by
SOW Review of
SOW Client with zero SM and signed off
preparation SOW
level estimates with Client

1. Project initiation
1. Preparation Project meeting conducted.
of PIN Initiation 2. Project
2. Invite Meeting with dependencies
Project Initiation Approved SOW
stakeholders representation agreed upon by
3. Conduct kick- from groups.
off meeting stakeholders 3. Meeting minutes
circulated.

Project plan, all

sub-plans, Life
Preparation of Review of cycle model and
PIN
Project Planning PMP, & Project PMP and tailoring guidelines
Plan Project Plan reviewed by QA
and approved by
SM

Review of BRD/PRS/SRD
BRD/PRS/SRD
BRD/PRS/SRD BRD/PRS/SR Approved by Client
Preparation
S and/or SM
Requirements
Review of System Test Plan
System Test
BRD/PRS/SRD System Test and Cases
Planning
Plan & Cases approved by PM

First level Estimation SOW Review of Estimation

Estimation Preparation BRD/PRS/SRD Estimation approved by SM

Review of
Design Design documents
BRD/PRS/SRD Design
Preparation approved by PM
documents
Design Review of
Integration Test
Integration Test Design Integration
Plan and Cases
Planning documents Test Plan &
approved by PM
Cases

Estimation
Second level Design Review of Estimation
Preparation /
Estimation Documents Estimation approved by SM
Revisit

Code Design Review of Code approved by

Development
preparation documents Code PM

Page 5 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

Review of Unit Unit Test Plan and

Unit Test Design
Test Plan & Cases approved by
Planning documents
Cases PM

Review of Unit Test Logs

Preparation of UTCs Unit Test Results /
UTCs
UTCs Defect Report
Execution of
Code Unit Tested Code
Unit Testing Unit Test
Cases approved by PM

Testing Integration Test

Review of Logs
Preparation of Integration Test
ITCs ITCs
ITCs Results / Defect
Unit Tested Execution of Report
Integration
Code Integration Integration Tested
Testing
Test Cases Code approved by
PM

1.System Test
Results / Defect
Integration Execution of
Report
System Testing Tested Code (of System Test
2.System Tested
Release all releases) Cases
Code approved by
PM

System Tested Final Release

Final Release Final Release Note
Code audit

Page 6 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

4. Incremental Model
4.1 Model Representation
SOW with zero level
estimate

Project Initiation

Project Planning

Requirements

First level estimate

Design Yes

Increment
Client Feedback
Second level estimate (1 to n)

No
Coding

Testing

Release

Project Closure

Page 7 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

4.2 Tasks
Task / Verification & Exit Criteria /
Phase Entry Criteria
Activity Validation Output
Proposal from SOW approved by
SOW
SOW Client with zero Review of SOW SM and signed off
preparation
level estimates with Client

1.
1. Project initiation
Preparation
meeting conducted.
of PIN Project Initiation
2. Project
2. Invite Meeting with
Approved SOW & dependencies
Project Initiation stakeholder representation
Estimation agreed upon by
s from
groups.
3. Conduct stakeholders
3. Meeting minutes
kick-off
circulated.
meeting

Project plan, all sub-

Preparation Review of
plans, Life cycle
of Project Project
Project PIN model and tailoring
Developmen Development
Planning guidelines reviewed
t Plan, & Plan and
by QA and approved
Project Plan Project Plan
by SM
Increment 1
BRD/PRS/S Review of BRD/PRS/SRD
RD BRD/PRS/SRD BRD/PRS/SR Approved by Client
Preparation D and/or SM
Requirements
Review of System Test Plan
System Test
BRD/PRS/SRD System Test and Cases
Planning
Plan & Cases approved by PM

First level Estimation SOW Review of Estimation

Estimation Preparation BRD/PRS/SRD Estimation approved by SM

Review of
Design Design documents
BRD/PRS/SRD Design
Preparation approved by PM
documents
Design Review of
Integration Integration Test
Integration
Test Design documents Plan and Cases
Test Plan &
Planning approved by PM
Cases

Estimation
Second level Review of Estimation
Preparation Design Documents
Estimation Estimation approved by SM
/ Revisit

Code Review of Code approved by

Development Design documents
preparation Code PM

Page 8 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

Review of Unit Unit Test Plan and

Unit Test
Design documents Test Plan & Cases approved by
Planning
Cases PM

Review of Unit Test Logs

Preparation UTCs Unit Test Results /
UTCs
of UTCs Defect Report
Execution of
Code Unit Tested Code
Unit Testing Unit Test
Cases approved by PM

Testing Integration Test

Logs
Preparation Review of ITCs Integration Test
of ITCs ITCs Results / Defect
Execution of
Integration Unit Tested Code Integration Report
Testing Test Cases Integration Tested
Code approved by
PM

Incremental Integration Tested

Release Release audit Release Note
Release Code
Increment n
BRD/PRS/BRD/PR
BRD/PRS/S Review of
User / business S/SRS Approved
RS BRD/PRS/SR
requirements by Client and/or
Preparation D
Requirements SM

Review of System Test Plan

System Test
BRD/PRS/SRD System Test and Cases
Planning
Plan & Cases approved by PM

First level Estimation SOW Review of Estimation

Estimation Preparation BRD/PRS/SRD Estimation approved by SM

Review of
Design BRD/PRS/BRD/P Design documents
Design
Preparation RS/SRS approved by PM
documents
Design Review of
Integration Integration Test
Integration
Test Design documents Plan and Cases
Test Plan &
Planning approved by PM
Cases

Estimation
Second level Review of Estimation
Preparation Design Documents
Estimation Estimation approved by SM
/ Revisit

Development Code Design documents Review of Code approved by

preparation Code PM

Page 9 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

Review of Unit Unit Test Plan and

Unit Test
Design documents Test Plan & Cases approved by
Planning
Cases PM

Review of Unit Test Logs

Preparation UTCs Unit Test Results /
UTCs
of UTCs Defect Report
Execution of
Code Unit Tested Code
Unit Testing Unit Test
Cases approved by PM

Testing Integration Test

Logs
Preparation Review of ITCs Integration Test
of ITCs ITCs Results / Defect
Execution of
Integration Unit Tested Code Integration Report
Testing Test Cases Integration Tested
Code approved by
PM

Incremental Integration Tested

Release Release audit Release Note
Release Code

1.System Test
Results / Defect
Integration Tested Execution of
System Report
Code (of all System Test
Testing 2.System Tested
Final Release releases) Cases
Code approved by
PM

Final System Tested Final Release

Final Release Note
Release Code audit

Page 10 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

5. Maintenance Model
5.1 Model Representation
SOW with zero level
estimate

Project Initiation

Project Planning

Maintenance
Tracker

Defect Call Enhancement

(impact analysis ) Analysis (impact analysis )

Effort Analysis Effort Analysis

Defect Fixing Code Enhancement

Unit Testing

Functional / Integration
Testing

Release

Page 11 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

5.2 Tasks
Task / Verification & Exit Criteria /
Phase Entry Criteria
Activity Validation Output
SOW approved
SOW Proposal from
by SM and
SOW preparati Client with zero Review of SOW
signed off with
on level estimate
Client

1. Project
1.
initiation
Preparati
meeting
on of PIN
conducted.
2. Invite Project Initiation
2. Project
stakehold Meeting with
Project Initiation Approved SOW dependencies
ers representation from
agreed upon by
3. stakeholders
groups.
Conduct
3. Meeting
kick-off
minutes
meeting
circulated.

Project plan, all

Preparati
sub-plans, Life
on of
cycle model
Project
Review of Project and tailoring
Develop PIN
Project Planning Development Plan guidelines
ment
and Project Plan reviewed by
Plan, &
QA and
Project
approved by
Plan
SM

Track all
the
Review of
issues Calls received Maintenance
raised
Issues logged in Tracker in weekly Maintenance
Maintenance Tracker through
Issue Tracking implementation Tracker
calls and
Tool checks and other
Issue
audits
Tracking
Tool
Defect Call
Issue Tracking Review of impact
Impact analysis
Impact Tool / analysis by
Defect in Issue
analysis Maintenance stakeholders in
Tracking Tool
Tracker Issue Tracking Tool

Effort
Effort analysis
analysis Maintenance Review of effort
Effort Analysis approved by
to fix Tracker analysis
PM/Lead
defect

Page 12 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

Defect log /
Make Defects in
1. Baselined
necessar Issue Tracking
Code Testing of re-worked
Defect Fixing y Tool
2. Maintenance code
changes
Tracker Tested code
to code

Enhancement Call
Maintenance
Review of
Impact Maintenance Tracker
Enhancement Maintenance
analysis Tracker approved by
Tracker
PM/Lead

Effort Analysis Effort

analysis Effort analysis
Maintenance Review of effort
for approved by
Tracker analysis
enhance PM/Lead
ment

Make Defect log /

1. Baselined Defects in
necessar
Code Testing of re-worked Issue Tracking
Code Enhancement y
2. Maintenance code Tool
changes
Tracker
to code Tested code

Preparati Unit Test Logs

on of Review of UTCs Unit Test
UTCs Results /
Unit Testing UTCs
Execution of Unit Defect Report
Re-worked Code
Unit Test Cases Unit Tested
Testing Code

Preparati
Defect Report
on of Review of
Defects in
FTCs/ITC FTCs/ITCs
FTCs/ITCs Issue Tracking
Functional / s
Execution of Tool
Integration Testing Unit Tested
Function Functional /
Code Functional /
al / Integration Test
Integration
Integratio Cases
Tested Code
n Testing

Functional /
Release Release Integration Release audit Release Note
Tested Code

6. Test Automation
6.1 Model Representation

Page 13 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

SOW with zero level

estimate

Project Initiation

Project Planning

Client’s manual test

cases

Manual execution of
test cases
Project Closure

First level estimate

Yes
Test Case Scripting
All test cases
completed?
No
Compilation,
Change / Update
Debugging &
Execution
Yes

Changes /
Validation by on-site Updates Release
No

Page 14 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

6.2 Tasks

Entry Verification
Phase Task / Activity Exit Criteria / Output
Criteria & Validation
Proposal
from Client
SOW Review of SOW approved by SM and signed
SOW with zero
preparation SOW off with Client
level
estimate

1. Preparation Project
1. Project initiation meeting
of PIN Initiation
conducted.
Project 2. Invite Approved Meeting with
2. Project dependencies agreed
Initiation stakeholders SOW representatio
upon by groups.
3. Conduct n from
3. Meeting minutes circulated.
kick-off meeting stakeholders

Preparation of Review of
Project plan, all sub-plans, Life
Project Project
Project PIN cycle model and tailoring guidelines
Development Developmen
Planning reviewed by QA and approved by
Plan, & Project t Plan and
SM
Plan Project Plan

Manual Review of
Client’s
executio Execute test test case Test case execution report
manual
n of Test cases manually execution Approved by PM
test cases
Cases report

First Client’s Analysis and

Estimation
level requireme split up of Estimation Approved by SM
preparation
estimate nts Estimation

Test Write test Test case Review of Test Scripts Approved by PM

Case scripts for the execution Test Scripts
Scripting test scenarios report

Execution of Approved Testing Defect log and Test results

Testing Automated test Test
scripts scripts

Successful Review
Validatio Run the
run of report of Successful run of automated test
n by on- automated test
automated executed scripts (on-site)
site scripts
test scripts test cases

Successful
run of Release
Release Release Release Note
automated audit
test scripts

Page 15 of 16
 Q2 Quest for Quality
Q2 – Lifecycle Models

Document Information
Author 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 All To comply with ISO 14-Jul-08
necessar 9001:2000, CMMI L5 and
y SAS 70
sections
1.1 Refer JIRA ID 4153 17-Aug-09

Page 16 of 16