Expected Learning Outcomes

$-$ develop computer programs in one or more high level language programming environment;

$-$ design and develop structured and documented computer programs;

$-$ explain the fundamentals of object$-$oriented programming and apply it in computer program development;

$-$ integrate the computer programming techniques to solve practical problems.

Introduction

In this assignment, you are going to develop an $"$AI Service Token Management System" that runs in the command line environment. The system maintains user records and manages the use of tokens by a user which can be used to pay for various web$-$based AI services. The system allows users to check their token balance and update their token balance upon purchasing new tokens or using a particular AI service.

Tasks

Each group is required to write a Win$32$ Console Application program called TMS$.$cpp$.$

$-$ Each student is required to submit a video recording $($at most $2-$minute long$)$ to demonstrate his$/$her individual contribution in the group project.

$-$ Each student is required to submit a Peer$-$to$-$Peer evaluation form $($through the given Word file$)$ via Blackboard. Program Requirements

R$0$ When the program starts, the console should display a welcome message, followed by the Main Menu of the program. Users can enter the options of the corresponding actions $($see R$1$ to R$6$ below$).$

Welcome Message designed by your group

$***$ Main Menu $***$

$[1]$ Load Starting Data

$[2]$ Show User Records

$[3]$ Edit Users

$[4]$ Enter User View

SEHH$/$SEHS$204224-25$ Semester One $-$ Group Project

$[5]$ Show System Usage Summary

$[6]$ Credits and Exit

Option $(1-6)$: R$1$

$[1]$ Load Starting Data

When the user inputs $1$ in the Main Menn, the systam is loaded with starting data. The starting data includes user records as ghownin R$1\mathrm{.}1$ below. After the starting data is loaded, the system returns to the Main Mern

R$1\mathrm{.}1$ The starting data to be loaded, togethar with the required data format of the data fields, are described below:

User records

Data format of each field:

$-$ User ID: A string that uriquely identifies $2$ wsar in the systam $($assume at most $50$ characters long$)$; it is case$-$sensitive You can assume it does not contain white space.

$-$ Type: A character $($T$,$ F or S$)$ that represarts the account type Different restrictions about using the AI services, and differant charging policies are wsed for different accourt types. See re$$urement R$7$ for detvils.

$-$ Token Balance: The token balance onnad by the weer.

$-$ Auto Top$-$up: A character $($ Y or N $)$ to indicate whether extra tokers would be purchased automatically if the tokan balance is not enough for a particular AI service. R$1\mathrm{.}2$ Options $2$ to $5$ in the Main Menu are enabled only after the system is loaded with the starting data. If the user enters options $2$ to $5$ before starting data is loaded, an error message should be shown, and then the system returns to the Main Menu.

R$2[2]$ Show User Records

$[$After the starting data is loaded$]$ When the user inputs $2$ in the Main Menu, the system displays all the fields of all user records. A tabular format should be displayed, and the records are sorted in alphabetical order based on the ID values. Data shown should be the latest set of data since the starting data is loaded $($updates on the user records resulted by the operations under options $3$ or $4$ in the Main Menu should be included$).$ After showing the records, the system returns to the Main Menu. R$3$

$[3]$ Edit Users

$[$After the starting data is loaded$]$ When the user inputs $3$ in the Main Menu, the system prompts for the next user input of a User ID$.$ If such User ID does not exist in the system, it is an add user operation. Otherwise, it is a delete user operation.

You can assume the system will store at most $100$ user records.

Add user

The system asks the user to input the information of the remaining three fields: $(1)$ Type, $(2)$ Token Balance, and $(3)$ Auto Top$-$up$.$ After getting all user inputs, the new user should be added into the system. For any invalid inputs $($e$.$g$.,$ wrong field values, incorrect range for token balance, etc.$),$ the system allows TWO more retries. With more than THREE times of invalid inputs, no user is added. The system prints an appropriate error message and returns to the Main Menu.

Delete customer

The system displays the information of the user $($including all the fields$),$ and prompts for user's "Yes$/$No$"$ confirmation on the delete operation. The user record is deleted from the system if it is confirmed.

A message showing the summary of the above operation is then displayed, and the system returns to the Main Menu.