Difference between revisions of "F19: Tetris"
Proj user1 (talk | contribs) (→Team Deliverables Schedule) |
Proj user1 (talk | contribs) (→Technical Responsibilities) |
||
| Line 55: | Line 55: | ||
== '''Technical Responsibilities''' == | == '''Technical Responsibilities''' == | ||
| − | + | {| class="wikitable" style="margin-left: 0px; margin-right: auto;" | |
| + | |- style="vertical-align: top;" | ||
| + | ! colspan="5" style="background:#7a8ae2" | <span style="color:#FFFFFF">Technical Responsibilities </span> | ||
| + | |- | ||
| + | ! style="text-align: left;" | | ||
| + | * <span style="color:#000000"> Gaming Logic & Driver </span> | ||
| + | |<font color="Rainbow"><B> Kevin Chan & Lawrence Wan & Yuming Cheng & James Din </B></font> | ||
| + | |- | ||
| + | ! style="text-align: left;" | | ||
| + | * <span style="color:#000000"> Enclosing </span> | ||
| + | |<font color="blue"><B> Yuming Cheng & Lawrence Wan </B></font> | ||
| + | |- | ||
| + | ! style="text-align: left;" | | ||
| + | * <span style="color:#000000">PCB </span> | ||
| + | |<font color="red"><B> Lawrence Wan </B></font> | ||
| + | |- | ||
| + | ! style="text-align: left;" | | ||
| + | * <span style="color:#000000"> BGM </span> | ||
| + | |<font color="blue"><B> James Din </B></font> | ||
| + | |} | ||
==''' Schedule '''== | ==''' Schedule '''== | ||
Revision as of 03:18, 13 November 2019
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
LED Matrix Tetris
Abstract
Our project is creating the game of Tetris using the LED matrix as our display and creating the driver for the game using the SJSU2 board from the class.
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 & Main Responsibilities
| Administrative Roles | ||||
|---|---|---|---|---|
|
Kevin Chan & Lawrence Wan | |||
|
Yuming Cheng | |||
|
Lawrence Wan | |||
|
Yuming Cheng & James Ding | |||
|
Kevin Chan | |||
|
Lawrence Wan & Kevin Chan | |||
Technical Responsibilities
| Technical Responsibilities | ||||
|---|---|---|---|---|
|
Kevin Chan & Lawrence Wan & Yuming Cheng & James Din | |||
|
Yuming Cheng & Lawrence Wan | |||
|
Lawrence Wan | |||
|
James Din | |||
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.
Team Deliverables Schedule
| WEEK |
START DATE |
END DATE |
TASK DETAILS |
STATUS |
|---|---|---|---|---|
| 1 | 8 Oct 2019 | 21 Oct 2019 |
Create and establish GitLab repository |
In Progress In Progress In Progress Complete Complete Complete |
| 2 | 22 Oct 2019 | 4 Nov 2019 |
Create a Bill of Materials. |
In Progress Complete In progress |
| 3 | 5 Nov 2019 | 11 Nov 2019 |
Finalize the Wiki schedule for submission |
In progress Complete (Basic function complete) In Progress (working on rotation) |
| 4 | 12 Nov 2019 | 18 Nov 2019 |
Received the PCB and start working on connections |
In progress ( Waiting for PCB ) In progress In progress In progress In progress |
| 5 | 19 Nov 2019 | 25 Nov 2019 |
Starting to assemble the enclosing |
Waiting for Materials In progress In progress Not Started Not Started (Debating accordingly to our progress) |
| 6 | 26 Nov 2019 | 2 Dec 2019 |
Polishing the Hardware and Software for project. |
Not Started Not Started Not Started In progress |
| 7 | 3 Dec 2019 | 9 Dec 2019 |
FIELD TESTING - CRITICAL WEEK |
Not Started Not Started Not Started Not Started |
| 8 | 10 Dec 2019 | 17 Dec 2019 |
All hands on testing and final bug fixes. |
Not Started Not Started Not Started Not Started |
| Final | 18 Dec 2019 |
DEMO: Final Project |
In progress In progress |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| PART NAME |
PART MODEL & SOURCE |
QUANTITY |
COST (USD) |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Total Cost: |
|
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.
