MAD S1 2019 ASSIGNMENT 1 MAD S1 2019 ASSIGNMENT 1 Criteria Ratings Pts This criterion is linked to a
MAD S1 2019 ASSIGNMENT 1
MAD S1 2019 ASSIGNMENT 1
Criteria
Ratings
Pts
This criterion is linked to a learning outcomeMovie Events Add/Remove an Event.
1.0 pts
This criterion is linked to a learning outcomeAdd Movie Details Movies are populated with all necessary fields (e.g. Title, Year, Poster). Images correctly displayed. Separate activity/screen.
1.5 pts
This criterion is linked to a learning outcomeEditing All data can be edited for both events and the associated movie. Movies are clearly linked to a specific event.
1.5 pts
This criterion is linked to a learning outcomeContacts User can add/remove contacts to an event. Selected from the system address book.
1.5 pts
This criterion is linked to a learning outcomeList View Display a scrollable list of Events. List sorted by date and time. Date handling is implemented and formatted appropriately (Date/TimePicker ok here).
2.0 pts
This criterion is linked to a learning outcomeCustom Calendar (Month or Week View) Week view allows scrolling or mechanism for displaying multiple events. Month view handles changing month with correct day/date layout. Custom layout used, no hard coding, prominent bugs or limited functionality.
2.5 pts
This criterion is linked to a learning outcomeUsability of App Intuitive workflow (users know how to use the App easily), Appropriate use of UI Elements, Meaningful Feedback (toasts, alerts etc.)., Text should be readable/appropriate font size
2.0 pts
This criterion is linked to a learning outcomeOverall Design and MVC Separate packages for model, view and controller. Only business logic in the model. Only presentation logic in the views. Listeners are separate from the Android Activities (i.e. in the controllers or small anonymous inner classes delegate to controllers). Controllers are light – delegate to model/view/service. Clear (to read) separation of MVC layers.
3.0 pts
This criterion is linked to a learning outcomeModel Design Models the problem domain using principles of software engineering. E.g. Encapsulation, Information hiding, Single Responsibility etc. Model is Android independent.
2.0 pts
This criterion is linked to a learning outcomeCode Quality Class/method names are meaningful yet succinct. No code duplication. High cohesion and low coupling. Clear separation of concerns. Follows code quality appendix from assignment specification.
2.0 pts
This criterion is linked to a learning outcomeAndroid Conventions Use of value resources: string.xml, dimensions.xml, colors.xml. Use of Android components: Adapters, Views, Contexts etc.
1.0 pts

