Solution

Concept:

The production of requirements stage of the software development process is Software Requirements Specifications (SRS) (also called a requirements document).

Characteristics of Software Requirement Specification:

Correctness: The SRS document is deemed to be correct if the requirements stated in it are expected from the system itself.

Clarity: SRS documentation should be easy to understand for all members of the development process, from stakeholders to developers and other specialists.

Viability: An SRS document should be created will all the current conditions and limitations in mind. They include budget, technical capabilities, team size, and deadline.

Compleness: Your SRS should be complete with details and cover most user scenarios so that your development team can use this document as their guide and avoid any confusion during the development.

Flexibility: A rare product stays unchanged throughout the whole development process, so your documentation should be flexible enough to accept changes. Try to keep all the information well-structured, so that you can make changes quickly in one section of the document.

Consistency: The requirements in your SRS document shouldn’t contradict each other, and you should use the same terminology across the documentation. The structure of your document should be clear and predictable.

Accuracy: The document should have clear requirements and instructions so that any team member can use it without having to ask any additional questions. Avoid ambiguity, loopholes, subjective suggestions, and so on.

The Correct Answer is option 4.