Principles of Software Construction
Minimum price
Suggested price


Journalists and bloggers: please do not publish anything about this until the embargo is lifted!

Please contact the author for more information about when this is.

Principles of Software Construction

About the Book

About the Author

Table of Contents

  • Introduction to Java
    • An Introduction to Java
      • Objectives of CPEN 221
      • Objectives for this Reading
      • What is Java?
      • Java Programs and the JVM
      • Hello World! in Java
      • Of Classes and Objects
  • Static Checking, Testing and Code Reviews
    • Static Checking
      • Objectives for This Reading
      • Hailstone Sequence
      • Types
      • Static Typing
      • Static Checking, Dynamic Checking, No Checking
      • The Goal of CPEN 221
      • Why we use Java in this course
    • Testing and Code Review
      • Validation
      • Putting on Your Testing Hat
      • Test-first Programming
      • Why Software Testing is Hard
      • Choosing Test Cases by Partitioning
      • Blackbox and Whitebox Testing
      • Automated Testing and Regression Testing
      • Code Review
      • Smelly Example #1
      • Smelly Example #2
      • Smelly Example #3
      • Summary
  • Specifications
    • Need for Specifications
      • Why Specifications?
      • The Role of a Specification
      • The Structure of a Specification
      • Testing and Specifications
      • Specifications for Mutating Methods
    • Exceptions
      • Exceptions for Signalling Bugs
      • Exceptions for Special Results
      • Checked and Unchecked Exceptions
      • Throwable Hierarchy
      • Exception Design Considerations
      • Abuse of Exceptions
      • Test Yourself
    • Designing Specifications
      • Deterministic vs. Underdetermined specs
      • Declarative vs. operational specs
      • Stronger vs. Weaker Specifications
      • Diagramming Specifications
      • Designing Good Specifications
      • Precondition or Postcondition?
      • About Static vs. Instance methods
      • Summary
  • Debugging
    • How To Avoid Debugging
      • Objectives
      • First Defense: Make Bugs Impossible
      • Second Defense: Localize Bugs
      • Assertions
      • What to Assert
      • What Not to Assert
      • Incremental Development
      • Modularity & Encapsulation
      • Summary
      • Test Yourself
    • How to Debug
      • Instance Diagrams
      • Debug Systematically
      • Fix the Bug
      • Summary
    • Mutability and Immutability
      • Risks of Mutation
      • Specifications for mutating methods
      • Iterating over arrays and lists
      • Mutation undermines an iterator
      • Mutation and contracts
      • Useful immutable types
      • Summary
  • Abstract Data Types
    • Abstract Data Types
      • What Abstraction Means
      • User-Defined Types
      • Classifying Types and Operations
      • Designing an Abstract Type
      • Representation Independence
      • Why Interfaces?
      • Testing an Abstract Data Type
      • Invariants
      • Immutability
      • How to Establish Invariants
      • Summary
    • Rep Invariants and Abstraction Functions
      • Rep Invariant and Abstraction Function
      • Checking the Rep Invariant
      • Summary
    • Interfaces
      • Interfaces
      • Example: MyString
      • Example: Set
    • Subtypes
      • Subtyping
      • Subclassing
      • Subtyping vs. Subclassing
      • Summary
      • Test Yourself
    • Equality
      • Abstraction Function and Equality
      • Three Ways to Regard Equality
      • vs. equals()
      • Equality of Immutable Types
      • The Object Contract
      • Equality of Mutable Types
      • The Final Rule for equals and hashCode()
      • Expressing Ordering
      • Summary
  • Notes

The Leanpub 60-day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms

80% Royalties. Earn $16 on a $20 book.

We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub