Department of Computer Engineering
Faculty of Engineering
University of Tripoli
FPGA Design for Embedded
Systems
Final Project
Schedule, Organization & Grading
1
Final Project: Schedule
• Project Abstract
• Start discussing ideas now with me.
• One page description of the project itself.
• Proposal Conference
• Submit it on-line (MS Teams).
• Block Diagram Conference
• Review major components and overall design approach.
• Project Design Presentation to class
• Each student will make a 15-20 min presentation (~15 slides).
• Required attendance.
2
• Final Project Report
• Submit hard copy and soft copy of your final report.
• No late reports will be accepted.
3
Project Grading (70% Total)
• Deadlines and effort (5%)
• Problem Definition and Relevance, Architecture,
Design methodology (30%)
• What is the problem
• Why is it important or interesting
• System architecture and partitioning
• Design choices and principles used
• Style of coding
• All of the above should be stated in the project and report
• Functionality (10%)
• Did you complete what you promised (i.e., graded by the
proposal checklist)
• Contribution, Complexity, Innovation (25%)
4
Presentation & Report Grading (30%)
• Project Proposal (5%)
• Class Presentation (10%)
• Final Report (15% technical)
Required Attendance
5
Final Report Grading Rubric
• For technical grading, we assign a max of 15 points
as follows:
• Technical content of overview/motivation: (0, 1, 2)
• Logical, readable diagrams and timing (if appropriate)
( 0, 1, 2)
• Enough details so the project can be replicated by a fellow
student (0, 2, 4)
• Discussion on methodology/challenges/measurements of
interesting signals and results (if appropriate) (0, 3, 6)
• Lessons learned, advice for the future projects, (0, 0.5, 1)
6
Motivation & Problem Definition
• Does this report sufficiently describe motivation of this
project?
• Does the report clearly define a research problem?
• Does the report adequately describe related work?
• Does the report cite and use appropriate references?
• Does the report clearly & adequately present your research
approach (algorithm description, pseudo code, etc.)?
• Does this report clarify your evaluation’s objectives
(research questions raised by you)?
7
• Does this report concretely describe what can be measured and
compared to existing approaches (if exist) to answer such research
questions?
• Does the report include empirical results that support the
author’s claims/ research goals?
• Does the report suggest future research directions or make
suggestions to improve or augment the current research?
• Did the report demonstrate consideration of alternative
approaches?
• Does the report discuss what they accomplished?