Fred's organization is using a plan-driven approach for the business analysis deliverables. In this approach how will the requirements be captured?

Allowing the business analysis team to choose documentation at their discretion reflects an adaptive or informal approach, not a plan-driven one.

The project management information system is a tool for tracking project data such as schedules and resources, not a mechanism for capturing business analysis requirements.

Choosing whatever forms are most appropriate is an ad-hoc practice inconsistent with the structured, pre-defined nature of a plan-driven approach.

A plan-driven (predictive) approach emphasizes upfront planning, governance, and repeatability, which means requirements are captured using standardized templates defined before work begins. Standardized templates ensure that all necessary information is consistently collected across the project and that documentation meets organizational and audit standards. This contrasts with adaptive approaches where documentation formats are chosen flexibly as the project evolves.