Engineer Your Software!

Preface
Who Should Read This Book
How This Book is Built
Acknowledgments
Engineering is a Verb
	What is Engineering, Exactly?
	Engineering as Experiment
	Software Should be Cynical
	Engineering is NOT ``Anti-Agile''
	Toward More Principled Design
		Single Responsibility
		Open-Closed
		Liskov Substitution
		Interface Segregation
		Dependency Inversion
		One Copy of Data
		Keep Business Logic in its Place
	What Makes a Design ``Good''?
		Sufficiency
		Completeness
		Cohesion
		Complexity
		Coupling
		Primitiveness
		Similarity
		Volatility
	A Word About Our Case Study
	Summary
	Further Reading
Architecture Matters
	It's All About the Problem You Are Solving
	Create a Pattern Language for Your Solution
	What Influences Architecture?
		Problems Have a Shape
		Where Should Things Go?
		How Many Users are There and How Many Time Zones?
		Where is the Data Generated and Used?
		What are the Availability Requirements?
		What Scale and Scalability do You Need?
		What Level of Performance is Required?
		Where Does Volatility Live?
		Security, Always Security
	Choose Wisely
		Programming Style
		Design Approach
	With All That, There are Shortcuts
	Summary
	Further Reading
Solve the Right Problem
	Four Domains of Design
		Problem Domain
		Application Domain
		Application-Specific Domain
		Application-Generic Domain
	Problem Domain Design
		Identify System Responsibilities
		Identify Problem Domain Abstractions
		Identify Structures
		Identify Communication Patterns
		Identify Timing and Concurrency Constraints
		Identify and Describe Attributes
		Identify Instance Connections
		Identify Abstraction States
		Identify Services
		Identify Message Connections
		Simplify the Model
	Summary
	Further Reading
Engineer Deliberately
	A Couple of Things to Keep in Mind
		Abstractions Have a Life
		Abstractions Need Hands and Legs
	Set the Boundary
	Border Control
		People as Roles
		Events are Just Messages
		Devices are Like Users (Mostly)
		Mix-In Ingredients for Role Enforcement
		Passwords?
	Acknowledge the CRUD
	Combating Volatility
		Isolation
		Dynamic Attributes
	It's OK to Inherit for Reuse
	A Strategy for Substitution
	Decorative Modifications
	Addresses Everywhere
	Dealing with Those Pesky M:N Relationships
		The Normal Solution
		When Normal Doesn't Work: The Lowly Shipment
	The Transaction as Time Capsule
	Beware of Shared Resources
		Logs and Audit Tables: Not Just for Auditing Anymore
		Data Access
		Delegate, Delegate, Delegate
	Simplify the Model
	Test your Design
	Summary
	Further Reading
Make Your Life Easier Down the Road
	Picking Teams
		Do I Need to See You?
		Components that Change Together Go Together
		Components That are Used Together Go Together
	Can I Get Here from Here?
	Don't Forget to Look Outside Your Code
		Your Application is Not Alone
		Redundant Geography
		Pool Connections
		Cache Content
		Push Content to the Edge
		Precompute Values
		Create Steady States
		Database Replication
		Auto-Generated Database Keys
		Consider Machine Learning
		Make Room for MATLAB®
	Summary
	Further Reading
Conclusion
Bibliography
Author's Biography
Blank Page