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 02 Vocabulary standardization

Task 02. Screen consistency review (Terminology Standardization)

Analyze vocabulary inconsistencies between planning documents, API specifications, screen UI, and DB schema domains and build an integrated standard dictionary.

Task 02 Screen Consistency Review Practice Guide

šŸ“„ Practice Input

  • ā€¢ fragmented-terms.md (Statement of mixed use of terms)

šŸ’¾ Practice output (Output)

  • ā€¢ project-glossary.md (Standard Glossary)

1. Story and practice background

Late in the project, a strange conversation occurs during a bug review meeting. The planner said, ā€œAn error occurred on the customer withdrawal screen,ā€ the API developer said, ā€œA member referential integrity error occurred when processing Delete from the DB marked with ā€˜IDā€™,ā€ and the publisher said, ā€œOn the admin page, it says customer company.ā€

In this way, if different terms are used for a business domain such as plan (member), API specification (indicated as 'ID'), front screen (customer), and DB table (member), communication costs between developers are amplified and it becomes a hotbed of code rework.

In this exercise, you will use Codex to fully investigate the state of fragmentation of terms scattered throughout the entire project document, and learn techniques for building a standardized terminology dictionary that covers everything from planning to DB variable names.

2. Learning objectives

  • The fragmentation status of domain-specific terms used in documents and design specifications can be identified.
  • Project violation areas and English abbreviations (domain standard names) can be defined.
  • A dictionary of standard terms to be commonly followed by planners, developers, and designers can be defined.
  • Using AI, you can map legacy words to variable names and data types.

šŸ› ļø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 standardization mandate: Build by sending the **Codex request prompt** below to the Codex Client prompt input window.
  3. Vocabulary Dictionary Review: Check whether fragmented terms in the generated dictionary are accurately mapped to violation areas, English standard names, and DB recommended column names.

Download practice materials

Codex request prompt

Task 02 Prompt
Please compare the design details of each screen in the provided day5_signup_flow.md, analyze elements that lack consistency in button placement rules, terms used, and feedback messages, and create a screen comparison report.

4. Example results

Codex comprehensively analyzes multiple terms to derive a normalized master dictionary as follows:

violation area Sign-up screen (LOGIN-001) data type Existing mixed words Recommended Sorting Behavior (TO-BE)
user label Marked as ā€˜IDā€™ VARCHAR(50) Written as ā€˜Customer IDā€™, written as ā€˜IDā€™ Standardization of all input unit label names as ā€˜IDā€™
Main button structure Small green Done button at top right VARCHAR(50) Full-width blue login button at the bottom, small green Done button at the top right. Action buttons are unified in the bottom full width primary color
Consultation reservation Reservation VARCHAR(50) Reservation, application, Book, Reservation reservation_id
Reservation status ReservationStatus VARCHAR(20) Status, Category, Step, Status res_status