Artefacts
The documents you will write. Prepare a sample of each to talk through in interviews.
See the diagram: Core data model (entity relationship) →A business requirements document (BRD) says what the business needs and why; a functional requirements document (FRD) says what the system must do. A rating specification lists every table, formula, rounding rule and effective date.
ExampleRequirement MTR-OD-014: 'The system shall apply NCB to OD before NCB, rounded to the nearest rupee, and shall never apply NCB to TP.'
Swimlane diagrams show who does what across customer, intermediary, insurer and third parties, with the systems used and time limits at each step.
ExampleA cashless health claim map with lanes for patient, hospital, TPA and insurer, marking the 1-hour and 3-hour deadlines.
Gherkin writes acceptance criteria as Given, When, Then. Decision tables list every combination of conditions and its outcome, which makes missing cases easy to spot.
ExampleGiven a health proposal with all adults under 45, SI up to ₹10 lakh and no pre-existing disease, When it is submitted, Then it is issued without underwriter referral.
Data mapping shows each field from source to target with any transformation. UAT scenarios state inputs and the expected premium to the rupee. A traceability matrix links each requirement to its tests and results.
ExampleUAT case: the default car quote on 26 October 2026 must give an IDV of ₹5,95,000 and a total of ₹14,892. This site's automated tests check exactly that.