Legacy dependencies

Find what still depends on the system you plan to retire.

A bounded assessment of the financial rules, interfaces, reports, reconciliations and manual work that need a home in the transition.

When to engage

An application inventory does not explain all its obligations.

A retiring component may support allocations, file-based interfaces, reference enrichment or operational reports that are absent from the target design.

For CIOs, enterprise architects, programme sponsors and delivery partners preparing a retirement, replacement or coexistence decision.

What you receive

An actionable dependency and transition register.

Capability and dependency mapConnect business services and finance obligations to applications, jobs, interfaces, reports and manual interventions.

Evidence and ownership registerRecord each dependency, its source, evidence status, accountable owner and missing information.

Transition dispositionIdentify what must move, remain, be rebuilt or be examined further, with the implications for the target state.

Validation plan and decision conditionsDefine the evidence needed to confirm continuity, assign actions and review unresolved material dependencies.

Client participation

Start with a component and a retirement decision.

Provide the proposed scope, available interfaces and scheduler information, relevant process documentation and access to business, finance and technology owners.

The assessment does not infer that code is unused because a dependency has not yet been observed. Unattributed behaviour is recorded for investigation.

Inspect a synthetic dependency finding

Your next decision

Discuss a retirement or transition dependency.

Start with the decision you need to make. Scope, evidence requirements, responsibilities and fees are agreed after an introductory conversation.

Discuss your problem View sample outputs