Product Release

Testing Life Cycle

by Prashant Chavan

27th Jan 2009

Confidential | Copyright © Larsen & Toubro Infotech Ltd.

 Limit

 45 Mins

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 2

 Agenda

1 Introduction & Objective

2 Overview: Product Release Testing Life Cycle

3 Testing Approach

4 Testing Phases - Concepts & Scope:

A Pre-alpha
B Alpha
C Beta
D RC
E RTM
F GA
G Post Launch
5 Summary, Query/Suggestions, & References

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 3

 Introduction

A ‘Product Release' is the distribution of an

initial or upgraded version of a computer
software product.

A product release process is a structure

imposed on the development of a software
product. Synonyms include software life
cycle and software process. There are
several models for such processes, each
describing approaches to a variety of tasks
or activities that take place during the
process.

Each time a software program or system is

developed/changed, the software
engineers and company doing the work
decide on how to distribute the program or
system, or changes to that program or
system.
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 4
 Objective
Orient towards the –
Release Phases, Concepts,
and
Testing Scope
from the perspective of
Product Release Life Cycle

The presentation is to provide a generic overview about different

Stages involved in product release process adopted by contemporary
Software firms. Today’s session will give insight and visibility into
product release testing life cycle, such as system/product integration,
product releases, testing phases, and Testing approach.

This will create an opportunity to come up to speed on the

understanding of the product to be released, so that we can meet
client’s expectations in terms of functionality, cost, delivery schedule,
and effective project management
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 5
 Agenda

1 Introduction & Objective

2 Overview: Product Release Testing Life Cycle

3 Testing Approach

4 Testing Phases - Concepts & Scope:

A Pre-alpha
B Alpha
C Beta
D RC
E RTM
F GA
G Post Launch
5 Summary, Query/Suggestions, & References

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 6

 Overview: Product Release Testing Life Cycle

Pre-alpha

Alpha
Product Development

Product Testing/QA
Beta

Life Cycle
Life Cycle

RC

RTM

GA (Final)
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 7
 Agenda

1 Introduction & Objective

2 Overview: Product Release Testing Life Cycle

3 Testing Approach

4 Testing Phases - Concepts & Scope:

A Pre-alpha
B Alpha
C Beta
D RC
E RTM
F GA
G Post Launch
5 Summary, Query/Suggestions, & References

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 8

 Testing Approach

System
Test
GA
QA
Complexity (@ Product Releases)

Phase

Functional
Test Phase

Core
Prod Component
Dev Test Phase
Test Accelerators: Phases
Unit overlap to enable earlier
Test downstream testing.
Phase

Time (@ Testing Phases)

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 9

 Testing Approach (Cont’d)

Entry & Exit Criteria:

Planning & Testing &

Concept Development Maintanance
Specification Evaluation

Customer feature PRD Approved schedule All features RTM (Release to

requests First draft of ERD ERD complete Manufacturing)
New business idea, Functional specification PRD All test cases are
standards defined
Mapping features to Devs Test Plan
implementation
Documentation Plan
Critical Bug Fixes for
maintenance releases Other cross-functional
docs.

PRD PRD All features are All tests are run and Post-release
(Project Requirement ERD complete passed activities.
Document) Master Test Plan Test cases authoring is All bugs are fixed. Product Sustaining.
ERD complete Documentation Product End of
Documentation Plan
(Engineering reviewed and Support (when the
Other cross-functional
Requirement finalized. next product major
plans (Certification Plan,
Document) Certification has version is released).
Beta Program Plan,
etc.). started.
Key personnel and other All Betas and RCes
resources (budget, are completed. Gold
hardware). CD is handed off to
Product Marketing.
Concrete schedule is
reviewed and approved.
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 10
 Testing Approach (Cont’d)

Key Stages/Activities/Components:
The release life cycle is composed of
different stages that describe the
stability of a piece of software and the
amount of development it requires
before final release.

Each major version of a product usually

goes through
• a phase when new features are added
(alpha phase);
• a phase when it is being actively
debugged (beta phase);
• and finally a phase when all important
bugs have been removed (RC phase).

These stages informally describe the

state of a product.
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 11
 Agenda

1 Introduction & Objective

2 Overview: Product Release Testing Life Cycle

3 Testing Approach

4 Testing Phases - Concepts & Scope:

A Pre-alpha
B Alpha
C Beta
D RC
E RTM
F GA
G Post Launch
5 Summary, Query/Suggestions, & References

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 12

 Testing Phases - Concepts & Scope:
Product Release Life Cycle

Post Launch

Product Release GA
Testing Life
Cycle RTM

Release Candidate

Beta

Alpha

Pre-Alpha

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 13

 Pre-alpha

Concept:
Pre-alpha stage consists of the period of time from the start of the
development phase until Alpha release.

Testing Scope::
 When it is used, it refers to all activities performed during the
software project prior to software testing.

 These activities can include:

