Professional Documents
Culture Documents
Objective
The biggest benefit of doing a project is that it will expose you to a broader range of the
activities that come up in real engineering applications of digital circuits, instead of the narrow
core we've mostly covered in class. For this reason, the core requirement is that you do some
kind of design and construct a digital circuits from the simple components we studied in our
course as example (AND, OR, NAND , NOR, Invertor, Latches, Flip Flops, you can go for
circuits like Decoders, comparators, half adders, etc ) for a selected input. -- i.e., I don't want a
purely theoretical discussion, and I don't want experiments on ideal problem. In some cases,
it's useful to work with synthetic input (ones you have constructed yourself, rather than
gathered from the real world), but they should be as "real" as possible.
Description
Projects can be done individually only. Your choice of project should be agreed with me;
the easiest way is probably via email to the TA. Some ideas are given at the bottom of this
page, but they are only to get you thinking; your project can be on any topic that interests you,
and I encourage you to choose something that will help harness your enthusiasm.
I encourage you to consider teaming up, primarily because it will allow you to do a more
interesting project. The projects will be graded based on a project report (of around 8-10 pages),
the design and the hardware, as well as in-class presentation for 10 to 15 min.
1
Assessment of the project is based on three components.
1) A 8-10 page technical report (30%). Your report must have the following structure,
using these section headings:
Introduction: A general description of the area of your project and why you're
doing it.
Problem Specification: A clear and succinct technical description of the problem
you're addressing. Formulating a general problem into a well-defined technical goal
is often the most important part of a project.
Data: What are the real-world and/or synthetic input you are going to use to
develop and evaluate your work?
Evaluation Criteria: How are you going to measure how well your project
performs? The best criteria are objective, quantitative, and discriminatory. You want
to be able to demonstrate and measure improvements in your system.
Approach: A description of how you went about trying to solve the problem.
Sometimes you can make a nice project by contrasting two or more different
approaches.
Results and Analysis: What happened when you evaluated your system using the
data and criteria introduced above? What were the principal shorfalls? (This may
require you to choose or synthesize data that will reveal these shortcomings.) Your
analysis of what happened is one of the most important opportunities to display
your command of signal processing concepts.
Development: If possible, you will come up with ideas about how to improve the
shortcomings identified in the previous section, and then implement and evaluate
them. Did they, in fact, help? Were there unexpected side-effects?
Conclusions: What did you learn from doing the project? What did you
demonstrate about how to solve your problem?
References: Complete list of sources you used in completing your project, with
explanations of what you got from each.
50%
• Prototype implementation
20%
• Discussion
Submission Dates
2
Deliverable Submission Method Deadline
The project reports and source code are due before the last week of classes. Electronic submission is
through blackboard for the report, Please compress your report and source code into one
first.lastname.project#.zip before submission
19. Password Security 20. Level monitoring and 21. Home Appliance
System indicating applications in Warning system
manufacturing processes
22. Seat belt warning system 23. Fuel level indicator 24. 7 segment
25. Tic Tac Toe game 26. 4 digit Electronic code
lock