{"resourceId":"aws-transform-mainframe-reimagine-requirements-coverage-20261103","versions":[{"version":"external-b86d6b89a057c46c49a05889029d65e0ac44d75fea883d9249b534e0e7e662ee","resource":{"id":"aws-transform-mainframe-reimagine-requirements-coverage-20261103","title":"AWS Transform for mainframe adds field-level business-function discovery and a line-level requirements coverage report before forward engineering","organization":"Amazon Web Services (AWS Transform)","sector":"Legacy modernization; agentic AI for code","geography":"All Regions where AWS Transform for mainframe is available","publishedAt":"2026-11-03","publicationDate":"2026-11-03","eventDate":null,"sourceName":"AWS What's New","sourceLabel":"AWS Transform for mainframe improves the reimagine modernization workflow","sourceUrl":"https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-mainframe-reimagine/","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","operating-model","governance-procurement"],"finding":"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).","sledRelevance":"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":"One-paragraph vendor feature notice; no accuracy, recall or customer evidence.","architectureImplications":"Fits the assess/reimagine phase before code generation; outputs feed IDE-based forward engineering.","governanceImplications":"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.","securityPrivacyImplications":"Legacy source and business rules may be sensitive; agencies should confirm where analysis runs and how artifacts are stored.","caveats":"Vendor claim; completeness of rule extraction is not independently measured. GovCloud availability of this feature should be confirmed.","streamIds":["aws"],"roles":{"sales":"Position the coverage report as an assurance artifact for state modernization programs, not as proof of faster migration. Mainframe projects often fail on missed business rules; a line-to-rule-to-requirement trace speaks directly to that risk and to IV&V oversight. Offer a scoped assessment of one bounded application to see whether the report holds up against subject-matter-expert review. Do not claim completeness or savings; AWS provides no accuracy data.","engineering":"Engineering should test the report against known ground truth: pick a COBOL module with documented rules and check recall of extracted rules and correctness of function grouping. Confirm the Region (GovCloud or commercial) and data handling for source code. Check how the report exports into requirements tools and whether forward-engineering outputs stay traceable to it.","delivery":"Delivery should make the coverage report a gate: no forward engineering until SMEs sign off on sampled rules and IV&V reviews unhandled lines. Track exceptions and keep traceability through testing. Plan for COBOL expertise to validate, not just to discover."},"roleDetails":{"sales":{"customerProblem":"Agencies modernizing mainframe systems risk losing undocumented business rules.","stakeholders":["Agency CIO","Modernization program manager","IV&V vendor","Program SMEs"],"discoveryQuestions":["Which mainframe applications are planned for modernization?","How are business rules documented today?","Does your IV&V contractor need traceability evidence?"],"valueHypothesis":"Traceability may reduce missed-rule risk and support oversight; effect unmeasured.","potentialEngagement":"A one-application assessment comparing the coverage report with SME review.","unsupportedClaims":["Complete rule extraction","Migration time or cost savings","GovCloud availability without confirmation"]},"engineering":{"fit":"z/OS COBOL and PL/I estates already considering AWS Transform.","architectureIntegration":"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.","proofOfValue":["Measure rule recall on a module with documented rules","SME review of a sample of grouped functions","Check unhandled-line classifications"]},"delivery":{"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.","skillsAdoption":"Analysts must learn to read and challenge the coverage report.","governanceCheckpoints":["SME sign-off on sampled rules","IV&V review of coverage report","Traceability check at test"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-11-04T04:09:38Z","enrichedAt":"2026-11-04T04:12:18Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"May reduce reliance on scarce COBOL experts for discovery but increases need for reviewers who can validate AI-extracted rules.","procurementImplications":"IV&V vendors and modernization contracts could require coverage reports as deliverables.","operatingModelImplications":"Shifts modernization toward requirements-first rebuilds with traceability checkpoints.","sourceVerification":{"openedUrl":"https://aws.amazon.com/about-aws/whats-new/2026/11/aws-transform-mainframe-reimagine/","referenceExcerpt":"Business functions are now grouped only when they affect the same data fields.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}