Skip to content
Pawel Works

10 · Handover

Reverse engineering and method package

Someone left. The file stayed. Map the model, recover the requirements, write the ADR, put tests on the grain, train the next person.

Service · Recover the logic. Write it down.

When this is the job

The only person who knew the measure is gone. Grain is implied. Queries are named after Tuesdays. There is no ADR. The next analyst is reverse-engineering in production, on live numbers, without a net.

How it runs

Treat the file as a source system. Map model, queries, measures, grain. Recover requirements from behaviour, not from memory. Write the architecture decision record. Put tests on the cuts that must not drift. Train the person who inherits it. The method package is the product: requirements, reverse engineering, ADR, build report, data-quality report.

  1. L1

    Map

    Model, query, measure, grain. As it actually is.

  2. L2

    Recover

    Requirements from behaviour. Not from memory.

  3. L3

    Decide

    ADR. Why this cut, not the other.

  4. L4

    Pack

    Tests, reports, training. The file can be inherited.

What you leave with

Logic that no longer lives in one head. Documents that survive a challenge. A next person who can open the file without a guided tour.