C857 - Software Quality Assurance –
WGU Top Questions & Answers.
Verified.
3 Types of Acceptance Tests - ✔✔-Benchmark, Pilot, Parallel
(details below)
Benchmark tests - ✔✔-tests ran by users using *predefined test cases*
Pilot tests - ✔✔-tests ran by users under *normal or everyday situation*
Beta testing - ✔✔-done at customer's site
Alpha testing - ✔✔-done at developer's site
Parallel test - ✔✔-New system operates in parallel with previous version to make transition easier for
user
LOC measurement of productivity - ✔✔-Error per line of code is better. LOC is not good for all programs
because it is hard to measure. Some programs only use one line.
Cyclomatic complexity - ✔✔-a measure of the complexity of a module's decision structure.
Module Design Complexity - ✔✔-iv(G);
is the cyclomatic number for the module
Design Complexity - ✔✔-SO;
, sum of iv(G) for itself and all decedents
Integration complexity - ✔✔-S1;
SO - n + 1
Module Integration testing - ✔✔-evaluate just the module and its immediate children
Design Integration testing - ✔✔-evaluate the entire graph
White box testing - ✔✔-look into program graph at cyclomatic #, basis, IP, DU path coverage, and
program slice
Functional testing - ✔✔-do not look at program structure, only at the specifications or requirements
Unit level testing - ✔✔-White box and functional testing of each module
Integration testing - ✔✔-integrate modules, that have been tested at unit level
Unit and Functional testing - ✔✔-verification that the programmer implemented the design correctly
System testing - ✔✔-validation that the system does what the customer wants it to do
*System testing steps* - ✔✔-functional testing,
performance testing,
acceptance testing,
installation testing
*Function point* - ✔✔-used early in lifecycle at requirements analysis as a mechanism to estimate the
project with the use of a historical baseline for comparison
WGU Top Questions & Answers.
Verified.
3 Types of Acceptance Tests - ✔✔-Benchmark, Pilot, Parallel
(details below)
Benchmark tests - ✔✔-tests ran by users using *predefined test cases*
Pilot tests - ✔✔-tests ran by users under *normal or everyday situation*
Beta testing - ✔✔-done at customer's site
Alpha testing - ✔✔-done at developer's site
Parallel test - ✔✔-New system operates in parallel with previous version to make transition easier for
user
LOC measurement of productivity - ✔✔-Error per line of code is better. LOC is not good for all programs
because it is hard to measure. Some programs only use one line.
Cyclomatic complexity - ✔✔-a measure of the complexity of a module's decision structure.
Module Design Complexity - ✔✔-iv(G);
is the cyclomatic number for the module
Design Complexity - ✔✔-SO;
, sum of iv(G) for itself and all decedents
Integration complexity - ✔✔-S1;
SO - n + 1
Module Integration testing - ✔✔-evaluate just the module and its immediate children
Design Integration testing - ✔✔-evaluate the entire graph
White box testing - ✔✔-look into program graph at cyclomatic #, basis, IP, DU path coverage, and
program slice
Functional testing - ✔✔-do not look at program structure, only at the specifications or requirements
Unit level testing - ✔✔-White box and functional testing of each module
Integration testing - ✔✔-integrate modules, that have been tested at unit level
Unit and Functional testing - ✔✔-verification that the programmer implemented the design correctly
System testing - ✔✔-validation that the system does what the customer wants it to do
*System testing steps* - ✔✔-functional testing,
performance testing,
acceptance testing,
installation testing
*Function point* - ✔✔-used early in lifecycle at requirements analysis as a mechanism to estimate the
project with the use of a historical baseline for comparison
