Learning Outcomes to be Assessed:
1. Identify opportunities and challenges for mobile and wearable applications.
2. Architect a mobile/wearable application.
3. Select an appropriate set of technologies to use on an application development project.
4. Develop software for deployment on mobile and wearable devices.
Assessment Details:
Title: Mobile and Wearable App Design & Development
Type: Coursework
Style: Presentation and Demonstration of Design Concept and Implemented Prototype
Rationale: This module explores the direction mobile and wearable technologies are taking
and aims to equip students with the essential design and programming skills to develop their
own robust, usable and ubiquitous applications for at least one of the most popular mobile
and smart watch platforms.
Description:
Submission 1.1: A brief submitted (PowerPoint) presentation that will form the basis of a
brief discussion about a Project idea that provides coherence to your Prototype Apps. The
presentation should take five minutes followed up by questions/answers and feedback. This
should include a clear description of your Application idea showing its originality and
novelty [30%].
Submission 1.2: A brief demonstration and discussion of a submitted prototype Mobile and
Wearable Application, particularly illustrating an understanding and systematic approach to
designing and implementing the required features, of particular importance is the inclusion
of data persistence [70%].
Additional information:
Prototype development platform/ IDE: Android Studio
For advice on writing style, referencing and academic skills, please make use of the Centre
for Academic Success: https://icity.bcu.ac.uk/celt/centre-for-academic-success
4
Workload: This coursework is notionally regarded as a written work of 4000 words for
support summary purposes, therein facilitating an additional 10 working days, postsubmission deadline for the extended submission.
The typical student would be expected to invest at least 60 hours on this coursework.
Transferable skills:
Concept / Idea generation skills.
Communication skills encompassing Presentation / Concept Pitch Delivery skills.
Problem solving skills.
Debugging and Testing skills.
5
Marking Criteria:
Table of Assessment Criteria and Associated Grading Criteria
Assessment
Criteria
1. Identify
opportunities
and
challenges
for mobile
and
wearable
applications.
2. Architect a
mobile/wearable
application.
3. Select an
appropriate set
of technologies
to use on an
application
development
project.
4. Develop software
for deployment on
mobile and
wearable devices.
Weighting: 10% 10% 10% 70%
Grading
Criteria
what technologies
/ libraries that
could be used, an
excellent
exploration of the
pros / cons of
same and
alternatives
possibilities.
An excellent
presentation of a fully
functional
demonstration
showing a deep
understanding of the
core concepts
covered in the
module. Also able to
suggest detailed and
novel improvements
to the presented
design and prototype
90 100%
A*
An excellent
and highly
unique novel
project idea,
backed by an
in-depth
research of
the target
platform
features and
an in-depth
knowledge of
essential
libraries
An excellent and highly
unique project design
has been created
backed up with a very
in-depth awareness of
what is to be
developed. A very
significant and in-depth
level of design detail
and documentation
presented.
An excellent and
in-depth
awareness for
what technologies
/ libraries that
could be used, an
excellent and indepth exploration
of the pros / cons
of same and
alternatives
possibilities.
An excellent,
professional and
confident
presentation of a fully
functional
demonstration
showing a deep
understanding of the
core concepts
covered in the
module. Also able to
suggest detailed and
novel improvements
to the presented
design and prototype.
The discussion
should show a full
understanding of
issues involved in the
deployment and
release of a
professional
application
7
Fit to Submit:
Are you ready to submit your assignment review this assignment brief and consider
whether you have met the criteria. Use any checklists provided to ensure that you have
done everything needed.
Presentation Checklist:
Title slide, giving proposed applications and authors name, etc.
Overview of application project idea.
Application Requirements (e.g. Use Cases).
Application external Design (UI screenshots and storyboard).
Application internal Design (e.g. Class diagram).
Exploration of possible forms of persistence in the mobile domain pros / cons.
Proposed use of Data persistence (e.g. Data design / E-R diagrams).
Proposed use of additional Frameworks (beyond those required above).
Perceived Challenges.
Demonstration / Implementation Checklist:
Fully commented application source code (submitted as a .zip file).
Clear demonstration of implementation of prototype to include requirements, design and
feature set as proposed in Presentation.
Ability to discuss design decisions and changes (if any) to original proposed design
Ability to discuss internal design and architecture of application (including an
understanding of the design patterns employed).
Ability to propose alternative ideas for developing the application design further.
Walkthrough presentation (PowerPoint file) stepping through all the features of the
application, including plenty of screenshots to illustrate the workings of same
So im doing a game database that will use data persistence to store game information, user data, using tiles as the main design concept for the software, i need a log in screen sign up that will store it inside of a database prefereably firebase. i need a home page that has access to the users account a search bar, navigation and tiles that can take the user to any specific game doesn’t really matter then those tiles need a second screen to display some bs about the game and then they can add that game to their favourites
which stores in the database as well
Fully commented application source code (submitted as a .zip file).
Clear demonstration of implementation of prototype to include requirements, design and
feature set as proposed in Presentation.
Ability to discuss design decisions and changes (if any) to original proposed design
Ability to discuss internal design and architecture of application (including an
understanding of the design patterns employed).
Ability to propose alternative ideas for developing the application design further.
Walkthrough presentation (PowerPoint file) stepping through all the features of the
application, including plenty of screenshots to illustrate the workings of same
August 30th, 2020 
