1

School of Science and Technology

COURSEWORK ASSESSMENT SPECIFICATION

Details of Module and Team

What Learning Outcomes are assessed?
What are my Deadlines and how much does this
assessment contribute to my Module Grade?

What am I required to do in the assessment?

What are my assessment criteria? (What do I
have to achieve for each grade?)
Can I get formative feedback before submitting ?
If so, how?
What extra support could I look for myself?

How and when do I submit this assessment?

How and when will I get summative feedback?
What skills might this work evidence to
employers?
2

Module Code SOFT40151

Module Title Mobile Interactive Systems

Module Leader Brad Patrick
Module Team Dr. Thomas Johnson
Coursework Title Mobile Application Project
Module Learning outcomes K1, K2, K3, K4, S1, S2, S3, S4
assessed
Apprentice Learning outcomes N/A
assessed
Contribution to element 1 of 1 component (100% of element)
Date set Monday 22nd January 2024
Deadline for submissions Friday 8th March 2024 at 2.30 pm
Method of Submission NOW Dropbox
Deadline for Feedback After 3 weeks from submission
Method of Feedback NOW Dropbox
Work handed in up to five working days late will be given a maximum Grade of a Pass whilst
work that arrives more than five working days will be given a mark of zero.
Work will only be accepted beyond the five working day deadline if satisfactory evidence,
for example, an NEC is provided. https://www.ntu.ac.uk/studenthub/my-course/student-
handbook/submit-a-notification-of-extenuating-circumstances

The University views plagiarism and collusion as serious academic irregularities and there
are a number of different penalties which may be applied to such offences. The Student
Handbook has a section on Academic Irregularities, which outlines the penalties and states
that plagiarism includes:

'The incorporation of material (including text, graph, diagrams, videos etc.) derived from
the work (published or unpublished) of another, by unacknowledged quotation,
paraphrased imitation or other device in any work submitted for progression towards or
for the completion of an award, which in any way suggests that it is the student's own
original work. Such work may include printed material in textbooks, journals and material
accessible electronically for example from web pages.'

Whereas collusion includes:

“Unauthorised and unacknowledged copying or use of material prepared by another
person for use in submitted work. This may be with or without their consent or agreement
to the copying or use of their work.”

If copied with the agreement of the other candidate both parties are considered guilty of
Academic Irregularity.
3
Please remember submitting portions of work already assessed is Self-Plagiarism and is
also a serious academic irregularity.

Penalties for Academic irregularities range from capped or zero grades for elements of
modules, to dismissal from the course and termination of studies.

To ensure that you are not accused of plagiarism, look at the sections on Plagiarism
Support and Turnitin support.

Chat GPT and other AI-powered language models

It is important to note when using any AI platform that they generate the most common
responses to questions, not necessarily the correct ones. They also fabricate evidence.
The material they produce is not your own words. Assessments require you answer
questions giving your own view and in your own words. The outputs from Chat GPT do not
provide that.

By presenting such material as your own words you are violating Academic Integrity
policy, a matter that NTU takes very seriously.

The skills you develop during your time with us allow you to interrogate material and
evaluate it, important skills in all careers. Chat GPT does not allow you to develop these.
4
I. Assessment Requirements

Mobile Application:
You will design and implement a mobile application of your choice using
Android Java* on the Android platform for a business or organisation of your
choice. If you’re not sure what kind of application to make, you may use any
of the ideas within the “Project Ideas” section on the NOW Learning Room.

Each project should have at least two interactive mobile development

features, here are some features which you can choose from:
• Graphics: writing interactive graphics applications with fast and
smooth animations.
• Drawing, or access to camera.
• Connecting and populating a database.
• Utilising sensor inputs: audio, camera, gesture, motion (tilt,
accelerometer).
• Location-based applications, GPS, CellID or WIFI. And integration with
mapping services such as Google Maps and mapping using GPS.
• Wireless connectivity: it could be Bluetooth, NFC, or Wi-Fi
connection(s).
• Handling Files, Audio or Video.

You may also use any other interactive features within your project, but you
need to highlight this in your video demonstration (see below).

The application can be developed for Android Mobile Phones or Tablets.

*Submissions using either Kotlin or Flutter are permitted but require authorisation
from the module leader. Submissions of Kotlin or Flutter projects without
authorisation will result in failure of the coursework.
5
Report:
You will also need to produce an accompanying report to explain what your
application will achieve and show evidence of design evolution through user
testing.

The report should be between 4 to 8 pages long (font to be used is Verdana,

11 point). If you include either a front cover sheet, list of tables, or
reference / bibliography pages these will not count towards the size
of the report.

