BA practice depth
Gherkin, traceability, SIT and UAT design, negative testing, defect management, root cause analysis
BA practice depth: Gherkin acceptance criteria, traceability, SIT and UAT design, negative testing, defect management and root cause analysis.
What You Can Do After This Chapter
Learning objective. Learner explains how a payments business analyst gathers requirements in the domain language, writes a BRD and a functional specification, and writes user stories with Gherkin acceptance criteria. Learner maps processes in BPMN, maps data field by field from MT to MX, designs a test strategy with SIT, UAT and negative testing, manages defects by severity, and runs production support and root cause analysis.
Practical assessment. Learner receives a case where a bank must add SEPA Instant to its hub, then writes the requirements, a Gherkin acceptance criterion, a field-by-field MT to MX mapping, and a test strategy with negative cases. Learner also triages three defects by severity and drafts the root cause analysis for a failed instant payment.
Expected deliverables.
- BRD outline for SEPA Instant
- Gherkin acceptance criteria set
- MT to MX field mapping table
- Test strategy and defect triage note
Completion criterion. Learner writes correct requirements and Gherkin criteria, maps the fields accurately, designs a complete test strategy, and triages the defects by the right severity.
- Requirements gathering for payments: workshops, elicitation and the domain language
- Writing a BRD and a functional specification for a payment product
- User stories and acceptance criteria for payments: Gherkin in practice
- Process mapping and BPMN: drawing the payment flow so everyone agrees
- Data mapping and message mapping: field by field, MT to MX
- Test strategy for payments: SIT, UAT, negative testing and the test pack
- Defect management: severity, triage and the defect lifecycle
- Production support and root cause analysis: keeping payments running