Skip to content

How the analysis works

A graph of the customer cancellation path

A reviewer wants to know what adding a cancellation reason could affect. Start at the HTTP registration, follow the captured handler, and read the guard immediately before the state write.

Code graph for change impact analysis

The graph

Follow an order cancellation from its route to the state write. See which calls the source supports and where a code graph leaves a gap.

Select a node to see what the code shows and what it cannot tell you. Toggle link types to see how much of the path is confirmed.

orders-api @ a41c9e2 · exports-job @ e98f4a0 · illustrative

checksusescalls?dispatchesreads?Entry pointPOST /orders/{id}/cancelHandlerOrderController.cancelServiceOrderService.cancelRepositoryOrderRepository.updateStatusColumnorders.statusGuardorder.isShipped()Libraryjakarta.validation @ValidPossible callerSupportController.overrideMap stops hererefunds.dispatch(event)Possible readerNightlyExportJob.run
An illustrative code graph for order cancellation. Confirmed links run from the route to the handler, service, repository and status column. A support controller is a possible caller, a nightly export job is a possible reader, validation is a library call, and the refund dispatch is unknown, so the map stops there.

Walkthrough

Step by step.

  1. Read the path

    The registration identifies one entry point. The call into the order service gives the investigator something to inspect. The shipped-order guard and status write support separate claims. Each link needs an origin in the captured version.

  2. Stop at the unknown call

    If a refund operation is dispatched dynamically or belongs to an unread repository, the path ends at that boundary. A possible edge can guide investigation. It cannot establish which consumer ran.

  3. Decide what to inspect next

    Keep direct edits separate from reachable callers and unresolved consumers. Before putting reason validation in a shared service, ask for evidence of other entry points that call it.

What each edge can establish

RelationshipEvidence to openWhat remains open
Registration → handlerCustomer cancellation route in the captured sourceWhich supported clients use it
Handler → shipping guardCall site and resolved target in the exampleWhether support reaches the same guard
Service → status updateThe update statement for the customer pathWhether a payment consumer sees the change