A business analyst (BA) has been writing requirements for a project that has several stakeholders...

 The level of decomposition needed for the requirements depends on the complexity of the system, the level of detail required by the stakeholders, and the level of architecture decomposition that is necessary to specify the system being developed. The BA must take into account the stakeholder perspectives when decomposing the requirements, as different stakeholders may have different needs and expectations for the granularity and clarity of the requirements. The BA must also ensure that the decomposed requirements are consistent, feasible, verifiable, and traceable to the higher-level requirements. References:

BABOK Guide v3, Section 5.2.3: Decompose Requirements - Guidelines and Tools1

Step 4: Analyze, Refine & Decompose Requirements - AcqNotes2

MDRE: Developer Derived/Decomposed Requirements | SpringerLink3

Requirements Decomposition - ArgonDigital | Making Technology a …4

Requirements decomposition - No Magic Product Documentation