Each student (or teams of two students) will design and implement an example of a pervasive healthcare tool over the course of this semester. The development platform, environment, languages, etc., are up to the student. The scope of the project should be chosen carefully to fit within 12 weeks and proof-of-concept implementations (e.g., a desktop proof-of-concept immplementation of an app or system that would actually be run on a mobile device or a system that simulates some of the sensor readings, etc.). If any specific hardware or software components are needed to complete your project, please talk to the instructor (we do have a budget for various small items, devices, software, sensors, etc., that can be used in these projects).

Project Proposal

Prepare a 1-page document (due 9/9/11; 11pt font or larger; doc/pdf/ps formats only) that describes your proposed project. There are very few constraints or requirements, so that you can be as creative as you want. You can also discuss your project idea with the instructor before the submission due date if you like. The due date (9/9) is also the start of the project, i.e., you are expected to begin working on your project immediately. An important requirement of the project is the periodic submission of progress reports (see information below).
A proposal must include the following components:
  • A descriptive title for the project.
  • The name(s) of the student(s) working on this project.
  • A motivation and problem statement (1-2 paragraphs).
  • A description of the proposed solution/approach (1-2 paragraphs).
  • A list of requirements to complete this project (hardware needs, development environment, programming language, tools, sensors, other devices, etc.).
In your AFS dropbox, make a directory called "project" and put the proposal into this directory. In addition, email your proposal to the instructor, who will provide feedback on your proposal.

Project Design Document

The second required document for the project phase of this course is a design document. A design document is a complete high-level solution to be presented that should be detailed enough so that somebody who already understands the problem could go out and code the project without having to make significant decisions. One of the main purposes of the design document is to make you think about how to implement your project (what will your app look like, how will the user interact, what information needs to be collected and provided, does my app interact with other computers, etc.) before you actually develop the system or code.

The design document should be at most 2 pages of text, but any number of figures, screenshots, etc., are allowed. The content of the design document will differ based on your project idea, but the list below should give you an indicator of what might be appropriate/useful to include in your design document:
  • Details about the platform your project will run on (type of computer, operating system, etc.) and other hardware/software components.
  • Target demographic of your app/system.
  • The different components of your system/app and how they interact (a graph is often the best way to show this). This could be some kind of graph that shows the usage of your project (e.g., how one navigates through the different screens of an app).
  • App/system elements, such as people involved (users), sensors used, information collected or presented on a screen, etc.
  • User interface details such as welcome/splash screens, main app screen, details about controls, settings/help screens, etc.
If your project is an application, you can provide mock-ups of the screens and user interfaces (though not required), including hand drawn mock-ups or generated using tools such as powerpoint etc.

The design document should be put into your dropbox, into the same directory as the proposal (i.e., a subdirectory called "project") and only files with pdf, ps, or doc extensions will be accepted.

Final Report

The final report should be at least 4 pages (11pt font or larger; doc/pdf/ps formats only) and should describe the final outcome of your course project, including screenshots, experimental evaluations, etc., if applicable. If your final document has figures and graphs that go beyond 1 page of the document, all figures and graphs above this limit will add to the page requirement, i.e., if you have 1.5 pages full of figures, your minimum page requirement is 4.5 pages. References if applicable should also be provided, but do not count towards the minimum page count. In the final document, describe the main features of your system or application, any unresolved issues, etc. Put the final document into your dropbox, together with the complete source code of your application. In addition to the final report, provide a README file that describes how to compile and execute your code.