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

Task 03. Improving user movement (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 User movement improvement 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

The rate of users accessing the app and completing reservation payments has dropped abnormally. After investigating, I found out that while going through a total of 9 screens and clicking and checking terms and conditions for consultation, I felt tired and left halfway through.

The development team is DB's Reservations on the table is_approved A column was hastily added and a status awaiting approval was added, but this important structural change was not shared in the consent and payment form 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.
  • You can identify and map consent and payment forms 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 day5_signup_flow.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 analyze the reservation detailed scenario flow in the provided day5_signup_flow.md and create a user journey improvement report (User Journey Report) that can minimize the click steps and screen movement until the user completes the consultation reservation.

4. Example results

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

movement stage AS-IS flow specification (step 9) TO-BE improvement flow (step 4) Major improvement measures and significance
Reservation Scheduling Reservations table status Common code refinement (add WAIT_APPROVE status) List ➔ Detail/Calendar tab integration ➔ Select time Modification of reservation scheduling definition and DDL query statement
Consent and Payment Reservation request ➔ Move to information consent ➔ Move to refund consent ➔ Select payment method ➔ Manually enter card 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