Main

ECE 576 - Project

Abstract

Projects will focus on applying the methodologies, techniques, and concepts discussed in lecture to create and refine a system level models or hardware/software codesigned implementations of specific applications.

Keywords

SystemC, transaction level modeling, hardware/software codesign.

Project Description

The course project will focus on designing a complex system using a transaction level modeling (TLM), SystemC, and hardware/software codesign techniques. The project is fairly open-ended allowing individuals/groups to define their own project with instructor approval. The following are the basic requirements for all projects.

You are allowed the option to work in groups of no larger than 3 students. However, once you have chosen a partner(s) you will be required to work with that partner(s) for the duration of the semester. Please choose your partner(s) carefully. It is also suggested that each student keep of log of his/her work to ensure any issues relating the group member contribution can be dealt with in a judicious manner.

Projects that tie together a student’s current research activities within the material presented in lecture are encouraged. If you are currently working with a faculty member, it is strong recommended that you discuss project options with your advisor. Most projects should minimally utilize or relate to TLM, SystemC, or HW/SW codesign methods.

Note: Using SystemC and C++ is not intended to be a significant hurdle for your project. As such, the instructor will be available to assist students/groups with development/debugging issues related to SystemC and C++.

Deliverables and Deadlines

Project Proposal (5%)

Provide project proposal detailing your proposed course project not to exceed two pages in length. Due to the individuality of each project the contents of the proposal will vary by group but at a minimum include the following:

  • System-level overview of proposed project along with a block diagram of the system showing the basic components of the system and how TLM or HW/SW Codesign will be utilized within the implementation.
  • A detailed list of ten requirements that will be achieved throughout the project implementations.
  • An estimate for the percentage of effort needed to implement each requirement. This percentage breakdown will be utilized in assessing your final project submission.
  • A list of requirements that will be implemented for the Mid-Project Review. This set of requirements should constitute at least 40% of the project effort.
  • References and brief summaries of at least two published IEEE/ACM journal or conference papers closely related to the course project.

Due Sunday, March 04 11:59PM via D2L

Mid-Project Review and Report (15%)

Provide a mid-project review report describing the current project implementation not to exceed two pages in length. The mid-project review report should explicitly specify which requirements have been fully or partially reached. If the proposed requirements have not been achieved, the mid-project review report should provide a clear and concise explanation as to why the requirements were not reached.

Students will be expected to provide a brief demonstration of the project status to the instructor before the mid-project review deadline. The mid-project review demonstration should not exceed 15 minutes in length.

Due Due Sunday, April 08 11:59PM via D2L

Final Project and Report (80%)

Design and implement the proposed project and provide a specification, implementation, and evaluation report along with any code and documentation for you code. The report should be submitted in a two-column IEEE/ACM format not to exceed 6 pages in length using this Word document as a template and include the following:

  • Abstract briefly describing project and accomplishments.
  • Introduction providing context and motivation for the final implementation.
  • Brief description of related work with appropriately formatted references. At a minimum this should provide a detailed discussion of the related papers identified within the Project Proposal.
  • Detailed description of the system-level implementation or relations to HW/SW codesign methods.
  • Experimental results providing an evaluation of the proposed design in context with the project requirements.

Students will be expected to provide a demonstration of the final project to the instructor before the final deadline. The demonstration should focus on highlighting the individual/group’s accomplishments and satisfaction of the project requirements and should not exceed 30 minutes in length.

Due End of Semester via D2L

Formatting

The Project Proposal, Mid-Project Review Report, and Final Report must be submitted as a Word or PDF document in two-column IEEE/ACM format.