Individual Progress Report

Description

The Individual Progress Report (IPR) is a chance to put your contributions to the team's progress in writing. The report will discuss not only the components and subsystems you have personally been responsible for, but what components you have helped work on as well. It is important to talk about the relation between your work and your teammates' work as well.

Importantly, we want to see what you have worked on, what works and doesn't, and how you are planning on overcoming your challenges.

Requirements and Grading

This report should be 5-12 pages of your own work. This means that you cannot take full paragraphs or sections from your Design Document, since that was a collaborative effort. The IPR Grading Rubric describes what we look for in grading this assignment. The requirements are expanded on below:

  1. General: Concise writing is encouraged, but it is important that all pertinent information is conveyed. All figures should be labeled and formatted consistently.
  2. Formatting: Please refer to the Final Report Guidelines for general writing guidelines, since the format of this report should be very similar to that of the final report. Note that each component of the Final Report may be tailored to the parts of the project the individual has been active in.
  3. Introduction: First, discuss what portion of the system you have been active in designing connects to which portion of a different subsystem, and how these interact to complete an overall objective. Then discuss what you have accomplished, what you are currently working on, and what you still have left to do.
  4. Design: Discuss the design work you have done so far. It is expected that you have done calculations and/or found relevant equations, created circuits for your parts of the project, and simulated / drawn schematics for your parts. You may have already, at a high level, discussed how your part fits into the rest of the project, but you should expand on the technical details and interface between your module(s) and the other modules of the project.
  5. Verification: Testing and verification is also very important. Make sure you describe each test that was performed and its procedure in detail, and give quantitative, meaningful results. Also describe tests that have yet to be performed. We should be convinced that if all your tests will pass, your part of the project will work.
  6. Conclusion: Discuss a plan and timeline for completing your responsibilities and your project as a whole. Also explain the ethical considerations of your project by consulting the IEEE Code of Ethics, ACM Code of Ethics, or another relevant Code of Ethics.
  7. Citations: You need citations. Cite sources for equations, Application Notes you referenced in your design, and any literature you used to help design or verify your work. If you checked something from another course's lecture slides, Google'd for things related to your project, or anything similar, then you have something you need to cite. At the very least, since you have talked about the ethical considerations of your project as it relates to a published code of ethics (e.g., IEEE or ACM), you should cite those!

Submission and Deadlines

The IPR should be submitted on Blackboard in PDF format by the deadline listed on the Course Calendar.

Authentication System for SARS-CoV-2 Management

Jiongfan Chen, Zheyuan Zhang, Zhonghao Zhang, Pengyang Zhou

Featured Project

## MEMBERS

- Pengyang Zhou [pz6]

- Jiongfan Chen [jc47]

- Zheyuan Zhang [zheyuan5]

- Zhonghao Zhang [zz46]

## PROBLEM

Preventing SARS-CoV-2 spread requires managing access to public spaces using a phone app. Scanning QR code at the entrance is inconvenient and leads to crowding. Specifically, access control in some other places requires users to take out their mobile phones and show green or blue codes to verify their identity, which also makes users feel troublesome. How to let the user be able to pass the access control quickly is a huge problem to be solved. On the other hand, the health code observed by the human eye is easy to fabricate. How to improve security is also a big problem.

## SOLUTION OVERVIEW

We plan to design a wearable wristband for users. When passing through the access control, a corresponding RFID detection device can send identity query requests to users' wristbands from a distance, and the users' wristbands will respond to convey users' identity and health information. In addition, the wristband itself will send out a signal every few seconds to interact with other wristbands. This would help to monitor people suspected of being infected.

## SOLUTION COMPONENTS

### Wristband Subsystem:

- Broadcast the user token for other wristbands to record the passers-by.

- Receiver the request for identity from the receiver and send back the user token.

### Inspection Device at Access Control Subsystem:

- Send signals to the wristband and receive the feedback of the user identity information, through the database verification and comparison to determine the health status of the user.

## CRITERION FOR SUCCESS

- The wristband connects the inspection device and carries out information transfer successfully, and interconnects with other wristbands.

- The inspection device and database can verify the identity and health information of the user trying to enter.

- If the wristband is lost, it cannot be used by others.

- The user token is hard to be fabricated.

## DISTRIBUTION OF WORK

- Wireless communication hardware design, setup, and verification - Zhonghao Zhang (EE).

- Design and manufacture of the wristband and inspection device at access control - Jiongfan Chen (ME).

- Build the data center; Encryption and handling of data - Zheyuan Zhang & Pengyang Zhou (ECEs).