• LOGIN

HThreads

Home › EECS 388 Laboratory

Report Format

Each laboratory project requires the submission of a report along with the design and source files. Every report should contain all of the information described below. Failure to include any of this information will result in a loss of points.

Abstract

This section should contain one short paragraph which summarizes the work that your performed for the laboratory and describes the results that you ended with. The abstract should be no more than five to ten sentences but should still be informative.

Introduction

This section should contain several paragraphs which discuss any background information which is pertinent to the laboratory. Additionally, it should describe what the purpose of the laboratory was and what the expected results of the laboratory are. Diagrams should be used to illustrate the system-on-chipi and software designs. Ensure that all diagrams are correctly labeled.

Design and Implementation

This section section should contain many paragraphs which describe the system that was designed and implemented. You should detail exactly what was built as part of the laboratory, how it was built, and why it was built. Block diagrams, figures, source code, and screen shots are all highly effective and consise ways of communicating your design and implementation.

Results

This section should contain several paragraphs which describe the results of the laboratory. Describe the functionality of the resulting design and discuss how well your design and implementation solved the original problem. Provide any useful system metrics such as the amount of code or the amount of time which was required to solve the problem. Also be sure to mention any problems which were encountered during your design and implementation.

Question Answers

This section should contain the answers to all of the questions which are part of the laboratory. The length of your answer is dependent on the question being asked, however, generally speaking answers should be between two sentences and two paragraphs. Answers should get to the core of the question without being overly verbose.

Conclusion

This section should contain one or two paragraphs which finish the report. Reiterate the original problem and quickly reason about how and why your design and implementation solve the problem. Provide any insight you might have about possible future work related to the project and provide any interesting extensions to the project that could be explored.

References

This section should list all of the reference material which was used during your design and implementation. As engineers you are accountable for your actions and reports. Providing references establishes credibility as to the design and provides a path of reasoning for you decisions and ideas. References should be cited in your report using the appropriate reference number as show below:

...
...
The Hthreads operating system established the effectiveness of hardware components in operating system design [1].
...
...

[1] J. Agron, W. Peck, E. Anderson, D. Andrews, E. Komp, R. Sass, F. Baijot, and J. Stevens, “Run-Time Services for Hybrid CPU/FPGAi Systems On Chip,” in Proceedings of the 27th IEEE International Real-Time Systems Symposium (RTSS), December 2006.

[2] MicroBlazei Processor Reference Guide - http://www.xilinx.com/ise/embedded/mb_ref_guide.pdf.

‹ Deliverables up Reference Materials ›
  • Printer-friendly version

Navigation

  • Home
  • EECS 388
  • FPGA Tutorials
  • MicroBlaze Tutorials
  • Frequently Asked Questions
  • Glossary
  • Search

Book navigation

  • EECS 388 Laboratory
    • Syllabus
    • Deliverables
    • Report Format
    • Reference Materials
    • Project Submission
    • Laboratory 1
    • Laboratory 2
    • Laboratory 3
    • Laboratory 4
    • Laboratory 5
    • Laboratory 6
  • Tutorials

(C) 2008 Wesley Peck
All Rights Reserved