AWS has updated Transform for mainframe so it can identify business functions more precisely and trace requirements back to the code and rules behind them. For teams modernising COBOL and PL/I systems, that means a clearer view of what an application does and what the proposed requirements cover before work moves into implementation.
AWS AI Watch analysis
What happened
AWS says business functions will now be grouped only when they affect the same data fields. The workflow also includes screens and queues, with clearer names and descriptions. Previously, functions using the same table or file could be grouped together, while customers had to build their own traceability reports from Transform artefacts.
A new requirements coverage report links each requirement to its supporting business rules, and each rule to the exact source-code lines it came from. It also classifies every line of source code by how it was handled. AWS says the changes are available in all Regions where Transform for mainframe is offered.
Why it matters
Mainframe modernisation is difficult partly because the original application’s business logic can be hard to untangle. More precise groupings and traceable requirements give teams a way to inspect what the tool has accounted for, from the wider portfolio down to individual lines, before they proceed to forward engineering in Kiro or another IDE.
That does not make a generated analysis correct by magic. But it does give reviewers a more concrete trail to examine than a report they have to assemble themselves. In a project where missing a business rule can have expensive consequences, being able to follow the reasoning back to the code is useful work, not decorative paperwork.
Our read
This is a practical improvement to the assessment and reimagine workflow, rather than a grand claim that old systems can now modernise themselves. The strongest change is the built-in chain from code, to business rules, to requirements. Teams considering the service can now check whether that extra visibility fits their review process before moving into implementation.
What to watch
- Whether teams find the more precise business-function groupings useful in real modernisation projects.
- How reviewers use the code-to-rule-to-requirement links to identify gaps before forward engineering.
- Whether AWS expands these reporting capabilities to other parts of the workflow.
Discussion spark: For mainframe modernisation, is a traceable link from requirements back to code enough to build confidence, or should teams require independent validation before implementation?
Sources and evidence
- AWS Transform for mainframe improves the reimagine modernization workflow (3 November 2026, 08:00 UTC)
not affiliated with or endorsed by Amazon Web Services (AWS)