Final Presentation

Description

Presentations of the projects are given a few days after the Final Demo to an audience of fellow student reviewers, the lab instructors, and occasionally faculty or even students from outside the class who are following up a project of personal interest to them. The style is formal and professional, and students should dress accordingly (Generally business professional, or what you would wear to a career fair).

Requirements and Grading

Each project team has 25 minutes for a Powerpoint presentation and questions. Every group member must present their own work contributing to the project and be ready to answer questions. Presentations are judged on the basis of presentation technique and of technical organization and content.

Presentation technique includes dress, use of display materials (slides), clarity of speech, absence of filler words/fidgeting, proper eye contact with audience and smooth transitions between speakers. Content is judged on use of a proper introduction, orderly and connected development of ideas, absence of unnecessary details, proper pacing to stay within the allotted time, and an adequate summary at the close of the talk. Quantitative results are expected whenever applicable. Here is a general outline to follow:

  1. Introduction to your team and your project.
  2. Objective. What problem are you solving?
  3. Brief review of original design, statement on areas of design that changed, and overview of each functional block's requirements.
  4. Description of project build and functional test results. You can choose to include a short (30s) video of your project here.
  5. Discussion of successes and challenges, as well as explanations of any failed verifications demonstrating and understanding of the engineering reason behind the failure
  6. Conclusions from the project: what did you learn, what would you do differently if you redesigned your project, etc.
  7. Recommendations for further work.

Any significant, relevant ethical issues should be briefly addressed, preferably in a single slide.

Presentations will be graded using the presentation grading rubric. Your slides should follow ECE or College of Engineering presentation theming.

Submission and Deadlines

Slides for your final presentation must be uploaded to your project page on PACE prior to your presentation time. Deadlines for signing up may be found on the Calendar. Sign-up for the final presentation is done through PACE. Remember to sign up for a peer review of another group.

Electronic Replacement for COVID-19 Building Monitors @ UIUC

Patrick McBrayer, Zewen Rao, Yijie Zhang

Featured Project

Team Members: Patrick McBrayer, Yijie Zhang, Zewen Rao

Problem Statement:

Students who volunteer to monitor buildings at UIUC are at increased risk of contracting COVID-19 itself, and passing it on to others before they are aware of the infection. Due to this, I propose a project that would create a technological solution to this issue using physical 2-factor authentication through the “airlock” style doorways we have at ECEB and across campus.

Solution Overview:

As we do not have access to the backend of the Safer Illinois application, or the ability to use campus buildings as a workspace for our project, we will be designing a proof of concept 2FA system for UIUC building access. Our solution would be composed of two main subsystems, one that allows initial entry into the “airlock” portion of the building using a scannable QR code, and the other that detects the number of people that entered the space, to determine whether or not the user will be granted access to the interior of the building.

Solution Components:

Subsystem #1: Initial Detection of Building Access

- QR/barcode scanner capable of reading the code presented by the user, that tells the system whether that person has been granted or denied building access. (An example of this type of sensor: (https://www.amazon.com/Barcode-Reading-Scanner-Electronic-Connector/dp/B082B8SVB2/ref=sr_1_11?dchild=1&keywords=gm65+scanner&qid=1595651995&sr=8-11)

- QR code generator using C++/Python to support the QR code scanner.

- Microcontroller to receive the information from the QR code reader and decode the information, then decide whether to unlock the door, or keep it shut. (The microcontroller would also need an internal timer, as we plan on encoding a lifespan into the QR code, therefore making them unusable after 4 days).

- LED Light to indicate to the user whether or not access was granted.

- Electronic locking mechanism to open both sets of doors.

Subsystem #2: Airlock Authentication of a Single User

- 2 aligned sensors ( one tx and other is rx) on the bottom of the door that counts the number of people crossing a certain line. (possibly considering two sets of these, so the person could not jump over, or move under the sensors. Most likely having the second set around the middle of the door frame.

- Microcontroller to decode the information provided by the door sensors, and then determine the number of people who have entered the space. Based on this information we can either grant or deny access to the interior building.

- LED Light to indicate to the user if they have been granted access.

- Possibly a speaker at this stage as well, to tell the user the reason they have not been granted access, and letting them know the

incident has been reported if they attempted to let someone into the building.

Criterion of Success:

- Our system generates valid QR codes that can be read by our scanner, and the data encoded such as lifespan of the code and building access is transmitted to the microcontroller.

- Our 2FA detection of multiple entries into the space works across a wide range of users. This includes users bound to wheelchairs, and a wide range of heights and body sizes.