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.

Approximate Topics

We expect to cover the following, with an emphasis on specification and design:

  • Reasoning about statements, loops, functions, and data types: pre- and post-conditions, invariants, and specifications
  • Testing: coverage, black- and white-box testing, test-first development, regression testing, JUnit
  • Debugging and assertions
  • More advanced Java language issues: generics, exceptions, equality, hashing, subclasses, overloading, and overriding
  • More advanced tools: IDE and version control
  • Code clarity: comments and JavaDoc
  • Program design: modularity, coupling, cohesion, and design patterns
  • User interfaces and event-driven programming


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.


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.



Lectures will be given in person, at the locations and times shown on the time schedule. One of these two lecture times will also be recorded, so that students who cannot attend can watch the video to stay up-to-speed.


Each week includes a TA-led quiz section, typically focused on preparation for the next homework assignment. These will not be recorded, but the printed material covered will be posted on the section list and calendar.


Homework will consist of 10 assignments, typically with one due each week. Assignments can require either solutions in the form of written answers or typed code or both. Generally, the amount of code required will increase as the course progresses. The first two assignments will be entirely written and the last five will be entirely coding.


The course will include a midterm exam, taken in class at one of the normal lecture times, and a final exam, during finals week. See the course calendar for the exact times and locations. Note that the final exam time & location may not be the same as the one listed on the university's final exam schedule.

The midterm will cover the material from the first five homework assignments, while the final exam will be comprehensive. The exams page will be updated with further information on the exam content before the exam dates.



You should expect and demand to be treated with respect by your classmates and the course staff. You belong here, and we are here to help you learn and enjoy a challenging course. If any incident occurs that challenges this commitment to a supportive and inclusive environment, please let the instructor know so the issue can be addressed.


Your overall grade will be determined roughly as follows (subject to change):

60% Homework assignments
15-20% Midterm Exam
20-25% Final Exam

Homework assignments are not weighted equally because they are of different length and sophistication. Later assignments are likely to be weighted more heavily because they are more involved. (The exact weighting will be determined later on.)

Students are expected to complete all homework assignments. Students who receive no (or essentially no) credit for an assignment risk failing. Outside of those circumstances, failing the course is highly unusual.

Grades of “incomplete” are reserved for situations covered by the UW policy.

Late Policy

Homework assignments are designed to be completed by the due dates listed. Situations may arise, however, where students are unable to complete the assignment by those dates. For that reason, we will allow students to submit assignments one day late with no penalty, provided that the following conditions are met:

  • You use no more than one late day per assignment. A “day” means 24 hours from the original due date/time.

  • You use no more than four late days total during the quarter.

Late work not meeting these conditions is only accepted with special permission from the instructor.

In addition, please note that:

  • Late days are atomic. You cannot, e.g., split up a late day into three pieces and submit three different assignments each 8 hours late.

  • Anything more than a few minutes late is just as late as something submitted the next day.

  • Late days are intended to cover any emergencies that arise. You should not plan to use up all your late days or you could be left without any when an emergency arises later on.

  • Finishing an assignment one date late means you have one fewer day to complete the next assignment.

For a description of how to submit a coding assignment late, see this document.

Staff Test Re-run

For some of the coding assignments, we will allow you to make changes to your assignments after the due date and have us re-run the staff tests on your updated solution. However, we will only change the correctness portion of your score, not style, design, etc. Furthermore, the maximum correctness score you can receive on a test re-run is 80%.

The purpose of this policy is to allow students who make minor mistakes that end up causing a large number of our correctness tests to fail to fix those mistakes and limit the point deduction to just 20% of correctness points.

By the end of the course, we expect students to be able to submit correct code the first time, as is expected of programmers in industry. For that reason, we will not re-run the staff tests on HW9.

Academic Integrity

Any attempt to misrepresent the work you submit will be dealt with via the appropriate University mechanisms, and your instructor will make every attempt to ensure the harshest allowable penalty. The guidelines for this course and more information about academic integrity are in a separate document. You are responsible for knowing the information in that document.


Please refer to university policies regarding disability accommodations or religious accommodations.


  • Do not skip class or section to work on homework, not even late in the quarter when you are more tired and busy. This will cost you time (not to mention learning) in the long run. Class will start promptly, and you will find the entire course easier and more educational if you arrive punctually, well-rested, and ready to pay attention for 50 minutes.

  • Start homeworks early. Aim to complete it the day before it is due. They are more difficult than assignments in earlier courses and you need time to make mistakes.

  • Consider buying a Java programming book (like Core Java). Past experience indicates that students tend to over-estimate the quality of the information to be found on the web and under-estimate the quality of the information found in such a book. You can ultimately save time by reading a book that is known to be high-quality and up-to-date instead of reading web pages that are either inaccurate or out-of-date only to find that their advice does not work for you.

  • Think about which lecture material applies to the homework you are working on. Each assignment is carefully designed to apply ideas from lecture, so if it does not seem that any lectures apply to what you are working on, there is a good chance that you are missing something. Knowing which ideas the homework is designed to apply should make it easier to complete. (The same point applies to exams.)

  • Learn a lot and have fun. The content of this course should be valuable for your career success. Mastering these ideas now will make later courses and projects easier.

    Also be sure to have fun. The ability of create things, solely with the power of your imagination, that express yourself and positively affect the lives of (potentially) millions of other people is a rare joy that, while available to anyone, most will never experience. For programmers, like yourself, it can be an everday occurrence. As you dig into the tools and techniques of programming, it is important not to lose sight of the big picture: programming should bring joy, not only to those that use the software you create but also to yourself. Please start by having fun in this class!