Software Archaeology Checklist

Use this checklist before repairing or replacing a poorly understood system.

Ten-stage checklist

  1. Preserve: old PCs, disks/images, source archives, binaries and data.
  2. Inventory: installers, DLL/OCX/BPL files, licenses/dongles and manuals.
  3. Identify: executable technologies, databases and file formats.
  4. Reproduce: a known-good workflow in an isolated copy.
  5. Observe: inputs, outputs, files, registry, network and devices.
  6. Map dependencies: runtimes, services, shares, drivers and startup order.
  7. Recover data: preserve schemas, encodings and sample outputs.
  8. Recover build: source, compilers, packages and scripts where possible.
  9. Document behavior: screenshots, states, errors and evidence confidence.
  10. Decide: preserve, repair, migrate or replace.

Minimum handover set

Include configuration and registry exports, database copies, network/device details, operator interviews, recovery steps and ownership. Store originals separately from experiments.

See software archaeology, documentation, dependency mapping and reverse engineering.

Describe your legacy system or problem

Share what still works, what failed, and what must be preserved.

EMAIL BOGLAR.NET