Business Analysis & Functional Analysis Skill

Requirements elicitation uses targeted questions to capture AS-IS processes, pain points, and goals, progressively turning vague topics into structured documentation and a functional model for accurate specs.

Start requirements elicitation by initiating an interactive discovery session for a chosen topic, which asks targeted questions to capture domain understanding and progressively build a structured analysis document.

Yes, business analysis builds a progressive functional model and structured documentation during interactive discovery, satisfying the necessary steps to later generate a formal functional spec including DOs and constraints.

Gap analysis captures AS-IS process states and user goals to identify pain points, guiding conversational discovery that documents current domain understanding before proposing solutions.

Interactive discovery requires active conversational participation to capture accurate AS-IS states and goals; without clear inputs for constraints and DOs, the generated functional spec may lack accuracy.