I think, we should figure out a way to reorganize the file hierarchy of the Android Application. It may get a bit crowded in the one package we have, It may be nice to find a way to organize the classes so there is less clutter.

Summary

There are a few changes I need to make to the master branch, regardless of the fact integration isn't for another two weeks. These changes should be merged into all feature branches. However, some branches will not be affected by these changes, namely data and login. These changes aren't really "major", but they are what I consider to be important. They will also greatly ease the pain of integration come the end of the second sprint. Integrating these into your branches may look messier than they really are, so don't be put off by git's output. You don't have to integrate these changes until Sunday if you don't want to; I will help you out on Sunday if it hasn't been done for your feature's branch yet. I'll close this issue with the specific changes listed after the fixes are integrated. Thanks.

There may be a issue when the user dismisses a notification instead of selecting it. More testing is required to pin point the cause. There may be an option to handle what happens when the user dismisses the notification.

Medications is does not include the functionality of deleting a medication from the file only from the list of medications. The "deleted" medication shows up after being deleted when you exit the list of medications and reenter it. Also the Medications when saved overwrite the file. So the user can't have multiple medications, only one at a time.

There was a crash with the notifications system in which the user would force the service to end when closing the application.This needs to be fixed as soon as possible.

There may be a better, cleaner way to read and write from to a file. Instead of using a map object, we can use a JSON Object as a parameter for the read and write since it is being converted to a JSON Object anyway. There needs to be some research done, to determine if dealing with Map Objects are better or not than JSON Objects. If there is no difference, we are just duplicating something we don't need to duplicate. If there is a change, a large amount of refactoring needs to be done. The sooner this is resolved the better.

This bug occurs when the user first attempts to view the graph demos available from the menu. This is because the Graph Manager is trying to generate data from a data file called "testdata" which has not yet been created on the user's local storage.

• First off, the file name should be changed to something other than "testdata".
• Second, some error checking for first-time graph generation should be made to prevent this error.

Animated graphs are a useful way to display data with touch-based capabilities and update in real time. These are a lot trickier to implement, but I'll try to have them done by Sunday.

The "OK" button on the Registration form had its text changed during integration because of merge conflicts in the strings.xml file. It now displays "Just OK" instead and will need to be switched back to "OK".

There is a bug that there may not be multiple notifications set to go off at the same time. I need to test it more and figure out the issues involved. But the application does something something wrong when notifications are set in the same time. Only one notification is sent, there may be another bug associated with this, but like I said, more testing is required.

The Application does some kind of crash in the medication form when the user attempts to save without entering anything. It reverts back to the Medication list, but it says that HealthMate has stop working. This is something that should not happen, error checking must be done for user input in the medication form.