Only pages dedicated to the following sections will count towards the page
limit:
1. Introduction (0.5-1 pages):
a. Introduce your application by explaining what your application is
intending to achieve for the business / organisation.
b. Explain what your application will do, i.e., the key features of your
application and how they are justified with the business
requirements.
2. Application Design (3-5 pages (inclusive of design images)):
a. Draw up an initial design for one section of your application and
provide this within the report.
b. You will need to do some background research (remember to
reference!) on the Android design guidelines (material io) and then
compare your design provided above to them guidelines.
c. You will also need to do some user testing on your initial design,
showing the design to others and getting feedback from them. The
easiest way to do this is with your peers in the timetabled lab
sessions.
d. Finally, provide a final design based on the researched guidelines
and user feedback explaining the changes made from your original
design. If your final design goes against either, you will need to
provide some justification.
3. Conclusion (0.5-2 pages):
a. Discuss the strengths and weaknesses of your final application such
as what you think worked well, how well the features implemented
suit the business / organisation, and what improvements could have
been made to the application.
6
Video Demonstration:
You are required to provide a video demonstration of your working
application. This video should be uploaded to a video streaming service such
as Microsoft Streams or YouTube. (Please make sure you give your lab tutor
permission to access your video demo. Failure to do so may result in your
grades and feedback arriving late!) You should NOT upload the raw video
file to the Dropbox, please upload it to a video streaming service.

The video demonstration is about demonstrating not only your application

working, but also your understanding of your application and programmed
code. Your video demo MUST have audio commentary provided by you to
show authorship of your work.

The easiest way of doing this is by recording a meeting in Microsoft Teams

as this allows you to capture audio while sharing your screen on multiple
devices (should you require them).

To make this easier, here is a guide of what is expected in your video

demonstration:

- Introduction: simply give a quick explanation of what your application

is and what it does. (Recommended no more than 1 minute)

- Demonstration of Features: Clearly show your application working,

showing the main features and any additional features of your
application functioning. You may discuss as many as you wish but bear
in mind the time limit (see below). If you have used any design
guidelines, explain them as you’re showing the features. You should
also explain any external hardware or software used, along with any
issues faced during the implementation stage. (Recommended 5
minutes)

- Demonstration of Code: Finally, you must go through and discuss your

code. You only need to do this for your main feature(s), discuss how
you have implemented the feature(s), what tools have been used
(e.g., Firebase) and why you have chosen to implement it in this
manner. (Recommended 4 minutes)

The video demonstration should be no more than 10 minutes in length.

If your documentation or video does not demonstrate your understanding of

how the app was developed, you may be asked to demonstrate in person.
Not submitting a video demonstration will result in failure of the
coursework!
7
Submission Instructions:
All your file names should include your name and student ID. Below are
instructions on how to submit each element to the Dropbox:

Declaration of Authorship: You must submit a completed Declaration of

Authorship form containing your name and any references that you have
within your code. You can download this form from the NOW learning room
to fill in and submit.

Mobile Application: You must submit your entire Android Studio Project as
a zipped folder (.ZIP). This should be uploaded to the Dropbox as a single
file.

Report: This must be submitted as either a Word Document (.docx) or a

PDF File (.pdf). The report should be uploaded to the Dropbox. Note:
Reports MUST NOT be submitted inside of ZIPPED Android Studio
folder.

Video Demonstration: This must be uploaded to a video steaming site

(either Microsoft Streams or YouTube). The raw video file should NOT be
uploaded to the Dropbox. The Dropbox allows you to leave comments,
please leave a link to the video inside the comments box.

Before pressing the final submit button your Dropbox should contain:
- a (.txt) file with your Declaration of Authorship.
- a (.ZIP) file containing your code
- a (.docx/.pdf) file containing your report
- a comment on the Dropbox containing the link to your video
demonstration that has been uploaded somewhere.

Make sure you backup your work all the time.

Note that Dropbox will allow to make multiple submissions. Make sure before
submitting, that all the files you want to submit are contained there (or in
the zip file you submit).

In the case of more than one submission, only your latest submission will be
marked, so make sure that all the files are included in the last submission
attempt and the last attempt is before the coursework deadline.

Plagiarism Detection software WILL be enabled for the submission.

 II. Assessment Criteria
8

Marking Distinction Commendation Pass Fail Zero Grade

