reportgd - Massachusetts Institute of Technology Department...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Massachusetts Institute of Technology Department of Electrical Engineering and Computer Science 6.111 - Introductory Digital Systems Laboratory Report Guide Introduction The purpose of this memorandum is to describe general requirements for the reports you must write for laboratory exercises and for the final project. It also describes how 6.111 is a (CI-M) Communications Intensive Subject. Good writing is more important than many of you think. The documents you produce are the principal way of communicating your work. Well-written reports reflect well on your work and on you. Badly written documents, on the other hand, will produce negative impressions, even if those documents represent very good technical work. It is worth the effort to pay careful attention to your writing. A well-written document contains more than clear language, correct syntax, grammar and spelling. It must also reflect clear thinking. Particularly with documents such as those you will produce in 6.111 (dealing with complex technical issues), it is important that care be taken to ensure that the writing clearly and accurately describes the topic. Pictures such as wiring and timing diagrams should be incorporated into the text and be clearly described both in the text and in the captions. CI-M Considerations 6.111 is a CI-M subject. Lab reports 1, 2, and 3, as well as each individual's part of the project report, will be graded for writing style and clarity, as well as for technical content. The report for Lab 2 has a required revision. You will receive detailed comments on technical content and writing style and have adequate time to make a revision which will then be graded. Report Style and Audience Write for your colleagues. You should assume an audience with technical capabilities similar to your own. It should be possible for other students and for faculty to understand your report. Thus you can assume general technical knowledge on the part of your reader. You should not assume that your reader has a lot of specific knowledge about your subject area. Write for yourself. A careful job of documenting your work can help you to organize your project. This can be particularly helpful if done early in the project. Your own carefully thought out explanation of how each element of your circuitry works can help in the process of design. Describe the function of each element and how the elements work together. Then think about what you have written. A surprising number of design errors can be discovered by this process, even before you start writing HDL (VHDL or Verilog) code or wiring. Organize your work carefully and do a neat job. Each of the reports should be typed. Powerful word processing tools are readily available to students in 6.111. Use them. Figures should be done on a computer graphics system or drawn with drafting aids (template and straight-edge). Lettering on figures can be done by hand, but must be neat and legible. Remember to leave yourself enough time to do the report properly. Proofread your report! Eliminate typographical
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/21/2009 for the course EECS 6.111 taught by Professor Prof.ananthachandrakasan during the Spring '04 term at MIT.

Page1 / 7

reportgd - Massachusetts Institute of Technology Department...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online