• Catalog Number: 30123
• Lectures/Discussion: 3150 DOW, MW: 12:00 PM – 1:30 PM
• Projects/Makeup: 1200 EECS, F 12:00 PM – 1:00 PM

ALL communication regarding this course must be via Piazza. This includes questions, discussions, announcements, as well as private messages.

Presentation slides and paper summaries should be emailed to eecs598-bigdata-staff@umich.edu.

This class will introduce you to the key concepts and the state-of-the-art in practical, scalable, and fault-tolerant software systems for AI and encourage you to think about either building new tools or how to apply an existing one in your own research.

Since datacenters and cloud computing form the backbone of modern computing, we will start with an overview of the two. We will then take a deep dive into systems for big data and AI landscapes, focusing on different types of problems. Our topics will include: backgrounds on datacenters and edge; systems for deep learning, machine learning, and reinforcement learning; runtime execution and compilers for AI; distributed and federated learning systems; serving systems and inference; scheduling and resource management in AI clusters; etc. We will cover topics from top conferences in systems, networking, and databases venues.

Note that this course is NOT focused on AI methods. Instead, we will focus on how one can build practical software systems so that existing AI methods can be used in practice.

Students are expected to have good programming skills and must have taken at least one undergraduate-level systems-related course (from operating systems/EECS482, databases/EECS484, distributed systems/EECS491, and networking/EECS489).

This course has no textbooks. We will read recent papers from top venues to understand trends in big data systems and their applications.

The Engineering Honor Code applies to all activities related to this course.

All activities of this course will be performed in groups of 2-3 students.

Declare your group's membership and paper preferences by January 20, 2020. After this date, we will form groups from the remaining students.

The course will be conducted as a seminar. Only one group will present in each class. Each group will be assigned to present a paper at least once throughout the semester. Presentations should last at most 45 minutes without interruption. However, presenters should expect questions and interruptions throughout. In the presentation, you should:

• Motivate the paper and provide background.
• Present the high level idea, approach, and/or insight (using examples, whenever appropriate).
• Discuss technical details so that one can understand the key details without carefully reading it.
• Explain the difference between this paper and related work.
• Raise questions throughout the presentation to generate discussion.

The slides for a presentation must be emailed to the instructor team at least 24 hours prior to the corresponding class. You should use this template for making your slides in powerpoint.

Each group will also be assigned to write one or more paper summaries. The paper summary assigned to a group may not be the same paper they have presented.

A paper summary must address the following four questions in sufficient details (2-3 pages):

• What is the problem addressed by the paper, and why is this problem important?
• What is the hypothesis of the work?
• What is the proposed solution, and what key insight guides their solution?
• What is one (or more) drawback or limitation of the proposal, and how will you improve it?

The paper summary of a paper must be emailed to the instructor team within 24 hours after its presentation. Late reviews will not be counted. You should use this template for writing your summary. Allocate enough time for your reading, discuss as a group, write the summary carefully, and finally, include key observations from the class discussion.

Because you do not have to write summaries/reviews for each paper, you cannot avoid reading a paper. Everyone is expected to have read all the papers. Being able to critically judge others' work is crucial for your understanding.

You are expected to attend all lectures (you may skip up to 2 lectures due to legitimate reasons), and more importantly, participate in class discussions.

A key part of participation will be in the form of discussion in piazza. The group in charge of the summary should initiate the discussion and the rest should participate. Not everyone must have add something every day, but it is expected that everyone has something to say over the semester.

You will have to complete substantive work an instructor-approved problem and have original contribution. Surveys are not permitted as projects; instead, each project must contain a survey of background and related work. You must meet the following milestones (unless otherwise specified in future announcements) to ensure a high-quality project at the end of the semester:

• Form a group of 2-3 members by January 20.
• Turn in a 2-page draft proposal (including references) by January 31. Remember to include the names and Michigan email addresses of the group members. Schedule a 15-minute meeting to pitch your idea and to get early feedback.
• Keep revising your initial idea and incorporate instructor feedback. However, your project proposal must be finalized and approved on or before February 14.
• Each group must present mid-semester progress during class hours on March 9 and March 11.
• Each group must turn in an 8-page final report and your code via email on or before 11:59PM EST on April 27. The report must be submitted as a PDF file, with formatting similar to that of the papers you've read in the class. The self-contained (i.e., include ALL dependencies) code must be submitted as a zip file. Each zip file containing the code must include a README file with a step-by-step guide on how to compile and run the provided code.