University of Westminster
School of Computer Science & Engineering
5COSC005W Coursework 1 (Semester 2)
Module leader Dr D. Dracopoulos
Unit Coursework 1
Weighting: 50%
Qualifying mark 30%
Description
Learning Outcomes
Covered in this
Assignment:
LO1, LO4, LO5
Handed Out: 3/2/2020
Due Date 2/3/ XXXXXXXXXX:00
Expected deliverables Source code/XML files/Resources (images, etc)
Method of Submission: Online via Blackboard
Type of Feedback and
Due Date:
Individual feedback ve
ally straight after the viva and written
individual feedback via Blackboard within 2 weeks of submission
All marks will remain provisional until formally agreed by
an Assessment Board.
Assessment regulations
Refer to section 4 of the “How you study” guide for undergraduate students for a
clarification of how you are assessed, penalties and late submissions, what constitutes
plagiarism etc.
Penalty for Late Submission
If you submit your coursework late but within 24 hours or one working day of the
specified deadline, 10 marks will be deducted from the final mark, as a penalty for late
submission, except for work which obtains a mark in the range 40 – 49%, in which case
the mark will be capped at the pass mark (40%). If you submit your coursework more
than 24 hours or more than one working day after the specified deadline you will be
given a mark of zero for the work in question unless a claim of Mitigating Circumstances
has been submitted and accepted as valid.
It is recognised that on occasion, illness or a personal crisis can mean that you fail to
submit a piece of work on time. In such cases you must inform the Campus Office in
writing on a mitigating circumstances form, giving the reason for your late or non-
submission. You must provide relevant documentary evidence with the form. This
information will be reported to the relevant Assessment Board that will decide whethe
the mark of zero shall stand. For more detailed information regarding University
Assessment Regulations, please refer to the following
website:http:
www.westminster.ac.uk/study/cu
ent-students
esources
academic-regulations
http:
www.westminster.ac.uk/study/cu
ent-students
esources/academic-regulations
http:
www.westminster.ac.uk/study/cu
ent-students
esources/academic-regulations
5COSC005W MOBILE APPLICATION
DEVELOPMENT - Assignment 1
Deadline 2/3/2020, 13:00
Dr Dimitris C. Dracopoulos
Email: XXXXXXXXXX
Description
You are required to implement an Android application using Java described by the specifications
elow.
You are not allowed to use third-party li
aries. The only li
aries you can use
are the standard Android API li
aries found in the following URL:
https:
developer.android.com
eference
It is important to follow exactly the specifications and your implementation must
conform to these:
The application developed will be displaying dog images of different
eeds and you should
use the images found in the following website:
http:
vision.stanford.edu/aditya86/ImageNetDogs
The website provides images for 120 dog
eeds. Your application does not need to deal with
all
eeds and all images but it can use a subset of them as long as it gives a sufficient variety
to the user. At a minimum, it should deal with images of 10
eeds but you might want to
include more to keep the user more interested. For simplicity and for all the tasks below, you
can hardcode in your program
eed names and/or mappings of
eed names to filenames.
You can download all images from the Download section of the above URL, from the link
called Images (filename: images.tar).
1. When the application starts, it presents the user with 3 buttons labelled Identify the Breed,
Identify the Dog and Search Dog Breeds. (4 marks)
2. (a) Clicking on the Identify the Breed button, it should display to the user one random
dog image picked randomly (and NOT in the same random sequence every time the
application restarts) from the dog images that your application contains.
The screen should also display a dropdown list with ALL the names of the
eeds
that you chose to include (see the comment above) and a button labelled Submit.
The user should use the list to select the
eed that the dog images co
esponds to
and clicking the “Submit” button he/she submits the guess to the app. (13 marks)
1
(b) As soon as the user submits the answer, the message CORRECT! (in green colour)
or the message WRONG! (in red colour) appears on the screen with the name of the
co
ect
eed in Blue colour, depending on whether the answer given is co
ect o
inco
ect respectively. (11 marks)
(c) Following this, the label of the “Submit” button should change to display “Next”.
The user should click the “Next” button to advance to another screen presenting him
with a new random dog image and giving him the chance to play again. Every time
that this option is chosen a different dog image (possibly the same
eed though)
should be displayed.
(5 marks)
3. Clicking on the Identify the Dog button, it should display to the user 3 different unique
andom different
eed dog images. The images should be clickable. It is not allowed to
display the same image more than once, i.e. the 3 images should be unique, as it should
also be the
eed.
The screen should also display the name of a
eed co
esponding to one of the displayed
images and a button labelled Next.
The user’s aim is to click on the dog image co
esponding to the displayed
eed name,
after which (a single attempt is only allowed) the message CORRECT! (in green colour)
or the message WRONG! (in red colour) appears, depending on whether the answer given
is co
ect or inco
ect respectively.
Following this, the user should click the “Next” button to advance to another screen
presenting him with 3 new random images and giving him the chance to play again. Every
time that this option is chosen different images should be displayed.
(18 marks)
4. Clicking on the Search Dog Breeds button, it should display to the user a textbox, a
Submit button and a Stop button.
The user will be using this part of the app to extend his/her knowledge about dog
eeds.
Typing the name of a
eed and pressing the “Submit” button will start displaying to the
user dog images belonging to the typed
eed. A new image will automatically appear to
the user every 5 seconds, like a slide show (without the need to press again the “Submit”
utton). The images will keep alternating in a completely random order for ever until the
user presses the “Stop” button. Once the “Stop” button is pressed the image slide show
stops and the user can type the name of a new
eed and resubmit to start the display of
a new sequence of images.
(17 marks)
5. Extend the application by providing a “Switch” button in the app home screen (first screen
with the 3 buttons game levels) which can be switched on or off. Every time it is switched
on, the first 2 game levels (“Identify the Breed” and “Identify the Dog”) will include a
countdown timer, counting from 10 down to 1, every tick occu
ing after 1 second exactly.
The countdown timer is displayed in the main screen of these 2 game levels.
As soon as the counter reaches the value of 0, the cu
ent game screen stops, i.e. the mes-
sage CORRECT! or WRONG! is displayed to the user and the “Submit” button changes
status and becomes the “Next” button as described before. Effectively, every time the
counter reaches zero is equivalent to the user pressing once the “Submit” button for that
game level.
2
(15 marks)
6. For all the tasks the application should behave in a user friendly manner when the device
is rotated from portrait to landscape and back to portrait mode. I.e. the application
should resume from exactly the same point (same screen and data) when the orientation
changes.
(7 marks)
Marking Scheme: The marks achieved for each part of the program are indicated in the
description of the task above. In addition to these the following will be taken into account:
• Code readability (structure, comments, variable naming, etc,): 5%
• Implementation (e.g. quality, efficiency, look and feel of the application, based on fonts,
colours, etc.): 5%
The maximum for work which does not compile (or XML files with syntax e
ors causing
the Java code not to compile) is 30%.
Based on the functionality implemented, the marks awarded will consist of 2 parts:
• 30% of the marks achieved will be awarded based on the submission.
• The remaining 70% of the marks for the implementation will be awarded after a compulsory
viva, that will test the understanding of the code by the student. The student will be asked
to demonstrate the application and will be asked questions about the code to demonstrate
his/her understanding. No understanding of any parts of the code will result in no marks
given for this component (i.e. a maximum of 30% can only be achieved if a students cannot
explain his/her code and he is unable to point to any references within the code of where
this code was found in a textbook or internet).
A compulsory viva for each student based on his/her submission will take place
during the next tutorial session after the submission (all of them taking place in the
weeks starting the 2nd of March and 9th of March). Each student will be notified
a specific slot that he/she needs to attend. Failure to turn up in the viva slot
designated (no changes will be allowed as this a normal examination) will result in
awarding only 30% of the marks achieved for the submission (see marking scheme
above)
It is the responsibility of each student to make sure that during the viva the code
uns properly in the lab used during the viva, i.e. you should make sure in advance
(allow enough time before the viva day) that everything is running properly in the
machine you will be using. If you developed code at your home computer, it is you
esponsibility that you port it to the lab in advance, before the viva. Marks will be
awarded based on the demo/viva and excuses of the type “it used to run - don’t
know what happened since last time” will not be accepted or awarded with extra
marks.
You are allowed to use your own laptop during the viva if you wish to.
Submission of assignments using a different method other than Blackboard will
not be accepted and zero (0) marks will be awarded in such cases.
Deadline: Monday 2nd of March 2020, 13:00.
3
Submission Instructions
Files to submit: All of the files of the Android Studio project of your application in a zip file.
Referencing code: Any code taken from other resources (i.e. a textbook or internet) should be
eferenced in comments within your code (full textbook details or full web