Final Presentation and The Final Report

                        Final Report and Presentation

Here is the link to the final presentation followed by a link to the final presentation.

Final Report:  https://docs.google.com/document/d/1J6HFib_AizdFlfMms35wuAc7D6ebljKYrXHuhOrCWt0/edit

Final Presentation: 

https://docs.google.com/presentation/d/1sLrDZEV_wzowMBobBL1-NIZ3d8t1dglUWJun5sYJh58/edit#slide=id.g11397edf6d_0_6

Final work on Application

                   Some of the final debugging on the Code

Some of the difficulties while coding in android studio were as follows:

1.  Debugging in android studio was quite difficult considering the complexity of the code being made for the application.
2. Technical difficulties were faced by the team on many fronts. Especially hardware issues with the entire teams laptops. We received assistance in overcoming these difficulties with the help of Drexel IRT.
3. Lack of descriptive tutorials for android studio made it difficult to code and debug in Android studio.

These were some of the challenges faced by the team throughout the project.

Video resources

    Video and other Information resources utilized in the project

There are many video resources utilized for this project. These resources were used to code in android studio. Another source of knowledge about android studio were some websites that we also used in order to try and understand the language and in order to code the language.

Videos are an amazing source of information for this project since seeing and coding is much easier than just coding on your own. Here is a link to a video resources that were used in coding the project.

https://youtube.com/watch?v=P3CwlckiLTU

This video was helpful in understanding the set for the http server system on the application that calls on the website drugs.com. Using drugs.com one is able to find and view different types of medications.

Here are some websites used to debug the code. They provide some reference on how to debug certain problems in a JAVA code.

http://stackoverflow.com/questions/19079400/arrayadapter-in-android-to-create-simple-listview

An Explanation of model Application

                   Model- View -Controller for Android 

The model view controller is a system developed in order to easily integrate new changes into the code of the application easily without having to change other parts of the code. The best way to understand the concept or analogy of the model view controller is to analyse the application. We can think of the Model as the application containing data. The Android device can be used to manipulate the model or change the view. This is really helpful especially when we have multiple people editing the code at the same time in Java. Since the interface remains constant throughout the entire duration of the edit, no one needs to change all the variables in case a single variable is changed. It is a highly efficient way of working on an android application not to mention an efficient way for the application to function itself.

Figure 1: Shows how the model view controller works using Java.

Figure 2: Shows a graphical Representation of the model.

References:

The start of the code and the begining of the API System (Application Programming Interface)

The API system is the main data base used in Javascript. This week's concept was to use the API to generate a database system to produce an output showing which slot in the pill case had been used. For Example, If the patient is supposed to take pills on Monday morning then the pill case will light up telling the patient to take his/her pills and once they have taken it and closed that specific slot, the app will send a notification to the caretaker stating the day, date, time and slot that was opened and closed. This will provide the caretaker with information as to when the patient took their pills. And which pills they took.