Software Validation

V&V — Two Goals

1 pts

volume_mute

Software validation — or more generally Verification and Validation (V&V) — is intended to show two things about a system. Which two? Select both.

That a system generates profit for the organisation

That a system conforms to its specification

That a system uses fewer lines of code than its predecessor

That a system meets the expectations of the system customer

note_alt Add notes

flag Flag

Correct Answer

Explanation

Principal Validation Technique

1 pts

volume_mute

What is the principal validation technique used in software engineering?

Program testing, where the system is executed using simulated test data

Code review by an independent team

Requirements walkthroughs with all stakeholders

Formal mathematical proof of correctness

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three-Stage Testing Process

1 pts

Please drag and drop the options to sort them

Software validation uses a three-stage testing process. The diagram below shows the three stages. Sort them into the correct order, from first to last.

System testing

Acceptance testing

Component testing

note_alt Add notes

flag Flag

Correct Answer

Explanation

Component Testing — Who and How

1 pts

Complete the sentence about component testing.

The components making up the system are tested by (1). Each component is tested (2), without other system components.

Please drag and drop the selected option in the right place or type it instead

the people developing the system

independently

note_alt Add notes

flag Flag

Correct Answer

Explanation

System Testing Focus

1 pts

volume_mute

System testing integrates components to create a complete system. Which of the following are concerns of system testing? Select all that apply.

Testing emergent system properties

Verifying that the system meets its functional and non-functional requirements

Catching syntax errors in individual functions

Detecting component interface problems

Finding errors from unanticipated interactions between components

note_alt Add notes

flag Flag

Correct Answer

Explanation

Acceptance Testing — Data Used

1 pts

volume_mute

What distinguishes acceptance testing from earlier testing stages in terms of the data used?

Acceptance testing uses the same simulated data as component testing

Acceptance testing uses randomly generated synthetic data

Acceptance testing uses data supplied by the system customer rather than simulated test data

Acceptance testing uses no data — it is purely a documentation review

note_alt Add notes

flag Flag

Correct Answer

Explanation

Alpha Testing vs Beta Testing

1 pts

Match each testing term to its correct description.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Term

Alpha testing

Beta testing

Description

Acceptance testing for custom systems — the process continues until the client and developer agree the system is an acceptable implementation of the requirements

A system is delivered to a number of potential customers who agree to use it and report problems, exposing the product to real use before general release

note_alt Add notes

flag Flag

Correct Answer

Explanation

Plan-Driven Testing — The V-Model

1 pts

volume_mute

In a plan-driven software process, an independent team of testers works from pre-formulated test plans. The diagram below illustrates how specification stages on the top row each link to a corresponding test stage on the bottom row — this is sometimes called the V-model of development.

What do the test plans in this model represent?

A list of all known defects in the system

The link between testing activities and the development activities that produced the corresponding specification

The acceptance criteria written by end-users after deployment

The project schedule for the development team

note_alt Add notes

flag Flag

Correct Answer

Explanation

Testing in Incremental Development

1 pts

volume_mute

In an incremental approach to development, how should testing be organised?

Each increment should be tested as it is developed, with tests based on the requirements for that increment

Testing is deferred until the final increment is complete and the full system is available

Only acceptance testing is used — component and system testing are skipped

An independent external team carries out all testing after each increment

note_alt Add notes

flag Flag

Correct Answer

Explanation

Testing Process — Iterative Nature

1 pts

Complete the sentence about how defects discovered during testing affect the overall testing process.

When defects are discovered, the program must be (1) and this may require other stages in the testing process to be (2).

Please drag and drop the selected option in the right place or type it instead

debugged

repeated

note_alt Add notes

flag Flag

V&V — Two Goals

Correct Answer

Explanation

Principal Validation Technique

Correct Answer

Explanation

Three-Stage Testing Process

Correct Answer

Explanation

Component Testing — Who and How

Correct Answer

Explanation

System Testing Focus

Correct Answer

Explanation

Acceptance Testing — Data Used

Correct Answer

Explanation

Alpha Testing vs Beta Testing

Term

Description

Correct Answer

Explanation

Plan-Driven Testing — The V-Model

Correct Answer

Explanation

Testing in Incremental Development

Correct Answer

Explanation

Testing Process — Iterative Nature

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: