Difference between revisions of "F24: Tilt Maze"
Proj user4 (talk | contribs) (Created page with "F24: Tilt Maze Contents 1 Grading Criteria 2 Project Title 3 Abstract 4 Objectives & Introduction 4.1 Team Members & Responsibilities 5 Schedule 6 Parts List & Cost 7 Design &...") |
Proj user4 (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | === Grading Criteria === | |
| − | + | <font color="green"> | |
| − | + | * 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. | |
| − | + | </font> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | == Project Title == | |
| − | + | Tilt Maze | |
| − | + | ||
| − | + | == Abstract == | |
| − | + | Parking Frenzy is car parking video game. The player will be able to move the car in right or left direction, the road itself will be descending towards the car and will also consist of obstacles such as other vehicles. The road will have lanes through which the car must navigate to ultimately be able to slot itself into the right parking spot alongside the road. The parking spots will be randomly generated along the edge of the LED matrix and the player must navigate the car into the spot at the right time or else it will result in a crash. The difficulty of the game will increase as the player reaches a certain amount of points. The difficulty will increase in terms of the speed of the car and the number of obstacles. The final score of the player will be displayed at the end of every game. a speaker attached to the board will generate the game sounds. | |
| − | + | ||
| − | + | == 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 === | |
| − | + | * Shreya Belide | |
| + | ** | ||
| + | * Jyoshna Mallineni | ||
| + | ** | ||
| + | * Pavan Charith | ||
| + | ** | ||
| + | |||
| + | == Schedule == | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | ! scope="col"| Week# | ||
| + | ! scope="col"| Start Date | ||
| + | ! scope="col"| End Date | ||
| + | ! scope="col"| Task | ||
| + | ! scope="col"| Status | ||
| + | |- | ||
| + | ! scope="row"| 1 | ||
| + | | | ||
| + | * | ||
| + | | | ||
| + | * | ||
| + | | | ||
| + | * | ||
| + | | | ||
| + | * | ||
| + | |- | ||
| + | ! | ||
| + | | | ||
| + | * | ||
| + | | | ||
| + | * | ||
| + | | | ||
| − | + | * | |
| − | + | * | |
| + | |- | ||
| + | ! | ||
| + | | | ||
| + | * | ||
| − | + | | | |
| − | |||
| − | + | <HR> | |
| − | + | <BR/> | |
| − | |||
| − | |||
| − | |||
| − | Parts List & Cost | + | == Parts List & Cost == |
| − | Give a simple list of the cost of your project broken down by components. Do not write long stories here. | + | Give a simple list of the cost of your project broken down by components. Do not write long stories here. |
| − | Design & Implementation | + | == 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. | + | 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 | + | === Hardware Design === |
| − | Discuss your hardware design here. Show detailed schematics, and the interface here. | + | Discuss your hardware design here. Show detailed schematics, and the interface here. |
| − | Hardware Interface | + | === 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. | + | 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 | + | === 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. | + | 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 | + | === 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. | + | 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 | + | == 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. | + | 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: | Include sub-sections that list out a problem and solution, such as: | ||
| − | <Bug/issue name> | + | === <Bug/issue name> === |
Discuss the issue and resolution. | Discuss the issue and resolution. | ||
| − | Conclusion | + | == 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? | + | 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 | + | === Project Video === |
Upload a video of your project and post the link here. | Upload a video of your project and post the link here. | ||
| − | Project Source Code | + | === Project Source Code === |
| − | Sourceforge Source Code Link | + | * [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link] |
| − | References | + | |
| − | Acknowledgement | + | == References == |
| + | === Acknowledgement === | ||
Any acknowledgement that you may wish to provide can be included here. | Any acknowledgement that you may wish to provide can be included here. | ||
| − | References Used | + | === References Used === |
List any references used in project. | List any references used in project. | ||
| − | Appendix | + | === Appendix === |
You can list the references you used. | You can list the references you used. | ||
Revision as of 20:56, 1 November 2024
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
Tilt Maze
Abstract
Parking Frenzy is car parking video game. The player will be able to move the car in right or left direction, the road itself will be descending towards the car and will also consist of obstacles such as other vehicles. The road will have lanes through which the car must navigate to ultimately be able to slot itself into the right parking spot alongside the road. The parking spots will be randomly generated along the edge of the LED matrix and the player must navigate the car into the spot at the right time or else it will result in a crash. The difficulty of the game will increase as the player reaches a certain amount of points. The difficulty will increase in terms of the speed of the car and the number of obstacles. The final score of the player will be displayed at the end of every game. a speaker attached to the board will generate the game sounds.
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
- Shreya Belide
- Jyoshna Mallineni
- Pavan Charith
Schedule
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 |
|
|
|
|
|
|
|
| ||
|
|
Parts List & CostGive a simple list of the cost of your project broken down by components. Do not write long stories here. Design & ImplementationThe design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation. Hardware DesignDiscuss your hardware design here. Show detailed schematics, and the interface here. Hardware InterfaceIn 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 DesignShow 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. ImplementationThis 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 ChallengesDescribe 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: <Bug/issue name>Discuss the issue and resolution. ConclusionConclude 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 VideoUpload a video of your project and post the link here. Project Source CodeReferencesAcknowledgementAny acknowledgement that you may wish to provide can be included here. References UsedList any references used in project. AppendixYou can list the references you used. |
