Difference between revisions of "F20: Bubble Shooter"
Proj user7 (talk | contribs) |
Proj user7 (talk | contribs) (→Technical Responsibilities) |
||
| Line 20: | Line 20: | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
* Game Logic Development | * Game Logic Development | ||
| + | | Hisaam Hashim | ||
| | | | ||
|- | |- | ||
| Line 28: | Line 29: | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
* LED Display Driver | * LED Display Driver | ||
| − | | | + | | Amiraj Nigam, Anirudh Ashrit |
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
* Graphics Driver | * Graphics Driver | ||
| − | | | + | | Amiraj Nigam, Anirudh Ashrit |
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
| Line 39: | Line 40: | ||
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
| − | * Mp3 Decoder | + | * Mp3 Decoder Driver |
| − | | | + | | Akshat Bhutiani |
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
| Line 51: | Line 52: | ||
|- | |- | ||
|} | |} | ||
| − | |||
== Schedule == | == Schedule == | ||
Revision as of 01:15, 11 November 2020
Contents
Abstract
Bubble shooter is an arcade game that has bubbles or balls present on the screen. The bubbles are of different colors and the goal is to clear them by forming a group of bubbles (3 or more) of the same color. Points are earned upon clearing the bubbles and increases with the number of bubbles cleared in a single shot. The player wins upon clearing the screen and loses when the bubbles touch the bottom of the screen.
Objectives & Introduction
Show a 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
Technical Responsibilities
| Administrative Roles | ||||
|---|---|---|---|---|
|
Hisaam Hashim | |||
|
||||
|
Amiraj Nigam, Anirudh Ashrit | |||
|
Amiraj Nigam, Anirudh Ashrit | |||
|
||||
|
Akshat Bhutiani | |||
|
||||
|
||||
Schedule
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 |
|
|
|
|
| 2 |
|
|
|
|
| 3 |
|
|
|
|
| 4 |
|
|
|
|
| 5 |
|
|
|
|
| 6 |
|
|
|
|
| 7 |
|
|
|
|
| 8 |
|
|
|
|
| 9 |
|
|
|
|
| 10 |
|
|
|
|
Bill Of Materials
| Item# | Part Description | Part Model & Vendor | Quantity | Cost |
|---|---|---|---|---|
| 1 | Microcontroller Boards | SJ2 Boards (Purchased from Preet Kang) | 1 | $50.00 |
| 2 | LED Matrix Display | RGB LED Matrix Panel - 32X64 | 1 | $55.00 |
| 3 | Audio decoder Breakout Board | MP3 PLayer Shield | 1 | $26.95 |
| 4 | Analog 2-axis Thumb Joystick | Analog 2-axis Joystick | 1 | $10.36 |
| 5 | Power Supply | 5V/3A Power Supply | 1 | $8.99 |
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 advice would you give yourself or someone else if your project can be 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 learned 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 acknowledgment that you may wish to provide can be included here.
References Used
List any references used in the project.
Appendix
You can list the references you used.
