User interface

Loops

JavaScript

Debugging

The Raft Consensus Algorithm

Discussion of "A Philosophy of Software Design"

PrimeGenerator

Message-Passing

HTTP Design

The UNIX Timesharing System

CS 190: Software Design Studio Stanford University Winter 2023 This course aims to teach the art of software design by breaking down complex systems into manageable classes. It covers concepts like information hiding, API design, and error handling. Enrolment is application-based, and prior C++ experience is a must. The curriculum encourages simplicity in system building for easy implementation and maintenance. It is based on "A Philosophy of Software Design" book. This course teaches the art of software design: how to decompose large complex systems into classes that can be implemented and maintained easily. Topics include information hiding, deep classes, API design, managing complexity, error handling, and how to write in-code documentation. The class involves significant system software implementation and uses an iterative approach consisting of implementation, review, and revision. The course is taught in a studio format consisting mostly of in-class discussions and code reviews. Course enrollment is limited; you must apply for admission. The CS curriculum here has several classes that teach you the mechanics of writing programs (if statements, recursion, inheritance, etc.). We have classes that teach you how to write correct code, how to write efficient code, and how to use various software engineering tools such as make and git. However, we have no other class that teaches software design: how to decompose a complex problem into modules that can be implemented and maintained relatively independently. In CS 190, the primary focus is on complexity: how can we build systems that are as simple as possible, so they can be written quickly and maintained easily?

At the beginning of the class you will learn a set of philosophical principles to guide software design. You will then attempt to apply these principles in a series of programming projects. We will use code reviews and project revisions to improve your ability to work with the design principles. The overall goal for the class is to change the way you think about software design and to give you a foundation that can help you develop into an elite programmer. All of the programming for this class will be in C++; prior C++ experience is essential. This course is based on the material in the book [A Philosophy of Software Design](https://www.amazon.com/gp/product/173210221X?pf_rd_r=3BHQ3F7KKFW99APD4VG2&pf_rd_p=1ab92b69-98d7-4842-a89b-ad387c54783f&pd_rd_r=61dc7911-3d18-4357-a09e-1c84797620fc&pd_rd_w=KkY2M&pd_rd_wg=vOvJT&ref_=pd_gw_unk), which can be purchased from Amazon (be sure to get the Second Edition). I will not go over the material of the book in detail in lecture, but the material is essential for the class; I will refer to it extensively during the course. You should read the entire book except for Chapters 19-20, which are optional, and familiarize yourself with this material by the first Friday of the quarter.

CS 190: Software Design Studio

Android (operating system)

Human–computer interaction

Framework vs. Toolkit vs. Library

Android software development

Java (programming language)

Animation

User Interface Layout

Visual Perception

Application security

Accessibility

Event (computing)

Interactor hierarchy

Finite-state machine

Motor control

Fitts's law

Usability testing

Data analysis

Application Design Principles

Mental Models

Undo (Computing)

Persuasive technology

Location Services

Sensors

Dark pattern

CSE 340 Interaction Programming University of Washington Spring 2022 This course focuses on the design and programming of interactive systems, exploring various programming paradigms, event handling, and accessibility. It requires prior knowledge of Java and familiarity with data structures. This course helps to develop user-friendly interfaces and study existing interfaces. Although the platform used is Android, it's not strictly an Android programming course. Interactive technology is changing society. Some of today’s interfaces are used by a billion people at a time. Almost everything we create is created for people to use, through user interfaces. We will learn about interactive systems, including programming paradigms and design of event handling, layout, undo, accessibility and context awareness. ## Why should I take this class?

Interfaces are an important part of our daily lives and many of them are created as a connection from a human to a machine. Even a new machine learning algorithm or a database system requires some human connection in order for those systems to work.

User interfaces are incredibly important, but interactive user interaction requires a different programming paradigm than you may have learned before. In this you will learn how to:

- write an event-driven program which reacts to user input and displays output using abstractions in a structured and maintainable way. These abstractions generally transfer to almost any other user interface toolkit.
- think about the design and implementation of novel interaction techniques such as voice based interfaces or augmented reality, in order to enrich the user experience.
- build inclusive and accessible user interfaces.
- implement implement user-centered features, such as Undo, that following well studied design principles that are applicable in any user interface.
- critique and study existing user interfaces using light weight informal and formal methods.
- communicate your findings through comprehensive reports as well as reflections on your learning

The [Course Details](https://courses.cs.washington.edu/courses/cse340/22sp/course-details.html) page describes each of our course modules as well as other classes that complement the learning goals in CSE 340.
 The only official requirement for this class is that you have taken **CSE 142 and 143 or an equivalent class**, meaning you are comfortable programming in Java, and have some experience with data structures.

There are other skills that are required for the class that are not explicitly taught, which means you should **plan to spend extra time (either independently or in OH) learning and practicing those skills**. These include:

- working in an Integrated Development Environment (IDE) that is more complicated than JGrasp
- Using a version control systems (Git)
- Reading and understanding library and toolkit documentation
- Reading and understanding a larger starter code base
- Reflecting on and explaining the coding work you have done
- Reading through assignment specifications which are “more complicated and less detailed” than a typical Introduction to CS assignment specification.

Taking CSE 391 just before or concurrently with 340 can help, but our staff can also assist where needed.

The specific platform and language for this class are **Java on Android phones** (or simulators); using the IntelliJ IDE (Android Studio). While Google is switching over to Kotlin, there are good reasons to [start learning Android with Java first](https://dzone.com/articles/java-vs-kotlin-which-language-android-developer-sh).

Note that this class is designed for CSE majors, and other students who work regularly with information technology and are strong programmers. While we will consider applications from outside the major, other restrictions may limit space for such students. ### What should I expect as a student in this class?

This is an **interaction programming course** which will teach the abstractions that underly all user interfaces (see the [Course Details](https://courses.cs.washington.edu/courses/cse340/22sp/course-details.html) page for more information). To learn these concepts, we will cover a mix of theoretical aspects of HCI (such as how to predict the time it will take to click on a button, or why Undo is important to implement) and practical aspects of HCI (such as how to handle user interface events). What we will not cover is Android programming.

To re-iterate, *this is not an Android programming class and you will be expected to research Android programming yourself*. We will point you at the relevant of Android documentation but you must be willing to read through and explore this documentation on your own.

Taking any class is a commitment, and this one is no exeception. We want to make sure you get the most out of your experience. Below is some information about prerequisites and expectations.

CSE 340 Interaction Programming

Reasoning

Specifications

Data Abstraction

Abstract Data Type (ADT)

Abstraction Functions (AFs)

Representation Invariants (RIs)

Software testing

Identity (object-oriented programming)

Hashing

Equality

Assertion (software development)

Exception handling

Module Design & Style

Subtypes

Generics

Event-Driven Programming

TypeScript

React

HTTP Servers

Web Clients

Software design pattern

JSON

CSE 331 Software Design & Implementation University of Washington Spring 2022 This course aims to improve students' software development skills, focusing on building correct, scalable, and easy-to-understand software. It relies on a solid understanding of Java and the concepts covered in CSE 143. Students will learn about software design principles, modern programming languages, and software tools. It covers software testing, type systems, design patterns, and more. The aim of this course is to help students write programs of higher quality and increased complexity. This requires creating software that is correct, easy to change, easy to understand, and easy to scale. The course covers principled approaches to achieving each of these. The aim of this course is to help students write programs of higher quality and increased complexity. This requires creating software that is (1) correct, (2) easy to change, (3) easy to understand, and (4) easy to scale. We will study principled approaches to achieving these four goals.

After completing this course successfully students should be able to:

- Successfully build medium-scale software projects in principled ways
- Understand the role of specifications and abstractions and how to verify that an implementation is correct, including effective testing and verification strategies and the use of formal reasoning
- Analyze a software development problem and be able to design effective program structures to solve it, including appropriate modularity, separation of abstraction and implementation concerns, use of standard design patterns to solve recurring design problems, and use of standard libraries
- Use modern programming languages effectively, including understanding type systems, objects and classes, modularity, notions of identity and equality, and proper use of exceptions and assertions
- Use and learn new contemporary software tools, including integrated development environments, test frameworks, debuggers, version control, and documentation processing tools

In this class, we will use Java and associated tools like IntelliJ, JUnit, JavaDoc, and git, but the goal is to understand the underlying ideas and concepts that are generally applicable to software construction. The only formal prerequisite is CSE 143. We will very much rely on a thorough understanding of the concepts from CSE 143 as well as Java programming skills. We will go much further and you will be challenged to approach software development much differently than you have in CSE 143 or other courses. ### Texts

The required text for the course is the following:

- Effective Java by Joshua Bloch, 3rd ed., Addison-Wesley, 2018.

Contains a great deal of distilled wisdom about Java best practices, technical details, and style issues.

There will be assigned readings from this book during the quarter, and there will be questions on the exams about those readings.

Besides the required text, the following books may be helpful to you:

- The Pragmatic Programmer by Andrew Hunt and David Thomas, 20th anniversary (2nd) edition, Addison-Wesley, 2020.

Contains a great deal of distilled wisdom about software construction and the craft of programming, including many things that those who read the book later in their careers wish they had learned early on.

- Program Development in Java by Barbara Liskov and John Guttag, 1st ed, Addison Wesley, 2000.

The content of this well-written book closely mirrors much of the content of the course. The only downside is that it was written 17 years ago, so it is out-of-date with regard to some of key parts of the Java language and libraries. Nonetheless, it is a good place to look for another presentation of the material covered in class, if you can ignore those parts.

- Core Java Vol. I - Fundamentals by Cay Horstmann, 10th ed, Prentice-Hall, 2016; 11th ed, 2018.

This is a good general reference for the Java language and basic libraries. While technical documentation for these things is available on the web, the discussions in a book like this one are usually easier to follow and typically include advice not found in the formal documentation. Either recent edition will cover what we need for CSE 331.

CSE 331 Software Design & Implementation

Contracts

Data structure

Ghosts

Semantics

Regular Expressions from Axioms

Dynamic Logic

Compositional Reasoning

Array (data structure)

Induction

Convergence

Predicate transformer semantics

Sequent Calculus

Resolution

Propositional Encodings

DPLL

Sound Transformations

Satisfiability Modulo Theories (SMT)

Equality and Arrays

SAT Certificates

Blasting & Quantifiers

Temporal logic

15-414 Bug Catching: Automated Program Verification Carnegie Mellon University Spring 2022 This course is about software verification, with the goal of writing bug-free code. Students will learn to formalize program correctness, write verified code, and use automated tools for verification. It explores the principles behind verification tools, logical specifications, and deductive reasoning. Previous knowledge in program correctness reasoning is beneficial. High-profile bugs continue to plague the software industry, leading to major problems in the reliability, safety, and security of systems. This course teaches students how to write bug-free code through the process of software verification, which aims to prove the correctness of a program with respect to a mathematical specification. Along the way, students will learn how to:

- Specify correct program behavior
- Prove the correctness of their code
- Use formal semantics to reason about the soundness of proof rules
- Write practical and efficient verified code
- Use decision procedures and model checkers to reduce verification effort

Students will learn the principles and algorithms behind automated verification tools, and understand their practical limitations while gaining experience writing verified, machine-checked code that solves real problems. **Identify and formalize program correctness.** In order to reason about the existence of bugs in code, and ultimately justify their absence, we need to state what it means for the code to be correct. Students will learn how to formalize correctness using logical specifications that give precise meaning to the program's intended behavior.

**Understand how to write correct software from the ground up.** Writing good specifications of program correctness is essential to showing that there aren't any bugs in the code, but it is also useful for writing good code from the start. Students will develop experience reasoning about correctness as they implement functionality, learning how to write code that establishes and preserves properties and invariants needed to meet a target specification.

**Apply rigorous reasoning to program correctness.** Program verification is the process of mathematically proving that all possible behaviors of a given program adhere to its specification. Students will learn how to use deductive reasoning and state space exploration to realize this goal, and gain experience verifying their own code against logical correctness specifications.

**Learn to use automated tools to aid in verification.** Formally verifying real code is challenging, but given the scale of modern software, can also be tedious and labor-intensive. A number of tools exist for automating key parts of the verification process, notably deductive verification tools and model checkers. Students will learn how to use these tools when developing correct software, and gain experience applying them to non-trivial implementations.

**Understand how verification tools work.** Verification tools are not perfect, and will never be able to scale universally to all software development needs. Understanding the principles and techniques that these tools use is necessary for evaluating when it is appropriate to use a particular tool, and for addressing a tool's limitations when they arise in practice.  There is no textbook for this class, and detailed lecture notes will be posted to the website within a few days after each class. Keep in mind that lecture notes may not contain everything we cover in class. Comments and corrections are welcome, please give them to the course staff on Piazza.

15-414 Bug Catching: Automated Program Verification

Software engineering is the application of engineering principles to the design, development, and maintenance of software systems. Common subtopics include Integrated Development Environment (IDE), Version Control, Testing, Debugging etc. It is an essential field for anyone interested in pursuing a career in software development or a related field.

Software Engineering

Computer Science

Software Engineering

Prerequisites

Common concepts