Purpose:

The purpose of this assessment is to allow us to evaluate progress and give feedback on the development of your final app (Assessment 4). This is conducted during 4 unique weeks from weeks 8– 12 within the allocated lab class. You can choose which 4 of the 5 weeks you are    evaluated for (recognising you may have assessments from other units during this period).     Here “progress” means both the quantity and quality of what you have implemented.

This assessment should demonstrate the following learning outcomes:

-    Analyse mobile interface guidelines and technical constraints to design effective navigation and user interfaces for mobile apps

-    Apply object-oriented design patterns such as Model-View-Controller and Delegation

-    Follow iOS best practices to design, construct and test non-trivial iOS apps with a web service component

Task:

For this assessment, you are required to demonstrate the progress you have achieved on the development of your final mobile app (Assessment 4), which will be based on your designs    from Assessment 1. From the time you receive feedback for Assessment 1, you should be    using your lab class and private study time to develop your final assessment app.

During each lab class from Week 8– 12, you will have the opportunity to demonstrate the    current design and functionality of your app, via an interview with your lab demonstrator. As part of this, they will also review and discuss the underlying code of the app.

This assessment provides you with the opportunity to discuss development progress and receive feedback. You can talk with your demonstrator about any issues that have arisen during development and decide if your project scope needs to be changed.

You are required to employ version control to back up your development history in a private   Monash GitLab repository. This repository must be shared with your demonstrator, providing them maintainer-level access.

For each demonstration, you should present a running app, though it is acceptable for some functionality to be absent or for there to be bugs. While you will still be working on your app  during the Weeks 8– 12 lab class, you need to be ready to give the demo of a working app   when your demonstrator asks. This means you might need to employ the use of Git stashes or branches to be able to show the last working version while you are busy working on the   next addition.

Marking Criteria:

This assessment is worth 16% of the total marks for this unit, with each prototype worth 4%.

Your mark (as a 0.5 increment) will be based on the overall development progress, visual design of the app and the quality of the implemented functionality and code, as per marking criteria below.

Since every student’s app design is different and it makes sense to develop the functionality of different apps in different orders, it is not possible to give a detailed description of expected     weekly development progress, but some example progress for a week of work are outlined     below.

Your project timeline and scope outlined in your specification (Assessment 1) should serve as a guide for the functionality you develop each week, though this should be continually revised in consultation with your demonstrator. You can also discuss any implementation difficulties  you are encountering.

As a guide, you should be spending a minimum of 9 hours a week working on your final assessment from Week 7 onwards. This includes your 3 hours of scheduled lab time (where this assessment happens and where you may do optional lab exercises where these are relevant to your assessment) and 6 hours of private study time.

The scope of the lab exercises plus extension activities should serve as examples of reasonable progress that could be expected in one week.  Some examples of reasonable weekly progress could be:

● Fully implementing 2–3 view controllers and their associated logic and communication.

●   Implemented data persistence layer including implementation of data and/or model classes.