S19: Tech Savy
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
Git Project Link: Tech Savy
Git users
- preet
- iamkash30
- Jain_Vidushi
- vatsalkirit.makani
- prashantgandhi27
- Jay0019
- saumil.shah1
- akshata.kulkarni
- halakv
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
| Team Members | Administrative Roles | Technical Roles |
|---|---|---|
| Aakash Chitroda | Team Lead Finance Manager |
Master Controller (Lead) LCD controller (UI) Sensors Controller |
| Akshata Kulkarni | Gantt Chart - Progress Report | Android CAN Interfacing |
| Halak Vyas | Wiki Report Manager (Lead) | Sensor Controller (Lead) CAN + DBC TX,Rx |
| Jay Parsana | Bluetooth Controller (Lead) Testing And Verification (Lead) | |
| Prashant Gandhi | Component Purchase Manager | Hardware Integration PCB (Lead) Hardware Testing and Validation GPS Controller |
| Saumil Shah | Android(Lead) Bluetooth | |
| Vatsal Makani | Git Repository Manager Bill of Materials Manager |
Motor Controller(Lead), RPM Sensor and Servo Motor Hardware Integration PCB (Co-Lead) Sensor controller |
| Vidushi Jain | Documentation Wiki Report Git Repository Manager |
LCD Controller (Co-Lead) Bridge Communication (Lead) Geographic Controller (Lead) |
Schedule
Show a simple table or figures that show you're 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 | Deadline | Task | Status |
|---|---|---|---|
| 1 | 26 Feb | Create and establish GitLab repository Establish slack |
Complete Complete |
| 2 | 4 March | Look through previous years projects and study it Distribute major roles among team members |
Complete Complete |
| 3 | 12 March | Create a Bill of Materials Select and order an RC car Make Repo on Gitlab for all modules - Follow Naming Convention |
In Progress In Progress In Progress |
| 4 | 19 March | Development of sensors (Halak, Akash) Designing and deciding PCB tool(Prashant, Vatsal) Finalizing GPS module by doing some research (Vidushi) Finalize and order LCD (Akash, Vidushi) Finalize Motor and Order it (Vatsal) Environmental setup of Android (Saumil) |
Complete? Complete? Complete? Complete? Complete? Complete? |
| 5 | 26 March | Discuss and solve power issues Start designing the hardware and layout |
Complete? Complete? |
| 6 | |||
| 7 | |||
| 8 | |||
| 9 |
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 the 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 the exact code, but you may show pseudocode and fragments of code. Keep in mind that you are showing the 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 implementations.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can is started from scratch again? Make a smooth transition to the testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
<Bug/issue name>
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.
