sytematic approach to develop software applications

SDLC
Models:
Sequential model- waterfall,vmodel
Incremental model-agile,spiral,xp - is very expensive success rate is very high
Levels
1.unit/program/module/component-performed by developers
2.Integration testing-similiar to unit
3.System testing-performed by testers(independent testers using blackbox testing
is a specification base testing)
4.Acceptance Testing- end user(customer side people)
blackbox testing- no need to aware of code
white box testing- structural testing
Types:
a)Function testing- it is mandatory 82-85 percent market area
verifying component or system functionality with respect to functional requireme
nts
ex:
1.funtionality testing
2.security testing
b)Non-Functional testing-15-20percent market area
verify sytems quality attributes with respect to non-functional requirements
ex:
load/stress/endurance/performance
usaubility
localiztion
internaliztion
recovery
reliability
configuration
Test design techniques(easy way to do something):
exhaustive testing(is impratctical)-testing with all possible input and pre-cond
itions
in order to reduce input domain we use test design techniques.
1.White box-internal or code/structure base testing
statement testing
condition testing
multicondtion testing
decision testing
2.Black box-external testing,specification base techinque,independent testers us
e this testing
equivalent classes or partition
ex
boundary values analysis
decision table
state transisition
use case testing
3.Experience based techniques-informal way
formal and informal testing
formal testing
time is limited or no documentation or less budget or less infrastructure we fol

low experience base testing

informal testing
error guessing,exploratory testing
software test process/STLC-It is a standarad process
A. Test planning-tl or manager responsible, members contribution also required f
or test planning
B.Test design-understanding requirements,deriving scenarios,test case documentat
ion,test data collection
C.Test execution- forming test batches,execution queue.
levels of TE
sanity testing-verifying built is acceptable or not by executing basic functiona
lity testing ex:login
comprehensive testing-executing all possible or maximum cases,Defect reporting a
nd tracking,Re and Regression testing on modified software builds
D.Test closure
Evaluating exit criteria
collecting all artifacts from test activities
preparing test summary reports
summarizing all test activities
sending test deliverables to customer
Software quality standards
difference between testing and quality
testing improves quality if we conduct better testing can improve quality of the
application
a.ISO Standards(Internation standarads for organization)
b.IEEE standards
c.CMM/CMMI standards-capability maturity model integration
Focusing areas
Understanding requirements
test case documentation
test data collection
test execution
defect reporting and tracking