High-Order Testing Flashcards
1
Q
___ specify why the program is needed.
A
Requirements
2
Q
___ specify what the program should do and how well the program should do it.
A
Objectives
3
Q
___ define the exact representation of the program to users.
A
External specifications
4
Q
___ associated with the subsequent processes specifies, in increasing levels of detail, how the program is constructed.
A
Documentation
5
Q
The first step in the software development process.
A
End User
6
Q
This comes after “End User” in the software development process.
A
Requirements
7
Q
This comes after “Requirements” in the software development process.
A
Objectives
8
Q
This comes after “Objectives” in the software development process.
A
External Specifications
9
Q
This comes after “External Specifications” in the software development process.
A
System Design
10
Q
This comes after “System Design” in the software development process.
A
Program Structure Design
11
Q
This comes after “Program Structure Design” in the software development process.
A
Module Interface Specifications
12
Q
The final step in the software development process.
A
Code
13
Q
The purpose of a ___ test is to find discrepancies between the program’s modules and their interface specifications.
A
module
14
Q
The purpose of a ___ test is to show that a program does not match its external specifications.
A
function
15
Q
The purpose of a ___ test is to show that the product is inconsistent with its original objectives.
A
system
16
Q
A ___ test is used for Module Interface Specifications.
A
Module
17
Q
An ___ test is used for Program Structure Design.
A
Integration
18
Q
An ___ test is used for System Design.
A
Integration
19
Q
A ___ test is used for External Specifications.
A
Function
20
Q
A ___ test is used for Objectives.
A
System
21
Q
An ___ test is used for Requirements.
A
Acceptance
22
Q
Category of test case. Ensure that the functionality in the objectives is implemented.
A
Facility
23
Q
Category of test case. Subject the program to abnormally large volumes of data to process.
A
Volume
24
Q
Category of test case. Subject the program to abnormally large loads, generally concurrent processing.
A
Stress
25
Category of test case. Determine how well the end user can interact with the program.
Usability
26
Category of test case. Try to subvert the program's security measures.
Security
27
Category of test case. Determine whether the program meets response and throughput requriements.
Performance
28
Category of test case. Ensure the program correctly manages its storage needs, both system and physical.
Storage
29
Category of test case. Check that the program performs adequately on the recommended configurations.
Configuration
30
Category of test case. Determine whether new versions of the program are compatible with previous releases.
Compatibility / Conversion
31
Category of test case. Ensure the installation methods work on all supported platforms.
Installation
32
Category of test case. Determine whether the program meets reliability specifications such as uptime and MTBF.
Reliability
33
Category of test case. Determine whether the application correctly provides mechanisms to yield data on events requiring technical support.
Serviceability / Maintenance
34
Category of test case. Validate the accuracy of all user documentation.
Documentation
35
Category of test case. Determine the accuracy of special procedures required to use or maintain a program.
Procedure
36
An MTBF of no more than 20 hours presents testing possibilities. What does MTBF stand for?
Mean Time Between Failures
37
Reliability testing and the concept of SRE are with us today. What does SRE stand for?
Software Reliability Engineering
38
One design goal is to minimize the MTTR. What does MTTR stand for?
Mean Time To Recovery
39
Component of a good test plan. The objectives of each testing phase must be defined.
Objectives
40
Component of a good test plan. Criteria must be designed to specify when each testing phase will be judged to be complete.
Completion criteria
41
Component of a good test plan. Calendar time schedules are needed for each phase.
Schedules
42
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.
Responsibilities
43
Component of a good test plan. Systematic methods of identifying, writing, and storing test cases.
Test case libraries and standards
44
Component of a good test plan. The required test tools must be identified.
Tools
45
Component of a good test plan. A plan for the amount of computer time needed for each testing phase.
Computer time
46
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.
Hardware configuration
47
Component of a good test plan. A definition of how the program will be pieced together.
Integration
48
Component of a good test plan. Identify means to track various aspects of the testing progress.
Tracking procedures
49
Component of a good test plan. Define mechanisms for reporting detected errors, tracking the progress of corrections, and adding the corrections to the system.
Debugging procedures
50
Component of a good test plan. Performed after making a functional improvement or repair to the program.
Regression testing
51
Software development process stage:
1) Translate the program user's needs into a set of written requirements. These are the goals for the product
Requirements
52
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.
Objectives
53
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.
External specification
54
Software development process stage:
4) This step partitions the system into individual program, components, or subsystems, and defines their interfaces.
System design
55
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.
Program structure design
56
Software development process stage:
6) Develop a precise specification that defines the interface to, and function of, each module.
Module interface specifications
57
Software development process stage:
7) Translate, through one or more sub-steps, the module interface specification into the source code algorithm of each module.
Code
58
Specify why the program is needed.
Requirements
59
Specify what the program should do and how well the program should do it.
Objectives
60
Define the exact representation of the program to users.
External specifications
61
___ associated with the subsequent processes specifies, in increasing levels of detail, how the program in constructed.
Documentation
62
The purpose of a ___ test is to find discrepancies between the program's modules and their interface specifications.
module
63
The purpose of a ___ test is to show that a program does not match its external specifications.
function
64
The purpose of a ___ test is to show that the product is inconsistent with its original objectives.
system
65
The end user and requirements stages of the software development life-cycle use an ___ test.
acceptance
66
The objectives stage of the software development life-cycle uses a ___ test.
system
67
The external specifications stage of the software development life-cycle uses a ___ test.
function
68
The system design and program structure design stages of the software development life-cycle use an ___ test.
integration
69
The module interface specifications stage of the software development life-cycle uses a ___ test.
module
70
___ testing is a process of attempting to find discrepancies between the program and the external specification.
Function
71
An ___ is a precise description of the program's behavior from the end-user point of view.
external specification
72
___ testing has a particular purpose: to compare the system or program to its original objectives.
System
73
Category of test case. Ensure that the functionality in the objectives is implemented.
Facility
74
Category of test case. Subject the program to abnormally large volumes of data to process.
Volume
75
Category of test case. Subject the program to abnormally large loads, generally concurrent processing.
Stress
76
Category of test case. Determine how well the end user can interact with the program.
Usability
77
Category of test case. Try to subvert the program's security measures.
Security
78
Category of test case. Determine whether the program meets response and throughput requirements.
Performance
79
Category of test case. Ensure the program correctly manages its storage needs, both system and physical.
Storage
80
Category of test case. Check that the program performs adequately on the recommended configurations.
Configuration
81
Category of test case. Determine whether new versions of the program are compatible with previous releases.
Compatibility / Conversion
82
Category of test case. Ensure the installation methods work on all supported platforms.
Installation
83
Category of test case. Determine whether the program meets reliability specifications such as up-time and MTBF.
Reliability
84
Category of test case. Test whether the system's recovery facilities work as designed.
Recovery
85
Category of test case. Determine whether the application correctly provides mechanisms to yield data on events requiring technical support.
Serviceability / Maintenance
86
Category of test case. Validate the accuracy of all user documentation.
Documentation
87
Category of test case. Determine the accuracy of special procedures required to use or maintain the program.
Procedure
88
___ testing is the process of comparing the program to its initial requirements and the current needs of its end users.
Acceptance
89
Component of a good test plan. The objectives of each testing phase must be defined.
Objectives
90
Component of a good test plan. Criteria must be designed to specify when each testing phase will be judged to be complete.
Completion criteria
91
Component of a good test plan. Calendar time schedules are needed for each phase.
Schedules
92
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.
Responsiblities
93
Component of a good test plan. In a large project, systematic methods of identifying, writing, and storing test cases are necessary.
Test case libraries and standards
94
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.
Tools
95
Component of a good test plan. This is a plan for the amount of computer time needed for each testing phase.
Computer time
96
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.
Hardware configuration
97
Component of a good test plan. Part of the test plan is a definition of how the program will be pieced together.
Integration
98
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.
Tracking procedures
99
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.
Debugging procedures.
100
Component of a good test plan. Performed after making a functional improvement or repair to the program.
Regression testing
