Which practice is recommended when documenting functional requirements?

When documenting functional requirements, the most effective approach is to focus on what you want the system to do, which aligns with the correct choice. This practice ensures clarity and conciseness, making requirements easier for stakeholders to understand and for developers to implement. By clearly articulating the desired functionality, the documentation can serve as a precise guideline throughout the development process.

In contrast, documenting all requirements in multiple places could lead to confusion and inconsistencies, making it difficult to maintain a single source of truth. Prioritizing requirements after they are written can lead to challenges in managing changes or understanding critical needs early in the project, potentially causing delays and increased costs. Including unnecessary details can clutter the requirements, making it harder for both developers and stakeholders to grasp the core functionalities and can create ambiguity regarding the priorities of those details.

Focusing solely on what the system should accomplish allows for more effective communication and clarity in the development efforts.