Difference between revisions of "ECE434 Project - Cornhole Board"

From eLinux.org
Jump to: navigation, search
(Created page with "PT PT {{YoderHead}} Team members: Mark A. Yoder == Grading Template == I'm using the following template to g...")
 
(Executive Summary)
(3 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
{{YoderHead}}
 
{{YoderHead}}
  
Team members: [[user:Yoder|Mark A. Yoder]]
+
Team members: [[user:hedricsd|Sam Hedrick]], Tristen Foisy
  
 
== Grading Template ==
 
== Grading Template ==
Line 10: Line 10:
  
 
<pre style="color:red">
 
<pre style="color:red">
09 Executive Summary
+
10 Executive Summary
09 Packaging
+
10 Packaging
09 Installation Instructions  
+
10 Installation Instructions  
09 User Instructions
+
10 User Instructions
09 Highlights
+
10 Highlights
09 Theory of Operation
+
10 Theory of Operation
09 Work Breakdown
+
10 Work Breakdown
09 Future Work/Conclusions
+
10 Future Work/Conclusions
09 Hackster.io
+
10 Hackster.io
09 Demo/Poster
+
10 Demo/Poster
 
00 Not Late
 
00 Not Late
  
Score:  90/100
+
Score:  100/100
 
</pre>
 
</pre>
  
 
== Executive Summary ==
 
== Executive Summary ==
 +
This page will be updated more frequently when we have a better idea of our project.
  
 
Picture that summarizes the project.
 
Picture that summarizes the project.

Revision as of 11:58, 18 October 2021

thumb‎ Embedded Linux Class by Mark A. Yoder


Team members: Sam Hedrick, Tristen Foisy

Grading Template

I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!

10 Executive Summary
10 Packaging
10 Installation Instructions 
10 User Instructions
10 Highlights
10 Theory of Operation
10 Work Breakdown
10 Future Work/Conclusions
10 Hackster.io
10 Demo/Poster
00 Not Late

Score:  100/100

Executive Summary

This page will be updated more frequently when we have a better idea of our project.

Picture that summarizes the project.

Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.

Packaging

If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.

Installation Instructions

Give step by step instructions on how to install your project.

  • Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
  • Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
  • Include a Makefile for your code if using C.
  • Include any additional packages installed via apt. Include install.sh and setup.sh files.
  • Include kernel mods.
  • If there is extra hardware needed, include links to where it can be obtained.

User Instructions

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

Consider making it autostart for full credit.

Highlights

Here is where you brag about what your project can do.

Include a YouTube demo the audio description.

Theory of Operation

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

Work Breakdown

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

Future Work

Suggest addition things that could be done with this project.

Conclusions

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.




thumb‎ Embedded Linux Class by Mark A. Yoder