Agenda

Software Development Process

Software Quality Process
Software Support Process
Sales
HR
Accounts

Software Development
Process

Software development customized

scrum process
TMP-000024 System Architecture

TMP-000020 Interface Control

Document
TMP-000037 High Level Design
Initial
Architectur
e
vision

Daily
Work

Daily coordination
meeting
GL-0000004 Java Code standard
TMP-000010 Software Design Review Checklist
TMP-000016 Deployment Plan
TMP-000043 DAR

Iteratio
n

TMP-000019 Iteration Assessment

RP-QC-662 Delivery Release Note

Identify, prioritize,
and select projects

Highest-priority
Work Items

Initial
Initial vision
Requirement
and funding
s
Product visionand release
plan
Initial
TMP-00004-SRS
modeling,
planning, and
organization

Iteration
backlog

Tasks

TMP-000018 Iteration CHK-000052 Planning Checklist

Plan
Iteration planning
session to select work
items and identify work
tasks for current iteration

TMP-000013 POC

Business roadmap,
technology roadmap

Consumable
solution

PD-QC-631
QA SOP

Consumable
QA & QC
solution

PD-SD-632
SSA

Product
support

defect reports (JIRA)

feedback
Enhancement requests
and defect reports (JIRA)

Work
items

Envision the
future

Demo to
stakeholders,
Retrospective
meeting,
QA Release

JIRA Tool

Inception
One or more short iterations
Shareholder vision
Proven architecture

Construction

Transition

Many short iterations producing a potentially consumable solution

each iteration
short iterations
Sufficient functionality
Project viability
(several)

About this lifecycle:

This customized Scrum-based lifecycle
The team produces a consumable solution at the end of each construction iteration
(typically 2-6 weeks in length).
Work items are typically prioritized based on a combination of business value and
technical risk.

One or more

Delighted stakeholders

Production ready

Process tools

Feature development workflow

Bugs handling work flow

Software Quality Process

Objective

Introduction to QA & Process Compliance team

Software testing process
Configuration management & testing artifacts
Tools used in testing activities
Overview of the tools & its use in testing

About the QA & Process Compliance team

Team lead
Team consists of Team Leads, Sr. Software Test Engineers
Most of the team members are ISTQB certified testers
STLC process followed to adhere with CMMI standards
Performs functional and non functional testing
Automation testing
Mobile application testing

Software testing lifecycle process

Requirement
Requirement
analysis
analysis and
and
walkthrough
walkthrough

Testing
Testing strategy
strategy
and
planning
and planning

Test
Test case
case
development
development

Test
Test execution
execution
and
and defects
defects
reporting
reporting

Test
Test results
results
preparation
preparation and
and
analysis
analysis

Test
Test closure
closure

Software Testing Service

Standard operating procedure

Software testing lifecycle process

Requirement Analysis

Entry Criteria: Requirements from BA

Input: Set of requirements in JIRA/Document

Output: Requirement Review comments/clarifications, approved requirement

Exit Criteria: Requirement walkthrough completed and approved requirements

Test Planning & Strategy

Entry Criteria: Set of approved requirements

Input: Finalized and approved set of requirement(SRS or JIRA)

Output: Test Plan document

Exit Criteria: Test Plan approved by Test manager

Test Case Design

Entry Criteria: Set of approved requirements

Input: Finalized and approved set of requirement(SRS or JIRA), Requirement

walkthrough

Output: Test case document, Review Comments

Exit Criteria: Test case document approved by Business Analyst after peer review

Software testing lifecycle process

Test Execution & Defects Reporting

Entry Criteria: Test release form with the list of features and defects

Input: Finalized and approved set of test cases

Output: Executed test case document, Defects in JIRA

Exit Criteria: Test case document with execution status for each features and
updated defect status in JIRA after validation of all released defects

Test Results Preparation

Entry Criteria: Executed test case document

Input: Test execution report, list of defects in JIRA, updated status of released
defects

Output: Test Summary Report with status of released features and defects

Exit Criteria: Test summary report approved by Test Manager

Test Closure

Entry Criteria: Approved test summary report

Input: Test Summary report & Test Plan

Output: Signoff document

Exit Criteria: Signoff document approved by Test Manager

Configuration management
Subversion (SVN) is identified and used as the configuration management tool for the team.
The exclusive repository for QA & Process compliance team.
All the projects have separate folders in the repository under PROJECTS folder. The
subfolders inside each projects has four classifications.
Customer- All customer related items and artifacts are stored here
Engineering- The main folder where the bulk of testing related activities/artifacts are
stored. The folder contains subfolders for requirement specs, User manual, change
requests and work products related to software testing
Project Management- Project plans, test plans, test schedules/estimations and other
project management activities comes here
Support- All support related artifacts including MOM, release notes, Work reports and
training documents are stored here
This is designed in line with CMMI standards.

SVN folder structure - projects and

process
Folder structure of test artifacts

Folder structure of process documents/templates

Type of testing performed by the team (functional

& non-functional)

Sanity Testing
GUI Testing
Database Testing

Data mapping/migration
testing

SOAP/REST API's
Service chaining &
sequencing

Integration Testing
End-to-End & System
Testing
Regression Testing
User Acceptance Testing

API Testing

Mobile Application
Testing

Web application automation

(Selenium Web Driver /
TestNG)
Service Chaining
Automation (Ready! API)

Performance Testing

Android
iOS

Automation Testing

JMeter Load Testing

(Concurrent Users &
Throughput)

Usability Testing

Security testing

Tools used by the team

Requirements
Management
Requirements/New
feature/Story management
Tool
JIRA
Mantis

Test Case Design

Test Case Management

Tool
Testlink

Test Execution
API Testing Tool

Test Reporting

SOAP UI

Defect Reporting & Tracking

Tool

REST Client

JIRA

Postman-REST Client

Mantis

Remote client access & file sharing

tool
WinSCP

Non Functional testing

tools

Selenium Web Driver with

TestNG framework

Putty
Network Sniffing Tool
Wireshark
tcpdump
Device Simulation Tool
Hercules

Automation Testing

Performance Testing
Jmeter

Security Testing Tool

RetinaScan
ZAP

Software Support Process

Software support functional process

Custome
r

Custome
r
Technica
l
Support
Level 1
Support

Customer
Customer
request help
request
help
or report issue

More
More
feedback

Finished

Finished
Finished

Confirm
with client
client
with

Confirm
with client

Yes

Get
Get more
more
details

Resolve &
report
report to
to client
client

Issue

Reproduce
issue

Test
Test issue
issue

Update
issue
issue in
in
Mantis
Mantis

Close
Close
issue in
Mantis
Mantis

Post
Post issue
issue
in Mantis

Update
customer
Support Team

Update
customer
Support Team
Deployment
Close
Close
issue in
JIRA

Post
Post issue
issue
in JIRA

Valid issue

Close
issue
issue in
in
Mantis

No

Yes

Level 2
Support

Resolve &
report
report to
to client
client

Release
management
management

Close
issue in
issue
in
JIRA

No

Yes

QA Team

Business
Business
impact analysis
&
brainstorming
brainstorming

Coding & unit

testing

Design
Design

Yes
Verification
Verification
No

Resolved

Feature enhancement work flow

Defect handling work flow

Thank You