S17: Smart collision alert system

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 collision alert system

Objectives & Introduction

Team Members & Responsibilities

• Abhishek Singh
• Aniket Achyut Bapat
• Bhupendra Naphade
• Jerry John
• Saurabh Ravindra Deshmukh

Schedule

Week	Start Date	End Date	Task	Status	Actual Completion Date
1	3/21	3/25	Requirement analysis and parts ordering	In Progress
2	3/25	3/29	Software pre-analysis to identify common data elements	Plan
3	3/26	4/2	PCB design and ordering	Plan
4	3/26	3/29	Algorithm design	Plan
5	3/30	4/10	Interface the GSM, GPS, Sensor, CAN module with the SJOne board Project report update on wiki	Plan
6	4/11	4/18	Integration of modules and hardware package buildup*	Plan
7	4/19	4/31	Integration testing and bug fix Project report update on wiki	Plan
8	4/26	5/5	Extra feature identification and implementation Project report update on wiki	Plan
9	5/5	5/14	Testing and Debugging Project report update on wiki and final presentation	Plan
10	5/15	5/23	Wiki Report completion and Final Demonstration	Plan

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

• Sourceforge Source Code Link

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.