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 4 Task 03 Scope of Impact Analysis

Task 03. API change impact analysis (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 API Change Impact Analysis Practice Guide

📥 Practice Input

  • • day4_api_change_request.md (Change Request)

💾 Practice output (Output)

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

1. Story and practice background

As the service gets back on track, changes to new business specifications are issued. "Previously, the payment amount was sent immediately at the time of reservation creation, but for transparency in the payment process, please separate the flow so that the payment amount field is excluded when creating a reservation and the amount is entered when a separate payment is made after creating the 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 front-end UI or planning document 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.
  • You can identify and map front-end UI and screen lists that require immediate revision due to changes.
  • 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 day4_api_change_request.md Download the 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, new payment API button, and status window action requirements are properly organized.

Download practice materials

Codex request prompt

Task 03 Prompt
Analyze the contents of the provided API change request (day4_api_change_request.md) to derive a list of other system areas and documents affected when modifying the reservation request API, and prepare an API impact analysis that can be immediately shared with team members.

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
API spec Reservations table status Common code refinement (add WAIT_APPROVE status) High Modification of API specification definition and DDL query statement
Front-end UI Remove or transfer payment amount input field from reservation application form screen high Edit related APIs in api-specification.md
New payment API 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