Create the UML class diagram for the complete application. You do not need to show constructors, getters or setters in the methods. You do not need to show private methods or attributes which are for implementation only. This diagram should focus on your model classes. You do not need to model the UI screens, since these were covered in the earlier milestone (UI prototypes).
You should now implement the water availability screen. This screen should display a Map (you can use any api you wish, although google maps is pretty well documented.). The map should have markers at each location that water has been reported. Clicking on the pin should provide information from the water report.
PERSISTENCE IS NOT YET REQUIRED, SO IT IS OK TO HAVE TO ENTER USERS AND REPORTS BEFORE SHOWING THE MAP.
Show that previous functionality still works.
Provide a way to navigate to the water availability screen.
Display a map
Place pins at the locations of each report
Show report details for a pin when it is selected by the user
Class Diagram ..................... 40
Previous functionality still works ................................. 05
Navigation option to show water availability screen .............. 05
Map displays ................. 15
Pins are on map at each report location .............. 10
Selecting a pin shows details of the report .......... 10
Javadocs and code style, Design Discussion ............... 15
Electronic submissions should be submitted in .PDF format.
Total value 40 points
Regular associations have labels … 3
Multiplicity shown ................. 3
Class names singular unless collection … 3
Attribute formats ...................5
Method formats ......................5
Appropriate use of inheritance ...... 3
Class identification appropriate … 10
Collaborations appropriate ..... 8
deductions: double declarations -2