Massachusetts Institute of Technology Department of Electrical Engineering and Computer Science 6.111 - Introductory Digital Systems Laboratory Project Information Introduction The term project in 6.111 is your opportunity to specify and design a small digital system. You will design, build, debug, demonstrate, and report on this system. This memorandum sets forth our expectations and requirements for this project and makes a few suggestions which should help to make your project a success. In order to accomplish all that is expected by the end of the term, it is essential that you stay on schedule. Both the determination of grades and the project time requirements are inherently subjective. Lab 3 provides some guidance to the evaluation of project size and complexity. Instructions 1. The first step in starting your project is to find a partner with whom you wish to work. Two-person projects are preferred, but three-person projects are permitted. Individual projects must be approved by the lecturer. 2. The second step is to decide what you wish to do. A list of past projects can be found on the course web site. 3. The third step is to submit a PROPOSAL ABSTRACT (one for each group) using the attached form. This item and the PROPOSAL which follows are to be prepared jointly with your partner. We will use the proposal abstract to assign project teams to members of the teaching staff. Those assignments will be posted shortly after the deadline for proposal submission. Once you receive feedback from the staff, we request you polish the abstract so we can post it on the course website. 4. The fourth step is to write the PROPOSAL. It is comprised of: 1. A description of the project in words, stating what your system is going to do and how you plan to implement it. 2. A block diagram. 3. A set of specifications that define in detail what your system is (in input, output terms) and what tests will be used to prove that it functions properly.4. A statement of how the project work is to be divided among the partners. The block diagram should be referenced. The project should be partitioned into two separately testable subsystems. Each subsystem is to be the responsibility of a single partner. The proposal should be typewritten. Typically, it should be two to five pages in length, single-spaced, plus the block diagram and any figures you may need. 5. The fifth step is the Proposal Conference, which is when the proposal is to be submitted. Each project Proposal must also be presented orally to the Staff so that both you and we understand what it is you are attempting, and whether your basic design approach is sound. Each project group should sign up for a 30 minute session. Sign-up sheets will be posted in the lab in advance of the first day of proposal conferences. Be sure to bring extra copies of your Proposal with you to the presentation so that TA's can follow your talk without your having to draw your block diagram on the chalk-board. Also, discuss the proposal and required resources with the professor. 6. The sixth step is to prepare detailed Module Designs and Logic Diagrams for each of the blocks in the block diagram, and have these approved by your project TA at the Block Diagram Conference. This approval is a prerequisite to your adding 6 extra units of 6.905. You and your project partner(s) are to present your project design to the rest of the class. You are required to use power point OR PDF. Do not count on drawing it on the board as there is not enough time for this. The presentation day will be chosen by the teaching staff and communicated to you by email and also posted on the web. You are required to email the PDFs or Power point file to the professor by 11AM on the day of the presentation. Your presentation PDF will be posted on the course website. 7. The seventh step is to build, debug and test your system. Project CONSTRUCTION may not begin until you have: 1. Completed and handed in all problem sets and assigned lab exercises and, 2. Had your detailed logic diagram approved by your TA. 8. The eighth step is to demonstrate your project to a member of the Staff. We will videotape your presentation and post it on the website (with your permission). 9. The ninth step is to complete and submit the PROJECT REPORT. Material from the proposal can be used. The report should be prepared jointly:• The Introduction and Summary sections can be joint efforts of the project team, but it must contain separate sections, individually written, describing subsystems for which each partner is responsible. Each section of the report should indicate the responsible author. See the Report Guide handout for general requirements for the Final Project Report. 10. The final step is to turn in your kit and other components. Remove all wires from the socket strips and return the chips to their places in the box. Schedule Refer to the on-line syllabus for pertinent due dates. Pertinent milestones are as follows: Formation of Project Teams Monday, March 28, 2005 Project Abstracts Monday, April 4, 2005 Proposal Submission and Conferences Wed. – Fri., April 6-8, 2005 Block Diagram Conferences Mon. – Fri., April 11-15, 2005 Checklist Due Wednesday, April 20, 2005 Last Day 6.905 forms signed (Drop Date) Thursday, April 21, 2005 Project Design Presentations Wednesday, April 20 through Wednesday, April 27, 2005 Project Check-off (30 minutes with TA) Tuesday May 10, 2005 Video Taping (3-4 minutes per group) Wednesday May 11, 2005 Project Reports due by 5:00 p.m. Thursday, May 12, 2005Extra Units for “Large” 6.111 Projects Most 6.111 students spend more hours per week than warranted by the 12 unit rating. Primarily this is due to large final projects. It is now possible to register for an additional 6 units of credit for 6.111. Our motivation for enabling the availability of these extra units is two-fold. Foremost is our desire to convince 6.111 students that they need NOT do a project which is bigger and more complicated than ever done in the past. Secondly, recognizing that many students will continue to do ambitious projects, we would like to credit 6.111 students with units appropriate to work expended. We are concerned that the availability of extra units may be taken as a signal to escalate the size of 6.111 projects. Indeed, if we perceive this to be the result, we may discontinue this procedure. While a
View Full Document
Unlocking...