ASSESSMENT BRIEF
Class Group: CS
Assessor: Bernie Farrell
Component Title and 6N0736 - Graphical User Interface Programming
Code:
Assessment Technique: Skills Demonstration
Weighting: 30%
Title: Assessment 1
Issue Date: 24th October 2023
Submission Date: 23rd November 2023
Learning Outcomes 1, 2, 4, 5, 6, 7, 9 and 10
Assessed:
Guidelines:
Carry out the skills demonstration in accordance with the guidance provided in this document.
Assessment Criteria:
Program documentation to include evidence or prototyping and rapid application development.
(6 marks)
Application interface to include at least its look, ease of navigation, ease of use, simplicity,
consistency, feedback, and a help subsystem. (8 marks)
Quality of application to include at least adherence to user specifications, correctness, user error
trapping and feedback, robustness, and adherence to best practice. (12 marks)
Testing of application to include at least suitable test data, expected results and actual results.
(4 marks)
Page 1
Learner Name:
I confirm that:
1. I have been provided with information about Cork ETB’s assessment and appeals procedures
and my responsibilities with regard to assessment
2. The assessment work produced by me is all my own original work
Learner Signature:
Date:
Note to Learners:
Assessments will not be accepted without this coversheet.
Plagiarism is the presentation of someone else’s ideas, arguments, concepts or work as your
own by failing to reference or acknowledge it properly. All such work must be acknowledged.
Any learner, who presents another’s work as their own, will be investigated in line with Cork
ETB Assessment Malpractice procedures and may be awarded a zero grade.
Learners should keep copies of all assessment submitted, where applicable.
Page 2
Vending Machine
A vending machine sells 4 different types of soft drinks. Each drink costs €1.80. The price of
the drink is clearly displayed or “Out of stock” is displayed where a particular drink is not
available. Users can purchase more than 1 drink at a time.
A user can sign up for an account which will allow them to top-up their vending machine
account from their credit card details. They must log into this account to purchase a drink, as
each time they buy a drink, their balance is reduced by the amount they spend. Account
holders will receive a 10 cent reduction on every drink they purchase. If their balance is
below €2.00, they will get a notification after they login.
When a user wants to buy a drink, that doesn't have an account set up, they can log in using a
guest account. The vending machine will not dispense any change. They insert their money
into the vending machine and select the drink. The user must enter the correct amount or
more than the correct amount, then the drink that they selected is dispensed but NO change is
given. If a user inserts more money than the price of the drink, a warning message must tell
them that “This machine does not give change” and they can choose to still select the drink
and forfeit the change, or they can cancel the order. If a customer isn’t sure of what to do,
they can access a help facility at the vending machine.
Setting up an account
When signing up for an vending machine account, the user enters the following details:
Pin number (Must be 4 digits)
First name (letters, spaces, no numbers)
Last name (letters, spaces, no numbers)
Date of birth (those under 18 years of age cannot legally avail of the service as you
must be at least 18 years old to get a credit card by yourself)
Gender
Email address
Mobile number
Address (up to 3 lines, but 1 line is sufficient)
County (if Ireland) and
Country (if not Ireland).
Page 3
The user will be created with a pin number and their First name. It is only necessary to save
the pin and name of the customer. The customer must accept the terms and conditions
displayed.
Once those details are entered, the customer is invited to enter their:
Credit card number (16-digit) number.
Credit card expiry date and
Credit card security code (a 3-digit number)
A top-up amount that will be saved on their account (at least €10).
You must also be able to save the top-up amount that the user enters and there must
be a facility for further top-ups.
The Manager
The vending machine manager regularly goes to the machine to add more drinks and to
remove any coins from the machine. He/She does not require a login account. The manager
can then add drinks to the machine (up to a maximum of 20 units per drink) and can remove
money. The manager can also have a report displayed that indicates:
The count of each drink sold.
The amount of revenue generated. This should include the amount generated through
sales and the amount generated through unreturned change.
The amount of money that was removed from the machine.
The number of users with an account and their total spend.
Machine Maintenance
If a customer notices that a vending machine is damaged, not allowing entry of coins or
drinks are “Out of stock”, they can report it via the Vending Machine screen. They enter a
brief description of the fault or the drink that is “Out of stock”. The details are added to the
maintenance log.
The manager routinely displays the maintenance log. As each fault is repaired, coin entry
facility fixed or restocked with drink, the complaint description, date and time of
maintenance are sent to the repaired log and removed from the maintenance log. So this
means there are two lists or logs maintained.
Page 4
Data Stored
Program needs to be able to retrieve user name, pin number and account credit for each
account created. Drinks and money can be added via an array, file or hard coding data for the
different drinks in the Vending Machine.
You are required to design, code and test an application for the Vending Machine using
prototyping and rapid application development.
Submit
1. The design of your project.
This should include all the preliminary work for your project i.e. all the work that you
prepared using prototyping and rapid application development, to produce the final
product.
2. The screen layouts scanned into a word document.
3. The source code copied into a word document.
This should include the code for all the screens that you have used in your project and any
additional code (e.g. module code).
4. How you tested your program.
The testing that you carried out on each implemented prototype should be shown. This
should include testing of the functionality of the program and of any other tests e.g. data
validation, user/pin check etc... that you carried out to ensure that your program is
robust. This should be saved into a document.
5. The program files
Please ensure that you create your program using eclipse. All files should be zipped to be
uploaded to Moodle, include the entire JavaFX package/project and any additional files
that you have used in the program. Do not forget any user files, drink files or any CSS
styling files in your submission as this will impact the running and correcting of your
code.
Marks will be allocated as shown on the cover page.
Page 5
