Skip to content

How the analysis works

Recover the user goal behind a cluster of paths

A new maintainer inherits an order service with no current functional specification. The first useful unit is a goal the product supports. A route, a table or a shared utility can provide evidence without being a use case on its own.

Recover existing requirements from code

Where requirements sit

Turn captured entry points and call paths into an evidence-linked baseline of use cases, stories, rules and open questions.

Recovered use cases are the top layer of the twin. Select the layers below them to see the evidence a baseline is built from.

Code structureSymbolsCall chainsData modelsBehaviourBusiness modelRequirements

Requirements

Use cases and stories recovered from existing code, plus new ones a team asks for. Each points at the behaviour that implements it, or says nothing does yet.

use case  Customer cancels an order
story     Require a cancellation reason
criterion Shipped orders stay ineligible
code      none yet
Requested, not yet builtRecover requirements from code

Walkthrough

Step by step.

  1. Group paths with a reason

    Group available entry paths using the route boundary, resource, topic or command. Use the captured actors, effects and branches to propose a use case and its stories. Require a separate citation for a guard or outcome that the registration itself cannot prove.

  2. Compare two snapshots

    A later scan no longer shows the returns endpoint. Compare the captured scope before assuming a removal. If the pertinent repository was unreadable or a route became unresolved, label it Not seen in latest code and retain the prior evidence.

  3. Keep delivery work separate

    A maintainer can correct a baseline interpretation and preserve the underlying extracted facts. A new requirement still goes through its own version and review. The baseline explains existing behaviour so the team can decide what to preserve.

What to say after a fresh scan

What changedWhat to showNext decision
A handler was renamed with witnessed continuitySame workflow, new source locationUpdate the citation and keep the history
The relevant repository was unreadableNot seen in latest codeRecover coverage before deciding whether it was removed
Comparable inputs show the registration was removedRemoval with evidenceCheck callers and dependent delivery work