Stop 15 · Interview PreparationRequirements & Documentation · 2/3

Documentation & Traceability Questions

Part of the Business Analyst Roadmap

In short

'How would you structure a BRD?' and 'How do you keep requirements traceable?' are classics. Interviewers can tell quickly if you've actually written these documents or only read about them.

'Walk me through how you'd structure a BRD' or 'how do you ensure requirements traceability?' — testing genuine documentation fluency from Phase 3, not just naming document types.

The purple blob carries a wooden crate of tiffin boxes, each marked with coloured dots.

Think of it like this

The dabbawala's code

Mumbai's dabbawalas move huge numbers of tiffins every day using simple marks on each box. Every tiffin is traceable from a kitchen to one desk and back. Traceability means every requirement can be followed from its source to its test, just as reliably.

Watch it happen

Answering 'how do you ensure traceability?'

Goal
Requirement
Story
Test
Change

1/5Start from business goals or objectives, each with an ID, like G1: cut booking time.

The big ideas

What you need to know

Know a BRD's sections

Purpose, scope, stakeholders, business requirements, assumptions, constraints, glossary, sign-off. Say them in a sensible order.

RTM, in one line

A requirements traceability matrix links each requirement to its goal, source, design or story, and tests.

Traceability enables impact analysis

Explain the 'why': when a rule changes, you can see exactly what else must change.

Use a real example

'In my canteen case study, FR-03 traced to G2 and TC-03' is far more convincing than theory.

See it in code

Walk through the code

text
1Req ID | Goal | Source       | Story   | Test   | Status2FR-01  | G1   | Interview #2 | CAN-12  | TC-01  | Passed3FR-02  | G1   | Policy doc   | CAN-13  | TC-02  | Failed4FR-03  | G2   | Shadowing    | CAN-15  | -      | No test!

1/3The columns that make a requirement traceable both ways.

A tiny traceability matrix. The last row shows its real value: a requirement with no test sticks out immediately.

Save yourself the pain

Common mistakes

Oops

Saying 'I just list the document types: BRD, FRD, SRS'.

Do this instead

Explain what goes in one, who reads it, and how you kept it current.

Oops

Describing traceability as just a spreadsheet you fill once.

Do this instead

Describe it as a living link you use for impact analysis and test coverage.

Your mission

Build a mini RTM

~25 min

Quick check

A business rule changes mid-project. How does a traceability matrix help?

Go deeper

  1. 1Review Phase 3 and practice explaining the BRD/FRD structure and RTM purpose clearly.
  2. 2Prepare to discuss your Phase 3 practice BRD project if you built one.
  3. 3Practice explaining why traceability matters concretely, with a specific example.

More requirements & documentation at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge