C1

Question 1

validation

Answer 1

The process of evaluating software at the end of software development to ensure compliance with intended usage: are we building the right system?

Question 2

verification

Answer 2

The process of determining whether the products of a given phase of the software development process fulfill the requirements established during the previous phase: are we building the system right?

Question 3

why is software verification difficult?

Answer 3

• many different requirements
• evolving structure
• uneven distribution of faults

Question 4

software fault

Answer 4

A static defect in the software, the root of the
failures. Faults are design mistakes.

Question 5

software error

Answer 5

the execution of an incorrect internal state
(runtime) resulting from a fault

Question 6

software failure

Answer 6

External observable incorrect behavior with
respect to the requirements or other description of the expected behavior

Question 7

testing central issue

Answer 7

Given a fault, not all inputs will trigger the fault into a failure.

Problem: finding inputs that cause a software failure

Question 8

3 conditions for a failure to be observed

Answer 8

1. reachability: location in the program that contains the fault must be reachable
2. infection: when executed the states of the program must be incorrect
3. propagation: the infected state must propagate to cause some output of the program to be incorrect

Question 9

testing

Answer 9

the process of systematic evaluation of software by observing its execution possibly identifying some of the failures

part of verification and validation process in which testers and developers work together to reduce the software risk

Testing can only show the presence of failures, but not the correctness of a program

Question 10

test coverage criteria

Answer 10

measures of adequacy to increase the
confidence that we have tested enough

Question 11

black-box testing

Answer 11

Deriving tests from external descriptions
of the software (requirements, specification, design)

Question 12

white-box testing

Answer 12

Deriving test case from the source code
internals (conditional, statements, internal state)

Question 13

unit testing

Answer 13

A unit is a small testable software component
- Procedure, method
- Class
Assess software with respect to implementation or detailed design

units are tested in isolation

Question 14

integration testing

Answer 14

Testing of more than one (tested) unit together to determine if they function correctly.
- assess software with respect to subsystem design
- focus on interfaces and communication between units

Question 15

system testing

Answer 15

testing the system as a whole
- assess software with respect to architectural design
- verify that specifications are met

Question 16

acceptance testing

Answer 16

Validate that the system can be used for the intended purpose:
- done by real business users
- enables the customer to determine whether to accept the system or not

• assess software with respect to requirements
  also called beta testing

Question 17

regression testing

Answer 17

testing during maintenance
- assess software with respect to new and old requirements