CIS1500 Assignment 2
CIS1500 Assignment 2
Assignment Description
Assignments are meant to replicate real-world requests for customers to develop applications. This means
you’re intended to discuss any unclear requirements with our teaching team. Please post questions to the
discussion boards and review the discussion board for clarification for any unclear requirements.
Description
Recently, the online game ‘Wordle’ has become quite popular. This simple yet elegant game quickly engages
users without much coding requirements. We will develop a text-based version of the game for this assignment
with a few simplifications. For those unfamiliar with the game, you may learn the rules at ( by clicking the ‘?’
on the top left): https://www.nytimes.com/games/wordle/index.html
The game requires the user to identify a hidden 5-letter word. The player has multiple rounds to guess the
secret word. They lose the game if they do not successfully guess the word within the rounds. After each
guess, hints are revealed in the official game that indicates if any of the correct letters are present. Hints are
displayed in two types; if the letter is the correct letter and in the proper position, the letter is highlighted in
green. If the guessed letters occur in the word but at a different position, it is highlighted in yellow. Guessed
letters that don’t appear in the secret word remain unhighlighted.
For our version of the game, we have a maximum of 5 rounds of guessing. Each word will contain 5 letters.
Unlike the original game, we will not validate if the 5 letter word is a real word. Our game starts with a user
entering a secret 5-letter word. After which, the player has 5 rounds of guessing. The game ends when the
player guesses the correct word or has no more rounds of guessing. If the correct word is guessed, your
program should print a message indicating the player has won. Suppose the player is unable to correctly guess
the word in the number of rounds. In that case, your program should display a message indicating the player
has lost the game and the secret word. If the player guesses the correct letter at the correct position, we indicate
this with ‘+’. If the letter occurs within the word but at a different position, your program should indicate this
by ‘-‘, and if it does not occur in the word, we use an ‘x’. Please review the solution and the samples provided
here for the expectations of the program.
Example Input/Output
Sample input and output are given on the following pages. These are only samples – your program must run
for any set of values. You should consider all the possible inputs and mimick the results of the solution
program. Please note error checking for your program does not need to include invalid data types. For instance,
you will never be given the character ‘a’ as an int. However, you must select the correct data type to solve the
problem correctly.
Note: Your input and output should match precisely the solution program provided. These examples should
match as well. However, due to the spacing of Microsoft word, it can appear differently. Use these examples as
a template, your program should match the official solution program.
Expectations
The examples provided do not cover the full scope of the problem or the potential inputs. Part of the
assignment is to explore the problem description and solution program to determine what is expected. You
should use the discussion boards to discuss any program requirements (ie tasks) that you want to be clarified.
This mimics real-world software development practices and helps identify intended and unintended
ambiguities in the program description. Please note any spelling mistakes or format issues in the solution will
need to be replicated rather than fixed since your output must match ours.
Grades Scheme
50% Auto-graded - Test cases (You can test these yourself)
25% TA Test cases
( Similar to auto-grade tests but different values and reviewed manually )
Examples of test cases are error cases or invalid data.
These tests have the same format as the auto-graded tests but have different input values. These are
considered edge cases or cases that might cause your program to crash.
Common Deductions
Other deductions may apply these are common deductions.
Code that does not compile ( will receive 0 )
Missing student information in comments.
Missing instructions on how to run your program.
Incorrect or inconsistent code formatting.
Printing unrequired information to the screen.
Variables names are non-descriptive or not in camelCase.
Poorly formatted output to the screen