SQA

Software Quality Assurance

2021
SQA

Lecture: 05
Alignment testing with project

www.company.com
 Agenda
SQA

• Software Requirements & Types

• Software Test Process Models
• Plans for Achieving and Improving
Software Quality

www.company.com
 What are software requirements?
SQA

A software requirements specification (SRS) is a

comprehensive description of the intended purpose and
environment for software under development. The SRS
fully describes what the software will do and how it will be
expected to perform.

It deals with establishing the needs of stakeholders that

are to be solved by software before even developing the
software.

www.company.com
 Software Requirements
SQA
(Wiki)
The activities related to working with software requirements can
broadly be broken up into

• Elicitation
• Analysis
• Specification
• Validation
• Management

www.company.com
 Elicitation, Analysis, Specification &
SQA
Management
• Elicitation is the gathering and discovery of requirements from
stakeholders via sessions, interviews, document analysis
• Analysis involves reaching a richer and more precise
understanding of each requirement and representing sets of
requirements in multiple, complementary ways
• Specification involves representing and storing the collected
requirements knowledge in a persistent and well-organized
fashion
• Validation involves techniques to confirm that the correct set
of requirements has been specified to build a solution
• Requirements change during projects and there are often
many of them. Management of this change becomes
paramount to ensuring that the correct software is built 

www.company.com
 Software Requirements Types
SQA

• Business Requirements
• Market Requirements
• Functional Requirements 
• Non-Functional Requirements
• UI Requirements

www.company.com
 Software Test Process Models
SQA

• Testing is a process rather than a single activity

• This process starts from test planning then designing
test cases, preparing for execution and evaluating
status till the test closure
• Basic Model
1)    Planning and Control
2)    Analysis and Design
3)    Implementation and Execution
4)    Evaluating exit criteria and Reporting
5)    Test Closure activities

www.company.com
 Basic Model
SQA
Planning and Control
Test planning has following major tasks:
•To determine the scope and risks and identify the objectives of testing.
•To determine the test approach.
•To implement the test policy and/or the test strategy. (Test strategy is an
outline that describes the testing portion of the software development
cycle. It is created to inform PM, testers and developers about some key
issues of the testing process. This includes the testing objectives, method
of testing, total time and resources required for the project and the testing
environments.).
•To determine the required test resources like people, test environments,
PCs, etc.
•To schedule test analysis and design tasks, test implementation,
execution and evaluation.
•To determine the Exit criteria we need to set criteria such as Coverage
criteria

www.company.com
 Basic Model
SQA
Planning and Control
Test control has the following major tasks
•To measure and analyze the results of reviews and testing.
•To monitor and document progress, test coverage and exit
criteria.
•To provide information on testing.
•To initiate corrective actions.
•To make decisions.

www.company.com
 Basic Model
SQA
Analysis and Design
• To review the test basis. (The test basis is the information
we need in order to start the test analysis and   create our
own test cases. Basically it’s a documentation on which test
cases are based, such as requirements, design
specifications, product risk analysis, architecture and
interfaces. We can use the test basis documents to
understand what the system should do once built.)
• To identify test conditions.
• To design the tests.
• To evaluate testability of the requirements and system.
• To design the test environment set-up and identify and
required infrastructure and tools.

www.company.com
 Basic Model
SQA
Implementation and Execution
Test implementation has the following major task:
•To develop and prioritize our test cases by using techniques
and create test data for those tests
•We also write some instructions for carrying out the tests which
is known as test procedures.
•We may also need to automate some tests using test harness
and automated tests scripts. To create test suites from the test
cases for efficient test execution.
•To implement and verify the environment.

www.company.com
 Basic Model
SQA
Implementation and Execution
Test execution has the following major task:
•To execute test suites and individual test cases following the
test procedures.
•To re-execute the tests that previously failed in order to confirm
a fix. This is known as confirmation testing or re-testing.
•To log the outcome of the test execution and record the
identities and versions of the software under tests. The test log is
used for the audit trial. To Compare actual results with expected
results.
•Where there are differences between actual and expected
results, it report discrepancies as Incidents.

www.company.com
 Basic Model
SQA
Evaluating Exit criteria and Reporting
Exit criteria come into picture, when:
•Maximum test cases are executed with certain pass percentage.
•Bug rate falls below certain level.
•When achieved the deadlines.

Evaluating exit criteria has the following major tasks:

•To check the test logs against the exit criteria specified in test planning.
•To assess if more test are needed or if the exit criteria specified should
be changed.
•To write a test summary report for stakeholders.

www.company.com
 Basic Model
SQA
Test Closure activities
Test closure activities have the following major tasks:
•To check which planned deliverables are actually delivered and to
ensure that all incident reports have been resolved.
•To finalize and archive software such as scripts, test environments, etc.
for later reuse.
•To handover the software to the maintenance organization. They will
give support to the software.
•To evaluate how the testing went and learn lessons for future releases
and projects.

www.company.com
 Software Test Process Models
SQA

www.company.com
 The V Model
SQA

www.company.com
 The V Model
SQA

www.company.com
 The V Model
SQA

• Requirements like BRS and SRS begin the life cycle model
just like the waterfall model. But, in this model before
development is started, a system test plan is created
• The high-level design (HLD) phase focuses on system
architecture and design. It provide overview of solution,
platform, system, product and service/process
• The low-level design (LLD) phase is where the actual
software components are designed. It defines the actual logic
for each and every component of the system. Class diagram
with all the methods and relation between classes comes
under LLD. Component tests are created in this phase as
well.

www.company.com
 The V Model
SQA

• The implementation phase is, again, where all coding takes

place. Once coding is complete, the path of execution
continues up the right side of the V where the test plans
developed earlier are now put to use.

• Coding: This is at the bottom of the V-Shape model. Module

design is converted into code by developers.

www.company.com
 Advantages of V-model
SQA

• Simple and easy to use.

• Testing activities like planning, test designing happens well
before coding. This saves a lot of time. Hence higher chance
of success over the waterfall model.
• Proactive defect tracking – that is defects are found at early
stage.
• Avoids the downward flow of the defects.
• Works well for small projects where requirements are easily
understood.

www.company.com
 Disadvantages of V-model
SQA

• Very rigid and least flexible.

• Software is developed during the implementation phase, so
no early prototypes of the software are produced.
• If any changes happen in midway, then the test documents
along with requirement documents has to be updated

www.company.com
 The V Model
SQA

• The V-shaped model should be used for small to medium

sized projects where requirements are clearly defined and
fixed.
• The V-Shaped model should be chosen when technical
resources are available with needed technical expertise.

www.company.com