Purpose and use
A team wants to estimate or modernize a legacy system without knowing which evidence must be collected first.
Who should use it
Enterprise, Government, Partner decision owners, technical owners, reviewers, and delivery partners.
Decision supported
A team wants to estimate or modernize a legacy system without knowing which evidence must be collected first.
System evidence
For each item, record the responsible owner, evidence, and whether the answer is Yes, Partly, No, Unknown, or Not applicable when the worksheet format supports it.
- Applications, repositories, branches, frameworks, and build paths
- Databases, schemas, stored procedures, jobs, reports, and retention
- Interfaces, file exchanges, vendors, and scheduled dependencies
- Environments, deployment, configuration, secrets handling, and monitoring
Behavior evidence
For each item, record the responsible owner, evidence, and whether the answer is Yes, Partly, No, Unknown, or Not applicable when the worksheet format supports it.
- Critical workflows and exception paths
- Calculations, approvals, permissions, and reports
- Representative production scenarios and historical defects
- Manual workarounds and domain-owner knowledge
- Comparison and reconciliation rules
Decision evidence
For each item, record the responsible owner, evidence, and whether the answer is Yes, Partly, No, Unknown, or Not applicable when the worksheet format supports it.
- Business and technical owners
- Continuity, downtime, and rollback constraints
- Unsupported components and key-person risks
- Known unknowns and disputed behavior
- Acceptance criteria by modernization seam