Requirements Validation

Purpose of Requirements Validation

1 pts

volume_mute

Requirements validation is the process of:

Estimating the cost and schedule for implementing the specified requirements

Writing down the user and system requirements in a formal specification document

Checking that requirements actually define the system that the customer really wants

Testing the implemented software system to verify it meets performance benchmarks

note_alt Add notes

flag Flag

Correct Answer

Explanation

Cost of Requirements Errors

1 pts

volume_mute

True or False: The cost of fixing a requirements problem by making a system change is usually much greater than repairing a design or coding error.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

Why Requirements Changes Are So Expensive

1 pts

volume_mute

Why does a change to requirements usually cost more than a change at the design or code level?

Because requirements are written in natural language which is harder to edit than code

Because requirements engineers charge higher hourly rates than developers

Because a change to requirements usually means the system design and implementation must also be changed, and the system must then be re-tested

Because requirements documents are longer than design documents

note_alt Add notes

flag Flag

Correct Answer

Explanation

Five Types of Validation Checks

3 pts

Match each type of validation check 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

Check Type

Validity Checks

Consistency Checks

Completeness Checks

Realism Checks

Verifiability

Description

Requirements should always be written so that a set of tests can demonstrate the delivered system meets each requirement

The requirements document should include requirements defining all functions and constraints intended by the system user

Using knowledge of existing technology, requirements should be checked to ensure they can actually be implemented within budget and schedule

Analysis may identify additional or different functions required beyond what stakeholders initially thought they needed

Requirements in the document should not conflict — no contradictory constraints or different descriptions of the same system function

note_alt Add notes

flag Flag

Correct Answer

Explanation

Verifiability Check

1 pts

volume_mute

True or False: If a test for a particular requirement is difficult or impossible to design during validation, this usually means the requirement will be difficult to implement and should be reconsidered.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three Requirements Validation Techniques

2 pts

volume_mute

Which of the following are the three main requirements validation techniques? Select all that apply.

Performance Profiling

Prototyping

Requirements Reviews

Static Code Analysis

Regression Testing

Test-Case Generation

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Reviews

1 pts

volume_mute

In a requirements review, a group of people from the system customer and the system developer read the requirements document in detail and check for:

The cost of implementing each requirement

Spelling and grammar mistakes only

The aesthetic quality of the document layout

Errors, anomalies, and inconsistencies in the requirements

note_alt Add notes

flag Flag

Correct Answer

Explanation

Prototyping as Validation

1 pts

volume_mute

When prototyping is used as a requirements validation technique, an executable model of the system is demonstrated to end-users and customers so they can:

Replace the need for a requirements document entirely

Produce the final test documentation for the system

Write source code for the final system directly from the prototype

Experiment with the model to see if it meets their real needs and identify missing or incorrect requirements

note_alt Add notes

flag Flag

Correct Answer

Explanation

Test-Case Generation and Extreme Programming

1 pts

volume_mute

True or False: Developing tests from user requirements before any code is written is an integral part of Extreme Programming.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

Why Complete Validation Is Difficult

2 pts

volume_mute

Why is it difficult to fully validate that a set of requirements meets a user's actual needs? Select all that apply.

Users need to picture the system in operation and imagine how it would fit into their work — this is hard even for skilled professionals

It is rare to find all requirements problems during validation — further changes are inevitable after the document is agreed upon

Requirements validation tools are always too expensive

Only external consultants are qualified to perform requirements validation

The requirements engineering team is always too small to conduct a thorough review

note_alt Add notes

flag Flag

Purpose of Requirements Validation

Correct Answer

Explanation

Cost of Requirements Errors

Correct Answer

Explanation

Why Requirements Changes Are So Expensive

Correct Answer

Explanation

Five Types of Validation Checks

Check Type

Description

Correct Answer

Explanation

Verifiability Check

Correct Answer

Explanation

Three Requirements Validation Techniques

Correct Answer

Explanation

Requirements Reviews

Correct Answer

Explanation

Prototyping as Validation

Correct Answer

Explanation

Test-Case Generation and Extreme Programming

Correct Answer

Explanation

Why Complete Validation Is Difficult

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: