Difference between revisions of "S14: Location Tracker"
Proj user5 (talk | contribs) (→Schedule) |
Proj user5 (talk | contribs) (→Schedule) |
||
| Line 44: | Line 44: | ||
*System design | *System design | ||
*Order parts | *Order parts | ||
| − | |Ordered GSM/GPRS | + | | |
| + | *Ordered GSM/GPRS module | ||
| + | *Obtained GPS module from previous project | ||
|- | |- | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
| Line 51: | Line 53: | ||
*Android app UI design | *Android app UI design | ||
| | | | ||
| + | *Decided UI requirements | ||
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| Line 59: | Line 62: | ||
*Test GPS parsing | *Test GPS parsing | ||
| | | | ||
| + | *Begin interfacing GPS and GSM/GPRS modules | ||
|- | |- | ||
! scope="row"| 4 | ! scope="row"| 4 | ||
| Line 66: | Line 70: | ||
*Test sending SMS messages | *Test sending SMS messages | ||
| | | | ||
| + | *GPS data parsing complete | ||
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| Line 72: | Line 77: | ||
*Make Android app recognize and parse SMS message | *Make Android app recognize and parse SMS message | ||
| | | | ||
| + | *SJ One board sends SMS messages | ||
| + | *Begin work on Android app | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| Line 78: | Line 85: | ||
*Integrate Google Map into app | *Integrate Google Map into app | ||
| | | | ||
| + | *Continue trying to get app to send and receive SMS | ||
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| Line 85: | Line 93: | ||
*Testing | *Testing | ||
| | | | ||
| + | *Android app sends and receive SMS messages | ||
| + | *Locations is displayed on map | ||
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
Revision as of 01:45, 25 April 2014
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
Abstract
This section should be a couple lines to describe what your project does.
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
- Arpit Amin
- Caleb Chow
- Cynthia Ho
- Abraham Ruiz
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 | Actual |
|---|---|---|---|
| 1 | 3/6 |
|
|
| 2 | 3/13 |
|
|
| 3 | 3/20 |
|
|
| 4 | 3/27 |
|
|
| 5 | 4/3 |
|
|
| 6 | 4/10 |
|
|
| 7 | 4/17 |
|
|
| 8 | 4/24 |
|
|
| 9 | 5/1 |
|
|
| 10 | 5/8 |
|
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
Send me your zipped source code and I will upload this to SourceForge and link it for you.
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.
