A business analyst (BA) elicits requirements for the sales order processing of multiple product lines.

A high level of abstraction means that the requirements are expressed in general terms, without specifying details or implementation methods. This allows the requirements to be more flexible and adaptable to changing business needs and contexts. For the seasonal products, which are likely to be different every year and require major variations in some business processes, using a high level of abstraction would help to manage the requirements in the long term, as they would not need to be revised or updated frequently. On the other hand, using a low level of abstraction, which means that the requirements are expressed in specific and detailed terms, would make the requirements more rigid and prone to changes, as they would need to be aligned with the particular characteristics and constraints of each seasonal product and process variation.

References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Elicitation, p. 97-98

[BABOK Guide v3], Section 4.1: Prepare for Elicitation, p. 94-95

Certified Business Analysis Professional™ (CBAP®) Specialization, Course 2: Business Analysis: Requirements Analysis and Design Definition, Week 2: Requirements Classification and Prioritization, Video: Requirements Abstraction Levels