FINAL DRAFT 8 SYSTEM REQUIREMENTS SOFTWARE
The review team consists of software engineers, users, and other stakeholders who examine the specification to ensure that the problems associated with consistency, omissions, and errors are detected and corrected. To avoid the problems stated above, a requirements review is conducted, which consists of a review team that performs a systematic analysis of the requirements. Lack of conformance to quality standards.Errors in the requirements elicitation and analysis.Conflicting requirements are not detected during requirements analysis.The problems encountered during requirements validation are listed below. Requirements validation determines whether the requirements are substantial to design the system. Other Requirements Validation Techniques.Requirements validation and requirements analysis can be summarized as follows: Requirements validation studies the ‘final draft’ of the requirements document while requirements analysis studies the ‘raw requirements’ from the system stakeholders (users). Requirements validation is similar to requirements analysis as both processes review the gathered requirements. To check the requirements document for completeness, accuracy, consistency, requirement conflict‘, conformance to standards and technical errors.To ensure that the actual requirements of the system are reflected in the SRS.To certify that the SRS contains an acceptable description of the system to be implemented.Other objectives of the requirements document are listed below.
The basic objective is to ensure that the SRS reflects the actual requirements accurately and clearly. In the validation phase, the work products produced as a consequence of requirements engineering are examined for consistency, omissions, and ambiguity. To check all the issues related to requirements, requirements validation is performed. Hence, it is desirable to detect errors in the requirements before the design and development of the software begins. Also, errors present in the SRS will adversely affect the cost if they are detected later in the development process or when the software is delivered to the user. For this, it is necessary to ensure that the requirements specification contains no errors and that it specifies the user’s requirements correctly. One of the objectives of this document is to check whether the delivered software system is acceptable. The development of software begins once the requirements document is ‘ready’.