Scribd
Upload
102 views

Chapter 4: Ensuring Your Requirements Are Correct: Requirement Validation Techniques

The document discusses requirement validation techniques. It states that requirement validation is important to identify inconsistencies, incompleteness, and ambiguities in requirements. This helps ensure requirements are correct before later development stages where fixes are more expensive. Several techniques can be used including prototyping, reviews, modeling from different viewpoints, and use case testing to validate requirements are complete and correct in the requirements specification document.

Uploaded by

Endris Mamo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
102 views

Chapter 4: Ensuring Your Requirements Are Correct: Requirement Validation Techniques

The document discusses requirement validation techniques. It states that requirement validation is important to identify inconsistencies, incompleteness, and ambiguities in requirements. This helps ensure requirements are correct before later development stages where fixes are more expensive. Several techniques can be used including prototyping, reviews, modeling from different viewpoints, and use case testing to validate requirements are complete and correct in the requirements specification document.

Uploaded by

Endris Mamo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Chapter 4: Ensuring Your Requirements Are correct: Requirement

validation Techniques

Requirements engineering is a process in which various activities are performed in a structured


way to elicit, validate, and maintain user requirements.

Requirements validation makes it possible to eradicate all the conflicts among requirements in
software requirements specification. It relates to requirements analysis since it is more concerned
with detecting problems with the requirements, i.e. inconsistencies, incompleteness and
ambiguities among requirements. It highlights the ambiguous requirements - which may have
multiple perceptions, inconsistent requirements - in which the same requirement is stated
differently at different places in SRS, and incomplete requirements - which do not convey a
complete meaningful requirement.

Requirements validation is crucial because the errors identified in the later phases of the software
development would be more expensive to rectify because the cost of fixing a problem which
arises due to the problem in requirements is much more expensive than fixing a design or code
errors. Errors in requirements lead to failure of meeting customers’ need and hence leads to
failure of the project. Any change in requirements at the later phase means that you will need to
make changes in design and architecture or implementation.

The goal of using Requirement validation techniques is to guarantee that specified user
specifications have been stated completely and there is no faulty requirement in the SRS
document. Several techniques for requirements validation are practiced in industry, which
includes, requirements prototyping, requirements reviews, viewpoint-oriented requirements
validation and use-case based modeling . In this module, some of those techniques have been
discussed.

4.1. Testing Early and Often


4.2 . Use Case Scenario Testing

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy