A Case for Requirements Validation
2004
Loading...
View/Download File
Persistent link to this item
Statistics
View StatisticsJournal Title
Journal ISSN
Volume Title
Title
A Case for Requirements Validation
Authors
Published Date
2004
Publisher
Type
Report
Abstract
In software engineering we make a distinction between the validation and the verifi-
cation of a software system under development. Verification is concerned with demonstrating
that the software implements the functional and non-functional requirements.
Verification answers the question "is this implementation correct with respect to its
requirements?" Validation, on the other hand, is concerned with determining if the
functional and non-functional requirements are the right requirements. Validation answers
the question "will this system, if build correctly, be safe and effective for its
intended use?" There is ample evidence that most safety problems can be traced to
erroneous and inadequate requirements. Therefore, to improve the safety of software
intensive systems it is critical that the requirements are properly validated. Unfortunately,
current certication standards, for example, DO-178B, focus almost exclusively
on various verication activities; consequently, most industry practices are geared towards
verification activities such as extensive testing and code inspections. Thus, one
of the most critical problems with current certification standards is a lack of robust and
reliable ways of assessing whether the requirements have been adequately validated.
Keywords
Description
Associated research group: Critical Systems Research Group
Related to
Replaces
License
Series/Report Number
Funding information
Isbn identifier
Doi identifier
Previously Published Citation
Proceeding of National Academies Workshop on Software Certification and Dependability., Washington DC, April, 2004
Suggested citation
Heimdahl, Mats. (2004). A Case for Requirements Validation. Retrieved from the University Digital Conservancy, https://hdl.handle.net/11299/217329.
Content distributed via the University Digital Conservancy may be subject to additional license and use restrictions applied by the depositor. By using these files, users agree to the Terms of Use. Materials in the UDC may contain content that is disturbing and/or harmful. For more information, please see our statement on harmful content in digital repositories.