0% found this document useful (0 votes)
6 views138 pages

Complete Manual

The document outlines the Software Development Life Cycle (SDLC), detailing its phases including requirement collection, feasibility study, design, coding, testing, installation, and maintenance. It discusses various SDLC models such as Waterfall, Prototype, Spiral, V&V, and Hybrid models, highlighting their advantages and disadvantages. Additionally, it emphasizes the importance of clear requirements and the processes of verification and validation in software development.

Uploaded by

Mahesh Degala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views138 pages

Complete Manual

The document outlines the Software Development Life Cycle (SDLC), detailing its phases including requirement collection, feasibility study, design, coding, testing, installation, and maintenance. It discusses various SDLC models such as Waterfall, Prototype, Spiral, V&V, and Hybrid models, highlighting their advantages and disadvantages. Additionally, it emphasizes the importance of clear requirements and the processes of verification and validation in software development.

Uploaded by

Mahesh Degala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 138

OM

clíent /Customer ’ Comes up with Req


&approaches o compong

B oes to chen t place uderstond


Cust reQuYImeots, Collect those In
form of docu ments.

BA
Requirnt Client
Prem

Business Analyst
Shop
Requirement olection ’ GA

profitablity
finance Team : check

Feasibility
Stud y
HR Team:Resource avalability
ArchiteCt/ PM : Technical doability

module-level Desig CHLO)


Design
ConponeDt -leve Design CLD)

Coding’ by Dev Jcompose.


feature
To
oY
Deects Module SenBoz
code
ychat
Testing ' Test Eng
Componnts

Ins tallation ’ Test Eng

mainte neoce ’ 1R
SDLC:

’ SDLC Stonds for SOftawore DevelopreNt Life Cycle.


’ It is a Step by Step prOCdure to develop on pplication.

’ It ConsistS of VarioUs phases SUcb as


Rquirementcolle cton,
Feasibility study. Design, Coding, Testing, tnstoll ation ond
maintenence

C) RequiremeNt ollection:

In this phase, the businesS analySt Collects thr busincss needs


of the client /customer in the form of document and bring it
back to the company
(a) Feasibility Study :
In this phase, a team of people Sit together a decide obether
the project is doable or not, i-e HR team decides the aailability
resour Ces, finance teom decides the OSt whereas pOect
manogers and architects decide technally te project doable
OY not

C3) Design:
De sign means blueprint of the applicQion. It is of 2types :
(a) High Level Design
cb) LoW ievel Des ign

Ca) HLD:

HLD IS also kOown as Module 1evel Design & it is done by


the orchitects.

Cb) LLD:
LLD iS dso Known as
coponent tevel sign & it is dore by
projcct managers
(4) coding:
the Code by
To this phase, the developer Starts writing
cne programmng larguag.
chosing the code by developes
continJe untl
This proress
he application is Tadg
(5) Testing:
applration is ready, the test enganRer Star ts
-’ one the checking the applica6,
cohile
checking the qpplicaion.
enounCY SoMe de fe cts
the test ngineer ay to the
handed Over
dcveloper. The develcm
defects are the defects o
code changes to fin
do the necessar9
test Ergincer
give it back to the test ergine
finding the defects by the
’ Tbis prOcess of developcY continue, unil th reqdy
the
ond get it fixed by
application becomeS Stable.

(6) lnstollaton:
application is moved from ompany
In this phasc,tothe stable
the Custoer enviYonment: Tt is done by a
envronment
aled instalhtion to
Separate team

C) Maintence
into the customer's envi
deployed
Once the applcation is the application. chik
ronment the Customer start us ng
Customer may encoUNter Some issues ln
using it, the
and
ver CMe Such isS
UeSget it resolved
Order to
Test erqiner and one developer
imme ditey, one Custoner'S eOVIYONNeNt for a par ticular
deployed into the

period of time.
Models of SDLC :

|o Watey fall Model


& Prototype Model
3" Spiral Model
4 V& V Model
5. Ny brid Mel
gile Methodology

>why chent ask for in betueen changes ?


Business need incTeasS CBaby Prooduct)
Market Ompetetion CICICI- HDFC)
Te chrology changes CAdd UPI Pay ment)

Cn waterfall Madel :

SDLC = Release

Release-I Rèlcasc-2 Release-3

Rea, Colection Reg. colectio

Feas1bility Study chengesFS


changes

besign Design rsgn


coding coding
Teshng Testing Testng
Installaion Instalotion Instalaon
mntenene
rintene MCintca
model is the base model of SDLC and all motels
’ (UatCrfall
are derived from it.
iE is freezed
’ ln this model, once Yequirements are Colecled
On thereaftcY the application is developd in a Seq uentioal
ONder ie phase is the input of the next
phase.
implemcnted i the
’ ln betcween Changes given buy clhent aYe
allocsed.
net Release. Hence Release-lvel changes are

Disavantages :
not ollocxe
’ In betaren changes
’ No poYallel Deliverables
Revieu pYOCCSS doesn t exist.

flow of Detects.
’ Do aonaord
only
’ coding Testig is done by developers medialSoftaarr
Advantages
ife riticat and
suita ble model for
’ It is the best
machine CTitI( al applications
Smitary Sl
(3) Prototy pe Model:

Requrement Collecion

Feasibilty study

Prototypr Developnertuox eng


Prototyr Testing

Revieo & Approval

Design

Coding
Testing
Installotion

maintenere

for Prototype ts model, wbeever the custongS are


new to Softare.

’ In ths model, a raphca d the application is developed and


approved by the clhent before moving into actua devel opmd
of the applicaion he cient on ask for inberween Charges.

Ad vontaqes:

’ In between changes are allowed


eiSts.
’ No cUstome rejection /Custoncr SaISfactión
mlhple Sinilar
’ Prototy pe once developcd , On be re used fo
CUStOmer
Disadvantages

’ I t iS a time consuming moce l


’ No parallel deivera bles
does n't eiSt:
’ Revi ew pYCess

(3 Spiral Model
chenA
GMAL
Inbor
Compo
Db R
fogin
Design
Da Ra
Sent c6Y
Ta
Tb
+Tatb
l cr
t Qtbt
R DYaft
OUtboY
C
Spam
Chat
Coding Testing Lhelp
deperndent
’ we go for Spiral model, Uhneve the modules are
mdel, ce pick few ot the deperdent mdales,
’tn this
those and deliver those to the custor very intiay
develop apphcation for
thas the customer Start using the
Staoe, So on adding ne
wbile the comn pang keep
theiy business, Mean
features.
mti pe
’ The apphcatlon is delivere to the CustomeY n
enhanced erSon of the
is the
releases ,where each relcase
previous relase.

Advantages:
Customer StOrt using the applicaon at ery initial stage.

between YequrYeent Changes are alo wed
’ In
Disad vantages:
’ND paralel de liverables.
’ ReviCw Process doesn't ex1st

Y In-bet ueen changrs are qven bu the client are a 2 typo.


Ci) Mino1 Chan9
Ci) MajoY Chanoc

ci) MinoY Chan9e:


implecentation of
Minor charges Qe those Changes, due to
cUhiCh,the existing featuYes may ot get effected
’ Henc, Such charges are imple mcoted in the Some cycle.

eg- In atachment Section a the compose option, prev iousy h


m0 permissible Size aas o MB. NOw the Customer need the
Size to be 20 mg

ci) Major changc


Major Changes are thoe changes, due to implementatio of
whch,the exstrg features moy get eected.
’ Hencc, uch changs are implemented in the ne ycle.
ea- Previously in compose, atachmnt ans not there. Duc
to odditon of atachment as per ustomer requirencnt, the
exsting features ay ger ffectCd Hene, 1t is implemetra
in the net cycle.
Charocteristics o a Gcod RequiYeMent

’ Tt should be in Sinple engi sh loguage.


Seque
’ It Should be in propes
’ Tt Shauld be in detai.
’Tt Should be meouYa ble.
customeY Rquirement Specification SoftoaYe Reguirecnt Specitaton
(CRS) (SRS)
Business RequiYeoent Specikication Functonal Specification CFS)
(BRS)

1. To cget insck th a pplcation


Text Bo
a. Creote ail ad Send it |"|: Username L
accepts 4 Chagcters.
ShOu ld be Savd 1·1- I I t
3 Al sent mail
CTezt B07]
inside yecerver's c . |:2. PassJOrd
di9its.
mail should be Save I2-It accepts 4
1 A Copy c
13 Ok Cbuton)
in Sender's ale
erabled
1·3-1 It should be
Fast messaging servICe. 14- Canced [button]
cnabled
|41: [t should be
S(inK]
15- forgot Passord
It Should b active
|51

(verification & Valdation)


C4) V &VModel

Review the CRS

SRS
Review
Cwrte
UAT doc
the
ST doc
SRS

System
UAT chent
Review HLD
Testing
Arch
HLD
write IT DOL
Reviec LD
otTeegst1inagtion Testcr

verifcation - TFeustnincgtional
JLLD) urite CT
mangcr
Document/ Produ ction
Sorver
Developo
coding
’ 0e Q0 for V&V model, Cohenever the YeOuirements are
huor and comple
In Ihis madel, an the drowbacks of caterfall model has becn
erodicated.

Advantages
’Revew prOCeSS eXiSts
’ Para lel deliverables XISts
’ ln betwcen chanqcs aYe alloJed
’ No dounYd HoJ of defects

? Testino team are invol ved from the initial Stagc,henCe they
Over the reqrements
hove moYe clarity

Disadvan tages:
involved
’ It iS a OStiey approach, SinCe the (omplete tam aYe
from initial stage

’ It iS a tlne takig model, Since the hole project is geting


developed a delivered in a Single Yelease.
seUor k nred to be done
1C in between reaurement Changes , lot Ot

verificahion Vahdaton

i) Tt iS the pYDcess to cheek/ ensute


ci) valhdaton is a pYOceSs to ensure
that tte correct product is qeting the product cohich is Yead s mects
developed the CUstoner's businss rds
Cri) Tt includes go through, n thraug cy This pha se include s variouS types
Yeview,dotumeotation & coding
of Csting Such as wBT, FT, IT,ST
ciiy It i a staic proess, Sinee the entire and UAT,
prDCess Is fixed and changcs Qre Ciny aldation is a dyronic proRSS
done only by dient Se in this phasc, lot of chargcs y
(V) Verification is also KOODO a happen due to defots.
Quality fSsurance (O) civy Val'dation l_ also Knoon aS
Oualtg conhol (@cy
(5) Hybrid Model
Combintion oE too mOdels to derve / meet the customcr's
busineSS nccd 1S Knoon as hybrid moel

y T0o possiblc
combination ol models ore
Model
ciy Prototgpe & V
pe Mode!
(i) SpiYOJ & pDtoty
other
NOTE: waterfall model cant be com bincd cth anY
model, Since Caterfall mde), in between chonge
not allowed

C1) Prototype e VModel:

Review CRS
write UAT DOr.
Review SeS
CUYite ST OC
Revie HLD
Prototype Deu
CUY0 te IT D0
Prototy
peTesins HLD Prod uction
Review ADproval Review D Serve
LLD
Wite FT
F
Coding

wel as
’ auhen ever thr customr is DcJ to thc Softa)are
Co mbination
the project is huge ond comple, Je go for the
o prottype & V- Model.
’Ib this mode, once the sRS is Yeady, a Yapli ca of the appli
aion is develo ped and apprOVed by the client beto re moo
nto hioh level desion
’It hos Com bined advontage of prototype V-Modc
Advontaqes
alled
-’ In bet ween changes aYe
’Review pyoCeSS exISts.
flo Of defccts
3NO Pay dotoN wOrd
existS
PoYa llel deliverables have
hence they
in volved from initial Stag ,
Testing team 1s
ver
the Yequiremepts
more
eovty
CUstomer rejecton/customer atsfactiorn eists
Nb
develop , it on be used for muiple
’ Once PYototype is
Simllay projects
’ony
for1 s t
Releasc
Prototy pe Model:
Prototype Dev
Prototy pe Testins
Revieus Appuval client
22

Design Da Ra R.A
Co Ta

To+
Tats

cod ing Testung

customer is Des to the SOft oare as oell as


’ ohen ever the
ombingion
the madules are dependent, we go for the
SpiraJ u prototype model
-’ In this moel, 1st we make 9 Yaplica cf the opplcaton,
thereafter ae develop the appticaon
qt it approv ed by the dient,
in mWple releases.
Advantages:

’ln beween changes aYe allowed.


’ NO CUstomcY Tejection
be used for al su ch
’ onCe prototpe Is developed ,it can
SimiloY CUStomers

’ customers Start using the applation during initla stage.

waterfall Model

uSed Jhen th
(æ) anterfall modl is Used when C) VeU moc) is
softaare is life titcal aand requirenents are hge and
the
machine CTitical complex
e0Sts
exist ci) Revie) Proess
Cii) RevIC) PrDceSs drn't
are
Cin) Io betern chon9rs are
not cii) Io beteen Chonges
a llowed
deliver ed n q
relras Ci) En tire s/a) Is
Civ) There mght be multiple Sngle Yelease.
the S/w
in ofeY to deliver
qlloed)
Cie Relase level chonges (U) Porallel deliverables exist.
t exist
CU) Pongiel dehuera bes doesn CvD No downaord flow of
defeets

Cvi) oonard flo of Derects ocauY


Types or SOftware Testing

Sortyarc Testng

white- G0x Blaok B0X Grey Go


Testing Testing Testng
(Developer) CTE)

Jhite-or Testi ng:


performed ky the developers
testing
’ lo this type f testing. the develepeYs Check theiY o00
Code ine by ine before handing ove the application
to the test engineer.
’Sinnce. he Codes CYe Visible to the developer, it 1s
gloss box testing/Trans parent Tes ting
aled
NOTE : weT is not res ponsible for sta ble appications.
developer to Teduce the Cownt
Tt is done by the
Code Since , a Smnal eror in the
f eYYOrs in te
for the tes t
COde Can project a criticol bug
engineer.
Bhck-Bo Tstrg:
Erginers.
7T 1s a type of testirg pexfored by the Test the applicati
check
type & testig, the test engineer
’ In this
end cseY the appiatione
Usig cOde, it is also Krocn as
t see th
’ Since the test erginecY Can
Clos cd -Bo Testirg
to make thr appli
NOTE: B.T S (ocnplsory and it is YeSponsible
Cation Stable
Girey-Bor Testing
s tr ppiaton
’ Ris a typc cf testing in which, the Code os tuell
team ok people ie the Same teom peopl
are checked by Some
oloced by checkiA the
first check th (oe ine by ine
appli cation

NOTE hry Box Testing a bad approach,Snce cheCkng the coÀe ant
applicatin by Same team of peopie
CaUse lack cf aruYay

Uhite-gox Testing Proces

Requiremen ts Business Logic Unit Test Program

(1) Code to login

(2) Balcince EngYY (2) Codo for ba nce enguy c3)o re or bal. ene

Transfer
3) Amount tranifer
(3) Codr for omount tranfer c3 UTP for amt
(4) Statenent
fC4) Code for S taunent (4 UTe for stat cment

(5) ioans C5) code for Loans (5) UIp for loans

wYite the business logic for ther assiqned modales


’ Developers
Yeady, the de check their Code Line by
Once the code is

