Brainscape's Knowledge GenomeTM

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


See full index

software testing > Software Life cycle > Flashcards

Software Life cycle Flashcards

1
Q

verification

A

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.

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

validation

A

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

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

V-model

A

A framework to describe the software development lifecycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development lifecycle.

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

test level

A

A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test, integration test, system test and acceptance test.

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

Commercial Off-The-Shelf software
COTS
off-the-shelf software

A

A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.

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

incremental development model

A

A development lifecycle where a project is broken into a series of increments, each of which delivers a portion of the functionality in the overall project requirements. The requirements are prioritized and delivered in priority order in the appropriate increment. In some (but not all) versions of this lifecycle model, each subproject follows a ‘mini V-model’ with its own design, coding and testing phases.

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

iterative development model

A

A development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product.

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

component testing
module testing
program testing
unit testing

A

The testing of individual software components.

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

stub

A

A skeletal or special-purpose implementation of a software component, used to develop
or test a component that calls or is otherwise dependent on it. It replaces a called component.

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

driver

test driver

A

A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.

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

robustness testing

A

Testing to determine the robustness of the software product.

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

robustness

A

The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.

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

test driven development

test first approach

A

A way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.

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

integration testing

A

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

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

integration

A

The process of combining components or systems into larger assemblies.

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

component integration testing
integration testing in the small
link testing

A

Testing performed to expose defects in the interfaces and interaction between integrated components.

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

system integration testing

integration testing in the large

A

Testing the integration of systems and packages; testing interfaces to external organizations

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

system testing

A

The process of testing an integrated system to verify that it meets specified requirements.

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

non-functional requirement

A

A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.

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

functional requirement

A

A requirement that specifies a function that a component or system must perform.

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

test environment

test bed

A

An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.

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

user acceptance testing
acceptance testing
acceptance

A

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria
and to enable the user, customers or other authorized entity to determine whether or not to accept the system.

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

factory acceptance testing

A

Acceptance testing conducted at the site at which the product is developed and performed by employees of the supplier organization, to determine whether or not a component or system satisfies the requirements, normally including hardware as well as software.

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

operational acceptance testing

production acceptance testing

A

Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on operational aspects, e.g. recoverability, resource-behavior, installability and technical compliance. See also operational testing.

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

site acceptance testing

A

Acceptance testing by users/customers at their site, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes, normally including hardware as well as software.

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

compliance testing

A

The process of testing to determine the compliance of the component or system.

27
Q

compliance

A

The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions.

28
Q

alpha testing

A

Simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site, but outside the development organization. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing.

29
Q

beta testing

field testing

A

Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a component
or system satisfies the user/customer needs and fits within the business processes. Beta testing is often employed as a form of external acceptance testing for off-the-shelf software
in order to acquire feedback from the market.

30
Q

test type

A

A group of test activities aimed at testing a component or system focused on a
specific test objective, i.e. functional test, usability test, regression test etc. A test type may take place on one or more test levels or test phases.

31
Q

functional testing

A

Testing based on an analysis of the specification of the functionality of a component or system.

32
Q

black box testing

specification-based testing

A

Testing, either functional or non-functional, without reference to the internal structure of the component or system.

33
Q

functionality testing

A

The process of testing to determine the functionality of a software product.

34
Q

interoperability

A

The capability of the software product to interact with one or more specified components or systems

35
Q

interoperability testing

A

The process of testing to determine the interoperability of a software product.

36
Q

security testing

A

Testing to determine the security of the software product.

37
Q

security

A

Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.

38
Q

performance testing

A

The process of testing to determine the performance of a software product.

39
Q

performance

A

The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.

40
Q

load testing

A

A type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g. numbers of parallel users and/or numbers of transactions, to determine what load can be handled by the component or system.

41
Q

stress testing

A

A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced availability of resources such as access to memory or servers.

42
Q

reliability

A

The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations.

43
Q

usability

A

The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions.

44
Q

efficiency

A

(1) The capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions. (2) The capability of a process to produce the intended outcome, relative to the amount of resources used

45
Q

maintainability

A

The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment.

46
Q

portability

A

The ease with which the software product can be transferred from one hardware or software environment to another.

47
Q 
white-box testing
clear-box testing
structural testing
structure-based testing
glass-box testing
logic-coverage testing
logic-driven testing
code-based testing
A

Testing based on an analysis of the internal structure of the component or system.

48
Q

code coverage

A

An analysis method that determines which parts of the software have been
executed (covered) by the test suite and which parts have not been executed, e.g. statement
coverage, decision coverage or condition coverage.

49
Q 
white-box test design technique
white-box technique
structure-based test design technique
structure-based technique
structural test design technique
A

Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.

50
Q

test automation

A

The use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.

51
Q

maintenance testing

A

Testing the changes to an operational system or the impact of a changed environment to an operational system.

52
Q

oracle

test oracle

A

A source to determine expected results to compare with the actual result of the
software under test. An oracle may be the existing system (for a benchmark), other software, a user manual, or an individual’s specialized knowledge, but should not be the code.

53
Q

impact analysis

A

The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.

54
Q

operational testing

A

Testing conducted to evaluate a component or system in its operational environment.

55
Q

big bang testing

A

An integration testing approach in which software elements, hardware elements, or both are combined all at once into a component or an overall system, rather than in stages.

56
Q

incremental testing

A

Testing where components or systems are integrated and tested one or some at a time, until all the components or systems are integrated and tested.

57
Q

site acceptance testing

A

Acceptance testing by users/customers at their site, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes, normally including hardware as well as software.

58
Q

maintainability testing

A

The process of testing to determine the maintainability of a software product.

59
Q

metric

A

A measurement scale and the method used for measurement.

60
Q

portability testing

A

The process of testing to determine the portability of a software product.

61
Q

reliability testing

A

The process of testing to determine the reliability of a software product.

62
Q

stress testing tool

A

A tool that supports stress testing.

63
Q

test execution schedule

A

A scheme for the execution of test procedures. Note: The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.

64
Q

test procedure specification

A

A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829] See also test specification.

software testing (6 decks)

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