# Development change review worksheet

Use fictional test data. Keep credentials and private customer/source details out of shared evidence.

- Requirement, outcome, and acceptance owner:
- Actual IFS release/update, Oracle version, build home, Developer Studio version:
- Component, object names, layer, model-to-generated-file map:
- Public API contracts and consumers affected:
- Optional components and installed/absent test builds:
- Row-level restrictions and test users with different company/site access:
- Method grants and expected denied cases:
- Timestamp meaning, server/site reference, legacy-data treatment, DST cases:
- Query grain, null/duplicate/empty cases, and result comparison:
- Representative input sizes, bind values, actual plan, elapsed time, logical reads:
- Bulk batch size, final partial batch, error handling, memory observations:
- Dynamic SQL necessity, bound values, identifier allowlist, reviewer evidence:
- Transaction owner, lock order, stale-write behavior, retry/idempotency design:
- Migration preconditions, rerun behavior, backfill, constraints, reconciliation:
- Build/static checks, fixture results, unit/service/security tests:
- Delivery sequence, rollback/roll-forward, evidence and monitoring:
- Actual environment validation date and unresolved issues:

Documentation review and local fixture checking do not establish Oracle or IFS execution.