Difference between revisions of "F20: Son of a Gun"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Abstract)
(→‎Schedule)
Line 36: Line 36:
 
! scope="col"| Task
 
! scope="col"| Task
 
! scope="col"| Actual
 
! scope="col"| Actual
 +
! scope="col"| Status
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
| 10/8
+
|
−
| Task list
+
09/23 - 09/29
−
| Completed?  Problems Encountered?
+
|
−
|}
+
* Review previous projects
 +
* Brainstorm on games and proposals
 +
* Frame the project proposals
 +
|
 +
* 09/24
 +
* 09/25
 +
* 09/27
 +
|
 +
*<font color = "green"> Completed
 +
*<font color = "green"> Completed
 +
*<font color = "green"> Completed
 +
|-
 +
!scope="row" | 2
 +
|
 +
09/30 - 10/06
 +
|
 +
* Components search and analysis
 +
* Discuss probable gameplays and challenges
 +
|
 +
* 10/03
 +
* 10/04
 +
|
 +
*<font color = "green"> Completed
 +
*<font color = "green"> Completed
 +
|-
 +
!scope="row" | 3
 +
|
 +
10/07 - 10/13
 +
|
 +
* Set up git repository
 +
* Set up JIRA for project management
 +
|
 +
* 10/18
 +
* 10/10
 +
|
 +
*<font color = "green"> Completed
 +
*<font color = "green"> Completed
 +
|-
 +
 
 +
}
  
 
== Parts List & Cost ==
 
== Parts List & Cost ==

Revision as of 23:15, 19 October 2020

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.

Son of a Gun

Abstract

The LED Matrix will display some enemy and friend objects along with an aim cursor. The player has to shoot the enemy objects avoiding the friend objects by moving the aim cursor on the LED matrix by pointing a gun that consists of IR/Color sensor or Gyroscope.

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

  • Tejas Pidkalwar
  • Tirth Pandya
  • Nimit Patel

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.

}

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.

Week# Date Task Actual Status
1

09/23 - 09/29

  • Review previous projects
  • Brainstorm on games and proposals
  • Frame the project proposals
  • 09/24
  • 09/25
  • 09/27
  • Completed
  • Completed
  • Completed
2

09/30 - 10/06

  • Components search and analysis
  • Discuss probable gameplays and challenges
  • 10/03
  • 10/04
  • Completed
  • Completed
3

10/07 - 10/13

  • Set up git repository
  • Set up JIRA for project management
  • 10/18
  • 10/10
  • Completed
  • Completed
Retrieved from "http://socialledge.com/sjsu/index.php?title=F20:_Son_of_a_Gun&oldid=61393"