Where should we document conflicts?

Documenting conflicts is best done in a requirements issue log. This log serves as a dedicated repository for tracking any disputes, disagreements, or inconsistencies that arise during the requirements gathering and analysis process. By logging conflicts in this manner, stakeholders can ensure that these issues are visible, prioritized, and addressed systematically. The requirements issue log helps maintain clarity and organization, facilitating communication between team members and ensuring that resolution efforts are documented for future reference.

On the other hand, while the system requirements specification may contain the broader requirements of the project, it is not specifically designed to track conflicts. Entity relationship diagrams focus on the data structure and associations within a system, and use cases outline how users will interact with the system – neither of which are suitable for managing or documenting disputes related to requirements. Hence, the issue log is the most appropriate tool for this purpose.