Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 8

CET343 Android Mobile Development Assignment (2021/22)

This assignment contributes 100% to your final module mark and tests learning outcomes 1,2, 3 & 4. The
assessment has been designed to enable completion within a maximum time frame of 42 hours.

1. Advanced understanding of the various methodological approaches to native mobile design, including
different programming languages, storage designs and appropriate native mobile standards;

2. Comparative knowledge of design and development techniques for the design of native mobile
applications and storage systems

3. Ability to plan, analyse, design, build and implement a media and interaction rich native mobile
application in a chosen domain

4. Ability to plan, develop and implement an integrated testing and evaluation strategy accounting for user
experience, data integrity and network performance issues.

This assignment is split into three parts. Part A is worth 30 marks and is an analysis, design, functionality,
testing and evaluation report which offers you the opportunity to discuss your app’s life cycle, functionality
against the requirements, present your testing results and evaluate the overall success. Part B is worth 60
marks and this offers you the opportunity to create the app you have designed. The final section, Part C, is
worth 10 marks and gives you the opportunity to demonstrate your app.

The deadline for this assignment is Friday ... Please submit to the assignment space on canvas.
Scenario
JourneyJournal

You have been commissioned to create an app that will help people document their travel experiences. This
app will store a list of travel related journal entries, as well as pictures they have associated with each entry.
The app will also have scope to geotag the journal entries, as well as interact with other native applications and
hardware, such as the camera.

Typical user interactions

Walter has just embarked on a round the world travel adventure. He is trying to think of an easy way to
document his travel experiences. He decides to download an app, and after looking through the PlayStore,
decides on JourneyJournal.

After installing and then opening the app, he is prompted to either register or login. He notices a number of
registration options but decides to use traditional email and password. Once he has registered, he is
automatically logged in and is then presented with the apps homepage area. It is here he can see his journal
feed, which is currently empty. He presses the option to enter his first journal entry. He is taken to a screen
where he can record his thoughts as text, and enter a title of the journal entry. He notices he can also add a
photo to the journal entry, so he presses on this option. An option is now presented to either select an image
from the phone, or open the camera to take a new photograph. He takes a new photo and adds this to his
entry. The final option before completing the journal entry is to record his location. He decides to do this and
presses on the option. He is then presented with a map that loads his current location, but he is also able to
change the location by moving the map. Once he has selected his location, he is taken back to the journal
entry screen. He then saves his entry.

He is taken back to the main screen for the app where he can see a preview of his first entry, and it shows the
title, his photo, and the date and time of the entry. He clicks back into the entry and notices an option to edit or
delete the entry. He also notices the option to share this entry to social media apps that he has installed on his
device and decides to test his out by sharing his entry to the twitter app as a tweet.

He finishes using the app and signs out.


The prototype
Core requirements of the app:
● User registration and login.
● Main home area of the app.
● Create a journal entry.
● Manage my journal entries.
○ Delete entry.
○ Edit entry.

Optional Desirable Requirements for the app:


● The ability to Geotag a journal entry so the location of the entry can be recorded and then viewed on a
map.
● The ability to allow integration with other apps and hardware, such as social media and the camera.

There is no associated logo or house style for this app yet so you have free reign over the appearance,
but pay particular attention to Material Design.
Part A - Analysis, design, functionality, testing and evaluation (30 marks)
A technical report should be submitted. The document should include the following sections:
● Front cover. Include name, userID, registration number and programme.
● Analysis. This section requires you to provide a comparative evaluation of the various approaches to
mobile app design and development, including operating systems, options for different programming
languages, storage designs and appropriate native mobile standards. Your comparison should consider
iOS and Android based solutions at a minimum. This section should be in the region of 750 words.
● Design. This section should show your screen hierarchy, plus wireframe design and menu / layout
details. You should critically evaluate how your design matches current Material Design principles and
UX trends. Screenshots of XML layouts created in Android Studio are not acceptable and will
receive no marks.
● Functionality. Provide detail on key elements of your application’s functionality with a breakdown of
key examples of coding logic, ie how it works. You should give a clear description of the
implementation, including storage requirements and external APIs used (if relevant), and justify your
design and implementation choice.
● Test Strategy and Test Results. Summarise your strategy for testing and include a testing table of
tests and their results.
● Evaluation. Comment on the success of your implementation and make recommendations for
improvements.

Part B - Build of the mobile Android app - (60 marks)


The completed prototype app should be submitted. The application should be native and work well on an
Android phone or tablet device. For the purpose of this project all data persistence can be local but it is
encouraged to implement cloud solutions for data persistence.

Your prototype should include all of the core requirements mentioned in the scenario.

You are also to attempt one of the optional desirable features. Please only attempt one desirable
feature, as marks will only be awarded for one. You must make it clear which desirable requirement
you have attempted.

Please ensure that all code (XML and Java / Kotlin) is commented appropriately and that you have packaged
the app successfully before submitting a zipped project file to canvas.

Part C - Demo (10 marks)

You are required to demonstrate your app with a screencast recording. This should be no longer than 10
minutes. The purpose of this demonstration is to:
● To showcase the application and how well you have met the core requirements.
● To showcase the application and how well you have met the desirable requirement of your choice.
● To demonstrate any issues identified during testing which have not yet been resolved.
Submission

The deadline for submission is the .... This excludes anyone who has a support memo and may be entitled to
extra time.

Please submit the 3 files to canvas. A PDF for your report, a Zip file containing your android studio project and
an MP4 file of your screencast.

Marking Criteria

Part A
Analysis (4 marks)
Full marks will be awarded for a clear, detailed and accurate analysis and evaluation of the various methods
and approaches to native app development.

Design (10 marks)


Full marks will be awarded for a full collection of wireframe designs that follow current material design
standards and follow current trends in application design. User interaction needs to be fully considered to
ensure a good user experience and marks will reflect this. An explanation of your design and how it matches
material design must be included to achieve full marks for this section.

Functionality (4 marks)
Full marks for clearly explaining your app’s core functionality including explaining the storage of data and any
APIs you might have used.

Testing and Evaluation (8 marks)


Full marks awarded for detailing your chosen test strategy, presenting your findings and critically evaluating
how successful your app has been.

Presentation and referencing (4 marks)


Full marks for this section will be awarded for a professional report including a front cover and accurate
referencing.

Part B
Core functionality to include the following (maximum 48 marks):
● Entry screen with Login or Signup - the point of entry for your app. (8 marks)
● User registration and login (10 marks)
● Manage my journal entries (18 marks)
○ View entries
○ Delete entries
○ Edit Entries
● Create a Journal entry (12 marks)
Desired functionality (1 to be completed, maximum 6 marks)
● The ability to Geotag a journal entry so the location of the entry can be recorded and then viewed on a
map.
● The ability to allow integration with other apps and hardware, such as social media and the camera.

Part C
Demonstration (10 marks)
A short, successful and professional demo of your application explaining how you have met the core and
desirable requirement and any issues you had along the way. This is to be submitted as a screencast (mp4) no
longer than 10 minutes.

Marking Grid

Analysis 4 marks 2-3 marks 0-1 marks


A fully comprehensive A good analysis and A poor analysis of current
accurate analysis and evaluation of the methods and approaches
evaluation that includes methods and approaches to app development. This
the various methods and to native app may be significantly
approaches to native app development. This may lacking in detail and
development. be lacking in detail and critical evaluation.
critical evaluation.

Design 8-10 marks 3-7 marks 0-2 marks


A full collection of A full collection of Partially completed
wireframe designs that wireframe designs that wireframe designs with
follow current material partially conform to an evaluation that falls
design guidelines and material design significantly short of what
current trends in app guidelines. Your critical is required.
design, complete with a evaluation might be
detailed critical lacking in detail and
evaluation of how your justification.
design meets these
guidelines.

Functionality 4 marks 2-3 marks 0-1 marks


A fully comprehensive A description of most of A poor or missing
accurate description of the functionality of your description of the
the functionality included app but some parts may functionality of your app.
in your app. be missing or not
described.

Testing and evaluation 7-8 marks 3-6 marks 0-2 marks


A comprehensive test A good test strategy Partially completed or
strategy where all tests where testing is mostly missing test strategy with
are relevant and relevant and you have little or no evaluation.
documented, including a attempted to critically
detailed documentation evaluate how successful
of how successful your your app has been.
app has been.

Presentation and 3-4 marks 0-2 marks N/A


referencing Professional presentation Presentation of the
including contents page document might be
and front cover with lacking professionalism
accurate referencing and references might not
be accurate

Prototype app

Entry screen 7 - 8 marks 3 - 6 marks 1 - 2 mark 0 marks


with login or A fully working activity A partially working An incomplete / non No attempt
signup activity functioning activity

User 9 - 10 marks 4 - 8 marks 1 - 3 marks 0 marks


registration A fully working activity or A partially working An incomplete / non No attempt
and login very good attempt. activity functioning activity

View entries 6 marks 3 - 5 marks 1 - 2 marks 0 marks


A fully working activity A partially working An incomplete / non No attempt
activity functioning activity

Edit entries 6 marks 3 - 5 marks 1 - 2 marks 0 marks


A fully working activity A partially working An incomplete / non No attempt
activity functioning activity

Delete entries 6 marks 3 - 5 marks 1 - 2 marks 0 marks


A fully working activity A partially working An incomplete / non No attempt
activity functioning activity

Create a 10 - 12 marks 4 - 9 marks 1 - 3 marks 0 marks


journal entry A fully working activity or A partially working An incomplete / non No attempt
very good attempt. activity functioning activity

Desirable 6 marks 3 - 5 marks 1 - 2 marks 0 marks


feature A fully working activity A partially working An incomplete / non No attempt
activity functioning activity

Presentation screencast (maximum 10 marks)

Presentation 6-10 marks 1 - 5 marks 0 marks


screencast A professional demonstration of A demonstration of your app No attempt
your app covering how the app that may fall short of
meets the needs of the scenario explaining the core
with the core requirements and requirements of the app to the
any desirable requirements. desired level

You might also like