SDLC software testing

SDLC:
SDLC refers to a linear sequence of stages all systems naturally undergo to develop a system
from planning to analysis to design to implementation.

Traditional model of SDLC

Traditional model of SDLC includes the following phases:
 Requirements
 Design and architecture
 Coding and development
 QA and testing
 Implementation
 Maintenance

REQUIREMENTS:
Once the project is obtained from Client, BA team gathers the requirements from the clients,
for example how they need the application, it should window based or web based.
Obtaining all the requirements from the client will take place in this phase.

Job Oriented - Instructor Led - Face2Face-True Live Online I.T. Training for Everyone Worldwide
www.H2KINFOSYS.com||Training@H2KInfosys.com
USA:+1-770-777-1269 || UK:+44-0203-371-7165

ANALYSIS:
In the analysis phase the features that has to be tested, resources and the technology needed
for testing is analyzed. It also gives the software requirement specification.
Use-cases, Design Specifications, Technical specs, flowcharts will be designed.

DESIGN:
In the design the requirements gathered will broken into HLD and LLD to make BRD detailed
manner containing all the information in depth and crystal clear to make easier for
development and QA team to start up the process.
In the design phase the Technical Design Document is obtained from High level design (HLD)
and Low Level Design (LLD).
HLD: It is developed by higher leads of the organization according to the specifications of the
customers.
LLD: It is developed by the lower level people of the organization i.e. Team Leaders of the
respective departments.

CODING:
After the design is designed by the concerned departments the design is transferred into
machine-readable form. Codes generated should be easy to understand and should not be
with more complications.

TESTING:
After the code is developed i.e. testing begins to find if that contains bugs which affect the
product value and deviate from customer need.
At the end of testing phase the defect profile is created so that the defect can be corrected
before the final product is released.

IMPLEMENTATION:
After all the necessary testing and correction the application is implemented and released
into the market.

MAINTAINENCE:

USA:+1-770-777-1269 || UK:+44-0203-371-7165

After releasing the product the customer it is assured for quality can the customer is retained
by maintaining the product even if undergoes any change after release.

DIFFERENT TYPES OF SOFTWARE DEVELOPMENT LIFE CYCLE MODELS

There are various types of Software Development Life Cycle models. The types are
 Water Fall Model
 Spiral Model
 V Model
 Iterative Model

WATER FALL MODEL:

 The Water Fall Model has the planning, analysis, implementation and testing phase.
 This model is different from traditional model in such a way that testing phase comes
after the implementation phase.

USA:+1-770-777-1269 || UK:+44-0203-371-7165

 In such model after the complete software is produced and implemented onto the
application the testing is carried out.

Advantages:
o All the phases are completed at one time
o It has a rigid structure which is easy to use and each phase has review process.
o Good for small project

Disadvantages:
o Future adjustments in the project are not possible.
o No prototypes are produced
o Not suitable for projects with moderate requirements, long projects, and for the
projects which may undergo future changes.

SPIRAL MODEL:

 The spiral model has four phases planning, risk analysis, engineering and evaluation.
 It emphasis more on risk analysis.
 In this model the project undergoes each phases repeatedly called spirals.
 The planning phase is the baseline spiral and each subsequent spiral is build on spiral
model
 These type of model is used in risk analyzing projects for eg in space crafts.

Advantages:
o Importance is placed more on risk analysis
o Software is produced in the early stage.

Disadvantages:
o Not suitable for small projects
o It is very costly
USA:+1-770-777-1269 || UK:+44-0203-371-7165

o Needs expertise for such model

V MODEL:

 It explains the relationship between each phase and the associated testing phase.
 In this type each phase undergoes testing i.e for each phase a test deign is created and
testing is carried on the corresponding designs and undergoes coding phase if defect is
determined.
 Since it does not follow a linear path and bends after coding phase this model is
termed as V-model.

Advantages:
o Since each phase has its own test design it can produce good results.

USA:+1-770-777-1269 || UK:+44-0203-371-7165

o Simple and easy to use
o It can be used for small projects and the requirements are clearly understood.

Disadvantages:
o No prototypes are produced.
o Do not have the clear path the problems found after each testing phase.
o Adjustment in future is less or not possible.

Example FOR SDLC:

ATT is the Mobile Service Provider, and do not create or produce their own website, hence
they go in search of companies who can create their required application (website, paying
bills online, online chat)
Here the ATT Company is termed to the CLIENT and the Company who takes the project is
termed to SERVICE BASED COMPANY. In this example we can take H2K as Service based
Company.

Now the CLIENT needs an online application where they need their customers to pay their
bills online through various modes, view their call summary and do account management.

Requirements
In this phase H2K’s BA team discuss with ATT’s BA team and gathers requirements from ATT.

ATT says they need an online application where they need their customers to pay their bills

online through various modes, view their call summary and do account management.

H2K BA discuss in a meeting to make clear about the requirements and document the

requirements in a document called BRD (Business Requirement Document) containing

information like

What is all the browser they need this website to be opened

What are the modes of payment

If the customer needs to view what kind of user id and password etc

USA:+1-770-777-1269 || UK:+44-0203-371-7165

Design:
In this design phase the gathered requirements will converted into HLD and LLD. Use-cases,
Design Specifications, Technical specs, flowcharts will be designed.

HLD: Has the information about the structure of login application, screen navigation process.
It contains the flow-graph info, use cases of ATT website, how login is going to appear.
Example for the flow graph:

Open the Browser type in
URL www.att.com

Hits page on google
Corre No search
ct url

Yes

www.att.com page opens
with login option

Yes

Login has username and
password field

Yes

USA:+1-770-777-1269 || UK:+44-0203-371-7165

Login with valid
username and password

Displays error message
Corre
ct UN

Yes

Displays page
welcome<Customer Name>

LLD:

The LLD document contains info as follows
User Name:
 It should be 10 digits number i.e the customer mobile number

Password:
 It should be alphanumeric
 It should contain at least one upper case and one special character
 It should be max strength of 10 values and min of 6 values

Hence it contains every detail of HLD in a explanatory manner.

Coding Phase:
In this phase the login page is created on codes, and html tags.

Testing Phase:
In this phase QA testers of H2K tests this application with valid username and password and
test for that it do not invalid username and password and tests the whole application and
makes sure it produces the expected result, able to pay bills through all modes, etc checks
whether it meets all the requirements.

Maintenance and Support

USA:+1-770-777-1269 || UK:+44-0203-371-7165

Once after this application is developed and tested by H2K this application is given to ATT. If
ATT has any issues, if they have any doubts in future, H2K stays in track with ATT and
resolves issues to gain customer good will.
All the issues faced in this project will be summarized and will be documented for future
reference.

USA:+1-770-777-1269 || UK:+44-0203-371-7165

SDLC software testing

Recommandé

Recommandé

Contenu connexe

Similaire à SDLC software testing

Similaire à SDLC software testing (20)

Plus de H2Kinfosys

Plus de H2Kinfosys (18)

Dernier

Dernier (20)

SDLC software testing