Task 02 Change Impact Analysis Practice Guide
š„ Practice Input
- ā¢
requirements-before.md(v1.0 requirement) - ā¢
requirements-after.md(v2.0 requirement) - ā¢
screen-specification-v2.md(v1.0 screen design document) - ā¢
api-specification.md(v1.0 API specification)
š¤ Practice output (Output)
- ā¢ Change Analysis and Action Report Table
š ļøPractical guide to follow along
- Create file for practice: Click the download buttons below to download 4 files.
automation/Save it within the folder. - Request scope of influence mapping: In the Codex Client input window, Codex request promptBuild by sending .
- Check modification action items: Read the actions analyzed by AI and review scenarios where the addition of a front-end login button and the addition of a back-end sign-up API field are resolved.
Download practice materials
Codex request prompt
Task 02 PromptFirst, analyze which policy has been changed by comparing the 'requirements-before.md' and 'requirements-after.md' files in the project folder.
After that, analyze which part of the āscreen-specification-v2.mdā and āapi-specification.mdā documents, which remain at the v1.0 level, where the changed policy content should be reflected.
The results are output in a Markdown table format according to the format below:
1. āChange itemsā, āBefore changeā, āAfter changeā, āScope of influence (screen/API)ā, āActions (specific modification guide required)ā
2. Additionally, based on the v2.0 requirements, classify the importance of parts that require modification in the order of āhigh/medium/lowā and mark them in the column.
Expected results report
| Changed Items | Before change | After change | Scope of influence (screen/API) | importance | What to do (specific fix guide) |
|---|---|---|---|---|---|
| social login | Email login only | Added Google social login function | ā¢ Login screen (`SCR-01`) ā¢ Login API |
high | ā¢ Place āGoogle Loginā button component on login screen UI ā¢ Requires additional design of Google OAuth token reception parameter (`"oauth_token": "string"`) in API Payload |
| Membership registration verification | Email link verification | Check SMS authentication number by entering mobile phone number | ā¢ Membership registration screen (`SCR-02`) ā¢ Membership registration API |
high | ā¢ UI replacement of email sending component with mobile phone number input field and āsend/confirm authentication numberā field ā¢ Mobile phone number (`"phone": "string"`) and verification code (`"verification_code": "string"`) fields are required to be reflected in the subscription API payload. |
| Administrator rights | Automatic granting of single user permissions | Diversification of general user / system admin rights | ā¢ My Page screen (`SCR-03`) ā¢ Full security clearance API |
middle | ā¢ Added administrator-only dashboard screen design to be exposed when logging in with an administrator account ā¢ Design of authority role (`"role": "string"`) information receiver in API authentication header or member information response |