Overview

You will design the flow, appearance and behaviour of an app for both Android and iOS platforms,without programming the app.

Timelines and Expectations

Percentage value of task:10% (of final course mark)
Minimum time expectation:5 hours
Maximum time expectation:15 hours

Learning Outcomes Assessed

The following course learning outcomes are assessed by completing this assessment.
S3. Design basic user interfaces and develop storyboards to convey designed interaction sequences.
S5. Develop test cases to ensure correct behaviour

Assessment Details

You need to develop a scenario, a use case diagram, and storyboards/screen designs for an app. You get to decide the particular purpose of the app based on the instructions in this document. The following tasks must be completed as part of this assessment

Task 1 – Decide on a scenario for an app that you will design

You need to consider what type of app you will make. Consider who the typical users would be, and what they will want to accomplish by using the app.
➔ You need to write a clear description of the scenario. Describe who the expected users of the app would be. Describe what the app allows them to do, in a couple of sentences (or more if it is an unusual situation). Explain how the chosen scenario will address the requirements listed below. It should require at most one A4 page to describe the scenario completely.
The only restrictions on what scenario you can choose are as follows: The app should allow the user to input some data in various fields (e.g. text input) which is stored. The app should also allow the user to update this data at a later stage if they wish. The app should allow the user to do something using the data that was previously entered. For example, if we were designing a dialler app, a list of phone numbers (contacts) could be entered and one of those contacts could be selected at a later stage to make a phone call. The app must have at least 3 different functionalities (possibly more), but do not plan for more than 5 main functionalities that can be accomplished using the app. At least two functionalities are covered if you follow the preceding instructions. Some examples of scenarios that have been chosen in the past are listed below to give you an idea of what is expected: A holiday/travelling diary app that the user can share/post updates to other users (friends) and give ratings/recommendations of sight-seeing places that they visit, and to coordinate meet-ups with any friends that are going to be in the area on the same day An app for a tennis club’s organizing committee to keep track of the members of the club – whether they have paid their annual membership amount; creating the roster of who will play in which matches for each week (which can be viewed by the other members, using the members scaled-down version of the app), and entering scores (which also can be viewed on the scaleddown version). An app for school children visiting the museum, to compete in small groups, in trying to be the first group to collect photos of specific exhibits from various places around the museum. You are encouraged to come up with your own scenario but can use one of these scenarios if you are struggling to think of your own.

Task 2 – Use Case Diagram

Draw a use case diagram, like the one in the week 2 study materials, to summarise the functionality that the app will offer to the user. These functions should reflect what you have described in Task 1.

Task 3 – Storyboards

Develop storyboards for two (2) distinct functionalities that you have described in Task 1, showing success sequences. You may submit additional storyboards if you like but it is not required. Show at least one (1) failure or abort sequence for any of the functionalities that were chosen for a success sequence in part (a). In developing the storyboards, pay attention to the following: Be sure to explain for each screenshot in sequence what the screen is showing to us (in terms of where it fits in the sequence), and to indicate what it is that the user must do to get to the next screenshot (e.g. clicking a button). Number each screenshot clearly to indicate the sequence order.

Additional Instructions

Prepare a document in a word processor (e.g. Microsoft Word or Google Docs) that contains your responses to all three tasks and convert to a PDF file for submitting. You may hand-draw diagrams/storyboards and scan these for inclusion into the document you submit, or you may wish to generate these using software. Various software possibilities exist, such as Microsoft Visio, or Pencil. A web-based alternative is app.diagrams.ne. Please ensure that for your final submission all supporting material is compiled into a single document.

Plagiarism

Plagiarism is the presentation of the expressed thought or work of another person as though it is one’s own without properly acknowledging that person. You must not allow other students to copy your work and must take care to safeguard against this happening. More information about the plagiarism policy and procedure for the university can be found at federation.edu.au

Submission

Submit the final document containing your work to Moodle (again, please submit a PDF so that it reproduces the same on the marker’s screen as on your screen).

Feedback

You can expect to receive your final mark and feedback comments within 2 weeks of the due date or the date which you submitted your work – whichever is later. You may be required to attend an interview with the marker; if this is the case, your mark will be withheld until you have attended.

Marking Criteria/Rubric

To Download Click Here > ITECH2000Mobile Development Fundamentals App Design Report.pdf