Difference between revisions of "S17: Smart Health Gear"
Proj user5 (talk | contribs) m (→Abstract) |
Proj user5 (talk | contribs) (→Schedule) |
||
| Line 44: | Line 44: | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
| 3/23 | | 3/23 | ||
| − | | | + | | Work on documenting requirements and BOM |
| In process | | In process | ||
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| − | | 3/ | + | | 3/29 |
| − | | | + | | Initiate procurement of components and start with designing phase. |
| | | | ||
|- | |- | ||
! scope="row"| 4 | ! scope="row"| 4 | ||
| − | | 4/ | + | | 4/4 |
| − | | | + | | Finish design and documentation of the schematic and PCB layout |
| | | | ||
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| − | | 4/ | + | | 4/6 |
| − | | | + | | Design and documentation software architecture for health gear and Android application |
| | | | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| − | | 4/ | + | | 4/12 |
| − | | | + | | Development of software for health gear and application. Documentation of software modules. |
| | | | ||
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| − | | 4/ | + | | 4/17 |
| − | | | + | | Component and PCB testing. Documentation of testing |
| | | | ||
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| 4/24 | | 4/24 | ||
| − | | | + | | Preparation of unit and integration test plan |
| − | | | + | | |
|- | |- | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
| − | | 4/ | + | | 4/28 |
| − | | | + | | Unit testing of modules and updating results |
| | | | ||
|- | |- | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
| − | | 5/ | + | | 5/1 |
| − | | | + | | Bug fixing and re-testing |
| | | | ||
|- | |- | ||
! scope="row"| 11 | ! scope="row"| 11 | ||
| + | | 5/5 | ||
| + | | Integration testing and updating results | ||
| + | | | ||
| + | |- | ||
| + | ! scope="row"| 12 | ||
| + | | 5/7 | ||
| + | | Bug fixing and re-testing | ||
| + | | | ||
| + | |- | ||
| + | ! scope="row"| 13 | ||
| 5/10 | | 5/10 | ||
| − | | | + | | System testing and result documentation |
| + | |- | ||
| + | ! scope="row"| 14 | ||
| + | | 5/12 | ||
| + | | Bug fixing and re-testing | ||
| + | | | ||
| + | |- | ||
| + | ! scope="row"| 15 | ||
| + | | 5/14 | ||
| + | | Completion of project report | ||
| | | | ||
| + | |- | ||
| + | ! scope="row"| 16 | ||
| + | | 5/16 | ||
| + | | Demo preparation | ||
| + | | | ||
| + | |- | ||
| + | ! scope="row"| 16 | ||
| + | | 5/18 | ||
| + | | Ready for demo | ||
| + | | | ||
|} | |} | ||
Revision as of 00:08, 22 March 2017
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Project Title
Smart Health Gear
Abstract
Smart Health Gear is a wearable device will help to monitor various aspects of health like heart rate, foot steps count,blood pressure and body temperature. It will come with a compatible android application which will notify user on completion of daily activities and log all the data from the smart health gear to provide history.
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- Aniket Dali
- Jean Mary
- Manoj Ramesh Rao
- Neha Biradar
- Sushma Macha
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Date | Task | Comments |
|---|---|---|---|
| 1 | 3/2 | Submission of Project Proposals | Completed |
| 2 | 3/23 | Work on documenting requirements and BOM | In process |
| 3 | 3/29 | Initiate procurement of components and start with designing phase. | |
| 4 | 4/4 | Finish design and documentation of the schematic and PCB layout | |
| 5 | 4/6 | Design and documentation software architecture for health gear and Android application | |
| 6 | 4/12 | Development of software for health gear and application. Documentation of software modules. | |
| 7 | 4/17 | Component and PCB testing. Documentation of testing | |
| 8 | 4/24 | Preparation of unit and integration test plan | |
| 9 | 4/28 | Unit testing of modules and updating results | |
| 10 | 5/1 | Bug fixing and re-testing | |
| 11 | 5/5 | Integration testing and updating results | |
| 12 | 5/7 | Bug fixing and re-testing | |
| 13 | 5/10 | System testing and result documentation | |
| 14 | 5/12 | Bug fixing and re-testing | |
| 15 | 5/14 | Completion of project report | |
| 16 | 5/16 | Demo preparation | |
| 16 | 5/18 | Ready for demo |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
