Final Demo :: ECE 445 - Senior Design Laboratory

Final Demo

Description

The Final Demo is the single most important measure (and assignment) for the success of your project. The evaluation is holistic, focused on whether your project is completed, well-designed, reliable, and usable. You will demo your project to your professor, at least one TA, and a few peer reviewers. Other guests (e.g. alumni, high school students, sponsors, or other department affiliates) may also be present.

Requirements and Grading

Students must be able to demonstrate the full functionality of their project by proving that all the requirements in their Requirements and Verification (RV) table are met. Students must bring a printed out version of their block diagram, high level requirements, and RV table. Credit will not be given for feature which cannot be demonstrated.

For tests that are lengthy or require equipment not available at the time of demo, students should have their lab notebooks or printouts ready to show testing data. For any portion of the project which does not function as specified, students should have hypotehses (and supporting evidence) of what is causing the problem. If your demo needs to happen somewhere that is not the Senior Design Lab, you must communicate this with your TA!

The design team should be ready to justify design decisions and discuss any technical aspect of the project or its performance (not just one's own responsibilities). Quantitative results are expected wherever applicable. The demo grade depends on the following general areas: See the Demo Grading Rubric for specific details, but in general, show the following:

  1. Completion: The project has been entirely completed.
  2. Integration: The project is well-integrated, looking more like a final product than a prototype.
  3. Performance: Performance is completely verified, and operation is reliable.
  4. Understanding: Everyone on the project team must must be able to demonstrate understanding of his/her technical work and show that all members have contributed significantly.
  5. Polish & Attention to Detail: The project is well-polished with the user in mind. Good attention to detail is afforded to useability, presentation, and packaging.

 

Submission and Deadlines

Signing-up for a demo time is handled through the PACE system. Again, remember to sign up for a peer review as well.

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.