Difference between revisions of "F18: Two Zero Four Eight"
Proj user16 (talk | contribs) (→Schedule) |
Proj user16 (talk | contribs) (→Schedule) |
||
| Line 85: | Line 85: | ||
| 10/30/2018 | | 10/30/2018 | ||
| | | | ||
| − | * | + | * Testing Joystick for up, down, left and right movements |
| − | + | * Begin working on implementation of game strategy | |
| − | * | ||
| | | | ||
* | * | ||
| − | |||
* | * | ||
| | | | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| 11/06/18 | | 11/06/18 | ||
| | | | ||
| − | * | + | * Control LED Matrix using input device |
| − | * | + | * Finalize PCB design |
| | | | ||
* | * | ||
* | * | ||
| | | | ||
| − | |||
| − | |||
|- | |- | ||
| − | |||
! scope="row"| 7 | ! scope="row"| 7 | ||
| 11/13/18 | | 11/13/18 | ||
| Line 119: | Line 111: | ||
* | * | ||
| | | | ||
| − | |||
| − | |||
|- | |- | ||
| Line 126: | Line 116: | ||
| 11/20/18 | | 11/20/18 | ||
| | | | ||
| − | * | + | * Assembling components and testing |
| − | * | + | * Testing and debugging game |
| − | |||
| | | | ||
* | * | ||
| − | |||
* | * | ||
| | | | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| − | |||
! scope="row"| 9 | ! scope="row"| 9 | ||
| 11/27/18 | | 11/27/18 | ||
| | | | ||
| − | * Final | + | * Final Testing and debugging |
| − | * | + | * Finalize project demo, presentation and wiki report |
| | | | ||
* | * | ||
* | * | ||
| | | | ||
| − | + | |- | |
| − | + | ! scope="row"| 10 | |
| + | | 12/03/18 | ||
| + | | | ||
| + | * Ultimate deadline for completion of project | ||
| + | | | ||
| + | * | ||
| + | | | ||
|- | |- | ||
Revision as of 00:03, 28 October 2018
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
Flappy bird is a fun and intuitive single player game that lays focus on the players ability to avoid the obstacles and clear the maximum number of obstacles in order to beat the highest score. The flappy bird continues to traverse the environment so long as the player is able to avoid the obstacles by jumping over them with the help of the input taken from the push button switch connected externally. At the beginning of the game, the player is acknowledged of the controls, rules as well as the highest score that they have to beat. Once the Bird is unable to beat the last obstacle, the game is concluded and the score for that session is displayed.
Objectives & Introduction
Team Members & Responsibilities
- Deepak Shivani
- Navyashree Chandraiah
- Sai Kiran Duggineni
- Shrusti Shashidhar
- Vishal Govindraddi Yarabandi
Schedule
| Week# | Start Date | Task | Status | Completion Date |
|---|---|---|---|---|
| 1 | 09/18 |
|
|
09/25 |
| 2 | 10/09 |
|
|
10/16
10/16 |
| 3 | 10/16/2018 |
|
|
10/20
10/23 |
| 4 | 10/23/2018 |
|
|
|
| 5 | 10/30/2018 |
|
|
|
| 6 | 11/06/18 |
|
|
|
| 7 | 11/13/18 |
|
|
|
| 8 | 11/20/18 |
|
|
|
| 9 | 11/27/18 |
|
|
|
| 10 | 12/03/18 |
|
|
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:
<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.
