What guideline should be followed when writing a requirements specification?

When writing a requirements specification, adhering to the guideline of only one requirement per sentence and avoiding nesting of requirements is vital. This approach enhances clarity and comprehension, making it easier for stakeholders to understand each requirement independently. By ensuring that each sentence conveys a single requirement, ambiguity is reduced, which helps prevent misinterpretations and ensures that everyone involved has a clear understanding of what is needed.

Nesting requirements can complicate the relationship between different requirements, leading to confusion about their dependencies or how they interrelate. When requirements are stated simply and directly, it allows for better tracking, visibility, and management throughout the development process. This practice supports the ultimate goal of specifications, which is to communicate clear, actionable requirements that can be effectively implemented and validated.

Other options might propose ways to format or structure the document for efficiency, but those do not emphasize the fundamental importance of clarity and separation of requirements in ensuring that the specifications serve their intended purpose effectively.