Difference between revisions of "F16: Kasper"
Proj user18 (talk | contribs) (→Schedule) |
Proj user18 (talk | contribs) (Added Team Schedule which was deleted during other changes) |
||
Line 9: | Line 9: | ||
Objective of this project is to create a self driving car | Objective of this project is to create a self driving car | ||
− | + | == Team Members & Responsibilities == | |
We have used five controllers | We have used five controllers | ||
Line 27: | Line 27: | ||
**Bharat Khanna | **Bharat Khanna | ||
**Shantanu Vasishtha | **Shantanu Vasishtha | ||
+ | |||
+ | |||
+ | == Team Schedule == | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! scope="col"| Sl No. | ||
+ | ! scope="col"| Start Date | ||
+ | ! scope="col"| End Date | ||
+ | ! scope="col"| Task | ||
+ | ! scope="col"| Status | ||
+ | ! scope="col"| Actual Completion Date | ||
+ | |- | ||
+ | ! scope="row"| 1 | ||
+ | | 09/20/2016 | ||
+ | | 09/27/2016 | ||
+ | | | ||
+ | * Divide the overall project into modules. | ||
+ | * Assign the modules to a team of two. | ||
+ | | Completed | ||
+ | | 09/27/2016 | ||
+ | |- | ||
+ | ! scope="row"| 2 | ||
+ | | 09/28/2016 | ||
+ | | 10/04/2016 | ||
+ | | | ||
+ | * Study previous reports to get an overall understanding of the project | ||
+ | * Plan each task meticulously. | ||
+ | * Order components and review them for hardware errors | ||
+ | * Understand the placement of modules in the car | ||
+ | | Completed | ||
+ | | 10/04/2016 | ||
+ | |- | ||
+ | ! scope="row"| 3 | ||
+ | | 10/05/2016 | ||
+ | | 10/11/2016 | ||
+ | | | ||
+ | * Understand the hardware design and requirements of each task. | ||
+ | | In Progress | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 4 | ||
+ | | 10/12/2016 | ||
+ | | 10/18/2016 | ||
+ | | | ||
+ | * Design the overall architecture based on the protocol for communication, power requirement and the number of special purpose GPIOs required | ||
+ | * Consider CAN message IDs, data size and format proposals for all CAN messages on the bus | ||
+ | | Upcoming Task | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 5 | ||
+ | | 10/19/2016 | ||
+ | | 10/25/2016 | ||
+ | | | ||
+ | * Plan methods for testing individual modules based on communication protocols used. | ||
+ | | Upcoming Task | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 6 | ||
+ | | 10/26/2016 | ||
+ | | 11/08/2016 | ||
+ | | | ||
+ | * Integrate Sensor modules with SJone board | ||
+ | * Develop obstacle avoidance algorithm with sensor integration | ||
+ | * Develop Master for CAN communication | ||
+ | * Integrate Mobile app with the Controller | ||
+ | | Upcoming Task | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 7 | ||
+ | | 11/09/2016 | ||
+ | | 12/20/2016 | ||
+ | | | ||
+ | * Test individual sensor with Master controller using CAN communication | ||
+ | | Upcoming Task | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 8 | ||
+ | | 11/21/2016 | ||
+ | | 12/05/2016 | ||
+ | | | ||
+ | * Integrate and test extensively after connecting all sensors to the controller | ||
+ | | Upcoming Task | ||
+ | | | ||
+ | |} | ||
+ | |||
== Parts List & Cost == | == Parts List & Cost == | ||
Line 92: | Line 177: | ||
| 10/5/2016 | | 10/5/2016 | ||
| 10/11/2016 | | 10/11/2016 | ||
− | | Research and order the sensors to be used in the project | + | | |
+ | * Research and order the sensors to be used in the project | ||
| Completed | | Completed | ||
| 10/9/2016 | | 10/9/2016 | ||
Line 109: | Line 195: | ||
| 10/19/2016 | | 10/19/2016 | ||
| 10/25/2016 | | 10/25/2016 | ||
− | | Wire the sensors and check the sensors with the sample code. | + | | |
+ | * Wire the sensors and check the sensors with the sample code. | ||
|Upcoming Task | |Upcoming Task | ||
| | | | ||
Line 116: | Line 203: | ||
| 10/26/2016 | | 10/26/2016 | ||
| 11/1/2016 | | 11/1/2016 | ||
− | | Prepare the code sketch for sensor module. | + | | |
+ | * Prepare the code sketch for sensor module. | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 123: | Line 211: | ||
| 11/2/2016 | | 11/2/2016 | ||
| 11/08/2016 | | 11/08/2016 | ||
− | | Interface ADC ultrasonic sensor to SJOne board, read sensor values and filter the readings. | + | | |
+ | * Interface ADC ultrasonic sensor to SJOne board, read sensor values and filter the readings. | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 139: | Line 228: | ||
| 11/16/2016 | | 11/16/2016 | ||
| 11/22/2016 | | 11/22/2016 | ||
− | | Prepare sensor values to be sent over CAN bus and testing out the correctness of sensor can messages | + | | |
+ | * Prepare sensor values to be sent over CAN bus and testing out the correctness of sensor can messages | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 149: | Line 239: | ||
* Optimize the code. | * Optimize the code. | ||
* Collaborate with other teams and updating the code as needed. | * Collaborate with other teams and updating the code as needed. | ||
+ | | Upcoming Task | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 9 | ||
+ | | 11/30/2016 | ||
+ | | 11/05/2016 | ||
+ | | | ||
+ | * Test and debug | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 192: | Line 290: | ||
| 09/27/2016 | | 09/27/2016 | ||
| 10/04/2016 | | 10/04/2016 | ||
− | | Finalize project and team schedule and update project wiki | + | | |
+ | * Finalize project and team schedule and update project wiki | ||
| Completed | | Completed | ||
| 10/04/2016 | | 10/04/2016 | ||
Line 199: | Line 298: | ||
| 10/04/2016 | | 10/04/2016 | ||
| 10/11/2016 | | 10/11/2016 | ||
− | | LCD module selection and purchase | + | | |
+ | * LCD module selection and purchase | ||
| Completed | | Completed | ||
| 10/07/2016 | | 10/07/2016 | ||
Line 206: | Line 306: | ||
| 10/11/2016 | | 10/11/2016 | ||
| 10/18/2016 | | 10/18/2016 | ||
− | |Understanding LCD data sheets and testing the basic functionality | + | | |
+ | * Understanding LCD data sheets and testing the basic functionality | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 213: | Line 314: | ||
| 10/18/2016 | | 10/18/2016 | ||
| 10/25/2016 | | 10/25/2016 | ||
− | |Interfacing motors and test control of motors from the SJOne board | + | | |
+ | * Interfacing motors and test control of motors from the SJOne board | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 220: | Line 322: | ||
| 10/25/2016 | | 10/25/2016 | ||
| 11/1/2016 | | 11/1/2016 | ||
− | | Integrate LCD, Power, Motors together and control using SJOne board | + | | |
+ | * Integrate LCD, Power, Motors together and control using SJOne board | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 227: | Line 330: | ||
| 11/1/2016 | | 11/1/2016 | ||
| 11/15/2016 | | 11/15/2016 | ||
− | | Discuss with other teams to get simulated inputs from GPS and sensor module and test car control with those inputs. (Testing of obstacle avoidance) | + | | |
+ | * Discuss with other teams to get simulated inputs from GPS and sensor module and test car control with those inputs. (Testing of obstacle avoidance) | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 234: | Line 338: | ||
| 11/15/2016 | | 11/15/2016 | ||
| 11/28/2016 | | 11/28/2016 | ||
− | | Collaborate with other teams to establish CAN communication between all the modules | + | | |
+ | * Collaborate with other teams to establish CAN communication between all the modules | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 240: | Line 345: | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| 11/28/2016 | | 11/28/2016 | ||
− | | 12/ | + | | 12/05/2016 |
− | | Product testing and trial runs | + | | |
+ | * Product testing and trial runs | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 285: | Line 391: | ||
| 09/28/2016 | | 09/28/2016 | ||
| 10/4/2016 | | 10/4/2016 | ||
− | |GPS and Compass module selection and purchase | + | | |
+ | * GPS and Compass module selection and purchase | ||
| In Progress | | In Progress | ||
| | | | ||
Line 292: | Line 399: | ||
| 10/5/2016 | | 10/5/2016 | ||
| 10/11/2016 | | 10/11/2016 | ||
− | |Pin Identification and connection diagram | + | | |
+ | * Pin Identification and connection diagram | ||
|In Progress | |In Progress | ||
| | | | ||
Line 299: | Line 407: | ||
| 10/12/2016 | | 10/12/2016 | ||
| 10/18/2016 | | 10/18/2016 | ||
− | |GPS Firmware Development and individual testing | + | | |
+ | * GPS Firmware Development and individual testing | ||
|Upcoming Task | |Upcoming Task | ||
| | | | ||
Line 306: | Line 415: | ||
| 10/19/2016 | | 10/19/2016 | ||
| 10/25/2016 | | 10/25/2016 | ||
− | | Compass Firmware Development and individual testing | + | | |
+ | * Compass Firmware Development and individual testing | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 313: | Line 423: | ||
| 10/26/2016 | | 10/26/2016 | ||
| 11/01/2016 | | 11/01/2016 | ||
− | |Calibrating GPS and Compass Module | + | | |
+ | * Calibrating GPS and Compass Module | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 320: | Line 431: | ||
| 11/02/2016 | | 11/02/2016 | ||
| 11/08/2016 | | 11/08/2016 | ||
− | | Communication with Master using CAN | + | | |
+ | * Communication with Master using CAN | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 326: | Line 438: | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| 11/09/2016 | | 11/09/2016 | ||
− | | | + | | 12/05/2016 |
− | | Testing and debugging with whole system | + | | |
+ | * Testing and debugging with whole system | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 411: | Line 524: | ||
| 10/19/2016 | | 10/19/2016 | ||
| 10/25/2016 | | 10/25/2016 | ||
− | | Work on Bluetooth firmware development to integrate with SJ one board. | + | | |
+ | * Work on Bluetooth firmware development to integrate with SJ one board. | ||
| Upcoming Task | | Upcoming Task | ||
| | | | ||
Line 419: | Line 533: | ||
| 11/08/2016 | | 11/08/2016 | ||
| | | | ||
− | * | + | *Develop basic Android application to work with the Bluetooth module. |
*Test the communication between SJ one board and Android application over Bluetooth protocol. | *Test the communication between SJ one board and Android application over Bluetooth protocol. | ||
<!-- Integrating Sensor modules with SJone board--> | <!-- Integrating Sensor modules with SJone board--> | ||
Line 554: | Line 668: | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
| 11/23/2016 | | 11/23/2016 | ||
− | | 11/ | + | | 11/27/2016 |
| | | | ||
* Implement the Navigation algorithm based on the data received from the Geographical controller | * Implement the Navigation algorithm based on the data received from the Geographical controller | ||
Line 561: | Line 675: | ||
|- | |- | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
− | | | + | | 11/28/2016 |
− | | 12/ | + | | 12/05/2016 |
| | | | ||
* Test extensively and debug issues | * Test extensively and debug issues |
Revision as of 20:00, 11 October 2016
Contents
Project Title
Self Driving Car
Abstract
This project implements a self-driving car.
Objectives & Introduction
Objective of this project is to create a self driving car
Team Members & Responsibilities
We have used five controllers
- Sensor Controller
- Shruthi Narayan
- Rimjhim Ghosh
- Motor & I/O Controller
- Prashant Aithal
- Chethan Keshava
- Geographical Controller
- Ankit Gandhi
- Master Controller
- Aajna Karki
- Spoorthi Mysore Shivakumar
- Communication Bridge Controller
- Bharat Khanna
- Shantanu Vasishtha
Team Schedule
Sl No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/20/2016 | 09/27/2016 |
|
Completed | 09/27/2016 |
2 | 09/28/2016 | 10/04/2016 |
|
Completed | 10/04/2016 |
3 | 10/05/2016 | 10/11/2016 |
|
In Progress | |
4 | 10/12/2016 | 10/18/2016 |
|
Upcoming Task | |
5 | 10/19/2016 | 10/25/2016 |
|
Upcoming Task | |
6 | 10/26/2016 | 11/08/2016 |
|
Upcoming Task | |
7 | 11/09/2016 | 12/20/2016 |
|
Upcoming Task | |
8 | 11/21/2016 | 12/05/2016 |
|
Upcoming Task |
Parts List & Cost
Item# | Part Desciption | Vendor | Qty | Cost $ |
---|---|---|---|---|
1 | RC Car | From Preet | 1 | 0 |
2 | SJOne board | Preet | 5 | 80 |
3 | GPS Module | From Preet | 1 | 40 |
4 | Triple Axis Magnetometer (Compass) | Sparkfun | 1 | 15 |
5 | Bluetooth Module | Sparkfun | 1 | 24.95 |
6 | LCD screen | Adafruit | 1 | 24.95 |
Sensor Controller
Team Members & Responsibilities
- Shruthi Narayan
- Rimjhim Ghosh
Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date | |
---|---|---|---|---|---|---|
1 | 10/5/2016 | 10/11/2016 |
|
Completed | 10/9/2016 | |
2 | 10/12/2016 | 10/18/2016 |
|
In Progress | ||
3 | 10/19/2016 | 10/25/2016 |
|
Upcoming Task | ||
4 | 10/26/2016 | 11/1/2016 |
|
Upcoming Task | ||
5 | 11/2/2016 | 11/08/2016 |
|
Upcoming Task | ||
6 | 11/9/2016 | 11/15/2016 |
|
Upcoming Task | ||
7 | 11/16/2016 | 11/22/2016 |
|
Upcoming Task | ||
8 | 11/23/2016 | 11/29/2016 |
|
Upcoming Task | ||
9 | 11/30/2016 | 11/05/2016 |
|
Upcoming Task |
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.
Motor & I/O Controller
Team Members & Responsibilities
- Chethan Keshava
- Prashant Aithal
Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date | |
---|---|---|---|---|---|---|
1 | 09/27/2016 | 10/04/2016 |
|
Completed | 10/04/2016 | |
2 | 10/04/2016 | 10/11/2016 |
|
Completed | 10/07/2016 | |
3 | 10/11/2016 | 10/18/2016 |
|
Upcoming Task | ||
4 | 10/18/2016 | 10/25/2016 |
|
Upcoming Task | ||
5 | 10/25/2016 | 11/1/2016 |
|
Upcoming Task | ||
6 | 11/1/2016 | 11/15/2016 |
|
Upcoming Task | ||
7 | 11/15/2016 | 11/28/2016 |
|
Upcoming Task | ||
8 | 11/28/2016 | 12/05/2016 |
|
Upcoming Task |
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.
Geographical Controller
Team Members & Responsibilities
- Ankit Gandhi
Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/28/2016 | 10/4/2016 |
|
In Progress | |
3 | 10/5/2016 | 10/11/2016 |
|
In Progress | |
4 | 10/12/2016 | 10/18/2016 |
|
Upcoming Task | |
5 | 10/19/2016 | 10/25/2016 |
|
Upcoming Task | |
6 | 10/26/2016 | 11/01/2016 |
|
Upcoming Task | |
7 | 11/02/2016 | 11/08/2016 |
|
Upcoming Task | |
8 | 11/09/2016 | 12/05/2016 |
|
Upcoming Task |
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.
Communication Bridge Controller
Team Members & Responsibilities
- Bharat Khanna
- Shantanu Vashishtha
Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/20/2016 | 09/27/2016 |
|
Completed | 09/27/2016 |
2 | 09/28/2016 | 10/4/2016 |
|
Completed | 10/9/2016 |
3 | 10/5/2016 | 10/11/2016 |
|
In Progress | |
4 | 10/12/2016 | 10/18/2016 |
|
Upcoming Task | |
5 | 10/19/2016 | 10/25/2016 |
|
Upcoming Task | |
6 | 10/26/2016 | 11/08/2016 |
|
Upcoming Task | |
7 | 11/9/2016 | 11/20/2016 |
|
Upcoming Task | |
8 | 11/21/2016 | 12/05/2016 |
|
Upcoming Task |
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.
Master Controller
Team Members & Responsibilities
- Aajna Karki
- Spoorthi Mysore Shivakumar
Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/26/2016 | 10/02/2016 |
|
Completed | 10/02/2016 |
2 | 10/03/2016 | 10/11/2016 |
|
In Progress | |
3 | 10/12/2016 | 10/18/2016 |
|
Upcoming Task | |
4 | 10/19/2016 | 10/25/2016 |
|
Upcoming Task | |
5 | 10/26/2016 | 10/31/2016 |
|
Upcoming Task | |
6 | 11/01/2016 | 11/08/2016 |
|
Upcoming Task | |
7 | 11/9/2016 | 11/17/2016 |
|
Upcoming Task | |
8 | 11/18/2016 | 11/22/2016 |
|
Upcoming Task | |
9 | 11/23/2016 | 11/27/2016 |
|
Upcoming Task | |
10 | 11/28/2016 | 12/05/2016 |
|
Upcoming Task |
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.
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.