Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Quality Assurance > High-Order Testing > Flashcards

High-Order Testing Flashcards

1
Q

___ specify why the program is needed.

A

Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

___ specify what the program should do and how well the program should do it.

A

Objectives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

___ define the exact representation of the program to users.

A

External specifications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

___ associated with the subsequent processes specifies, in increasing levels of detail, how the program is constructed.

A

Documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

The first step in the software development process.

A

End User

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

This comes after “End User” in the software development process.

A

Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

This comes after “Requirements” in the software development process.

A

Objectives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

This comes after “Objectives” in the software development process.

A

External Specifications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

This comes after “External Specifications” in the software development process.

A

System Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

This comes after “System Design” in the software development process.

A

Program Structure Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

This comes after “Program Structure Design” in the software development process.

A

Module Interface Specifications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The final step in the software development process.

A

Code

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

The purpose of a ___ test is to find discrepancies between the program’s modules and their interface specifications.

A

module

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

The purpose of a ___ test is to show that a program does not match its external specifications.

A

function

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

The purpose of a ___ test is to show that the product is inconsistent with its original objectives.

A

system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

A ___ test is used for Module Interface Specifications.

A

Module

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

An ___ test is used for Program Structure Design.

A

Integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

An ___ test is used for System Design.

A

Integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

A ___ test is used for External Specifications.

A

Function

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

A ___ test is used for Objectives.

A

System

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

An ___ test is used for Requirements.

A

Acceptance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Category of test case. Ensure that the functionality in the objectives is implemented.

A

Facility

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Category of test case. Subject the program to abnormally large volumes of data to process.

A

Volume

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Category of test case. Subject the program to abnormally large loads, generally concurrent processing.

A

Stress

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Category of test case. Determine how well the end user can interact with the program.

A

Usability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Category of test case. Try to subvert the program’s security measures.

A

Security

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Category of test case. Determine whether the program meets response and throughput requriements.

A

Performance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Category of test case. Ensure the program correctly manages its storage needs, both system and physical.

A

Storage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Category of test case. Check that the program performs adequately on the recommended configurations.

A

Configuration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Category of test case. Determine whether new versions of the program are compatible with previous releases.

A

Compatibility / Conversion

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

Category of test case. Ensure the installation methods work on all supported platforms.

A

Installation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

Category of test case. Determine whether the program meets reliability specifications such as uptime and MTBF.

A

Reliability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Category of test case. Determine whether the application correctly provides mechanisms to yield data on events requiring technical support.

A

Serviceability / Maintenance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

Category of test case. Validate the accuracy of all user documentation.

A

Documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

Category of test case. Determine the accuracy of special procedures required to use or maintain a program.

A

Procedure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

An MTBF of no more than 20 hours presents testing possibilities. What does MTBF stand for?

A

Mean Time Between Failures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Reliability testing and the concept of SRE are with us today. What does SRE stand for?

A

Software Reliability Engineering

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

One design goal is to minimize the MTTR. What does MTTR stand for?

A

Mean Time To Recovery

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

Component of a good test plan. The objectives of each testing phase must be defined.

A

Objectives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

Component of a good test plan. Criteria must be designed to specify when each testing phase will be judged to be complete.

A

Completion criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

Component of a good test plan. Calendar time schedules are needed for each phase.

42
Q

Component of a good test plan. For each phase, the people who design, write, execute, and verify test cases, and the people who will repair discovered errors, should be identified.

A

Responsibilities

43
Q

Component of a good test plan. Systematic methods of identifying, writing, and storing test cases.

A

Test case libraries and standards

44
Q

Component of a good test plan. The required test tools must be identified.

45
Q

Component of a good test plan. A plan for the amount of computer time needed for each testing phase.

A

Computer time

46
Q

Component of a good test plan. If special hardware configurations or devices are needed, a plan is required that describes the requirements, how they will be met, and when they will be needed.

A

Hardware configuration

47
Q

Component of a good test plan. A definition of how the program will be pieced together.

A

Integration

48
Q

Component of a good test plan. Identify means to track various aspects of the testing progress.

A

Tracking procedures

49
Q

Component of a good test plan. Define mechanisms for reporting detected errors, tracking the progress of corrections, and adding the corrections to the system.

A

Debugging procedures

50
Q

Component of a good test plan. Performed after making a functional improvement or repair to the program.

A

Regression testing

51
Q

Software development process stage:

1) Translate the program user’s needs into a set of written requirements. These are the goals for the product

A

Requirements

52
Q

Software development process stage:

2) Translate the requirements into specific objectives by assessing feasibility, time, and cost, resolving conflicting requirements, and establishing priorities and trade-offs.

A

Objectives

53
Q

Software development process stage:

3) Translate the objectives into a precise product specification, viewing the product as a black box and considering only its interfaces and interactions with the end user.

A

External specification

54
Q

Software development process stage:

