Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

Requirements Analysis - Typical Process Description

[document] Submitted on 2 December, 2009 - 01:27
Keywords requirements requirements analysis requirements definition requirements engineering requirements process
Metadata
Date published
2001
Language of Attachment(s)
English
Document type
technical white paper
Pages
4
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
ReqtsAnalProcessDescript.pdf application/pdf   17.83 KB English DOWNLOAD!
File attachments
Extract(s)

1 . Objective of Requirements Analysis
At the detailed level of specifications of requirements (of all forms, including statements
of work and DIDs), the criterion for a satisfactory specification for contracting purposes
is that, with an acceptable level of risk, any item which can be supplied within the
bounds defined by the specification will satisfy the need. A method of determining the
adequacy of a specification against this criterion that is structured, efficient and effective
is described below. The method involves the capture of requirements which are missing
and the identification of defects in requirements which are already captured and
recorded. Recording (specification) follows the discovery of a missing requirement,
whilst correction follows the discovery of a material defect (i.e, one which warrants
correction) in a requirement.

Organisation(s)
Defines standard
Visit also