Mobile App Analysis

Assessment Overview
As part of this assessment, you are required to choose a mobile app that you are familiar with.
This familiarity could be due to your frequent use of the mobile app as a customer, or as a
staff member (i.e., you use or have used this software at work or in your business).
This software needs to be:
• Interactive, in that it allows the users to register and create personal accounts and
engage in interactive transactions.
• Fully-live in that it is being used in a real-life setting, i.e., not defunct, or in a pilot stage.
Note that the software can be aimed at users in any country, i.e., does not have to be an
Australian software. Of course, if the software is in a language other than English, translations
into English will be required.
The roadmap for this project:
Please submit the name of the mobile app on canvas before Week 7. There is no mark
allocated for you. Please note that if your software is already taken by another student, you
cannot use the same software. In short, two students cannot use the same software for this
assessment. If your software is taken, you might be asked to change it. If you are doubtful
about the software you are going to select, you can discuss this with your tutor or the lecturer.
We will let you know if the software you have selected is not suitable, it means that we do not
think this mobile app is appropriate, or perhaps, way too many students have selected it
(beware of hugely popular platforms such as Instagram, Uber Eats, WeChat, or eBay). If we
do not approve this mobile app, you will need to propose an alternate one, so best to ensure
you have a plan B mobile app ready, just in case.
Once you confirm the software with your tutor, you can commence on the project, which
involves introducing a new feature for the mobile app and decomposing the existing mobile
app.
You are required to provide the following deliverables. Refer to Deliverables section for more
details and Assessment Criteria for marking rubric:
a. The narrative of the new feature
b. Design one Use Case Diagram for a primary Actor
c. One expanded Use Case for one use case
d. Class Diagram for the entire application and highlight the new feature (if it introduces
new classes)
e. One Activity Diagram for the main functionality of the mobile app
f. One State Diagram
g. Explanation of how this software is following UI principles