A. None of the mentioned

B. Software availability

D. Software reliability

A. Grey box testing

B. Alpha Testing

D. White box testing

A. Define

B. Measure

D. Analyse

A. individual testing group

C. instantaneous test group

D. integration testing group

B. none of the mentioned

C. use-based testing

D. cluster testing

A. Output Comparator

C. Test Harness System

D. Test File Generator

A. Identification

B. Software

D. Status Accounting

A. Comparison of different data types

B. Incorrect logical operators or precedence

C. All of the mentioned

A. design model

B. analysis model

C. code levels

A. Access control

B. Version Control and Access control

C. CM Process

A. Test case

B. Software Version

C. Output

A. List of other items affected by the changes

B. A description of the proposed changes

C. Reasons for making the changes

A. The Six Sigma refers to six standard deviations

B. A Formal Technical Review(FTR) guideline for quality walkthrough or inspection

C. It is the most widely used strategy for statistical quality assurance

A. Business modeling

B. Configuration and management

D. Analysis and design

A. Multiple locations

C. Multiple user groups

D. Multiple teams

B. White-box testing

C. All of the mentioned

D. Yellow-box testing

A. All of the mentioned

B. Developers

D. Testers

A. Error noted does not correspond to error encountered

B. Error condition causes system intervention prior to error handling

C. Error description provide enough information to assist in the location of the cause of the error

A. Integration testing

B. Completion of Testing

D. Regression Testing

A. Users end

B. Developers & Users end

D. None of the mentioned

A. Black box testing

C. None of the mentioned

D. Unit testing

A. Retesting

C. Confirmation testing

D. Sanity testing

A. Yellow box

B. Black box

D. Gray box

A. Status Accounting

B. Software

C. Configuration

A. None of the mentioned

B. Software Concept Management

C. Software Control Management

A. All of the mentioned

B. Software

D. Configuration

A. Performance analysis

B. Verification

D. Validation

A. servers

C. access control

D. hard drive

B. External Failure

C. Prevention

D. Appraisal

A. Conventional testing

B. OO system validation testing

C. Test case design

A. Step Out

C. Step Over

D. Step Into

A. Decision Testing

B. Condition Coverage

D. Statement Testing

A. Controlled changes

B. All of the mentioned

D. Lack of reusability

B. By inspections

C. By reviews

D. All of the mentioned

A. None of the mentioned

B. Software Process Improvement and Control Determination

C. Software Process Improvement and Compatibility Determination

A. A stage of all projects

B. Finding broken code

C. None of the mentioned

B. KLOC

C. None of the mentioned

D. Function Points

A. defects

B. errors

D. failures

A. None of the mentioned

B. Attribute-based partitioning

D. State-based partitioning

B. Status Accounting

C. Identification

D. Auditing and Reviewing

A. Alpha Testing

B. Beta Testing

C. Validation Testing

A. Develop a testing plan that emphasizes rapid cycle testing.

C. State testing objectives explicitly

D. Use effective formal technical reviews as a filter prior to testing

A. CM Planning

C. Executing the CM process

D. CM audits

B. Validation tests

C. Integration tests

D. System tests

A. Code path analysis

B. None of the mentioned

C. Basic path testing

B. Quality of design

C. None of the mentioned

D. Quality of testing

A. stop execution at a particular point

B. examine memory & registers

C. search for references for particular variables, constant and registers

B. Testing is conducted by the developer of the software or an independent test group

C. None of the mentioned

D. Testing and debugging are different activities, but debugging must be accommodated in any testing strategy

A. none of the mentioned

B. thread-based testing

C. use-based testing

A. Cumulative Changes in Baseline

B. None of the mentioned

D. Change Control Baseline