If every requirement stated in the Software Requirement Specification (SRS) has only one interpretation, then SRS is said to be:

Correct option is C

When every requirement in a Software Requirement Specification (SRS) has only one interpretation, it is considered unambiguous. This ensures that there is no confusion or multiple meanings in the requirements, which is critical for accurate implementation and validation.
Information Booster
1. Unambiguity in SRS is essential to ensure clear communication between stakeholders, including developers, testers, and clients.
2. Requirements that are unambiguous prevent misunderstandings and reduce the chances of errors during software development.
3. An SRS achieves unambiguity by using well-defined terms, avoiding vague language, and using structured formats like templates or standardized notations.
4. Examples of ambiguous requirements include terms like "fast" or "user-friendly," which need precise definitions to avoid multiple interpretations.
5. Tools like natural language processors and formal methods can help check for and eliminate ambiguity in requirements.
Additional Knowledge
· Correctness ensures the system's requirements match the stakeholder needs but does not directly imply clarity.
· Consistency means there are no conflicting requirements in the SRS.
· Verifiability ensures that requirements can be tested and validated, but it doesn’t address clarity or interpretation.