Yequired to check the (ode before testrg


’ Since the time
fects are ound, the deueloper arite
Qrd aso to Yecheck once de
peice of (Cde in ordey to check the business
an itiona
Such s JUnt, TestNa
US ing els

’ he developer who has don the corrg îor a particular modue


S Yesponsi ble Writrg the Unit test Aogram afso
’Once the is read, t Can be usd oUtiple tie
both ot the tm of honng th applation the to the
Test cnginccr kor also wh oSt lzig the detcC

" whitc Box TesSting is done oth the helo of to


is
Since checking the ere ine by ine tedious proces,
as oel as accuracy my rot eist.
Some commony Used Unit testirg tools are Junt, TestnG
understars the TCOuYenents Of
Every deve lopg'r frst
their ossigned mcdales and arits the bysiness log
dlevelope Y urites
In order to check the lqic Simuwtonrous lg the
unt test prCgram eheOk the
peicC ot cDde Which in Yetarn
UTP iS a Soal
an buSiness logic
on thetr assg
Every develuper cteS the unit tcst program
modcles
ONe, the eveloper Yuns the unit test
one the ccg 15
pYOgsaIm cwith the hep of unt testig tool Cocde ond
he unt testirg tool identifg th errors
ae qenerate the YeSult
" Oe qain the developer dors the neceeOYY code chorge.do
developer aJill
GoheneU Test rgineer firs a dcfect, the identy
essay code chargcs a run the UTP to
Sefe the
the errOrS in the coce.
acYOSS t iele
Can be resus ed
Hence, the Unt test pragam
releases

unit test
Snce in WBT
NOTE C31 iS also Knoon as Unt Testia
uYitten to check thr Code linc by line.
prcgrams
Types of WBT
ci) Path Testing
cio Soop Testing
Ciw) Condition TeSting
CiV) Memorg Testng
(u) Res ponse Tior Testing

cis hth Testing


