Features

1. You app meets the software development best-practice of being an MVP (Minimum Viable Product).
2. All features promised in Features document are delivered.
3. Your UI navigation is easy to follow and user friendly. Please keep in mind that perception on this item is relative, so do your best and adjust to any feedback you are given before the final product is released (submitted in Canvas).
4. Future enhancements are clearly identified.
5. Your application flow (through wireframes) is clear and matches your ending implementation.
6. App uses at least 10 Android technologies, which are clearly identified in your Project Summary.
7. App demonstrates localization and internationalization in at least one part of the UI (and please identify it in your Project Summary).
   

1. All levels of design are documented and include:
   1. Overall Architecture - this should include block-diagrams of major modules, identify client/server modules, ...
   2. High-level App Design - this should include identfying main interfaces, 3rd-party APIs, services, content providers, ...
   3. Design Patterns - make sure to explain where and why you use them; identify which you coded versus those that your code uses.
   4. Low-level Design - this should include you data Schema, UML class design, ...
2. Diagrams are use wherever appropriate.
3. Documented design is appropriate and easy to understand given your audience (colleagues in the course).

1. Your submission works with API 19 or higher (Build SDK, Minimum Required SDK and AVD).
2. Provide resources to support at least two resolutions.
3. All proposed features in Features documents have been implemented.
4. Code is readable and easy to follow.
5. Coding follows Java coding standards.
6. Code is well documented and clearly identifies which team members worked on which parts.
   
7. Documented design is implemented in code and easy to understand.
8. Project is error and warnings free.
9. Properties values are declarative versus hard coded where-ever required (as guided by the compilation requirements).
10. Adequate exception handling to capture hangs, warnings or errors.
11. Code repetition is avoided.
12. Build classes/objects with adequate packaging.

1. Document Test cases for testing functional, boundary and negative/error tests.
2. Test cases for each documented and implemented use case.
3. Show test results for each test case. (Screen shots and comments would suffice).

Demo or Die! Final presentations will be made during Finals Week. All team members must participate.