From the AWS edition of November 3, 2026
AWS Transform for mainframe adds field-level business-function discovery and a line-level requirements coverage report before forward engineering
Amazon Web Services (AWS Transform) · Legacy modernization; agentic AI for code · All Regions where AWS Transform for mainframe is available
- Publisher
- AWS What's New
- Original publication
- 2026-11-03
- Source retrieved
- 2026-11-04
What happened
AWS announced on Nov 3 that AWS Transform for mainframe now groups business functions only when they affect the same data fields (previously, functions using the same table or file were grouped), includes screens and queues, and generates a requirements coverage report in the assess-and-reimagine workflow. AWS says every line of z/OS COBOL and PL/I source is classified by how it was handled, every business rule links to its source lines, and every requirement is backed by business rules, before forward engineering in Kiro or other IDEs. Availability matches existing Transform for mainframe Regions; the notice does not list GovCloud specifically (the archive notes Transform expanded to GovCloud on Oct 30).
Why it matters
State agencies running unemployment, tax, Medicaid and DMV systems on mainframes could use the traceability report as audit evidence that AI-extracted requirements cover legacy logic. Benefit is unproven: no accuracy data or public-sector customer.
Evidence and measured results
One-paragraph vendor feature notice; no accuracy, recall or customer evidence.
Limitations and uncertainty
Vendor claim; completeness of rule extraction is not independently measured. GovCloud availability of this feature should be confirmed.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies modernizing mainframe systems risk losing undocumented business rules.
- Stakeholders
- Agency CIO
- Modernization program manager
- IV&V vendor
- Program SMEs
- Discovery questions
- Which mainframe applications are planned for modernization?
- How are business rules documented today?
- Does your IV&V contractor need traceability evidence?
- Value hypothesis
- Traceability may reduce missed-rule risk and support oversight; effect unmeasured.
- Potential engagement
- A one-application assessment comparing the coverage report with SME review.
- Unsupported claims
- Complete rule extraction
- Migration time or cost savings
- GovCloud availability without confirmation
Pre-sales engineering
Role takeaway
- Fit
- z/OS COBOL and PL/I estates already considering AWS Transform.
- Architecture and integration
- Assess/reimagine output feeds Kiro or other IDEs for forward engineering.
- Prerequisites
- Access to source code and JCL
- SME availability
- Requirements tooling
- Constraints
- Only COBOL and PL/I named
- Region availability per Transform table
- No public accuracy metrics
- Security
- Confirm source code storage and access controls for analysis artifacts.
- Proof of value
- Measure rule recall on a module with documented rules
- SME review of a sample of grouped functions
- Check unhandled-line classifications
Delivery
Role takeaway
- Work
- Use the report as a gate before forward engineering.
- Dependencies
- Source access
- SMEs
- IV&V contract
- Ownership
- Modernization program manager owns gate; IV&V reviews.
- Skills and adoption
- Analysts must learn to read and challenge the coverage report.
- Governance checkpoints
- SME sign-off on sampled rules
- IV&V review of coverage report
- Traceability check at test
- Acceptance criteria
- Proposed: at least 95% of SME-documented rules found in the sample
- Proposed: all unhandled lines dispositioned before build
- Risks
- Overconfidence in AI-extracted requirements
- Loss of SME knowledge
- Region constraints
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Fits the assess/reimagine phase before code generation; outputs feed IDE-based forward engineering.
Governance
Who approves, reviews and stays accountable for outcomes?
Line-level traceability can support independent verification and validation (IV&V) of modernization projects, if the report is reviewed by people who know the legacy system.
Security and privacy
What data, permissions and controls need testing?
Legacy source and business rules may be sensitive; agencies should confirm where analysis runs and how artifacts are stored.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
May reduce reliance on scarce COBOL experts for discovery but increases need for reviewers who can validate AI-extracted rules.
Procurement
What should contracts, pricing and exit terms secure?
IV&V vendors and modernization contracts could require coverage reports as deliverables.
Operating model
Which teams own the service once it runs?
Shifts modernization toward requirements-first rebuilds with traceability checkpoints.
Publication history
- 2026-11-03AWS · Issue 064 resources
Stable resource ID: aws-transform-mainframe-reimagine-requirements-coverage-20261103