Day 2 Task 02 Change management

Task 02. Change Management

Learn how to control changes: when requirements change (v1.0 ➔ v2.0) because of new business policies, map the impact on downstream outputs (screen spec, API spec).

Task 02 Impact Analysis Lab Guide

📥 Lab input

  • • requirements-before.md (v1.0 requirements)
  • • requirements-after.md (v2.0 requirements)
  • • screen-specification-v2.md (v1.0 screen design)
  • • api-specification.md (v1.0 API spec)

📤 Lab output

  • • Change analysis and action report table

🛠️ Follow-along lab guide

  1. Create lab files: press the download buttons below and save the 4 files in the automation/ folder.
  2. Ask for an impact map: send the Codex request prompt below in Codex Client and build.
  3. Check action items: read the actions AI found and review scenarios that resolve the missing front-end login button and missing back-end sign-up API fields.

Download lab materials

Codex request prompt

Task 02 PromptFirst compare 'requirements-before.md' and 'requirements-after.md' in the project folder and analyze which policies changed.

Then analyze where the changed policies must be reflected in 'screen-specification-v2.md' and 'api-specification.md', which are still at v1.0.

Output the result as a Markdown table in this format:
1. 'Change item', 'Before', 'After', 'Impact area (screen/API)', 'Action (specific fix guide)'
2. Also mark the importance of each needed fix, based on the v2.0 requirements, as 'high/medium/low' in a column.

Expected result report

Change item Before After Impact area (screen/API) Importance Action (specific fix guide)
Social login Email login only Add Google social login • Login screen (`SCR-01`)
• Login API
High • Place a 'Sign in with Google' button component in the login screen UI
• Design a parameter in the API Payload to receive the Google OAuth token (`"oauth_token": "string"`)
Sign-up verification Email link verification SMS code check by entering a phone number • Sign-up screen (`SCR-02`)
• Sign-up API
High • Replace the email send component in the UI with a phone number field and a 'send/check code' field
• Add required phone number (`"phone": "string"`) and code (`"verification_code": "string"`) fields to the sign-up API Payload
Admin permissions Single User permission given automatically Split into regular User / system Admin permissions • My Page screen (`SCR-03`)
• All security authorization APIs
Medium • Add a design for an admin-only dashboard shown when logging in as admin
• Design a place to receive the role (`"role": "string"`) in the API auth header or member info response

💡 AI use and learning points

When the requirements doc is fixed, dynamically trace the sync state of downstream dev specs (API) and design docs (Screen spec) (Impact Mapping) to stop gaps in source code and planning.