I started reading Domain-Driven Design by Eric Evans last night. Started out a bit slow, but after about the first 60 pages I couldn't set it down.
In the first 200 pages, the books talks a lot about many of the ideas (terms) you hear day-to-day: Domain Model, Entities, Value Objects, Associations, Aggregates, Repositories, etc. Rather than focusing on code, the books references a lot of UML diagrams and mentions several design patterns you often see during the creation of the domain model. The book suggests your normal layered architecture, but especially isolates the domain model as a separate piece of the “business layer“.
This is one of those books that if read thoroughly will surely help you with software construction. In the future I hope to write specifics details about the book, but for now I need to concentrate on my chapter-by-chapter review of Expert C# Business Objects.