Task 1 (Data Structure) Task 2 (Terminology standardization) Task 3 (impact of change) Mission 1 (Decision Making) Mission 2 (Exception Scenario) 📊 View Summary ← Classroom
Day 3 Task 03 Scope of Impact Analysis

Task 03. Change Impact Analysis

When the database physical schema or core business logic changes, a summary is automatically created by analyzing the API specifications and UI screens affected.

Task 03 Change Impact Sharing Practice Guide

📥 Practice Input

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

💾 Practice output (Output)

  • • change-impact-report.md (Change Impact Analysis)

1. Story and practice background

After the database design was completed, the business specifications changed drastically. Previously, it was 'immediate payment after reservation', but it has been changed to 'step reservation where the payment window opens when the expert approves after reservation.'

The development team is DB's Reservations on the table is_approved A column was quickly added and a status awaiting approval was added, but this important structural change was not shared in the API specification or plan and was left unattended. This resulted in a large number of failures due to missing API parameters during the QA stage.

In this exercise, you will learn a workflow that uses Codex to automatically analyze the scope of API endpoints and screen design modifications that are sequentially affected when schema modifications occur and create a report to share with team members.

2. Learning objectives

  • You can track the chain effects of data structure changes (Schema Changes) on the system.
  • API specifications and screen lists that require immediate revision due to changes can be identified and mapped.
  • You can autonomously create a shared report to notify team members by summarizing changes and scope of impact.

🛠️Practical guide to follow along

  1. Create file for practice: Click the download button below schema-change-request.md file automation/ Save it within the folder.
  2. Codex Analysis Delegation: Build by sending the **Codex request prompt** below to the Codex Client prompt input window.
  3. Impact Report Check: In the generated report, check that DB status segmentation (Wait Approve), API Response field adjustment, screen UI buttons, and status window action requirements are properly organized.

Download practice materials

Codex request prompt

Task 03 Prompt
Please fill out the API specifications, DB schema, screens, and change sharing reports that are affected as the reservation confirmation process has been changed to 'Awaiting Approval' status and 'Payment after expert approval'.

4. Example results

Codex accurately tracks revision requirements across submodules based on schema changes.

area of influence Details of changes risk level Documents and specifications subject to action
DB schema Reservations table status Common code refinement (add WAIT_APPROVE status) Normal Modify DB schema definition and DDL query statement
API specification Added approved_at field to reservation detail inquiry API response, adjusted payment request API call timing high Edit related APIs in api-specification.md
Screen UI Added a disabled status for the 'Pay' button in the reservation details screen and added a 'Waiting for expert approval' information window. high Member reservation screen plan & UI component modification