– Requirements analysis
– Software design
– Software development and
– Unit testing

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 14

 Pre-alpha (Cont’d)

Pre-alpha Release::

 Sometimes a build known as pre-alpha is issued before the release

of an alpha or beta, as developers need to see how features work
in action as the development process proceeds.

 This is the very beginning stage in the release life cycle.

Business Term:

 In contrast to alpha and beta versions, the pre-alpha is not feature

complete.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 15

 Alpha
Concept:
The alpha build of the software is the build delivered to the
internal software testers, that is, people different from the
software engineers, but usually internal to the organization that
develops the software.

Testing Scope::
In this first phase of testing,
- developers generally test the software using white box techniques.
- additional validation is then performed using black box or grey box
techniques by another dedicated testing team.

Alpha Release::
 Moving to black box testing inside the organization is known as
alpha release.
 This is the first major stage in the release life cycle.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 16

 Alpha (Cont’d)

Business Term:
 In a rush to market, more and more companies are engaging
external customers or value-chain partners in their alpha testing
phase.

 This allows more extensive usability testing during the alpha

phase.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 17

 Beta
Concept:
'Beta' is a nickname for software,
- which has passed the alpha testing stage of development and
- has been released to a limited number of users for software
testing before its official release.

Testing Scope::
 Beta testing allows the software to undergo usability testing with
users who provide feedback, so that any malfunctions these users
find in the software can be reported to the developers and fixed.

 The users of a beta version are called beta testers. They are usually
customers or prospective customers of the organization that
develops the software. They receive the software for free or for a
reduced price, but act as free testers.
 Often this stage begins when the developers announce a feature
freeze on the product, indicating that no more feature requirements
will be accepted for this version of the product.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 18

 Beta (Cont’d)

Beta Release:
 The process of delivering a beta version to the users is called beta
release.

 Beta level software generally includes all features, but may also
include known issues and bugs of a less serious variety.

 Beta software may be unstable and could cause crashes or data

loss.

 This is the second major stage in the software testing release

cycle.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 19

 Beta (Cont’d)

Business Term:

 A 'beta version' is the first version released outside the

organization that develops the software, for the purpose of
evaluation or real-world black/grey-box testing.

 Some developers refer to this stage as a preview, a prototype, a

technical preview (TP) or as an early access.

 Beta version software is likely to be useful for internal

demonstrations and previews to select customers, but unstable
and not yet ready for release.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 20

 Beta (Cont’d)

Example:

 Microsoft started releasing regular Windows Vista community

technology previews (CTPs) to beta testers in January 2005. The
first of these was build 5219. Subsequent CTPs introduced most of
the planned features, as well as a number of changes to the user
interface, based in large part on feedback from beta testers.

 Windows Vista was deemed feature complete with the release of

build 5308 CTP, released on February 22, 2006, and much of the
remainder of work between that build and the final release of the
product focused on stability, performance, application and driver
compatibility, and documentation.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 21

 Release Candidate
Concept:
The term release candidate refers to a version with potential to be
a final product, ready to release unless fatal bugs emerge.

Testing Scope::
 In this stage, all product features have been designed, coded and
tested through one or more Alpha cycles with no known
showstopper-class bugs.
 There may still be source code changes to fix defects. There may
still be changes to documentation and data files, and to the code
for test cases or utilities. New code may be added in a future
release.

RC Release:
 A release is called code complete when the development team
agrees that no entirely new source code will be added to this
release.
 This is the third major stage in the release lifecycle.
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 22
 RTM

Concept:
The term “release to manufacturing” or “release to marketing” is used
to indicate that the software has met a defined quality level and is
ready for mass distribution either by electronic means or by physical
media.

Testing Scope::
 The term does NOT define the delivery mechanism, it only states that
the quality is sufficient for mass distribution.
 The deliverable from the engineering organization is usually in the
form of a gold master CD used for duplication or to produce the image
for the web.

RTM Release:
 RTM happens prior to general availability (GA).
 This is the fourth major stage in the release lifecycle

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 23

 GA
Concept:
General Availability (GA) is the point where all necessary
commercialization activities have been completed and the software has
been made available to the general market either via the web or physical
media.

Testing Scope:
 The time between RTM and GA can be from a week to months because of
the time needed to complete all commercialization activities required by
GA.

GA Release:
 Commercialization activities could include the availability of media world
wide via dispersed distribution centers, marketing collateral is completed
and available in as many languages necessary for the target market, etc.
 This is the final stage in the release lifecycle

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 24

 GA (Cont’d)

Release Notes:
 Release notes are documents which are distributed along with
software products, often when the product is still in the
development or test state (e.g., a beta release).
 For products that have already been in use by clients, the release
note is a supplementary document that is delivered to the
customer every time a bug is fixed or an enhancement is made on
the product.
 Release notes are frequently written in the present tense and
provide information that is clear, correct, and complete.

A release notes usually includes the following sections:

