Diabetes and better management when it comes to using mobile applications for self management

The document should include:
1) A brief introduction in which you discuss diabetes and the use of mobile application when it comes to the betterment of self management in making appointments and coaching, motivation (why), and specific objectives. It is also helpful to include a short paragraph or a few sentences that describe the layout of the document. What are the goals of interaction design, and how may they apply to your problem?
2) A short literature review in which relevant articles and issues are critically examined. Keep in mind that you are building an argument, not just discussing articles. You also want to situate your research within a broader context (e.g., clinical decision making, mobile health, clinical workflow, etc.).
3) Understanding the problem space: Characterize the problems or challenges with an existing system. What is currently the user experience or the product, why a change is needed, and how this change will improve the user experience. What are the opportunities for innovation or change?
4) Describe the user population (e.g., nurse, respiratory therapist, skill level, age). What makes them unique and what are their limitations?
5) Develop an approach to user-centered design. Characterize one or more (hypothetical) studies that you would like to do (e.g., interviews, participatory design, naturalistic observation). Please provide details about what you might do it and what you expect to learn. For example, if you plan to do interviews, what sort of questions are appropriate. Please note that this is to help you contextualize the work. You are not expected to collect data.
6) Conceptual model provides a working strategy and framework of general concepts and their interrelations. Address the following questions:
What will the users be doing when carrying out their tasks?
How will the system support these?
What kind of interface metaphor, if any, will be appropriate? (optional)
What kinds of interaction modes and styles to use?
What platform(s) are best suited to support the interaction.
The first two questions above are the most important ones.
7) Conduct a brief requirements analysis, which includes understanding characterizing the target users and their capabilities; how a new product might support users in their daily lives; users’ current tasks, goals, and contexts; constraints on the product’s performance; and so on. This understanding forms the basis of the product’s requirements and underpins design and construction. Please note that the requirements, conceptual model, and problem space are intertwined. Requirements are geared to define the needs with a greater level of precision.
8) Develop a modest prototype that embodies some of the above concepts/issues.
Start with a mockup low-fidelity prototype that may be a hand drawing, use post-it notes, or any sort of sketch. If you are more artistically inclined, you can paint an illustration. But the goal is to provide you guidance in creating a prototype.
9) Conduct a heuristic evaluation involving 2-3 people to evaluate your prototype. These people can be group members or, even better other students in the class who are not part of your group. Identify the problems with your system and suggest potential solutions to fix them
10) Write a discussion that summarizes all of the above and renders conclusions about the problem and the means to solve it. Discuss how a future system may be realized and what it may look like. For the latter, imagine that you have significant expertise and a nearly unlimited budget.
The Bottom line: The paper will be judged by the soundness of the rationale, conceptual framework, and the quality of the analysis. It is more important to ask interesting questions, test them in a sound way, as realized in the prototype, and provide informative analysis. The write up should suggest the possibility of further research. The recommended length is 25 pages double spaced, Times New Roman 12 font, one inch margins on all sides)but these are just guideposts.