College of Arts, Technology and Environment

ACADEMIC YEAR 2024/25

Assessment Brief
Submission and feedback dates
Submission deadline: Before 14:00 on 01/05/2025

Is eligible for 48-hour late submission window.

Marks and Feedback due on: 30/01/2025

N.B. all times are 24-hour clock, current local time (at time of submission) in the UK.

Submission details
Module title and code: UFCFGL-30-1 - Programming in C++

Assessment type: Practical coursework examination with oral demonstration

Assessment title: Oral Presentation - Task A

Assessment weighting: 40% of total module mark

Size or length of assessment: N/A

Module learning outcomes assessed by this task:

1. Develop and implement C++/C programmes using suitable language features.

2. Select suitable programming languages based on an understanding of the underlying
programming model.
3. Evaluate contextual issues related to software development, for example, security
issues, the use of open-source software, legal and ethical issues.

This is individual work.

You must complete and pass this task to pass the module.
What am I required to do on this assessment?
For this task you are required to complete small C++ project. The main body of work should
develop a terminal application, and should include examples of use, and documentation.
All work will be written in C++, developed on the csctcloud.uwe.ac.uk, and contained with
a Gitlab repo.

1
The assignment details are on Blackboard, under Learning Material/Assignment, and
submission is a Gitlab repo link, which is submitted via Blackboard.

A small library that provides console graphics for interaction and drawing is provided.
This framework must be used as the basis for the assignment.

There are three possible applications that you can implement:

• Tic-Tac-Toc
o You can score a mark of at most 70%
• A clone of the game 2048.
• A command line application.
o In this case you might implement something like the cp command line
program, supporting its different arguments, etc.

Each of these applications can simply use the terminal to display the output. For example,
Tic-Tac-Toe, would display the board after each move and so on. The goal of the assignment
is to understand the logic of the task and implement that, the UI being terminal based
allows you to focus on that without spending too much time on the look.

That is not to say that adding a UI for you application is a bad idea, and for the more
advanced of you, maybe take a look at ncurses, which enables simply terminal based UIs.
As another example, you might choose to create a gif generation CLI app in the same style
as worksheet 4 (though this should not be a game of life project).

To complete the assignment, you must:

• Choose one of the 3 options above;

• Implement a solution that includes:
• At least 2 C++ source files (.cpp)
• At least 1 C++ header file (.hpp)
A readme.md, in your Gitlab project for the assignment, then documents what you
have implemented, provides screen shots, and explains how to build and run it.

Where should I start?

Before progressing to the assignment, you need to complete the setup for the
remote development server, csctcloud.uwe.ac.uk.

• Accessing CSCT Cloud using Azure CLI and SSH Keys

• Setting up remote development for VSCode

For the most part this should be straightforward as you continue to use the remote server
as per first semester and needed to be completed for task B assessment.

2
What do I need to do to pass?

The assignment contains a marking scheme for each task, where each task is worth a
percentage of the overall mark. You must get a total minimum of 40% to pass this
task.
The following marking scheme is how each individual task will be marked.
IMPORTANT: Additionally, note that all work must be included in a Gitlab repo, with the link
to this repo submitted on Blackboard. Failure to provide a Gitlab repo link will result in a
mark of zero. It is not valid to submitted directly via Blackboard or via email.

3
 Outstanding
Percentage

Inadequate
Very Good

Very Poor
Adequate
Excellent
100-86

Poor/
85-70

69-60

59-50

49-40

39-30
Good

29-0
- Impressive - Excellent - Very good - Good demonstration - Some demonstration - Little or no - Little or no
demonstration of Demonstration of demonstration of of programming and of programming and demonstration of demonstration of
Programming and Programming and Programming and software development software development programming and programming and
software development software software development skills. skills. software development software development
skills. development skills. skills. - Demonstrates good - Demonstrates some skills. skills.
- Demonstrates - Demonstrates - Demonstrates very insights into the insights into the - Demonstrates some - Demonstrates little
outstanding insights excellent insights good insights into the technologies technologies insights into the or no insights into the
into the technologies into the technologies technologies employed. employed. technologies technologies
employed. employed. employed. - Appropriate - Some or poor employed. employed.
- Appropriate - Appropriate - Appropriate software testing; tests software testing; tests - Poor software - Little or no
software testing; tests software testing; software testing; tests most aspects of the some aspects of the testing; tests some software testing.
all aspects of the tests all aspects of all aspects of the product in detail. product. aspects of the product. - Limited or no
product in great the product in great product in great - Good reflection on - Limited reflection reflection on the tests’
details. detail. detail. the tests’ results. on the tests’ results. results.
- Outstanding - Excellent - Very good reflection
reflection on the tests’ reflection on the on the tests’ results.
results. tests’ results.

4
How do I achieve high marks in this assessment?
Completing all the tasks in the assignment will get you a good mark, but you need to add
some additionally features, ones not covered in the specification, to get a mark above 72.
We will discuss suitable examples of these in the practicals as the module progresses.
A key requirement for this assessment is a high-quality README.md, documenting
your work, how to use it, and demonstration of it running. This README is written in
Markdown, see Blackboard for resources, but also the cheat sheet is useful.
How does the learning and teaching relate to the assessment?

All lectures from TB1 (weeks 4 to 14) as well as lectures in weeks 17, 24 to 30 from TB2 will
cover martial that will be used to complete this assessment.
See the Blackboard schedule for details of what topics will be covered when.
What additional resources may help me complete this assessment?
• It is critical for success on this module to attend the weekly lecture and your practical.
• Markdown cheat sheet.
• The module team can be contacted by email and meetings can be arranged to discuss any
concerns.

What do I do if I am concerned about completing this assessment?

UWE Bristol offer a range of Assessment Support Options that you can explore through this
link, and both Academic Support and Wellbeing Support are available.
For further information, please see the Academic Survival Guide.
How do I avoid an Assessment Offence on this module?
Use the support above if you feel unable to submit your own work for this module.

5
Marks and Feedback
Your assessment will be marked according to the marking criteria in page 4.

You can use these to evaluate your own work before you submit.

1. In line with UWE Bristol’s Assessment Content Limit Policy (formerly the Word Count
Policy), word count includes all text, including (but not limited to): the main body of
text (including headings), all citations (both in and out of brackets), text boxes, tables
and graphs, figures and diagrams, quotes, lists.
2. UWE Bristol’s UWE’s Assessment Offences Policy requires that you submit work
that is entirely your own and reflects your own learning, so it is important to:
• Ensure you reference all sources used, using the UWE Harvard/OSCOLA
system and the guidance available on UWE’s Study Skills referencing
pages.
• Avoid copying and pasting any work into this assessment, including your own
previous assessments, work from other students or internet sources
• Develop your own style, arguments and wording, so avoid copying sources
and changing individual words but keeping, essentially, the same
sentences and/or structures from other sources
• Never give your work to others who may copy it
• If an individual assessment, develop your own work and preparation, and do
not allow anyone to make amends on your work (including proof-readers,
who may highlight issues but not edit the work) and
When submitting your work, you will be required to confirm that the work is your
own, and text-matching software and other methods are routinely used to check
submissions against other submissions to the university and internet sources.
Details of what constitutes plagiarism and how to avoid it can be found on UWE’s
Study Skills pages about avoiding plagiarism.