Difference between revisions of "F20: Hungry Snake"

Revision as of 22:00, 7 November 2020

Hungry Snake

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

Yang Chen
- Game Development, Algorithm Development, Code Repo Managment
Yanshen Luo
David Tang
Nuoya Xie

Schedule

TEAM SCHEDULE
Week#	Date	Task	Status
1	10/10/20	Place an order for LED matrix Initial delegation of tasks for different parts of the project Set up splitwise for splitting expenses	Complete Complete Complete
2	10/17/20	Determine initial project content and scope Determine game stages Set up project Git repository	Complete Complete Complete
3	10/24/20	Determine project software architecture Come up with a more detailed spec of the game Plan out how to distribute tasks for software game components Specify smaller code modules needed and start programming	Complete Complete Complete Complete
4	10/31/20	Start developing prototype of game logic for various games screens Start creating LED matrix driver Start creating controller driver	Complete Complete Complete
5	11/7/20	Display letters in LED matrix Detect joystick and button state from controller Develop prototype for snake movement logic and border detection/collision	Complete Complete Complete
6	11/14/20	Start design of interfacing board between LPC and other components of the system Testing LED matrix and controller driver Ability to print game state on console for debugging purposes Initialize game state with multiple sprites Determine feasibility of MP3 decoding as game feature Start game enclosure design	In progress In progress In progress In progress In progress In progress
7	11/21/20	Finish interface board design Start developing prototype for displaying a score board logic Testing of LED matrix and controller drivers complete Initial combination of software and hardware implementation Finish game enclosure
8	11/28/20	Refine and add more features to the game specs Complete playable MVP Fine tune the game logic and playability
9	12/5/20	Testing all components (software, hardware) working as expected Game enclosure created and game enclosed
10	12/12/20	Testing all components working together as expected Finalize Wiki report
11	12/16/20	Demo Day

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

Sourceforge Source Code Link

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.

@@ Line 18: / Line 18: @@
 == Schedule ==
-Show a simple table or figures that show your 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.
 {| class="wikitable" style="margin-left: 0px; margin-right: auto;"