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

Task 02. Terminology Standardization

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

Task 02 Terminology Standardization 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 user DB,” and the publisher said, “On the admin page, it says customer company.”

In this way, if different terms are used for a single business domain such as plan (member), API specification (User), 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.
  • You can define the project standard Korean name and English abbreviation (domain standard name).
  • 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 fragmented-terms.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 the fragmented terms in the generated dictionary are accurately mapped to standard Korean names, English standard names, and DB recommended column names.

Download practice materials

Codex request prompt

Task 02 Prompt
Please analyze terms such as 'Member/User/Customer/Member' and 'Counselor/Expert/Teacher/Counselor' that are used interchangeably throughout the project and create a dictionary of standard project terms in the form of a Markdown table.

4. Example results

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

Standard Korean name standard English name data type Existing mixed words Recommended DB column name
General member User VARCHAR(50) Member, Customer, Member, User user_id
Professional counselor Expert VARCHAR(50) Counselor, teacher, counselor, expert expert_id
Consultation reservation Reservation VARCHAR(50) Reservation, application, Book, Reservation reservation_id
Reservation status ReservationStatus VARCHAR(20) Status, Category, Step, Status res_status