Section A: Multiple Choices 1) The basic building block of any activity in any phase of

the SDLC which fo!s the coe of CTS"s #eviews and Testing $ocess is called the :
$ee #eview
%eification and %alidation Techni&ues
ETVX Model
All of the above
') (((((((( techni&ues e)a!ine input and output of test data and deive test cases based
on an analysis of the input and output do!ains*
+low, Coveage - .ased testing
Syste! .ased testing
Domain-Based testing
/one of the above
0) CTS is CMM1 Level 2 cetified ogani3ation* %eification and %alidation $ocess
Aeas lies at
CMM1 Level '
CMMI Level 3
CMM1 Level 4
CMM1 Level 2
4) The challenges in Testing ae:
Lack of testing tools
5eneation of ade&uate test cases
6ften develop!ent effot inceases and thee is vey little ti!e fo testing
All of the above
2) $epaation of a (((((((( is vey i!potant7 befoe conducting 8nit testing*
Syste! Test $lan
8nit Test Case
Unit Test Plan
All of the above
9) (((((((( is the pocess of evaluating a syste! to veify that it satisfies specified
e&uie!ents*
Testing
Veifi!ation
#eviews
1nspection
:) 1n a softwae develop!ent envion!ent (((((((((((( is confi!ation that the output
of a paticula phase of develop!ent !eets all of the input e&uie!ents fo that phase*
#eviews and Testing
"oft#ae Validation
Softwae Testing
Softwae %eification
;) The outputs of eview !eeting ae
Defect Log
#ewok Task list
#eview !eeting !inutes
All of the above
<) (((((((( is used to test opeation of the softwae and input-output data to ensue that
the softwae is pefo!ing well*
#eview Techni&ues
Veifi!ation
Softwae Testing
All of the above
1=) >os ae classified based on
Seveity
Type
Both $%& and $'&
/one of the above
11) ((((((((((( techni&ue can be used fo testing pocess
D(E and P)gh Mati*
D6> and ?+D
?+D and 6thogonal aay
D6> and 6thogonal aay
1') Advantages of Auto!ated testing tools ae:
#epeatability @ Scalability
#obustness
>cono!y
All of the above
10) (((((((((( is used to test syste! data and e)a!ine syste! output*
Softwae Analysing
Softwae #eview
"oft#ae Testing
Softwae 1nspection
14) (((((((( co!ple)ity is a !easue of algoith!ic co!ple)ity7 calculated by counting
opeatos and opeands*
McCabe
+alstead
Co!bination
/one of the above
12) Ahich of the following is the !ost i!potant citeia to stat eview of a wok ite!*
Che!, fo !om-leteness of the #o, item to be evie#ed BC)
Appoved by the $oDect Manage
Sign off by the custo!e
Check whethe esti!ations of eview is available
19) ((((((((((( stage ensues that eview co!!ents have been incopoated duing
ewok
#eview
.e#o,
Causal Analysis
+ollow up
1:) A visual e)a!ination of a softwae poduct to detect and identify softwae ano!alies
o defects including eos and deviations fo! standads is
Aalkthough
Ins-e!tion
Testing
/one of the above
1;) (((((((( helps analy3e the e&uied effots fo validating the acceptability of a
softwae poduct*
Test Case
Test $lan
Test Scipt
All of the above
1<) Ahich of the following eview types is used fo building code o docu!ents by
discussing with the !e!bes of the develop!ent tea! and i!poving the wok ite! *
Table .evie#
Aalk thoughs
1nspection
$ee #eview
'=) (((((((((( i!plies testing the syste! with the intent of confi!ing the eadiness of
the poduct and custo!e acceptance of the poduct*
Load testing
Syste! testing
A!!e-tan!e Testing
1ntegation testing
'1) 1f the cost of fi)ing a defect in the e&uie!ents phase is 17 what is the elative cost
of fi)ing a defect in the Testing $hase
%/-01
1=
1= to 12
E1==
'') Tools co!!only used fo causal analysis ae
$aeto Analysis
#oot cause analysis
Both $%& and $'&
/one of the above
'0) An info!al !eeting fo evaluation o info!ation pupose is a
2al,tho)gh
1nspection
Testing
/one of the above
'4) Ahich of the following pocedues ae elated to eviews in veloci-?C
#eview
#elease #eview
$oposal,Contact eview
All of the above
'2) Ahich of the following could be a citeia to stop eview
Defects ae ectified and veified by eview tea! leade
#eviewes decide that thee is no need fo anothe eview
Too !any eos ae found in the eview
All of the above
(((((((((((((((((((((((((((((((((((((((-

#eviews and Testing
Section A: Multiple Choices 1) Ahich of the following ae boad types of efficiency
techni&ues in testing :
+low, Coveage - .ased testing
Do!ain .ased testing
Syste! .ased testing
Both $a& and $b&
') (((((( povides a !easue of the conditions which could ensue that a banch is
e)ecuted*
Condition coveage
Condition opeand coveage
Decision coveage
.oth Ba) and Bb)
0) (((((((((( testing shall be caied out if thee ae !ultiple !odules in the poDect*
8nit
Mod)le3 4eat)e
.uild
Syste!
4) Ahich of the following eviews have well defined oles
Aalkthough
$ee eview
Table evie#
All of the above
2) ((((((((((((( is a way of poving that you syste! does what is intended and also
!eets all e&uie!ents*
%eification
%alidation
Veifi!ation and Validation
/one of the above
9) The inputs to planning stage in a eview pocess ae
Poblem definition
List of oles
#eview pocess !ap
/one of the above
:) (((((((((( efes to testing the featues, navigation, e)pected e)pectations7 when
!oe than one uses fo! diffeent !achines opeate on sa!e 6bDects*
Con!)ent testing BC)
+unctional testing
Module testing
All of the above
;) Ahich of the following eview types is used fo building code o docu!ents by
discussing with the !e!bes of the develop!ent tea! and i!poving the wok ite! *
Table #eview
Aalk thoughs
Ins-e!tion
$ee #eview
<) The pupose of ((((((((( is to assue that the poduct o poduct co!ponents fulfill
thei intended use when placed in thei intented envion!ent
Validation
%eification
8se Acceptance Testing
$oduct Testing
1=) Ahich of the following pocedues ae elated to eviews in veloci-?C
#eview
#elease #eview
$oposal,Contact eview
All of the above
11) ((((((((((( techni&ue can be used fo testing pocess
D(E and P)gh Mati*
D6> and ?+D
?+D and 6thogonal aay
D6> and 6thogonal aay
1') The pupose of +unctional testing ae:
finding defects
veifying that the !odule pefo!s its intended functions as stated in the specification
establishing !onfiden!e that a -ogam does #hat it is s)--osed to do
All of the above
10) The outputs of eview !eeting ae
Defect Log
#ewok Task list
#eview !eeting !inutes
All of the above
14) (((((((( can also be called Ahite bo) testing*
1nteface testing
Syste! testing
Unit o Com-onent testing
1ntegation testing
12) Ahich of the following could be a citeia to stop eview
Defects ae ectified and veified by eview tea! leade
#eviewes decide that thee is no need fo anothe eview
Too !any eos ae found in the eview
All of the above
19) Ahich of the following ae highlights of syste! testing C
testing is geneally done by an independent test tea!7 and not by the develope
ai!s at testing a host of vaiables like basic e&uie!ents7 i!plied e&uie!ents7
pefo!ance
testing is based on a vey stuctued appoach fo geneating test cases
All of the above
1:) An info!al !eeting fo evaluation o info!ation pupose is a
2al,tho)gh
1nspection
Testing
/one of the above
1;) The highlights of Acceptance testing ae :
checks the syste! against the e&uie!ent specification
focuses on whethe the syste! delives what was e&uested and is info!ed by the
business
testing done by custo!e and not the develope
All of the above
1<) #eview is a fo!al evaluation techni&ue in which softwae e&uie!ents7 design and
code is e)a!ined in detail by goups of pesons othe than the autho to detect
faults7violations of develop!ent standads and othe poble!s* This definition of eviews
is by
S>1
IEEE
#oge $ess!en
/one of the Above
'=) Testing is the pocess of ((((((((((
evaluating a syste! to veify that it satisfies the specified e&uie!ents
e)ecuting a poga! to find eos
veifying that specifications ae !et
Both $a& and $b&
'1) 1n a softwae develop!ent envion!ent (((((((((((( is confi!ation that the
output of a paticula phase of develop!ent !eets all of the input e&uie!ents fo that
phase*
#eviews and Testing
"oft#ae Validation
Softwae Testing
Softwae %eification
'') Ahich of the following testing is eco!!ended in ode to keep co!pany data and
esouces secue fo! !istaken o accidental uses7 hackes7 and othe !alevolent
attackes*
Safety testing
"e!)it5 testing
Mutation testing
.oth Ba) and Bb)
'0) Ahat is the coect definition of a Test SciptC
1t is a docu!ent that defines the input7 action and e)pected output to dete!ine if a
cetain featue of an application is woking coectly
1t is a docu!ent that descibes the se&uence of steps to e)ecute a test case*
It is a logi!al go)- of test !ases #hi!h #hen ta,en togethe test a -ati!)la
f)n!tion o )nit of the s5stem
/one of the above
'4) (((((((( co!ple)ity !easues the stuctual co!ple)ity of softwae by &uantifying
the nu!be of linealy-independent paths unning though a poga! !odule*
M!Cabe
Falstead
Co!bination
/one of the above
'2) A (((((((( is an i!itation of a unit7 used in place of the eal unit to facilitate
testing*
Test dive
Test bed
Test st)b
Test build
((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((--

#eviews and Testing
Section A: Multiple Choices 1) Ahich of the following ae obDectives of a eviewC
%eifying that specifications ae !et
1dentifying deviations fo! standads and specifications
Collecting data fo i!pove!ent
All of the above
') The highlights of Acceptance testing ae :
checks the syste! against the e&uie!ent specification
focuses on whethe the syste! delives what was e&uested and is info!ed by the
business
testing done by custo!e and not the develope
All of the above
0) Defects found in eviews ae classified in ' ways* The ' ways ae :
$ioity7 Souce
"eveit56 T5-e
MaDo7 Mino
Cos!etic7 Logical
4) Ahich of the following eview types is used fo building code o docu!ents by
discussing with the !e!bes of the develop!ent tea! and i!poving the wok ite! *
Table #eview
Aalk thoughs
Ins-e!tion
$ee #eview
2) ((((((((( can be done with checklists7 issues lists7 walkthoughs7 and inspection
!eetings*
%eification
%alidation
1nspection
Testing
9) #eview is a fo!al evaluation techni&ue in which softwae e&uie!ents7 design and
code is e)a!ined in detail by goups of pesons othe than the autho to detect
faults7violations of develop!ent standads and othe poble!s* This definition of eviews
is by
S>1
IEEE
#oge $ess!en
/one of the Above
:) Ahich of the following ae diffeent types of eviewsC
Aalkthough
1nspections
Both $a& and $b& BC)
/one of the above
;) (((((((((( efes to testing the featues, navigation, e)pected e)pectations7 when
!oe than one uses fo! diffeent !achines opeate on sa!e 6bDects*
Con!)ent testing BC)
+unctional testing
Module testing
All of the above
<) 1n a softwae develop!ent envion!ent (((((((((((( is confi!ation that the output
of a paticula phase of develop!ent !eets all of the input e&uie!ents fo that phase*
#eviews and Testing
"oft#ae Validation
Softwae Testing
Softwae %eification
1=) ((((((( is used to dete!ine whethe othe syste! softwae co!ponents such as
bowses utilities and co!peting softwae will conflict with the softwae being tested
Mutation Testing
.owse Testing
#eal Ti!e testing
Com-atibilit5 Testing
11) +ocus of the integation testing is to veify
the featues specified in the design has been i!ple!ented
functionality of the syste! as a whole
the inte-mod)le intea!tions thoo)ghl5
All of the above
1') Ahich of the following ae boad types of efficiency techni&ues in testing :
+low, Coveage - .ased testing
Do!ain .ased testing
Syste! .ased testing
Both $a& and $b&
10) %eification and %alidation utili3es (((((((( to analyse and check syste!
epesentations*
.evie# Te!hni7)es BC)
%alidation Techni&ues
Testing Techni&ues
All of the above
14) The outputs of eview !eeting ae
Defect Log
#ewok Task list
#eview !eeting !inutes
All of the above
12) Ahy is !ultiple ounds of syste! testing eco!!endedC
Set of test cases can be e)ecuted in each ound*
A!!ommodate b)g fi*es and eliminate ma*im)m defe!ts
+o testing basic e&uie!ent7 i!plied e&uie!ents 7 pefo!ance !easues in vaious
ounds
shotage of esouces to co!plete testing in one ound
19) Ahich of the following citeia seve as basis fo taking decision to stop testing :
Stop testing when all test cases e)ecute without poducing any eo
Stop testing when the specified test coveage is co!pleted without finding eos
Stop testing when it beco!es unpoductive
All of the above
1:) As the poDect !oves fo! e&uie!ents stage to co!pletion stage7 the cost of fi)ing
defects *
In!eases
Deceases
#e!ains the sa!e
is unaffected by eviews
1;) The diffeent types of flow,coveage based testing ae:
State!ent coveage
+ull $ath coveage
Decision coveage
All of the above
1<) ((((((((( is a docu!ent that defines the input7 action and the coesponding
e)pected output7 to dete!ine if a cetain featue of an application is woking coectly*
Test $lan
Test Scipt
Test Case
Test .ed
'=) $epaation of a (((((((( is vey i!potant7 befoe conducting 8nit testing*
Syste! Test $lan
8nit Test Case
Unit Test Plan
All of the above
'1) (((((((( techni&ues e)a!ine input and output of test data and deive test cases
based on an analysis of the input and output do!ains*
+low, Coveage - .ased testing
Syste! .ased testing
Domain-Based testing
/one of the above
'') The pupose of +unctional testing ae:
finding defects
veifying that the !odule pefo!s its intended functions as stated in the specification
establishing !onfiden!e that a -ogam does #hat it is s)--osed to do
All of the above
'0) The obDectives of #egession testing ae :
it detemines if b)g fi*es have been s)!!essf)l and the5 have not !eated an5 ne#
-oblems
ensues that no degadation of baseline functionality has occued
ensues pefo!ance of two o !oe !odules
.oth Ba) and Bb)
'4) (((((((((( is used to test syste! data and e)a!ine syste! output*
Softwae Analysing
Softwae #eview
"oft#ae Testing
Softwae 1nspection
'2) The pupose of ((((((((( is to assue that the poduct o poduct co!ponents fulfill
thei intended use when placed in thei intented envion!ent
Validation
%eification
8se Acceptance Testing
$oduct Testing





#eviews and Testing
Section A: Multiple Choices 1) Challenges of #eview and Testing ae:
Lack of do!ain e)petise
Monotony of the Dob and coping with e&uie!ent changes
Both $a& and $b&
/one of the above
') (((((((( is a pocess of e)ecuting a poga! with the intent of finding eos*
#eview
Testing
$ee eview
%eification
0) Ahich of the following could be a citeia to stop eview
Defects ae ectified and veified by eview tea! leade
#eviewes decide that thee is no need fo anothe eview
Too !any eos ae found in the eview
All of the above
4) 1n a softwae develop!ent envion!ent (((((((((((( is confi!ation that the output
of a paticula phase of develop!ent !eets all of the input e&uie!ents fo that phase*
#eviews and Testing
"oft#ae Validation
Softwae Testing
Softwae %eification
2) The basic building block of any activity in any phase of the SDLC which fo!s the
coe of CTS"s #eviews and Testing $ocess is called the :
$ee #eview
%eification and %alidation Techni&ues
ETVX Model
All of the above
9) The ((((((((((( based testing is a syste!atic7 statistical way of testing the softwae*
6thogonal Aay
8se inteface
4)n!tionalit5
/one of the above
:) (((((((( is a !ethod fo dete!ining if a set of test data o test cases is useful*
Auto!ated testing
M)tation testing
Module testing
+unctional testing
;) Mike +agan of 1.M published a pape in 1<:97 descibing a !ethod called
(((((((((( which fo!alised the softwae eview pocess*
Pee evie# BC)
6nline eview
$ai eview
Table eview
<) Ahich of the following eviews have well defined oles
Aalkthough
$ee eview
Table evie#
All of the above
1=) (((((( de!onstates satisfactoy suitability fo use in the intended opeating
envion!ent*
1nspection
%eification
Validation
#eview
11) The vaious kinds of classifications of testing ae ((((((((((
Level - based classification
Type - based classification
Syste! - based classification
Both $a& and $b&
1') (((((((( involves checking that each featue specified in the co!ponent design has
been i!ple!ented in the co!ponent*
Unit testing
1ntegation testing
1nteface testing
Syste! testing
10) GTest7 Gpobe7 $uify ae so!e of the (((((((((( used in poDects*
Veifi!ation tools
Testing tools
%alidation tools
All of the above
14) (((((((( involves testing two o !oe !odules togethe with the intent of finding
defects between the !odules*
8nit testing
Integation o intefa!e testing
Syste! testing
+eatue testing
12) Ahich of the following te!plates ae elated to eviews in veloci-?C
#eview
.elease .evie# ")mma5 BC)
Defect $evention #epot
All of the above
19) (((((((( techni&ues e)a!ine input and output of test data and deive test cases
based on an analysis of the input and output do!ains*
+low, Coveage - .ased testing
Syste! .ased testing
Domain-Based testing
/one of the above
1:) Ahich of the following ae the highlights of unit testing C
involves testing of basi! b)ilding blo!,s of the s5stem
testing to veify the inte-!odule inteactions thooughly
testing is geneally done by an independent test tea!7 and not by develope
All of the above
1;) A (((( povides a fa!ewok fo setting the input paa!etes7 e)ecuting the unit and
eading the output paa!ete*
Test bed
Test dive
Test stub
All of the above
1<) Ahich of the following ae obDectives of a eviewC
%eifying that specifications ae !et
1dentifying deviations fo! standads and specifications
Collecting data fo i!pove!ent
All of the above
'=) Ahich of the following ae diffeent types of eviewsC
Aalkthough
1nspections
Both $a& and $b& BC)
/one of the above
'1) The highlights of Acceptance testing ae :
checks the syste! against the e&uie!ent specification
focuses on whethe the syste! delives what was e&uested and is info!ed by the
business
testing done by custo!e and not the develope
All of the above
'') ((((((((( dete!ines how well a poduct pefo!s when a load is placed on the
syste! esouces that neas and then e)ceeds the syste! capacity*
"tess testing
Capacity testing
Load testing
Co!patibility Testing
'0) A goup of test scipts which when taken togethe test all functions of an entie
syste! is called the ((((((((((*
Test Suite
Test Bed
Test $oduct
All of the above
'4) >os ae classified based on
Seveity
Type
Both $%& and $'&
/one of the above
'2) (((((((((( efes to "Ae we building the poduct #15FTC"
#eview
%alidation
Veifi!ation
Testing

#eviews and testing
1) Softwae bugs occu due to ((((((((((( easons*
$oo undestanding of e&uie!ents
$ooly docu!ented code
Softwae co!ple)ity and inade&uate use of develop!ent tools
All of the above
') The ((((((((((( based testing is a syste!atic7 statistical way of testing the softwae*
6thogonal Aay
8se inteface
4)n!tionalit5
/one of the above
0) Ahich of the following te!plates ae elated to eviews in veloci-?C
#eview
.elease .evie# ")mma5 BC)
Defect $evention #epot
All of the above
4) +ocus of the integation testing is to veify
the featues specified in the design has been i!ple!ented
functionality of the syste! as a whole
the inte-mod)le intea!tions thoo)ghl5
All of the above
2) (((((((((( efes to "Ae we building the poduct #15FTC"
#eview
%alidation
Veifi!ation
Testing
9) Ahich of the following eviews have well defined oles
Aalkthough
$ee eview
Table evie#
All of the above
:) (((((((( involves testing two o !oe !odules togethe with the intent of finding
defects between the !odules*
8nit testing
Integation o intefa!e testing
Syste! testing
+eatue testing
;) A (((( povides a fa!ewok fo setting the input paa!etes7 e)ecuting the unit and
eading the output paa!ete*
Test bed
Test dive
Test stub
All of the above
<) So!eti!es a need !ay aise fo an e)tenal eview of the softwae poduct* Ahich of
the following needs will po!pt you to go fo an >#TC
Do!ain Content
Technical Content
Cos!etic Content
All of the above
1=) $epaation of a (((((((( is vey i!potant7 befoe conducting 8nit testing*
Syste! Test $lan
8nit Test Case
Unit Test Plan
All of the above
11) Ahich of the following ae boad types of efficiency techni&ues in testing :
+low, Coveage - .ased testing
Do!ain .ased testing
Syste! .ased testing
Both $a& and $b&
1') The highlights of Acceptance testing ae :
checks the syste! against the e&uie!ent specification
focuses on whethe the syste! delives what was e&uested and is info!ed by the
business
testing done by custo!e and not the develope
All of the above
10) Table eview pocess is followed !ostly fo eviewing docu!ents* Ahat is the othe
na!e of Table #eview $ocessC
$>ST Analysis
.ainsto!ing
+agan"s #eview $ocess
SA6T Analysis
14) The pupose of +unctional testing ae:
finding defects
veifying that the !odule pefo!s its intended functions as stated in the specification
establishing !onfiden!e that a -ogam does #hat it is s)--osed to do BC)
All of the above
12) Ahich of the following ae Code Co!ple)ity !easues used as basis fo testing :
McCabe !easues
Falstead !easues
Co!bination !easues
All of the above
19) (((((((((( is a fo!al evaluation techni&ue in which softwae e&uie!ents7
design7 o code ae e)a!ined to detect faults*
"5stem Testing BC)
%alidation
#eview
All of the above
1:) (((((( de!onstates satisfactoy suitability fo use in the intended opeating
envion!ent*
1nspection
%eification
Validation
#eview
1;) Advantages of Auto!ated testing tools ae:
#epeatability @ Scalability
#obustness
>cono!y
All of the above
1<) ((((((((( is a docu!ent that defines the input7 action and the coesponding
e)pected output7 to dete!ine if a cetain featue of an application is woking coectly*
Test $lan
Test Scipt
Test Case
Test .ed
'=) (((((((( dete!ines if a new softwae vesion is pefo!ing well enough to accept
it fo a !aDo testing effot*
Mutation testing
Load testing
"mo,e testing
#elease testing
'1) (((((((( is a pocess of e)ecuting a poga! with the intent of finding eos*
#eview
Testing
$ee eview
%eification
'') Ahich of the following is /6T a docu!ent defect type
$efo!ance
Cosmeti!
Lack of claity
%iolation of standads
'0) 1n a eview pocess7 who !odeates the eview sessionsC
Autho
#eviewe
.evie# Leade
#ecode
'4) Ahich of the following ae the highlights of unit testing C
involves testing of basi! b)ilding blo!,s of the s5stem
testing to veify the inte-!odule inteactions thooughly
testing is geneally done by an independent test tea!7 and not by develope
All of the above
'2) Ahy is !ultiple ounds of syste! testing eco!!endedC
Set of test cases can be e)ecuted in each ound*
A!!ommodate b)g fi*es and eliminate ma*im)m defe!ts
+o testing basic e&uie!ent7 i!plied e&uie!ents 7 pefo!ance !easues in vaious
ounds
shotage of esouces to co!plete testing in one ound
softwae config
1) A set of patches applied to syste! eleases like !ainfa!e opeating syste!s updates
is an e)a!ple of !odel*
Check-in7 Check-out
Co!position
Long Tansaction
Change set
') Aokspace is a concept using in which of the !odels
Co!position
Syste! Model
Long Tansaction
Change set
0) ((((((((((((( !odel focuses on vesioning of poduct co!ponents
Labeling
Check-in , Check-out
.anching
Meging
4) Ahich of the following is a e&uie!ent of 1S6 <==1
Contol of docu!ents
1dentification and taceability
Contol of non-confo!ing poduct
All of the above
2) Standadi3ed7 !easuable pocess fo change !anage!ent ae inheent of
SCM pocesses
SCM tools
SCM plan
/one of the above
9) Ahich of the following options ensue cost saving due to SCM:
1dentification of C1Bs)
Accuate elease contol
$ope esouce allocation
/one of the above
:) 1f you have two sets of changes to a single file and you need to eflect both the
changes7 the task to be pefo!ed is
Meging
#ollback
.anching
Labeling
;) Ahich of the following is /6T a C1 type
Design Docu!ent
>)ecutable Code
1nstallation Manual
Contact docu!ent
<) 1n the co!position !odel7 the two step pocess of co!position and selection can be
gaphically visuali3ed as (((((((((((( gaph
A/D-/6#
A/D-H6#
A/D-6#
H6#-A/D
1=) An aggegation of C1Bs) that has been fo!ally eviewed and ageed upon and taken
into contol at single point in ti!e can be defined byIIIII* and using and SCM
tool it is identified by IIIII* B+ill in the blank fo! espective co!!a sepaated
wods)
$oDect7 $inning
.aseline7 Label
.anch7 Tigge
Jeywod7 $inning
11) KSCM is the at of identifying7 ogani3ing and contolling !odifications to the
softwae being built by poga!!ing tea!* 1t !a)i!i3es poductivity by !ini!i3ing
!istakes*L 1t is SCMMs definition by:
S>1
1>>>
#oge $ess!en
Aayne .abich
1') Status Accounting povides
Status of change e&uest and defect epots
%esion status of vaious configuation ite!s BC1s)
Status of configuation ite!s in vaious poDect baselines
All of the above
10) 1n a poDect to identify the baseline atifacts which of the following techni&ues can be
adoptedC
Jeywods
Meging
Tigge
Labeling
14) Softwae Configuation !anage!ent is a CMMi Level ((((( pocess aea
'
0
4
2
12) Ahich of the following should be consideed as Configuation 1te!s fo any poDect:
$oDect plan7 #e&uie!ent specification7 Class diaga!s
Design specification7 Design tools7 Activity diaga!s
Souce Code7 Test plan7 test Scipt7 Test tools7 Test esults
All of the above
19) Manage!ent issues that need be consideed fo SCM tool evaluation ae
License Cost
Afte sales suppot
Availability of upgades
All of the above
1:) ((((((((( helps us to know how !eging woks
Meging !anual
Meging online help
Meging Se!antics
/one of the above
1;) Multiple people woking on one wok ite! is
Multi-Develop!ent
Multi-elease
Concuent develop!ent
/one of the above
1<) 1dentification of configuation ite! is an essential pat of SCM* Ahich is the
i!!ediate benefit of identifying the C1C
Managing elease of !ultiple vesions
$oducing $oduct Deltas
Analy3ing histoic info!ation
#epoting poDect status
'=) Ahich of the following needs to be taken into consideation fo SCM tool selection
6S Suppot
Develop!ent >nvion!ent
Fadwae #e&uie!ents
All of the above
'1) To ensue change contol7 %eloci-? pocedues says:
The e&uest of change should be ecoded in Change Contol #egiste
1!pact should be dete!ined and clientMs agee!ent should be eceived fo pay!ent
against change incopoation
Change should be tacked till it is $M appoves it
#isk assess!ent should be done in the end
'') Defining ights of individuals fo accessing the poDect epositoy is defined at which
of the following stage of SCM:
SCM $lanning
SCM Contol
SCM status accounting
SCM Audit
'0) (((((((epesent the syste! stuctue and povide a list of co!ponents o goups in
a hieachical stuctue*
Check-in7 Check-out
Co!position
Syste! Model
Change set
'4) CMMi level ' is descibed as
1nitial
#epeatable
6pti!i3ed
>volving
'2) So!e of the paa!etes consideed fo change evaluation ae
Co!ple)ity of Change
Cost
1!pact on e)isting syste!
All of the above
softwae config
1) (((((( ae conducted to find and eli!inate eos,defects in the ealy stages of
poduct develop!ent*
#eviews and Testing
#eviews
%alidation
All of the above
') 1n a table eview7 who ecods the defects and classifies eosC
Autho
#eade
#eview Leade
.e!ode
0) A (((((( is a docu!ent which descibes the obDective7 scope 7 appoach and focus of
a softwae testing effot
Test Stategy
Test Scipt
Test Case
Test Plan
4) 1n a softwae develop!ent envion!ent (((((((((((( is confi!ation that the output
of a paticula phase of develop!ent !eets all of the input e&uie!ents fo that phase*
.evie#s and Testing
Softwae %alidation
Softwae Testing
Softwae %eification
2) Tools co!!only used fo causal analysis ae
$aeto Analysis
#oot cause analysis
Both $%& and $'&
/one of the above
9) The diffeent types of flow,coveage based testing ae:
State!ent coveage
+ull $ath coveage
Decision coveage
All of the above
:) An info!al !eeting fo evaluation o info!ation pupose is a
2al,tho)gh
1nspection
Testing
/one of the above
;) Table eview pocess is followed !ostly fo eviewing docu!ents* Ahat is the othe
na!e of Table #eview $ocessC
$>ST Analysis
Bainstoming
+agan"s #eview $ocess
SA6T Analysis
<) ((((((((((( stage ensues that eview co!!ents have been incopoated duing
ewok
#eview
.e#o,
Causal Analysis
+ollow up
1=) (((((((( helps analy3e the e&uied effots fo validating the acceptability of a
softwae poduct*
Test Case
Test $lan
Test Scipt
All of the above
11) 1f the cost of fi)ing a defect in the e&uie!ents phase is 17 what is the elative cost
of fi)ing a defect in the Testing $hase
%/-01
1=
1= to 12
E1==
1') (((((((( co!ple)ity-based testing !easues poga! length and vocabulay7
volu!e7 difficulty7 and effot*
McCabe
Falstead
Combination
/one of the above
10) Mike +agan of 1.M published a pape in 1<:97 descibing a !ethod called
(((((((((( which fo!alised the softwae eview pocess*
$ee eview
6nline eview
$ai eview
Table evie#
14) (((((( povides a !easue of the conditions which could ensue that a banch is
e)ecuted*
Condition coveage
Condition opeand coveage
Decision coveage
Both $a& and $b&
12) Ahat is the coect definition of a Test SciptC
1t is a docu!ent that defines the input7 action and e)pected output to dete!ine if a
cetain featue of an application is woking coectly
1t is a docu!ent that descibes the se&uence of steps to e)ecute a test case*
It is a logi!al go)- of test !ases #hi!h #hen ta,en togethe test a -ati!)la
f)n!tion o )nit of the s5stem
/one of the above
19) ((((((((((((( is a way of poving that you syste! does what is intended and also
!eets all e&uie!ents*
%eification
%alidation
Veifi!ation and Validation
/one of the above
1:) N of effot eco!!ended fo eview pepaation is (((((((((
'N
%18
'2N
:2N
1;) $epaation of a (((((((( is vey i!potant7 befoe conducting 8nit testing*
Syste! Test $lan
8nit Test Case
Unit Test Plan
All of the above
1<) Ahich of the following ae the co!!only accepted levels of testing in the Softwae
Develop!ent Life Cycle C
8nit o Co!ponent testing
1ntegation testing
Syste! testing
All of the above
'=) (((((((((( efes to testing the featues, navigation, e)pected e)pectations7 when
!oe than one uses fo! diffeent !achines opeate on sa!e 6bDects*
Con!)ent testing
+unctional testing
Module testing
All of the above
'1) So!eti!es a need !ay aise fo an e)tenal eview of the softwae poduct* Ahich
of the following needs will po!pt you to go fo an >#TC
Do!ain Content
Technical Content
Cos!etic Content
All of the above
'') (((((((((( i!plies testing the syste! with the intent of confi!ing the eadiness of
the poduct and custo!e acceptance of the poduct*
Load testing
Syste! testing
Acceptance Testing
1ntegation testing
'0) The basic building block of any activity in any phase of the SDLC which fo!s the
coe of CTS"s #eviews and Testing $ocess is called the :
$ee #eview
%eification and %alidation Techni&ues
ETVX Model
All of the above
'4) ((((((( is done to validate the entie poduct*
Syste! testing
Acceptance testing
#egession testing
1ntegation testing
'2) GTest7 Gpobe7 $uify ae so!e of the (((((((((( used in poDects*
%eification tools
Testing tools
%alidation tools
All of the above
vel &
1) Ahich of this is not the intended use of MeticsC
To !onito the poDect pefo!ance
To take appopiate decisions based on !easued values
To !onito individual pefo!ance
To evise plans
') 6bDectives of custo!e focus is to:
>licit paa!etes that ae citical to &uality fo! custo!es
Collect data and !etics
Tack pefo!ance
All of the above
0) All Configuation Audit issues ae ecoded in -------------- and tacked to closue:
Softwae Configuation Audit #epot BSCA#)
Softwae Configuation 6de +o! BSC6+)
.aseline #ecod
$M#
4) The set of actions to be taken when the peceived isk beco!es a eality is
docu!ented as pat of
Contingency plan
Mitigation $lan
Defect $evention #epot
#isk Tacke
2) #isk &uantification is done based on
#isk pobability and i!pact of isk
#isk !itigation
#isk schedule
/one of the above
9) $actitiones woking on poDects can suggest pocess i!pove!ents though a
$ocess 1!pove!ent $oposal
Change #e&uest
>!ail,$hone
All of the above
:) ((((((((( seves as an i!potant veification activity to ensue the co!pleteness of
testing in ode to ensue poduct &uality*
8nit Testing
1ntegation Testing
Test Audit
Syste! testing
;) 5oup that focus on the tools used by poDects and the i!pact of using tools is
Tools goup
S?A
S>$5
All of the above
<) Coective and $eventive Action $lan should be dawn fo:
Custo!e co!plaints eceived
Custo!e feedback atings
Custo!e Satisfaction suveys
All of the above
1=) Look ahead !eetings and oot cause analysis ae e)a!ples of
Defect pevention activities
>o captue activities
Appaisal activities
/one of the above
11) The effectiveness of the ?uality Manage!ent Syste! is continuously i!poved
though
Audit esults7 coective and peventive actions7 CSATs7 Manage!ent #eview
Sales epots7 .alance sheets7 Co!pany audit epots
?uality goup ecuit!ents
1ndividual $efo!ance appaisals
1') $oDect !onitoing eviews ae conducted to
eview poDect pogess
undestand poDect e&uie!ents
!onito e&uie!ents volatality
All of the above
10) CTSMs &uality syste! is known as
Ai&Tee
%eloci-?
$oDect Data .ank
J-net
14) 1n the e)ecution of !aintenance poDects each tigge fo! the custo!e is ecoded
in a:
Change #e&uest
M#
$M#
Change contol #egiste
12) (((((((((is used to docu!ent the featues,functionality to be tested7 test stategy
and testing !ethods to be used*
Test $lan
Test +o!
Test develop!ent
Test Design
19) 6gani3ational leaning entes %eloci-? though
?ueies and $1$
Audit findings
$oDect $efo!ance Analysis
All of the above
1:) ((((((((( is a techni&ue used fo aiving and pioiti3ing e&uie!ents*
$ugh !ati)
?uality +unction Deploy!ent B?+D)
%oice 6f Custo!e B%6C)
All of the above
1;) #elease eview pocess involves
$M7 custo!e and TM
$M7 ?C7 TM
All tea! !e!bes
entie tea! along with S?AM and custo!e
1<) >ach phase ,activity of a life cycle !odel is epesented in veloci-? by the
(((((((((((( Citeia
A.S
DMAD%
>T%H
SDLC
'=) $ocess atifacts that help to pefo! poDect activities in a standad !anne ae
$olicies
$ocedues
Checklists and Te!plates
All of the above
'1) The theshold value of #isk Scoe beyond which the Mitigation and contingency
plans need to be docu!ented is
1;
1==
':
42
'') is a epositoy of data and leaning fo! closed poDects*
$oDect Data .ank
%eloci-?
Si) Sig!a
/one of the above
'0) Si) sig!a !ethodology that is used fo eduction of cycle ti!e is
Coss +unctional $ocess Map
DMA1C
DSSS
Si) steps
'4) is an initiative that involves !easuing and analy3ing business pocesses*
Si) Sig!a
#oot Cause Analysis
$ugh Mati)
/one of the above
'2) Si) Sig!a !easues defects based on:
the tea!Ms decision
CTSMs Senio !anage!entMs peception
Custo!eMs peception
nu!be of defects in the poDect
vel &
1) Configuation audits ae veification !echanis!s used to ensue that deliveables ae:
Defect fee
6n schedule
Consistent with e&uie!ents
/one of the above
') 1n CTS which !odel epesentation of CMM1 was adopted
#ank !odel
Linea !odel
Staged !odel
$ocess aea !odel
0) >ach phase ,activity of a life cycle !odel is epesented in veloci-? by the
(((((((((((( Citeia
A.S
DMAD%
>T%H
SDLC
4) $DCA stands fo
$lan7 Define7 Change7 Add
$lan7 Do7 Change7 Aid
$lan7 Do7 Check7 Act
$lan7 Define7 Check7 Add
2) 1n %eloci-?7 intentions and diections fo &uality initiative ae docu!ented in
$olicies section
$ocedue section
5uidelines section
All of the above
9) Ahat is the !onthly !echanis! to ecod and tack !etics of the poDectC
$DM#
Aok $lans
$M#
AS#
:) +o a poDect that involves esolving incidents7 Dob cycle !onitoing and softwae
upgades7 the pocess !odel to be chosen is
%-$ocess !odel
1teative $ocess !odel
$oduction Suppot pocess !odel
/one of the above
;) 1t is !andatoy to take coective and peventive actions fo
/on-confo!ances
6bsevations
Custo!e co!plaints
Ba) and Bc)
<) This is the testing pocedue accoding to which !odules7 sub !odules ae tested and
test case veification is done
+unctional testing
Module testing
8nit testing
Syste! testing
1=) ?uality is defined as
Ability of the poduct to !eet stated o i!plicit needs of custo!es
Set of pocess and pocedues
8se of checklists and te!plates
All of the above
11) 1S6 stands fo
1ntenational 6gani3ation fo Standadi3ation
1ntenational Syste!s fo 6gani3ation
1ntenational Syste!s 6ientation
1ntenational Syste!s 6gani3ation
1') (((((((( ae !istakes , faults caught duing the sa!e phase of SDLC
Defects
.ugs
>os
All of the above
10) Oou ae a $oDect >nginee who has Dust Doined CTS* Oou want to know all you
esponsibilities as defined by veloci-? fo you ole* Ahee would you goC
$D.
Teasue Fouse
5uidelines
/avigato
14) $io to stat of the poDect7 the $M should esti!ate
good idea - he can get fa!ilia with ou esti!ation guidelines
it is a !ust to plan bette on e)ecution of the poDect
veify esti!ation and addess diffeences if any
all of the above
12) The pocess !odel suited fo poDects with dissi!ila sevice e&uests is
Sevice $ocess !odel
#ational 8nified $ocess Model
%-$ocess Model
/one of the above
19) The pocess followed in the softwae develop!ent poDect should be:
Client specified pocesses
$ocesses as descibed in veloci?*
Tailoed 6DC specific pocesses
Any 6ne of the above
1:) %oice 6f Custo!e B%6C) can be used to
$ioiti3e custo!e e&uie!ents
Select e&uie!ents
Analy3e custo!e e&uie!ents
#e&uie!ents taceability
1;) 1n CMM1 the Level ' stage is descibed as
Managed
#epeatable
defined
opti!i3ed
1<) D$M6 stands fo
Defects pe !illion oppotunities
Defects pe !illion occasions
Deivations pe !illion oppotunities
Any of the above
'=) 1n the e)ecution of !aintenance poDects each tigge fo! the custo!e is ecoded
in a:
Change #e&uest
M#
$M#
Change contol #egiste
'1) Choose the odd one: 6ne of the pocess !odels /6T suitable fo Develop!ent
1teative !odel
Aatefall Develop!ent !odel
%-$ocess !odel
Convesion, $oting $ocess Model
'') The following is not a section of the poDect plan te!plate :
#esouce $lan
>)ecution $ocess $lan
$DM#
$oDect %ision
'0) Ahat does function point esti!ation !ean:
A standad !ethod to !easue si3e of softwae poDects
A Metic fo effot calculation
A eview techni&ue , !echanis!
An e)pei!ental !ethod to calculate poDect delivey ti!e
'4) 1n CMMi level softwae pocess is i!poved in a contolled !anne*
1
'
2
All of the above
'2) The &uality goup esponsible fo pocess definition7 !etics analysis and &uality
assuance activities at vetical,goup vetical level is
S>$5
S?A
Tools 5oup
/one of the above