Which of the following would you NOT likely find in a requirements document?

A requirements document is primarily focused on capturing and detailing the needs and expectations of stakeholders regarding a project or system. Its main goal is to outline what the system must do to meet these needs.

A traceability matrix is a common component found in requirements documentation. It helps to track the requirements throughout the project lifecycle, ensuring that all requirements are addressed in the final deliverables.

An organization chart may also be included in a requirements document but is less common. It can provide context regarding the stakeholders and their roles, which can help in understanding who the requirements apply to.

Assumptions are typically documented alongside requirements to clarify the context in which the requirements are valid, ensuring that all stakeholders have a shared understanding of the conditions under which the project operates.

On the other hand, detailing the effort required to deliver a system does not align with the primary function of a requirements document, which is to define what the system should do, rather than estimate the resources needed for implementation or delivery. Therefore, specifying effort is more aligned with project management documentation such as a project plan or feasibility study rather than a requirements specification.