As-is architectureHow your systems work today, as opposed to how they were designed or how you want them to work.

Target stateWhere you want the architecture to be at the end of a change programme.

Custom codeCode your organisation wrote or paid for on top of a standard platform, such as ABAP in SAP or Apex in Salesforce.

EnhancementA change that extends standard software behaviour without modifying the core product.

Integration or interfaceA connection that moves data between two systems.

Impact analysisWorking out everything a change will affect before you make it.

ReconciliationComparing what documents say with what the code actually does.

Declared gapSomething the source material doesn't cover, stated openly rather than guessed.

Grounded answerAn answer backed directly by a source you can check.

Inferred answerA conclusion reasoned from the source, but not stated in it.

Knowledge layerA shared model of your estate that other AI tools can query and cite.

Carve-outSeparating part of a business, and its systems, from the rest.

RationalisationDeciding which applications and customisations to keep, merge or retire.

Technical debtThe future cost of shortcuts and workarounds built into a system.

S/4HANASAP's current ERP platform, which many organisations are migrating to from SAP ECC.