Project Report

[gstro]

Hey all, Roy reminded us that we will need to complete a project report detailing our design decisions and implementations - you can check out the rubric. The idea is to create a document that can be transferred to a new team so they can get up to speed easily and allow them to pick up where we left off.

The report should have the customary outline with: abstract, introduction and motivation (a brief historical note may be included if appropriate), description of various parts of the project including the project management, conclusions etc. as given in the table below. There should be a references section at the end. Note that technical content part will depend on the specifics of the project and students should consult with their faculty advisor to find out if all items should be covered and/or if there are additional components that make sense for their project.

I've created a Google Doc in our shared folder because it's easy. Though it's not exactly version controlled so if we feel like we need to do a different method I'm ok with that too. The main point is to get everyone thinking about documenting their parts, collecting and presenting relevant data, and formulating our "Lessons Learned."

[gstro]

Hi @profroyk, are we to assume the report is due at the presentation on 06JUN2015? Or can we table it until finals week?

[profroyk]

I'd prefer that you have it done by the presentation date but it won't be the end of the world until it slips out to finals week. But, if you slip to finals week please make it available early in the week before I have the ECE 540 final projects to grade.

Roy

On Wed, May 20, 2015 at 2:03 PM, Greg notifications@github.com wrote:

Hi @profroyk https://github.com/profroyk, are we to assume the report is due at the presentation on 06JUN2015? Or can we table it until finals week?

— Reply to this email directly or view it on GitHub https://github.com/erebus-labs/blocks-o-code/issues/82#issuecomment-104038458 .

Roy Kravitz Westside Program Director Electrical and Computer Engineering Department Maseeh College of Engineering and Computer Science Portland State University

503-913-1678 (M) roy.kravitz@pdx.edu ece.pdx.edu

[dfrister]

Report looks to be in final revisions and document attaching (figures, appendix, test plans, etc). Greg and Tyler finished most of the large sections earlier today.

[profroyk]

Super. I'd like to get your grades done before the Thursday rush of ECE 540 final project deliverables.

Congratulations, again, for a fantastic accomplishment. You guys hit it out of the ballpark imho.

Roy

On Mon, Jun 8, 2015 at 10:55 PM, Daniel Frister notifications@github.com wrote:

Report looks to be in final revisions and document attaching (figures, appendix, test plans, etc). Greg and Tyler finished most of the large sections earlier today.

— Reply to this email directly or view it on GitHub https://github.com/erebus-labs/blocks-o-code/issues/82#issuecomment-110233511 .

Roy Kravitz Westside Program Director Electrical and Computer Engineering Department Maseeh College of Engineering and Computer Science Portland State University

503-913-1678 (M) roy.kravitz@pdx.edu ece.pdx.edu

[gstro]

Anyone have any last test plans to add to the Test Plan folder in our shared Google drive before they're collected for the report? @dfrister @Debrant @htylo @jmickiewicz

[gstro]

@profroyk, I stopped by your office just after noon today to submit:

• a hard-copy of the report
• our final evaluations (I believe @htylo (Tyler) emailed his eval already)
• your logic analyzer - it was a huge help
• and one of the 'operator' blocks from the set (#106)

I asked the ECE dept. front desk to put them all in your box. Thanks for a great capstone.