UNIVERSITY OF THE COMMONWEALTH CARIBBEAN
A Member of the Commonwealth & OAS Consortia of Universities
School of Technology & Mathematics
Department of Information Technology
Bachelor of Science Degree
in Information Technology
END OF SEMESTER ASSESSMENT
0 FALL R SPRING 0 SUMMER
CENTRE : ONLINE
MODULE : PROGRAMMING TECHNIQUES [ITT103]
DATE GIVEN :MARCH 31, 2021
DATE DUE : APRIL 11, 2021
PRESENTATION DATE: APRIL 12, 2021 OR APRIL 13, 2021
INSTRUCTIONS:
1. Please read all instructions carefully before attempting any question.
2. This individual project consists of one (1) compulsory task.
3. Read the given scenario, and then implement the instructions accordingly.
4. You must type and then upload your solution files for submission, on or before the
said time and due date.
5. No submission will be accepted via electronic mail.
6. You are required to do your presentation of the program in your class time during
the week of April 11, 2021.
7. Type your Student ID Number on your project or use the UCC cover page;
8. This Project assessment is worth 40% of your overall grade.
SECTION A
This coursework will constitute 40% of the final module mark, and must be submitted by date
mentioned on your course outline. Mark penalties will be applied for late submission (5% per
working day), and extensions are only allowed in cases of bone fide and documented extenuating
circumstances. You are required to do a 2-minute presentation of the program.
Introduction
You are required to implement an interactive graphical user interface. I have uploaded a sample GUI
program (Login and Registration) that can guide you (do not plagiarized the sample program, use it
as a guide). Your program should be able to perform the following:
1. Create an Account
2. Login an Existing User
3. File Menu option:
a. Check Credit Card – Use your assignment #2
b. A Game – Bonus
4. Help Menu option
5. Exit
Create an Account
This option should allow the user to create an account using their username, password, phone number and
address.
Login an Existing User
After the user created an account, the user should be able to login to the system. Display the username,
phone number and address when the user logged in.
Menus
When the user logged into the systems the menus options are shown such as:
• File Menu
o Check Credit Card Menu item
o Play a Game (Optional – Bonus Points) Menu Item
o Exit Menu Item
• Help Menu
Menu - File
This option will list the menu items, Check Credit Card, Play an Game and Exit.
2 of 6
Menu Item - Check Credit Card
This section allows the user to valid their credit card. You have completed this section in your assignment
#2. You have the option to modify your code.
Menu Item - Play A Game – Bonus Marks
This section allows the user to can play any games. You can build any game you like. The bonus marks for
this section is worth 15 points.
Menu Item - Exit
This section allows the user the exit the entire program.
Menu - Help
Give the user instructions on how to use your system.
MARKING:
Marking scheme for the program:
Note that your overall mark will be affected by the following areas and should be borne in mind at all times:
It should be well designed.
This includes well-designed classes, cohesive functions, minimal use of global variables, effective use of
parameters and so on.
Style and Readability
Programs are written not to just run, but also for others to read. Marks will be awarded for proper use of
3 of 6
indentation, spacing, descriptive identifiers, and general neatness.
Documentation
There is both internal and external documentation. The internal documentation is contained within the
program file(s) and includes a description at the top giving the inputs, overall processing, and outputs of the
program. It also includes a comment section for each function, listing what is being passed into it via the
parameters, what the function's main task is, and what values are being passed back out via the parameters or
function name. Internal documentation also includes a description of each user-defined class. External
documentation (readme file) is separate from the program and may consist of items like the specifications,
record of testing and so on.
Efficiency
Your program should not waste computer time or memory space. Make sure you don’t hand in unnecessary
codes.
Working Binary
The program must be able to compile and execute without errors.
SUBMISSION GUIDELINES
Your coursework must be emailed by August 11, 2021. The following procedures must be conducted:
1. DO NOT attach individual files. They MUST be zipped up as PT_<your fullname>.zip
Submissions that are not collected due to your computer not working, Internet connection is down, viruses
on computer, hard disk damaged, wedding, for example will incur 5% penalty.
To reiterate, all course works that are one working day late will be penalised 5%, two working days late 10%
and so on (unless you are very ill or have valid case then a formal letter must be written supporting a request
for extension).
PLAGIARISM
You are reminded of the policy regarding plagiarism (also known as copying, cheating, or getting no marks) that:
1. ALL codes will be checked thoroughly.
Please do not bother to plagiarize as it will just create problems for you, and more work for me, and I can
GUARANTEED you, it will be discovered.
4 of 6
5 of 6
Programming
Rubric
–
100%
Approx.
%
Criterion
Excellent
(100%)
Adequate
(80%)
Poor
(60%)
Not
Met
(0%)
of
Grade
Minor
details
of
the
Significant
details
of
No
errors,
program
Program
program
specification
the
specification
are
Program
only
functions
always
works
Specifications
/
50%*
are
violated,
program
violated,
program
correctly
in
very
limited
correctly
and
meets
Correctness
functions
incorrectly
for
often
exhibits
cases
or
not
at
all.
the
specification(s).
some
inputs.
incorrect
behavior.
At
least
one
major
Minor
issues
with
No
errors,
code
is
issue
with
consistent
indentation,
Major
problems
with
at
clean,
indentation,
Readability
20%
use
of
whitespace,
three
or
four
of
the
understandable,
and
whitespace,
variable
variable
naming,
or
readability
subcategories.
well-‐organized.
names,
or
general
organization.
organization.
File
header
missing,
One
or
two
places
that
complicated
lines
or
could
benefit
from
No
errors,
code
is
sections
of
code
No
file
header
or
Documentation
20%
comments
are
missing
well-‐commented.
uncommented
or
comments
present.
them
or
the
code
lacking
meaningful
is
overly
commented.
comments.
Many
things
in
the
code
No
errors,
code
uses
Code
uses
poorly-‐ could
have
been
Code
Efficiency
5%
the
best
approach
in
N/A
chosen
approaches
accomplished
in
an
every
case.
in
at
least
one
place.
easier,
faster,
or
otherwise
better
fashion.
Minor
details
of
the
assignment
Significant
details
of
the
specification
are
specification
are
violated,
Assignment
violated,
such
as
files
5%
No
errors
N/A
such
as
extra
instructions
Specifications
named
incorrectly
or
ignored
or
entirely
extra
instructions
misunderstood.
slightly
misunderstood.
6 of 6
