Verification, Validation, and Inspections

This quiz covers verification and validation definitions, confidence levels, inspections vs testing, and advantages of inspections

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 194

Questions #: 11

Time: 9 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Software Verification Definition

1 pts

volume_mute

Which of the following best defines software verification?

Checking that the software meets its stated functional and non-functional requirements

Reviewing the project schedule and budget against original estimates

Ensuring the software meets the customer's expectations beyond its written specification

Executing the software with real user data to find runtime errors

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Software Validation Goes Beyond Verification

1 pts

volume_mute

How does software validation differ from verification?

Validation is performed only by the development team; verification is done by the customer

Validation is a subset of verification and focuses only on functional requirements

Validation ensures the software meets customer expectations, going beyond conformance to specification

Validation checks conformance to specification; verification ensures customer expectations are met

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Inspections and Testing in the Software Process

1 pts

volume_mute

The diagram below shows where inspections and testing support V&V across different stages of the software process.

Based on this model, which artifacts can be subject to software inspections?

Only artifacts produced after coding begins

Only UML design models and database schemas

Requirements specifications, design models, database schemas, and program source code

Only the final program source code

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Nature of Inspections as a V&V Technique

1 pts

volume_mute

Software inspections are described as 'static' V&V techniques. What does this mean?

They do not require executing the software to verify it

They produce unchanging reports that cannot be updated

They are performed at a fixed point in time, once per project

They only examine the static structure of data, not program logic

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Advantages of Inspections Over Testing

1 pts

volume_mute

Software inspections have three stated advantages over testing. Which of the following are among those advantages? Select all that apply.

Inspections can consider broader quality attributes such as portability and maintainability

Inspections eliminate the need for a test plan

Inspections are always faster than testing for large systems

Inspections can detect inefficiencies, inappropriate algorithms, and poor programming style

Incomplete versions of a system can be inspected without additional cost

Errors cannot mask other errors during inspection because the system is not executed

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Error Masking in Testing

1 pts

volume_mute

A testing team discovers unexpected output in the middle of a long test run. They are unsure whether later anomalies are caused by a new error or are side effects of the first error found. Which inspection advantage does this scenario illustrate?

Inspections check broader quality attributes

Inspections can review incomplete systems

Inspections are cheaper per defect found than testing

During testing, errors can mask other errors, but inspection avoids this problem

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Effectiveness of Program Inspections

1 pts

volume_mute

Research and industry studies have reported on the defect-detection effectiveness of program inspections. Which of the following findings are supported by research cited in the literature? Select all that apply.

Inspections guarantee 100% defect detection when conducted formally

Inspections can replace software testing entirely in all project types

Fagan reported that more than 60% of errors can be detected using informal program inspections

The Cleanroom process claims more than 90% of defects can be discovered through inspections

Inspections have been shown to be more effective for defect discovery than program testing

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Limitations of Inspections

1 pts

volume_mute

Despite their effectiveness, inspections cannot replace software testing. Which types of defects are inspections NOT well suited to discover? Select all that apply.

Spelling errors and typos in variable names

Problems with system performance

Timing problems in concurrent or real-time systems

Violations of coding standards

Defects arising from unexpected interactions between different parts of a program

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Practical Challenges with Inspections

1 pts

volume_mute

In small companies or small development groups, what is a practical challenge that makes formal inspections difficult to conduct?

It is difficult and expensive to form a separate inspection team when all potential members are also developers

Regulatory frameworks prohibit small teams from conducting inspections without certification

Small teams lack access to version control tools needed for inspections

Small teams produce too little code to justify the overhead of formal inspections

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Classify V&V Activities

1 pts

volume_mute

Activities

×Reviewing UML design models for correctness

×Running a program with boundary value inputs

×Checking source code for compliance with coding standards

×Executing automated regression tests after a code change

Inspection (Static)

Testing (Dynamic)

Classify each of the following activities as either a static V&V technique (Inspection) or a dynamic V&V technique (Testing).

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

When V&V Checking Processes Begin

1 pts

volume_mute

At what point in the software development process do verification and validation checking processes begin?

Only after all code has been written and compiled

As soon as requirements become available, continuing through all stages of development

During the testing phase, which comes after design and implementation

Only when the system is ready for release to customers

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Software Verification Definition

Correct Answer

Explanation

Software Validation Goes Beyond Verification

Correct Answer

Explanation

Inspections and Testing in the Software Process

Correct Answer

Explanation

Nature of Inspections as a V&V Technique

Correct Answer

Explanation

Advantages of Inspections Over Testing

Correct Answer

Explanation

Error Masking in Testing

Correct Answer

Explanation

Effectiveness of Program Inspections

Correct Answer

Explanation

Limitations of Inspections

Correct Answer

Explanation

Practical Challenges with Inspections

Correct Answer

Explanation

Classify V&V Activities

Correct Answer

Explanation

When V&V Checking Processes Begin

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: