Subject: Software Engineering

Topic: Testing Stratergies and Tactics

Difficulty: High

SRS is used by various individuals in the organization. System customers need SRS to specify and verify whether requirements meet the desired needs. In addition, SRS enables the managers to plan for the system development processes. System engineers need a requirements document to understand what system is to be developed. These engineers also require this document to develop validation tests for the required system. Lastly, requirements document is needed by system maintenance engineers to use the requirement and the relationship between its parts.

Certain guidelines are followed while preparing SRS. These guidelines are listed below.

Functionality: It should be separate from implementation.

Analysis model: It should be developed according to the desired behavior of a system. This should include data and functional response of a system to various inputs given to it.

Cognitive model: It should be developed independently of design or implementation model. This model expresses a system as perceived by the users.

The content and structure of the specification: It should be flexible enough to accommodate changes.

Specification: It should be robust. That is, it should be tolerant towards incompleteness and complexity.

If software is developed using the iterative development process, the requirements document will be less detailed as compared to that of the software developed for critical systems. This is because specifications need to be very detailed and accurate in these systems.