Skip navigation
(Access key: S).
Contact information.
Failure of patients to adhere to their medication regimens is the foremost cause of medication failure. People fail to comply with these regimens for a variety of reasons, ranging from forgetfulness to regimen complexity. The goal of this project is to develop a portable, computer-aided drug dispenser that will accurately and reliably notify a patient when a given medication needs to be taken and subsequently dispense that medication.
A working prototype of the device designed by the team has been constructed. See the final paper and presentation below for details of the design, prototype, and plans for future developments. The team is currently on "hiatus" for semester break, but will continue work on this project beginning in late January.
| Week | Reporting Period Beginning | Activities |
|---|---|---|
| 1 | September 9 | Meet with client to discuss project and introduce new team members. |
| 2 | September 16 | Divide project into distinct parts (i.e. pill packaging, pill dispensing, pill dispenser programming) and assign roles. Then research, brainstorm, and develop design ideas for each part. As always, continuously update the PDS (Product Design Specification). |
| 3 | September 23 | Divide project into distinct parts (i.e. pill packaging, pill dispensing, pill dispenser programming) and assign roles. Then research, brainstorm, and develop design ideas for each part. As always, continuously update the PDS (Product Design Specification). |
| 4 | September 30 | Divide project into distinct parts (i.e. pill packaging, pill dispensing, pill dispenser programming) and assign roles. Then research, brainstorm, and develop design ideas for each part. As always, continuously update the PDS (Product Design Specification). |
| 5 | October 7 | Prepare mid-semester presentation |
| 6 | October 14 | Mid-semester presentations |
| 7 | October 21 | Continue to design and develop a functional prototype. As each portion of the design progresses, continually manage the overall project and verify that each component will satisfy the PDS. Also be sure to perform tests on the prototype. |
| 8 | October 28 | Continue to design and develop a functional prototype. As each portion of the design progresses, continually manage the overall project and verify that each component will satisfy the PDS. Also be sure to perform tests on the prototype. |
| 9 | November 4 | Continue to design and develop a functional prototype. As each portion of the design progresses, continually manage the overall project and verify that each component will satisfy the PDS. Also be sure to perform tests on the prototype. |
| 10 | November 11 | Continue to design and develop a functional prototype. As each portion of the design progresses, continually manage the overall project and verify that each component will satisfy the PDS. Also be sure to perform tests on the prototype. |
| 11 | November 18 | Complete development of final prototype. Combine the individual parts of the project into one functional unit. Also continue to perform tests. |
| 12 | November 25 | Prepare final poster presentation and paper |
| 13 | December 2 | Final poster presentation |
| 14 | December 9 | Final meeting with advisor |
| 15 | December 16 | -------- |
| Midterm Presentation (Oct 17 2003, 820 kb) | |
| Midterm paper (Oct 17 2003, 720 kb) | |
| Final Poster Presentation (Fall 2003) (Dec 11 2003, 948 kb) | |
| Final paper (Fall 2003) (Dec 11 2003, 2704 kb) | |
| Product Design Specifications (PDS) (Dec 11 2003, 25 kb) | |
| User interface requirements document (Dec 11 2003, 17 kb) |