Assignments Winter 2022
There will be five projects, which will count for a total of 65% of your course grade. You must work individually for Project 1 and with a partner for Projects 2–5. You may switch partners between projects, but not within a project.
You may consult general reference material, but you may not draw on anyone else's solution. The material you (and your partner, if applicable) turn in must be entirely your own work, and you are bound by the Honor Code. Please start early and attend lab for important instructions and extra help.
- Crypto Project – Part 1 due Wednesday, January 19 at 6 p.m.; Part 2 due Wednesday, February 2 at 6 p.m.
- Web Project (available Jan. 31) – due Feb. 16 at 6 p.m.
- Networking Project (available Feb. 14) – due Mar. 9 at 6 p.m.
- AppSec Project (available Mar. 14) – due Mar. 30 at 6 p.m.
- Forensics Project (available Mar. 28) – due Apr. 20 at 6 p.m.
For each lecture, we will assign a short quiz on Canvas (U-M login required) for you to gauge your understanding of the lecture material. See the Canvas page for specific deadlines.
For projects 1–3 and 5, EECS 388 distributes environments with all tools needed to complete each project through VS Code Development Containers using Docker. Learn more about Docker and get set up for the course with our Docker guide.
Assigned work is due at the dates and times listed above. We strongly recommend that you get started early. Late submissions will be penalized by 10% of the maximum attainable score, plus an additional 10% every 4 hours until received. Late work will not be accepted after the start of the next lab (of any section) following the day of the deadline, since we will begin reviewing solutions at that time. The professors may grant individual extensions, but only under extraordinary circumstances.
We are here to provide a nurturing environment for everyone enrolled in the course. However, acts of cheating and unacceptable collaboration will be reported to the Engineering or LS&A Honor Councils, as appropriate. Cheating is when you copy (with or without modification, in whole or in part) someone else’s solution to a problem or a part of a problem. Unacceptable collaboration is the knowing exposure of your own solutions or the use of someone else’s solutions. You are expected to exercise reasonable precautions to keep your solutions confidential, including not making your project code public.
At the same time, we encourage students to help each other learn the course material. As in most courses, there is a boundary separating these two situations. You may give or receive help on any of the concepts covered in lecture. You are allowed to consult with other students about the conceptualization of a project, or the general approach for solving problems. However, all work, whether in scrap or final form, must be done by you (or your project partner where applicable).
If you have any questions as to what constitutes unacceptable collaboration or cheating, please talk to an instructor right away.