Before beginning requirements elicitation, the business analyst should document how the relevant systems interact. This is an important activity that helps to understand the current state of the systems, their interfaces, dependencies, and data flows. It also helps to identify the gaps, issues, and opportunities for improvement in the systems. Documenting how the systems interact can be done using various techniques, such as system context diagrams, data flow diagrams, or interface analysis12.
Preparing the requirements traceability matrix, defining how the solution will be evaluated, and drafting a high-level data model are not activities that should be initiated before beginning requirements elicitation. These activities are part of the analysis, validation, and management of the requirements, and they should be done after the requirements have been elicited12.
References: 1 PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline, page 10-
11; 2 Business Analysis for Practitioners: A Practice Guide, page 131-132