ITECH2000 Assignment 2: App Design Task

Looking for ITECH2000 Mobile Development Fundamentals Assignment 2 Answers? Assignmenthelpaus.com is proud to offer online assignment help to the students of Australia, UK and USA. With the strength of MBA and PhD expert, Assignmenthelpaus.com pledges to help students to get through any troublesome situation by providing them assistance in assignment writing, essay and dissertation writing.

Assessment Details

You need to develop some screen designs, and storyboards, and sample inputs for an app. You get to decide the particular purpose of the app.

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

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.

The only restrictions on what you can choose are as follows:

The app must allow the user to enter some information (several fields/items) about something where only some information is known initially;
The app must allow the user to later update or add further information about things which were previously entered into the app;
The app must allow the user to do something regarding information that has been previously entered. For example, perhaps the user can select some of the data (e.g. particular records, or particular fields) with which some further task will be done (e.g. they have previously entered details about people, and so later are able to select some of them for doing something with);
The app must have at least 3 different functionalities (possibly more), but do not plan for more than 6 main functionalities that can be accomplished using the app. The preceding 3 dot-points would give you at least 2 functionalities (it depends whether the ‘add’ is for completely other information than the initial information);
The scenario cannot be anything related to a mobile diary (you cannot take assignment 1 as the basis of assignment 2), or to any scenario given in a lab task this semester (including the week 9 lab).

Some examples of scenarios that have been chosen in the past (you may use these topics but you are encouraged to come up with your own scenario) include:

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 to allow beef farmers to keep track of their cattle in terms of their health, weight gains, medicines given, and allocation to paddocks, over time, and alerting the farmer that it may be time to check up on particular animals.
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 scaled-down version).
An app for school children visiting the zoo, to compete in small groups, in trying to be the first group to collect photos of specific animals from various places around the zoo.

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 earlier. It should require at most one A4 page to describe the scenario completely.

During the week 9 lab class, your tutor will check your proposed scenario and give brief verbal feedback as to whether it is suitable, or else suggest to you some alterations to consider adopting.

Task 2 – Use Case Diagram

Draw a use case diagram, similar to the one in the week 8 study materials, to summarise the functionality that the app will offer to the user.

Task 3 – Storyboards

Develop storyboards for 3 distinct functionalities, showing success sequences. (You may submit additional storyboards if you )
Show at least one failure or abort sequence for any of the 3 functionalities that were chosen for a success sequence. In developing the storyboards, pay attention to the following:
- Be sure to explain for each screenshot in a sequence, what the screen is showing to us (in terms of where it fits in the sequence), and to indicate what is it that the user does to get to the next screenshot.
- Number each screenshot to clearly indicate the sequence.

Task 4 – Sample Inputs / Test Data

For at least 3 distinct functionalities, give an explanation of:

Two sets of sample inputs that the user might give for the functionality (that is the single inputs for each of two separate uses of those functionalities), if it is an input-oriented functionality.
Sample outputs or similar, that make use of each of the two sets of inputs, if it is an output-oriented functionality.

You must have at least one input-oriented and one output-oriented functionality (i.e. you cannot choose to do only input- oriented functions, without any output-oriented ones).

Thus if one functionality is the inputting of initial data, provide examples of the initial data. If another functionality depends on previously entered data to produce some new data or some output, utilise the data that was provided as initial data (i.e. assume it is the only data in the app when the output functionality is performed).

You don’t have to describe things too formally, just describe roughly what would be expected as output, for some sort of inputs.

Additional Instructions

Prepare a document in a word processor (e.g. Microsoft Word), and convert to a PDF file for submitting.

You may hand-draw diagrams, and scan these for inclusion into the document you submit, or you may use software. Various software possibilities exist: Microsoft Visio, or Pencil, are suggestions. However, please ensure that for your final submission all material is compiled into a single document.

You will be expected to be able to show your progress to your tutor in the class of week 10 or 11 (your tutor will confirm this in the week 9 class).

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 http://federation.edu.au/students/learning-and-study/online-help-with/plagiarism.

Submission

Submit the final document containing your work to Moodle (preferably a PDF so that it reproduces exactly the same on 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 on which you submitted your work, whichever is later. If you are required to attend an interview with the marker, your mark will be withheld until you have attended.

Marking Criteria/Rubric

Requirement	Marks	Awarded
Task 1:
Scenario Context has been adequately described, and at least 3 functionalities have	2
been adequately described
Scenario and functionalities chosen are appropriate for the assignment	1
Task 2 – Use Case Diagram
The use case diagram shows appropriate things as use cases, on the basis of what you	2
submitted for task 1.
Notations are correct for: use case, user, connections	0.5
Task 3 – Storyboards (General remarks) Each of the storyboards will be considered in a similar way to each other. Each has 2 marks for whether they show enough detail such as the types of input and output components chosen for the screens, and whether the snapshots over time give a clear sense of what the user will see/experience if using the app for that functionality.
Task 3a – Storyboard for Functionality 1 The storyboard sequence is complete and appropriate in showing the stages during the functionality, including the accompanying description of stages	2

Task 3b – Storyboard for Functionality 2 The storyboard sequence is complete and appropriate in showing the stages during the functionality, including the accompanying description of stages.	2
Task 3c – Storyboard for Functionality 3 The storyboard sequence is complete and appropriate in showing the stages during the functionality, including the accompanying description of stages.	2
Task 3d – Storyboard for Failure Sequence The storyboard sequence is complete and appropriate in showing the stages during the functionality, including the accompanying description of stages, and in showing commonality with the corresponding success sequence.	1
Task 3 overall: Storyboards are legible (clear to read)	0.5
Task 4 – Sample of Input Data and Expected Outputs Adequate provision of at least 2 sets of input is given for selected input-oriented functionalities, and the expected output for output-oriented functionalities that utilise that data is also given.	2
TOTAL:	15 marks
Feedback:

Reference ID: #getanswers2001262