4) This step partitions the system into individual program, components, or subsystems, and defines their interfaces.

A

System design

55
Q

Software development process stage:

5) Design the structure of the program or programs by specifying the function of each module, the hierarchical structure of the modules, and the interfaces between modules.

A

Program structure design

56
Q

Software development process stage:

6) Develop a precise specification that defines the interface to, and function of, each module.

A

Module interface specifications

57
Q

Software development process stage:

7) Translate, through one or more sub-steps, the module interface specification into the source code algorithm of each module.

58
Q

Specify why the program is needed.

A

Requirements

59
Q

Specify what the program should do and how well the program should do it.

A

Objectives

60
Q

Define the exact representation of the program to users.

A

External specifications

61
Q

___ associated with the subsequent processes specifies, in increasing levels of detail, how the program in constructed.

A

Documentation

62
Q

The purpose of a ___ test is to find discrepancies between the program’s modules and their interface specifications.

63
Q

The purpose of a ___ test is to show that a program does not match its external specifications.

64
Q

The purpose of a ___ test is to show that the product is inconsistent with its original objectives.

65
Q

The end user and requirements stages of the software development life-cycle use an ___ test.

A

acceptance

66
Q

The objectives stage of the software development life-cycle uses a ___ test.

67
Q

The external specifications stage of the software development life-cycle uses a ___ test.

68
Q

The system design and program structure design stages of the software development life-cycle use an ___ test.

A

integration

69
Q

The module interface specifications stage of the software development life-cycle uses a ___ test.

70
Q

___ testing is a process of attempting to find discrepancies between the program and the external specification.

71
Q

An ___ is a precise description of the program’s behavior from the end-user point of view.

A

external specification

72
Q

___ testing has a particular purpose: to compare the system or program to its original objectives.

73
Q

Category of test case. Ensure that the functionality in the objectives is implemented.

74
Q

Category of test case. Subject the program to abnormally large volumes of data to process.

75
Q

Category of test case. Subject the program to abnormally large loads, generally concurrent processing.

76
Q

Category of test case. Determine how well the end user can interact with the program.

77
Q

Category of test case. Try to subvert the program’s security measures.

78
Q

Category of test case. Determine whether the program meets response and throughput requirements.

A

Performance

79
Q

Category of test case. Ensure the program correctly manages its storage needs, both system and physical.

80
Q

Category of test case. Check that the program performs adequately on the recommended configurations.

A

Configuration

81
Q

Category of test case. Determine whether new versions of the program are compatible with previous releases.

A

Compatibility / Conversion

82
Q

Category of test case. Ensure the installation methods work on all supported platforms.

A

Installation

83
Q

Category of test case. Determine whether the program meets reliability specifications such as up-time and MTBF.

A

Reliability

84
Q

Category of test case. Test whether the system’s recovery facilities work as designed.

85
Q

Category of test case. Determine whether the application correctly provides mechanisms to yield data on events requiring technical support.

A

Serviceability / Maintenance

86
Q

Category of test case. Validate the accuracy of all user documentation.

A

Documentation

87
Q

Category of test case. Determine the accuracy of special procedures required to use or maintain the program.

88
Q

___ testing is the process of comparing the program to its initial requirements and the current needs of its end users.

A

Acceptance

89
Q

Component of a good test plan. The objectives of each testing phase must be defined.

A

Objectives

90
Q

Component of a good test plan. Criteria must be designed to specify when each testing phase will be judged to be complete.

A

Completion criteria

91
Q

Component of a good test plan. Calendar time schedules are needed for each phase.

92
Q

Component of a good test plan. For each phase, the people who will design, write, execute, and verify test cases, and the people who will repair discovered errors should be identified.

A

Responsiblities

93
Q

Component of a good test plan. In a large project, systematic methods of identifying, writing, and storing test cases are necessary.

A

Test case libraries and standards

94
Q

Component of a good test plan. The required test tools must be identified, including a plan for who will develop or acquire them, how they will be used, and when they will be needed.

95
Q

Component of a good test plan. This is a plan for the amount of computer time needed for each testing phase.

A

Computer time

96
Q

Component of a good test plan. If special hardware configurations or devices are needed, a plan is required that describes the requirements, how they will be met, and when they will be needed.

A

Hardware configuration

97
Q

Component of a good test plan. Part of the test plan is a definition of how the program will be pieced together.

A

Integration

98
Q

Component of a good test plan. You must identify means to track various aspects of the testing progress, including the location of error-prone modules and estimation of progress with respect to the schedule, resources, and completion criteria.

A

Tracking procedures

99
Q

Component of a good test plan. You must define mechanisms for reporting detected errors, tracking the progress of corrections, and adding the corrections to the system.

A

Debugging procedures.

100
Q

Component of a good test plan. Performed after making a functional improvement or repair to the program.

A

Regression testing

Software Quality Assurance (10 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions