Course Description

Design plays a crucial role in the success of a software product, as decisions made during the design stage have a long-lasting impact on qualities such as reliability, robustness, maintainability, scalability, and security. With the increasing use of AI-based programming tools (such as ChatGPT and Copilot), being able to effectively design large, complex software and reason about systems at scale will become highly sought-out skills in the software industry.

This course teaches students how to design complex, large-scale software systems that are reliable, robust, and built to last. It introduces fundamental concepts and techniques for designing software to achieve qualities of a successful product (such as maintainability, scalability, and robustness) and to avoid catastrophic failures. After taking this course, students will be able to (1) systematically generate and explore design alternatives, (2) specify and evaluate design options using appropriate abstractions, and (3) communicate and critique design decisions with other members of large, multi-team organizations. The discussions of these concepts will be driven by case studies of past failures and successes in real-world software systems. The course will be hands-on and involve a semester-long project where the students will work in teams to design, test, and deploy a complex software system. This course is aimed at both undergraduate and graduate students who are interested in the role of a software architect or designer in an organization.

Logistics

Prerequisites

  • Intermediate programming skills and/or experience with building medium-size programs
  • Experience with unit tests and version control systems (e.g., Git)
  • An interest in learning from failures and a growth mindset

Time & Location

  • Lectures: Mon & Wed, 12:30-1:50 PM (TBD)
  • Recitation: Friday, 1:00-1:50 PM (SH 238)

Course Staff

Office Hours

  • Eunsuk: TBD

Readings

There is no single official textbook for this course. Instead, readings will be assigned from academic and industry articles, book chapters, blog posts, and videos. Please see Canvas for more information about the readings.

Class Schedule (from Spring 2026; to be updated)

Date Topic Reading Assignment
Jan 12 Mon Introduction and motivation Just Enough Architecture Ch. 3  
Jan 14 Wed Problem vs. solution space The World and the Machine  
Jan 16 Fri Activity: Problem space    
Jan 19 Mon MLK Jr Day - No classes    
Jan 21 Wed Design abstractions Just Enough Architecture Ch. 6 & 9 HW1 out
Jan 23 Fri Activity: Design models    
Jan 26 Mon Quality attributes & trade-offs Software Architecture in Practice Ch. 3; Fowler article on quality  
Jan 28 Wed Designing interface specifications Program Development in Java Ch. 9 HW1 due; M1 out
Jan 30 Fri Activity: Interface specifications    
Feb 2 Mon Design for change IEEE Software article; Parnas 1972  
Feb 4 Wed Design for change (continued) Clean Architecture Ch. 7, 10, 11, 22  
Feb 6 Fri Activity: Changeability    
Feb 9 Mon Design for testability Effective Software Testing Ch. 6, 7 M1 due; M2 out
Feb 11 Wed Design for testability (continued) Effective Software Testing Ch. 4, 8  
Feb 13 Fri Activity: Testability    
Feb 16 Mon Midterm    
Feb 18 Wed Design for interoperability FAIR Principles  
Feb 20 Fri Midterm review    
Feb 23 Mon Design reviews Intellectual Control, Improving Design Reviews at Google  
Feb 25 Wed Designing with AI Google paper on software developers and AI  
Feb 27 Fri Project work time (no recitation)   M2 due; M3 out
Mar 2 Mon Spring break - No classes    
Mar 4 Wed Spring break - No classes    
Mar 6 Fri Spring break - No classes    
Mar 9 Mon Cross-team interface design session Design It! From Programmer to Software Architect Ch. 9  
Mar 11 Wed Design for scalability Designing Data-intensive Applications Ch. 1, 5, 6  
Mar 13 Fri Activity: Service integration    
Mar 16 Mon Design for scalability (continued) Monolith first  
Mar 18 Wed Design for scalability (continued)    
Mar 20 Fri Activity: Scalability   M3 due; M4 out
Mar 23 Mon Design for robustness Why software quality matters  
Mar 25 Wed Design for robustness (continued) Chaos testing at Netflix  
Mar 27 Fri Activity: Robustness    
Mar 30 Mon Design for security STRIDE approach  
Apr 1 Wed Design for security (continued) Security design principles; Security Architecture of qmail M4 Part A due
Apr 3 Fri Activity: Security    
Apr 6 Mon Design for usability Mental models; Usability design heuristics HW2 out
Apr 8 Wed Value Sensitive Design VSD: Introduction M5 out
Apr 10 Fri Spring Carnival - No classes M4 Part B due  
Apr 13 Mon Project work time (no lecture)    
Apr 15 Wed Project work time (no lecture)   Final Presentation out
Apr 17 Fri Project work time (no recitation)   HW2 due; M5 due (April 19)
Apr 20 Mon Course review    
Apr 22 Wed Project presentations   Final Presentation due
Apr 24 Fri Exam review    

Learning Objectives

After taking this course, students will be able to:

  • Describe, recognise, and apply design principles for (but not limited to): Reusability, testability, changeability, robustness, scalability, security, and safety.
  • Explain how to adapt a software design process to fit different domains, such as robotics, web apps, mobile apps, and medical systems
  • Identify, describe, and prioritize relevant requirements for a given design problem
  • Generate viable design solutions that appropriately satisfy the trade-offs between given requirements
  • Apply appropriate abstractions & modeling techniques to communicate and document design solutions
  • Evaluate design solutions based on their satisfaction of common design principles and trade-offs between different quality attributes

Course Philosophy

Hands-on Experience in a Collaborative Project

Interesting design challenges usually arise in complex systems and can only be fully understood via first-hand experience. Therefore, teams in this course will work together on a single project to collaboratively build a complex system that involves design decisions and discussions of interfaces between different teams. We will provide support structures to help you navigate potential cross-team issues.

Growth Mindset & Learning from Failures

When working on a complex software project, design issues and challenges will inevitably arise. In this course, we embrace a growth mindset and encourage students to see challenges in the project as an opportunity to learn based on the motto: “If you fail and you know why, you’ve succeeded. If you succeed and you don’t know why, you’ve failed”. We will focus on continuous, semester-long improvements, rather than achieving perfection in the first attempt.

Active Student Participation

Educational research shows that active student participation in lectures is crucial for ensuring a deep understanding of the material [MIS]. So rather than just presenting design principles in a traditional lecture style, our lectures are based on real-world case studies from which we will derive de