Software Development 1 SET09802 Coursework 2 Assessment Brief 2026 |University of Edinburgh

Coursework 2

Module Title: Software Development 1

Module Code: SET09802 2025-6 TR3 001

Assessment Type: Practical Assessment

Assessment Limit: 5 pages A4 for the report

Overall module assessment: 90% for this coursework (10% coursework 1) allocated as

• Functionality 30% (program works according to specification)
• Use of classes and methods 8% (good abstractions, reusable code in methods, etc)
• Programming style 8% (neat code, good variable names, use of methods, etc.)
• Comments 8% (at the head of every method, at sections of complex code, etc.)
• Extensibility 10%
• Report 10%
• Advanced features 16%

• Variable bet amount 8%
• High score table 8%

Submission Date: Friday August 21, 2026, 23:59 BST

Submission Method: Via Moodle

Assessment Details

You should use all the programming concepts that you have been taught to implement a dice game called Dice Poker. In this game, the computer rolls two standard six-sided dice and you bet on the outcome. The outcome is the configuration of the numbers rolled (explanation below). The input/output should utilize a graphical user interface (input and message boxes). You must ensure that what you submit can be opened in IntelliJ or Eclipse by another person, so take care not to miss any important files. We recommend you ZIP the root folder of your project's directory.

Game Flow

You start with some money in your bank. You play a number of rounds, where for each round you place a bet and the computer rolls the dice, checks the result and modifies your bank balance. After certain conditions, the game ends and you're presented with some final information shown as a message box.
Placing Bets

Before the computer rolls the dice, you can bet some money from your bank.

• If the numbers are sequential (e.g. 1 and 2, 5 and 4, etc. Not 6 and 1), you earn double your bet.
• If the numbers are identical (rolling doubles), you earn triple your bet.
• Otherwise, you win nothing therefore you lose the amount of money you bet.
• Before placing a bet, the computer should inform you of your current bank balance.

Additional rules

When the game starts you are given £6 in your bank. Each bet costs £1 and you are allowed to make up to five bets before the game ends. The game will end if you run out of money, or you have no more attempts left (you made all five bets). At the end of the game, you will be told which of these conditions has ended the game.

Results Display

Once the game has finished (all bets have been placed or you ran out of money) the computer will collate and display the results in a single message box, comprised by.

• One row per bet, displaying your bet, the numbers rolled, the amount of money earned or lost for that bet.
• One row at the end, displaying the amount of money that you have remaining in your bank at the end of the game.

Advanced features (optional, but count towards your marks)

Variable bet amount

 Allow the user to change how much they would like to bet and change the amount you win accordingly. Allow bets between £1 and £4 (integers only).

High score table

Create a high score table. The more money you have remaining in your bank at the end of the game the higher up the table you will be. In order to implement this, players will have to enter their name before they play. The high score table should be displayed as a separate message box after the   have been displayed at the end of the game (1.4).

Reprot

In your report (5 pages maximum) you should include:

• A class diagram.
• A description of your classes: what each does and how they relate to each other if applicable.
• A description of why you believe your program is extensible. E.g. Is it easy to change the number of dice? The number of rounds to play
• The sides of the dice? Etc.
• A description of how you tackled any advanced features.

Important ("Good to know")

Collaboration and Plagiarism

This is an individual piece of assessment and the work submitted should be entirely your own. You are not allowed to collaborate with other people or to copy the work of other people. Your coursework will be electronically checked against all other submissions. If any plagiarism is detected your coursework will not be marked. In the event of any doubt about authorship, you will be interviewed by the School of Computing Academic Conduct Officer and may be asked questions about any aspect of the work.

Submission

You should submit your code as assignment via Moodle. If you will have multiple files, you should compress the project folder so that you only have one file to submit. Please use ZIP format only and use your matriculation code as the name for the zip file. Comments should be added within the code that explains what each part of the assignment is doing. Do not forget to add your name at the beginning of the file(s) as comments. Again, you must ensure that what you submit can be opened in IntelliJ or Eclipse by another person, so take care not to miss any important files.

• By submitting the report via Moodle (or otherwise), you are confirming that it is your own work. (Please note regulation Section B5.3.b regards component weighting.)
• You are advised to keep a copy of your assessment solutions.
• Late submissions will be penalised following the University guidelines as follows:

a. Up to 5 working days late the grade will be capped at F1.

b. After 5 working days a grade of F5.

• Extensions to the submission date may only be given by the Module Leader for exceptional circumstances, by submitting the appropriate request form - Extenuating circumstances (napier.ac.uk)
• The University rules on Academic Integrity will apply to all submissions.
• Feedback on submissions will normally be provided within three working weeks from the submission date.17 zm