Lecture — TR 1:30-3:00pm — 1571 GGBL (also recorded via CAEN)
None (but see below, and a personal computer or laptop is required)
Successful software projects require more than just technical expertise. Figuring out what the client wants, collaborating in a team, managing complexity, mitigating risks, staying on time and budget, and determining, under various constraints, when a product is "good enough" to be shipped are equally important topics that often have a significant human component. This course explores these issues broadly and covers the fundamentals of modern software engineering and analysis.
This course focuses on software engineering and analysis. At a high level, the course is organized around five core topics:
This course draws inspiration from Carnegie Mellon's Foundations of Software Engineering (15-313) course as well as from the insights of Drs. Prem Devanbu, Christian Kästner, Marouane Kessentini, Kevin Leach, and Claire Le Goues.
If you believe you have been exposed to or have COVID-19, you should follow the official University instructions on the Campus Maize and Blueprint, which include contacting University Health Services at 734-764-8320 and isolating yourself.
In such a case, email EECS481Staff@gmail.com with a note indicating as much and we will ensure that you do not lose any points related to in-person attendance. We want to avoid any tension between the health of the community and your grade. (The length of time you should isolate depends on Univeristy policies and your health. The University currently recommends following the CDC guidelines.)
This course is delivered in person. Accommodations will be made for students via Services for Students with Disabilities or the office of the Associate Dean for Undergraduate Education. Accommodations will also be made for students following the Univeristy's policies about what to do for suspected COVID exposure. All others will be required to attend lectures in person, as per University policy.
Live, in-person attendance at the lectures is required (unless you believe you have been exposed to COVID, etc., as above) and significantly contributes to the participation portion of the course grade.
Lecture recordings will be available (both via Canvas and via the leccap server directly).
To encourage you to keep pace with the material, we will randomly assign reading comprehension quizzes. These quizzes may consist of elements such as (1) comprehension questions about any readings, especially those new since the last quiz, (2) questions about the lecture materials, (3) a 4-sentence summary of lecture material, or (4) a random code word shared during a lecture. You will have a 48 hour window to submit such on-line quizzes (which are announced via their visibility on Gradescope). The goal is to encourage engagement and retention.
Students are required to make use of course websites (such as Piazza and Gradescope) and check them for updates. Some information, including information about certain quizzes and assignments, and any last-minute changes or fixes to assignments or policies, is made presented on them.
With a small number of exceptions (e.g., for Homework 4), no graded assignments or graded participation will be recorded during discussion sections. However, students are encouraged to attend one discussion section each week.
As they have throughout the past year and a half, policies around academic and public health are subject to change as this pandemic evolves. This course will follow all policies issued by the University, which are documented on the Campus Blueprint's FAQ. These policies may change over the course of the term, so please review the Campus Blueprint's FAQ for the most up to date information.
The course schedule is available in advance so that you can plan accordingly.
If the autograder.io or gradescope assignment websites are inaccessible to all students for a short time, all due dates and times remain unchanged (plan ahead!). If they are down for a longer period of time, the course staff will likely extend the deadline slightly and post a notification to that effect. We will make such determinations on a case-by-case basis.
If you personally are unable to access an assignment website due to a temporary internet outage on your end, all of the due dates and times remain unchanged (plan ahead!).
If the main course webpage is inaccessible to all students, all due dates and times remain unchanged. (It is hosted by the EECS department, not by the professors personally, and occasionally exhibits service interruptions.) If it is down for a longer period of time, the course staff will likely extend a deadline slightly and post a notification.
If the course staff are unable to deliver a lecture at the scheduled time (i.e., if it fails for all students), no live participation grades for that lecture will be counted. If the lecture has not started within fifteen minutes of the scheduled time, you may consider it canceled. The course staff will post a notification and deliver the lecture later. No attendance will be taken at that make-up time, and the lecture recording will be made available as usual.
If you personally are unable to attend a lecture (e.g., if your internet access disappears), send proof (e.g., a photo of the dead router or network selection screen) to EECS481Staff@gmail.com.
With these policies, we are attempting to strike a balance between being as supportive as possible of students and remote education will holding students to similar standards of preparation and accountability. We may revisit these policies later in the semester if there are extenuating circumstances.
This course is an upper-level CS technical elective for both CS-Eng and CS-LSA. (It does not show up in some versions of the CS-LSA Program Guide, but it does, in fact, count. Students can check their Audits to confirm.)
It is not a capstone course or a major design experience course. It focuses on individual mastery of key software engineering concepts. It does not feature a large team project.
The expected workload for this class is "moderate" — one notch harder than UI Design, but two notches easier than Operating Systems.
One of the most common student complaints is about buying textbooks that are both expensive and out of date. As a result, I have structured this course so that there is no textbook and all of the readings are available on-line for free.
Because software engineering is often more engineering than science, the basic concepts are often easy to grasp but the trouble is found in the details. Questions such as "which of these methods works best in the real world?" and "what are successful companies actually doing?" are paramount. As a result, many of the readings are experience reports from companies (e.g., Microsoft, Google, etc.) or academic papers (e.g., with human studies). These detailed readings serve to flesh out high-level concepts that can otherwise be introduced via Wikipedia without costing you money.
The flip side of this is that you should actually do the reading. It will help you both in terms of understanding the lectures and also in terms of completing the assignments.
Finally, you may notice that some of the readings are marked optional. Next to each such optional reading I have included a small "advertisement" for why you might want to take a look. The optional readings are not required for any class assignments, but there may be extra credit questions on exams or quizzes that reference them.
For on-line reading comprehension quizzes, you will have a 48 hour period near the lecture period to begin your reading quiz (which are announced via their visibility on Gradescope). Once you begin the quiz, you will typically have 10 minutes to complete it. For in-person reading quizzes, we will pass out paper quizzes in class and you will complete them in-class within a set period of time (such as 5 or 10 minutes).
There are six homework assignments for this course. The assignments involve the electronic submission of artifacts. Some (e.g., test cases) are graded automatically and admit immediate feedback. Others (e.g., prose descriptions) are graded manually. For certain assignments it is possible to work as a team.
There are two exams during the semester. Both are delivered remotely and submitted via GradeScope as a PDF. The grading breakdown is as follows:
By default, this class has no curve. If we do implement a curve, we only ever curve up. If we do implement a curve, it would be calculated at the end of the semester (and not on a per-each-assignment basis).
Regrade requests for exams, assignments, or written assignments must be received within one week of you receiving your score. All regrade requests should be made via Gradescope (if a request absolutely cannot be made via Gradescope for a certain assignment, please submit it privately on the course forum). When we regrade an assignment we will look over it very carefully for correctness: it is possible that after a regrade you will end up with fewer points than before the regrade. Regrades should be treated with caution and used only when the graders have made a clear mistake evaluating your work.
If you miss an assignment deadline or in-class activity, we can be very lenient about extensions or makeups but only if you provide documentation. For example, for death or bereavement, a copy of the obituary or funeral program suffices; for illness or injury, any sort of doctor's note suffices. This policy follows that of other professors in the department. You may email EECS481Staff@gmail.com with supporting documentation (rather than posting it to Gradescope).
If you miss an assignment deadline without an approved, documented extension, you may receive no points. for that assignment. In some extenuating cases you may receive h% off, where h is the number of hours late.
The dates for the in-class examinations are posted well in advance. To request a rescheduled examination (e.g., for reasons other than a documented one as above, etc.), you must notify us via email at EECS481Staff@gmail.com (privately) at least one week before the date of the examination. Note that requests need not be granted.
All course materials submitted for a grade must be turned in by midnight on the last date listed on the course syllabus.
Historically, the single most common student question about this class relates to the waiting list. The question is some variant of (or logically reduces to) "I am currently at position X on the waiting list; am I likely to get in to the class before the deadline?"
Now, for the most common student question:
Unfortunately, I have no special insight here (i.e., it has never happened that a student has said to me "I plan to drop in X days but won't drop today", so I do not have any secret information about the plans of other students to drop or not). The best we can do is use the past to predict the future (see raw data above).
Students often experience strained relationships, increased anxiety, alcohol or drug problems, feeling down, difficulty concentrating, family issues, or a lack of motivation. Student mental health concerns are quite common but we don't always talk about them. The University of Michigan is committed to advancing the mental health and well-being of its students. If you or someone you know is feeling overwhelmed, depressed, or in need of support, confidential mental health services are available on campus.
Your class work might be used for research purposes. For example, we may use anonymized student assignments to design algorithms or build tools to help programmers. Any student who wishes to opt out can contact the instructor or teaching assistant to do so after final grades have been issued. This has no impact on your grade in any manner.
Students interested in considering undergraduate research should make an appointment to talk about it. I am happy to discuss independent study projects, senior projects, paid research work over the summer, research work for credit, and graduate school.