Day 3 Task 03 Impact analysis

Task 03. Change Impact Analysis

When the database physical schema or core business logic changes, analyze the affected API specs and UI screens and write a summary automatically.

Task 03 Change Impact Sharing Lab Guide

📥 Lab input

  • • schema-change-request.md (change request)

💾 Lab output

  • • change-impact-report.md (change impact analysis)

1. Story and lab background

After database design was done, a sudden business spec change came up. Before, it was 'pay right after booking'; now it's 'a step-based booking where the payment window opens after the expert approves'.

The dev team quickly added an is_approved column and a waiting-for-approval state to the DB's Reservations table, but this important structural change was never shared in the API spec or plan. As a result, many failures from missing API parameters showed up during QA.

In this lab, you'll learn a workflow: when the schema changes, use Codex to automatically analyze all the API endpoints and screen design changes affected in a chain, and write a report to share with teammates.

2. Learning goals

  • Trace the chain effects of a data structure change (Schema Change) on the system.
  • Identify and map the API specs and screens that need updating right away because of the change.
  • Independently produce a sharing report summarizing the changes and impact for teammates.

🛠️ Follow-along lab guide

  1. Create the lab file: press the download button below and save schema-change-request.md in the automation/ folder.
  2. Hand the analysis to Codex: send the **Codex request prompt** below in the Codex Client prompt box and build.
  3. Check the impact report: confirm the report properly covers the more detailed DB status (Wait Approve), API Response field changes and screen UI button and status panel requirements.

Download lab materials

Codex request prompt

Task 03 Prompt
The booking confirmation process changes to add a 'waiting for approval' state and 'pay after expert approval'. Write the affected API specs, DB schema, screens and a change sharing report.

4. Example output

Codex accurately traces the revision needs across all downstream modules based on the schema change.

Impact area Detailed change Risk level Docs and specs to update
DB schema More detailed status codes in the Reservations table (add WAIT_APPROVE state) Normal Update the DB schema doc and DDL queries
API spec Add an approved_at field to the booking detail API Response, adjust when the payment request API is called High Update the related APIs in api-specification.md
Screen UI Add a disabled state to the 'Pay' button on the booking detail screen and add a 'waiting for expert approval' panel High Update the member booking screen plan & UI components