CS 410 – Spring 2025 Iyengar Individual/Pair Programming Project

Due: End of Wednesday 1/29/2025

Managing SAT Word List Data

Input:              A text file named “words.dat” with a random number of words and their description.

                        Example:

                                                Abhor                          v          to detest strongly

                                                Mountain                     n          a natural elevation of the earth’s surface

                                                Great                           a          unusual, notable, important and/or consequential

Output:            GUI based display window and a menu window with buttons to choose from.

Control:           The user is requested to make a choice – who then clicks a button on the menu window. Output to be presented per

choice made on the display window. Repeat until user chooses quit option.

            The options are.

1) To add a new entry.

· Upon clicking this option – a new entry window pops up that requests the word (text input to be typed in), a selection of verb/noun/adjective, and a text input for the meaning of the word, and a submit button. Upon clicking this submit button, the word and its properties must be added to the list of words with the system.

2) To check meaning.

· Upon clicking this option – a new window pops up and requests a word (text input to be typed in) and a submit button. Upon clicking this button, the system searches and displays the word and its properties (if found) on the display window or displays an appropriate error message. Note – the words should be searched case insensitive.

3) To save the updated word list of words for later use (note if you run the application again – it should include the new added entries).

4) Quit Application

Assumptions: 

· Assume no duplicates

· Words are case insensitive

· A word can only be a verb or a noun or an adjective

Submission:

• You should save/export your project to your personal folder by the due date.
• All code must be clearly documented, to ensure the reader follows the intent of the code.
• All labels used must be descriptive of intended use.