’ Ih this typc wBT, the developeY Check for
Code Con br
of he Code uth multiple branch codes
inked Cuith Mtipe branch coes & cach bcnch code may
have miple Sb bronches.
’ As a develbper, the develcper makes Combiaion
cf coale reerives the desired output
A-B-E
A-B-F (onbinaONS
B A-C-G

A-D- I

ci dop esting enecution of th


check for th
wBT, the deulopcr part1cuar
’ in this type f times; i e 0nce we enecte a
no of ecuted for
CCde for desired Portion of th Code may qet
Code
times.
desiYa no tf
enteY
into
cin Condtion Testing
the occution
the deuclopey check tor
(orclition Satisty
Ct r code acCOli ng to the oition,ic if shaud
exect et .or else the
the ccde Shoubl gt
Skippcd
not
’ Each lne of the cole ay

lan bC eXecte
EilheY

(ív) Meny Testirg Check


the develo per Shoct be
’ in ths typc toof WBT
Codes i-e the lode
eecute tthe that it onscrRs
framc worK so
wel organiZed for
Same ode
tr diffe nt
the
Teusing
miniun memorg by
times

3
(v) ResponsSe Tine Testing
prformanc
In this type of W8T, the devciopey check for the execut cd
of the code ioe the timc taken by thr (cde io get
and relrive the desire Otput.
the
’ he lesser the ines of (cde thr deveopcr wYites , the faster
cde gets exected
’ In order to ake the coode excCUte iaster, al coiq Stanoard
Must be foloU.

Inpts for FAN


Inputs for TAN

vali - 22)222222)2 -M
invelid - 3333333891 Invaid 12343G7S4
Iwvoid Blant leill)
Invai abcdefqghy calpha) -£M
Invalid abdet
Invali - abc35)K 9-)-e
ghiyki)3q
Invalid (a# 123|: CS-c)-EM
Iwalid 5c@it K
(nvad i -
invc Same as fAN

Ioputs for

Volid

Invali d - 5000o
Inyauid - abced
abci23

Inald ( !
INalid- 200000
inatd- 50004&
Insufcit Rcnc
in valid-
thvald-ly
Tech M
Functional Testing
1CiCi
Ano Ticnsfer CMaleJ clicot
Lonline Banin5J
(omors Proet
AMouNr

Eoch mdcler have Uarious

Compoets / object 3-Statemen


4:Amt- TYansfer
joans

ononts,
modles as aell as it's
each and every
’ with
checking inpts indivisucllg or Or by one,
VariouS com biation c
is caM ed as functional testin
followd To perform Funchonal testing:
Reles to be then continue with
inpcut and
Alays StaYt testing aith valid
’ i0pts .
al other (om bintion Of for al other
Component, the inpats
extly
whle checking onc valid in order to lcate here
Compone Dts must be

is the defect iootsy Since Simky typ


Caith Similar typc of an DaCY-endncg
’ Do not test testing , hich is
CaUse OUCY
ck ippuws may
PYOCesS.
of pr edict t YcQuiyement. If thr Yeaurrment
’ Don' t aSSume the concened person.
clecoY, Cd it ClaYified by
are Dot
NOE: The tougheSi Port ciuring the testug procesS is to deidr
when to Stop testing & this decision is talken y
tes t
test engineer, hcn they feel that the maimuum
ac hicved:
oNe each & evexy modele well as it's (ompomts
as
are checKed Uith UCYIOUS combinaton of inpuk and
qets thr desired output , oe Say functioal testng
iS oveY -

IntegraioN Testing
or dta flo betOcen two deperdent
the elationsh
’ checking
mles is KnOCIn as Integraticn testing
Rules to be tollowed to Perform IntegratiOn Testr
for functional
the applicatlon is YeCcy

Aesing , ue go for integraton tstrng


’Once functiond testing is ouer and evey modde
donr foY eccc h
is modcrS,
’ functional testing betccen thr depcndent
(s done only pcrform
i-c for
testing
Som
madle Cindivisual modde),Cue dont

integrcticn testing good product


integrtion testing VeYY
’ In order to pevform
Yequired-
Knau ledg is
perform inteerian testing sOU rer, destinti
’ 1n order to
and ia oye
SOoYCC
to dest1ntion and
transfY from
’ Doo cUoy ScvC i0 thc destintion
Cocnpusoy it shauld qet

Dtar5ooDJ
Balan

500
Chating applicion, if chas aYC geting
yc, then it Comes Integration testig, whereas ectures
or
lateY
ash chat Chas Do Saved,SO the
gors for kuockienl testin

chat Bo J chalB0ML

Sourco
Destinajicn

’ Integr aHon testing sOuYce to dest ination


1s alays done bet

CThey Keep os chargng in de pertt modaes )

’Data may transfer {rom Single SOurC to mutiple dstiraion


& viCe - veYSa.

Login
Home
Saurc
Conpose
’Singir
SourcC
SeBorK Muin
Dest
Datt s<

Trash]
Spam
Chat
Hel p Independet Modcules
seting
’SomtimC modclc Heoe 1.1
data may transfer cOTthi the
the modle too
is done Cithn

Typcs c Intecrtion Testing

Incgraion Testin9

Increnent au NON. (ncement a


IT IT

ToP Doon Botion up

03 n3

m9

Ibgeeotal IT:
transfers in
’ In thi[ type cf Integrao testing cata alys bott o -Up.
top - botton oY
a Sequeotial order either from

Non-inreNtal IT:
inlegration testing. cdta may rancfer betewern
this tyrc ch
’ Io
cothow folbeing ang Sequence of paticn.
t o mcos
Susteom Testing

System Testn

(he appicatíon ike aN ena


’checking the end to end {low c
User ús iNg the application is knon as ystem Tectirng

testing. the Test ergineer navicarrsas throgh


7in System modcies a the
a whole
to che ck the appliatioH
Syatem: sI ystrn Testing.
(T follod by
’ vay test egineer pcrforms

A-7

FAN
’FAN
TAN
TAN
yanaunt
AMT

Tyanslr
I.T Ar.

ement
AT’ St at
A-T> Receiver's Ba

A-T’ loan
AT> CYedit car

(ogin Home ’ Bal Enq cgou'


NOTE
modes , each nod r may
ore application have n a

o-ct Sub-modies u each Sub- madee may
have n
of Componrnts Y objects
once function an intrgraion
S1is done by (he tect engine er
are done ouer.
tesing
finonl, integrai on a SySs tem Trstin9

You might also like