Criteria
Excep High Mid Low High Mid Low High Mid Low Marg Mid Low
Grade Point
*16 15 14 13 12 11 10 9 8 7 6 4 2 0
Suitability of Video demonstration shows Video demonstration shows Video demonstration shows Video demonstration shows
Design comprehensive implementation in-depth implementation of that few relevant design very little knowledge or
of relevant design guidelines most relevant design guidelines and principles understanding of implementing
(20%) and principles. guidelines and principles, but are used in-depth… design guidelines and
with some aspects not OR principles.
Learning Video demonstration provides considered. … video demonstration
Outcomes: evidence that accessibility shows that most Implementation demonstrates
No discussion of
K2, S4 requirements have been Evidence of research into relevant guidelines and design which goes against
design
considered. Design guidelines has been principles have been guidelines without justification
guidelines.
provided in the report. implemented but only at a in the report.
Evidence of research into superficial level.
multiple Design guidelines have Design guidelines have been
been provided in the report. Design guidelines have discussed but discussion is
been discussed with no incorrect in the report.
*Accessibility features supporting evidence of
implemented. research in the report.
Implementat Video demonstration shows the Video demonstration shows Video demonstration shows Video demonstration shows Video
ion (40%) implementation has provided the implementation has trivial functionality has been that the functionality is not demonstration
excellent functionality to a provided good functionality to produced for a business / appropriate to the problem of a does not show a
significant problem for a a significant problem for a organisation, which business / organisation… working app…
Learning business / organisation. business / organisation but addresses the problem in a OR OR
Outcomes: with a few key Android very limited way. …functionality so trivial that it …Implementation
K1, K4, S1, Video demo and code shows development aspects doesn’t solve the problem in relies on a 3rd
S3 high level of Android missing. Only utilises basic Android any way. party library to
development skills are tools with messy or little perform most/all
acquired. code provided which shows Very messy or very little code the application’s
Video demo and code shows little understanding of provided which shows minimal functionalities.
Application has all key features good level of Android Android development. understanding of Android
fully working. development skills are development. No conclusion
acquired. Few features fully working, provided in the
*Advanced Android features with many unfinished, Video demonstration provides report.
are included. Application has most key partially working or missing. no audio commentary from the
features fully working. student AND / OR does not
adequately demonstrate
9
Conclusion in the report
provides excellent coverage of
the strengths AND weaknesses
of the final implementation with
good discussion of how the
application fits into the
business / organisation.
Data Store Data Storage has been fully
(20%) implemented in a variety of
ways, appropriate to the data.
Learning *Advanced data
Outcomes: storage used and
S2 demonstrated (e.g.
APIs or multiple
connections).
User Testing Evidence of user feedback from
(20%) initial design has been provided
from multiple users *in
significant detail.
Learning
Outcomes: Final design of multiple screen
K3, S4 sequences of the mobile
application has been provided.
Conclusion in the report
provides good coverage of
the strengths AND
weaknesses of the final
implementation with some
discussion of how the
application fits into the
business / organisation.
Data Storage is mostly
implemented correctly, but
there may be better methods
in some instances.
Evidence of user feedback
from initial design has been
provided from at least two
different users.
Final design of a screen
sequence of the mobile
application has been
provided.
Conclusion in the report
provides some coverage of
either the strengths OR
weaknesses of the final
implementation with little
discussion of how the
application fits into the
business / organisation.
Data is stored in a way that
allows demonstration of
functionality (including user
interaction), but is not
appropriate for the app
(e.g., use of SQLite rather
than network database)
and understanding of
appropriate methods are
evident.
Some evidence of user
feedback has been
provided.
Final design of screen
within the mobile
application has been
provided.
understanding of
implementation.
Conclusion in the report
provides very little coverage of
either the strengths OR
weaknesses of the final
implementation with no
discussion of how it fits into
the business / organisation.
Data is hardcoded and No data storage
does not allow for user is used or there
interaction. Understanding is no evidence of
of different methods is evident, understanding.
however.
No evidence of user feedback No user testing
has been provided. has been
provided.
A poor final design of screen
within the mobile application
has been provided.
10

III. Feedback Opportunities

Formative (Whilst you’re working on the coursework)
You will frequently be given informal verbal or written feedback regarding your (or
the class’s) performance on tasks relating to the coursework assessment during the
scale-up sessions. Attendance is therefore important for your development and thus
coursework success. You may also request feedback during the surgery session.

Summative (After you’ve submitted the coursework)

You will receive specific feedback regarding your coursework submission together
with your awarded mark. Clearly, feedback provided with your coursework is only
for developmental purposes so that you can improve for the next assessment or
subject-related module.

IV. Resources that may be useful

Referencing styles please use Harvard as detailed here
Guide to planning your time here and an automated planner here
Guidance on avoiding cheating is here
Remember to use Outlook or physical calendars to block out time between lectures
and labs to work on this coursework.

V. Moderation

The Moderation Process

All assessments are subject to a two-stage moderation process. Firstly, any details
related to the assessment (e.g., clarity of information and the assessment criteria)
are considered by an independent person (usually a member of the module team).
Secondly, the grades awarded are considered by the module team to check for
consistency and fairness across the cohort for the piece of work submitted.

VI. Aspects for Professional Development

Professional Practice
• Understand more about the demands of a professional work
context and possible scenarios
• Learn how constraints and requirements affect working practice
(quality, time, cost, commercial considerations, materials and
documentation standards etc.)

The table provides examples of:

Professional • Simulation of work scenarios • Projects with simulated customer-

Practice • Enacting standard industry practices expert relationship (students as
using industry-standard specification experts)
and reporting formats • Students enacting industry-
standard practical techniques
11

• Work on project/assessment briefs

informed by industry input (e.g. data
or problem specification)

Many of these are useful transferable skills for employment applications.