COMP228/327 Assignment 1

Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

COMP228/327 Assignment 1

Developing a Mobile App based on the Mastermind game.

Your Task

You will design and develop an application written in Swift 5 (or later) for iPhone 11 (if the Mac and version of Xcode you’re using does not support iPhone 11, then use another standard-sized iPhone). . The App will play a version of the game Mastermind (see https://en.wikipedia.org/wiki/Mastermind_(board_game) for details of the game).

Rules of the game:

1. A code-maker creates a pattern of four coloured pegs (from six colour choices), and hides it from the player (note that the pattern may contain several pegs of the same colour).

2. The player makes a guess at the code pattern by selecting a sequence of four coloured pegs.

3. If the player’s pattern matches that of the code-maker, then the player wins the game.

4. If the player’s pattern does not match that of the code-maker then the code-maker compares the player’s pattern against the hidden code pattern and reports back to the player:

a. The number of pegs of the correct colour and in the correct position in the pattern (indicated by a black symbol in the feedback).

b. The number of pegs of the correct colour but in the wrong position in the pattern (indicated by a white symbol in the feedback). Note that a peg that has matched (a) cannot also match (b).

5. If the player has made ten guesses without successfully guessing the hidden code, the code-maker wins the game.

6. If the player has made fewer than ten guesses, the game repeats from step 2.

The App should:

1. Allow the user to play the game of Mastermind, against the App which acts as code-maker. (worth 20%)

2. Provide an interface that allows the player to select four coloured pegs. The user must be able to select the pegs they want using a sensible UI. (worth 10%)

3. Provide appropriate feedback on the user’s choice (in some versions of this game, this is done using a smaller white or black peg, that the code-maker places to the right of the player’s code sequence for each type of match – note that the code-maker does not tell the player which of the coloured pegs matches, just simply the amount of those that do). (worth 15%)

4. Previous patterns that the user has chosen in this particular game and the feedback on them, must be displayed so that the user can use the information to inform their next choice. (worth 15%)

5. Use a persistent storage mechanism to save the number of games won by the code-maker and by the player, so that on starting the app, a count of the games won and lost can be viewed. (worth 10%)

6. Playability and Aesthetics: The app must feel and play like a good mobile app should. e.g. it must not have any awkward or unnecessary alerts, transitions, popups etc., and Labels and controls must be positioned correctly. (worth 15%)

The app must work in portrait orientation, on both an iPhone 11, and an iPad (e.g. iPad Air), maintaining a sensible UI in both (worth 10%)

Please ensure that your code is appropriately commented and meaningful variable and constant names are used. (worth 5%)

So that the assessor can check your game logic, please print the App’s generated secret code to the console (i.e. use a Swift print( ) statement).

Important - Please note:

Do not use any third-party frameworks in your App (e.g. Alamofire). Use Apple standard frameworks ONLY (i.e. only frameworks provided with Xcode). Use of third-party frameworks will involve a penalty of 25%.

What to Submit

Your completed project should be zipped up and submitted via the online submission system.

(Right click the icon for the folder containing the project file and folder and choose “Compress”)

Also submit a short informal document (1-2 sides of A4 at most) documenting how to use your app, and indicating any notable features.

Reminder: This is the first of two assignments, each of which is worth 15% of the total mark for COMP228 / COMP327. Your portfolio of lab work will be worth another 10%.

Notes:

User interface suggestions (though feel free to design and implement your own interfaces for both the peg selection and the display of the user’s guess and feedback):