Header Overview Purpose
Issue Summary Steps to Reproduce Resolution
End-User Impact Support Impacts Notes
Disclaimers Contact
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 25
 GA (Cont’d)

Box Copy Release:

 A box copy is a physical version of the final product, printed on a

disc that is complete with disc graphic art.

 This term is used mostly by reviewers to differentiate from other

forms of the released product (e.g., a downloaded copy, or a gold
master burned on a generic disc).

 A box copy does not necessarily come enclosed in a box; it refers

to the disc itself.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 26

 GA (Cont’d)

Web Release:

 A web release is a means of software delivery that utilizes the

Internet for distribution.

 No physical media are produced in this type of release mechanism by

the manufacturer.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 27

 GA (Cont’d)

Production or Live Release:

 The production, live version is the final version of a particular

product. It is typically almost identical to the final release
candidate, with only last-minute bugs fixed.

 A live release is considered to be very stable and relatively bug-

free with a quality suitable for wide distribution and use by end
users.

 The expression that a software product "has gone live" means that
the code has been completed and is ready for distribution.

 Other terms for the live version include: live master, live release,
or live build. In some areas of software development the live
release is referred to as a gold release

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 28

 GA (Cont’d)

Stable or Unstable:

 The term stable refers to a version of software that is substantially

identical to a version that has been through enough real-world
testing to reasonably assume there are no showstopper problems,
or at least that any problems are known and documented.

 On the other hand, the term unstable does not necessarily mean
that there are problems - rather, that enhancements or changes
have been made to the software that have not undergone rigorous
testing and that more changes are expected to be imminent.

Users of such software are advised to use the stable version if it

meets their needs.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 29

 GA (Cont’d)

End-of-Life:

 Sometimes software companies stop selling or supporting their

software products (e.g., not releasing new patches). At this point
the product will be said to be in the status of "legacy", "vintage" or
"end of life."

For instance, on August 15, 2007, Apple announced that

AppleWorks reached "end-of-life status." This is also true of the
Netscape internet browser which stopped being supported in
March 2008.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 30

 Post Launch Activities

Post-launch validation will apply the lessons from pre-launch

activities to future support/maintenance work and the actual
products will be evaluated with the established analysis procedures.

Following factors will be considered in Post launch Activities:

 Stability – This is one of the important aspects in terms of

functionality with respect to business requirements, user friendliness
and product performance.

 Support – These are the set of activities will be considered with

respect to quality, defect leakage, and any testing missed-out during
test execution cycle. Also change request, support request, or
enhancements will be considered under support activities.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 31

 Post Launch Activities (Cont’d)

System Monitoring & Maintenance:

System Monitoring is a critical process and enfolds the system testing
life cycle. The process is applicable after the product launch. It ensures
that significant deviations are evaluated, resolved, and escalated to
management’s / customer’s attention in a timely manner.
System Maintenance Processes deals with issues and tickets and are
broadly classified into different categories in terms of priorities and the
response times are based on Service Level Agreements (SLA).
Sub-sets of System Monitoring & Maintenance:
 Launch status review
 Customer Feedback - Analyze and Resolve Customer complaints
 Manage changes to requirements effectively
 System support
 Continuous Tracking & Controlling
 System Fine Tuning & Recommendations
 Metrics monitoring
 Risk monitoring
 Defect prevention

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 32

 Agenda

1 Introduction & Objective

2 Overview: Product Release Testing Life Cycle

3 Testing Approach

4 Testing Phases - Concepts & Scope:

A Pre-alpha
B Alpha
C Beta
D RC
E RTM
F GA
G Post Launch
5 Summary, Query/Suggestions, & References

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 33

 Summary

Conceptually, a software/product release is just a very large project,

composed of multiple feature development, system level work,
maintenance, and/or support activities.
Work at the release level is larger in scope than the corresponding
individual development project.
Why it's useful?
 Decisions take at the release level regarding which functionalities
should be included in a particular release—and the scope of each of
feature decided as well—based on available resources, customer
needs.
 The work on each feature must be integrated successfully into a
coherent working software system with appropriate testing and
documentation.
 The Release Management ensure that the various components meet
customer needs and are integrated and released on time with high
quality, while insuring that the overall release reflects the best
choices amount scope, costs, and time for the company.
Confidential | Copyright © Larsen & Toubro Infotech Ltd. 34
 Do you have a Query Or A Suggestion???

• You may get back to us regarding

your doubts at
[email protected]

• You have a wonderful suggestion!!

Wow we would be glad to accept it.

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 35

 References

 Release Process & Product Lifecycle at Microsoft

June 2006

 External Links
http://www.bitpipe.com/tlist/Software-Development-Life-Cycles.html

http://www.stylusinc.com/Common/Concerns/SoftwareDevtPhilosophy.php

http://www.projectconnections.com/templates/detail/softwarereleaselifecy
cle.html

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 36

 Thank you

Our Business Knowledge

Your Winning Edge

Confidential | Copyright © Larsen & Toubro Infotech Ltd.