Scribd
Upload
218 views

Testing-PPT-2-Testing-Throughout-SDLC - Part-1

The document discusses functional testing and the software development life cycle (SDLC). It describes the typical phases of the SDLC as initial, analysis, design, coding, testing, and maintenance. For each phase except initial, it provides brief details on the goals, roles, and output documents. It notes that defects are most difficult and costly to fix later in the cycle during acceptance testing. The overall cost of fixing defects increases over time as the project moves through the different phases of the SDLC.

Uploaded by

Nagface
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
218 views

Testing-PPT-2-Testing-Throughout-SDLC - Part-1

The document discusses functional testing and the software development life cycle (SDLC). It describes the typical phases of the SDLC as initial, analysis, design, coding, testing, and maintenance. For each phase except initial, it provides brief details on the goals, roles, and output documents. It notes that defects are most difficult and costly to fix later in the cycle during acceptance testing. The overall cost of fixing defects increases over time as the project moves through the different phases of the SDLC.

Uploaded by

Nagface
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

TESTING

FUNCTIONAL TESTING
NAGARAJU DOMALA
Testing Throughout
SDLC
Part-1
Learning Objectives

 Software Development Life Cycle

 SDLC Phases

Nagaraju Domala
Software Development Life Cycle
 The Software Development Life Cycle is a step-by-step process involved in the
development of a software product.

 The whole process is generally classified into a set of steps and a specific operation
will be carried out in each of the steps.

 The basic classification of the whole process is as follows:


 Initial

 Analysis

 Design

 Coding

 Testing

 Maintenance

Initial:
●
The main aim of the initial phase is requirements gathering.
●
The responsible person is “BA – Business Analyst”
●
The outcome document name is “BRS – Business Requirements Specification”.

Nagaraju Domala
Contd..
Analysis:

●
In this phase requirements are analyzed for the feasibility of implementation.
●
Planning the project, Resource estimation, Schedule preparation, project prototype will takes place.
●
The outcome document name is “SRS – System Requirements Specification”.
●
At the end of this phase, both project plan and test plan documents are delivered.

Design:

●
The aim is to create the architecture of the total system(including database design).
●
Dividing the system into no. of module and sub-modules.
●
Preparing Data-flow diagrams, Control-flow diagrams, Use cases.
●
Designing Database
●
The outcome document name is “TDD – Technical Design Document”.

Coding:

●
In this phase, programmers prepares/write the code for given specification in the chosen programming language.
●
The outcome is “Source code”.

Nagaraju Domala
Contd..

Testing:

●
In this phase, testing team will execute the prepared test cases on the given build/system.
●
Main aim is, to verify that the given system working as per client requirements.
●
If test fails, they will raise an incident.
●
The outcome documents are: Test Cases, Incidents.

Maintenance:

●
In this phase, the system deployed into the client’s environment.
●
Any issue raised by client, environmental problems are handled.
●
Requirements change requests are handled
●
Maintenance is made up of:
●
Corrective maintenance
●
Ex: fixing customer-reported problems
●
Adaptive maintenance
●
Ex: making the software run on a new version of an OS or Database.
●
Preventive maintenance
●
Ex: changing the application program code to avoid a potential security hole in an OS code

Nagaraju Domala
Testing in SDLC
 When do defects arise?

Defect correction Hard to correct Acceptance testing


easy Because failure; very costly
–tester will fix design changes defects
required
Nagaraju Domala
Contd..
 Impact of defects
 A defect introduced during requirement specification and is not detected until
acceptance testing –it will be more expensive to fix

Cost in fixing defects


Cost

increases over time

Time
Requirements Design Build Test Use
SDLC Phases 
Nagaraju Domala

You might also like