Project Overview

The EECS 373 final project is a semester-long design challenge in which teams of three to four students build a complete embedded system around an ARM Cortex-M4 microcontroller. Teams propose their own device. It must accomplish a clear goal and draw on the core techniques taught in the course: serial bus interfacing (SPI, I2C, UART), device drivers, interrupts, general-purpose timers, and analog-to-digital or digital-to-analog conversion. Each team receives a parts budget and access to a large inventory of lab hardware. The central challenge is system integration: getting sensors, actuators, firmware, and power working together as a reliable device that can be demonstrated live. The semester ends with a public exhibition where teams demo their work to faculty, students, and industry visitors.

Due dates below are sourced from the EECS 373 - Project Due Dates - Master Sheet

Project Outline

The project runs in five phases. Each step links to the document that defines its requirements.

1. 1 Form a Team

   1. Ideation Slides: Each student submits slides pitching three or more project ideas.
      Due Date: Link Error: see the project due date google sheet
      • Assignment Description
      • Ideation Slide Examples
      • Slide Template
   2. Team Formation Event: An in-class event where students present ideas and form teams of three to four.
      Date: Link Error: see the project due date google sheet
      • Class Ideations Slides
   3. Team Registration: Each team submits one registration form. Registration creates the team's shared project folder, which holds every deliverable for the rest of the semester.
      Due Date: Link Error: see the project due date google sheet
   4. Team Project Folders: Each team will be assigned a Google Drive Project folder. This will constitute your primary work space and location for archiving milestones and assignments.
      • Link Error: see the project due date google sheet

2. 2 Propose

   1. Final Project Description: This document is the official handout for the project and describes the requirements, deliverables, and grading.
      • Final Project Description
   2. Proposal Review Sign-Up: Each team books a 30-minute review meeting with the instructors.
      • Due Date: Link Error: see the project due date google sheet
   3. Project Proposal and Slides: The proposal document is due the night before the review meeting. It includes a component diagram (modules, data interfaces, voltage and power), a firmware functional outline, and a short slide deck for the meeting.
      • Proposal Guidelines
      • Proposal Example
      • Slides Guidelines
   4. Project Pitch Meeting: Teams present their proposal to the instructors and receive feedback on scope, feasibility, and grading.
   5. Proposal Revision: Teams revise their proposal based on feedback to earn additional points. Both versions stay in the project folder.
      Date: Link Error: see the project due date google sheet

3. 3 Build

   1. Order Parts: Teams order components within their parts budget and draw on the lab inventory.
      • Parts ordering instructions
   2. Weekly Milestone Reports: Each week, teams report progress on each module, upload a short video of working subsystems, flag concerns, and set goals for the following week. Backup copies go in the project folder.
      • Milestone Report 1: Link Error: see the project due date google sheet
      • Milestone Report 2: Link Error: see the project due date google sheet
      • Milestone Report 3: Link Error: see the project due date google sheet

4. 4 Exhibit

   1. Poster: Teams design and print a poster describing the system, its architecture, and results.
      Due Date: Link Error: see the project due date google sheet
      • Poster Guidelines
      • Poster Template
   2. Project Evaluation Form: Submitted before the expo, this form lists every component and technique the project uses so instructors can credit all of it.
      Due Date: Link Error: see the project due date google sheet
   3. Project Expo: Teams demo their working systems live in the EECS Atrium to faculty, students, and visitors.
      Date: Link Error: see the project due date google sheet

5. 5 Wrap Up

   1. Digital Archive: Teams upload final code, schematics, CAD files, and documentation to the project folder.
      Due Date: Link Error: see the project due date google sheet
      • Archive checklist
   2. Project Video: A short video demonstrating the finished system.
      Due Date: Link Error: see the project due date google sheet
      • Video guidelines
   3. Member Contribution Form: Each student submits individually, describing what each teammate worked on.
      Due Date: Link Error: see the project due date google sheet
      • Member Contribution Form Instructions
   4. Lab Cleanup: Every student must participate in lab cleanup to receive a grade in the course.
      Due Date: Link Error: see the project due date google sheet

EECS 373 Embedded System Expo