Requirement_engg4_MscIt2
Good evening students!!
The requirement engineering tasks we have already discussed are
-
Inception
-
Elicitation
-
Elaboration
-
Negotiation
-
Specification
-
Validation
-
Requirement Management
We will be discussing the next three topics here
5.Specification :
The term specification means different things to different people in context to software engineering. A specification can be a written document, a set of graphical models a formal mathematical model, a collection of usage scenarios, a prototype, or any combination of these. Some template should also be developed and used for specification of requirements. The specification is the final work product produced by the requirements engineer. It serves as the foundation of subsequent software engineering activities. It describes the function and performance of a computer based system and the constraints that will govern its development.
6.Validation:
The work products produced as a consequence of requirement engineering are assessed for quality during this validation step. Requirement validation examines the specification to ensure that all software requirements have been stated unambiguously that inconsistencies, omissions and errors have been detected and corrected and that the work products confirm to the standards established for the process, the project and the product.
The primary requirement validation mechanism is the formal technical review. The review team that validates requirements includes software engineers, customers, users and other stake holders who examine the specification looking for errors in content or interpretation areas where clarification may be required, missing information inconsistencies, conflicting requirements or unrealistic requirements.
7.Requirement Management :
The requirements for the computer based system change and that the desire to change requirements persists throughout the life of the system. Requirement management is a set of activities that help the project team identify, control and track requirements and changes to requirements at any time as the project proceeds. Many of the requirement management activities are similar to software configuration management techniques. Steps are:
-
Requirement management begins with identification. Each requirement is assigned a unique identifier.
-
Once the requirement is identified, traceability tables are developed. Each traceability table relates the requirements to one or more aspects of the system or its environment