Problem Statement
What are the key practices you should follow when writing good requirements in an SRS, and how do these practices reduce project risk?
Explanation
When writing good requirements you should: use clear and unambiguous language (avoid vague words); ensure each requirement is testable and measurable; maintain consistency with terminology and format; include traceability links; assign identifiers and priority; modularise requirements so that changes affect minimal parts; review and validate with stakeholders. /n/n These practices reduce risk by preventing misunderstandings, reducing rework, enabling better planning/estimation, and facilitating effective testing and change-control. A strong SRS is a foundation for project success.