Professor in software engineering at Delft University of Technology. I use this account mostly for professional books on software engineering, testing, and technical leadership.
This link opens in a pop-up window
Solid 700 page coverage of classical software architecture, including styles, connectors, Architecture Description Languages (ADLs), adaptation, and domain-specific software engineering.
Being an architect is no longer about drawing UML diagrams and studying architectural styles. Rather, …
Argues that the successful architect should easily navigate between “engine room” (in the basement) and the boardroom (at the top of the sky scraper). Book based on years of experience from the trenches.
Don’t miss Hohpe’s 50 min. techtalk summarizing the key points of this book. www.youtube.com/watch?v=Zq2VcRZmz78
See also the summary on Martin Fowler’s bliki. martinfowler.com/articles/architect-elevator.html
More and more Agile projects are seeking architectural roots as they struggle with complexity and …
A book targeting smaller teams, with a strong focus on delivering (customer) value.
Good software developers often adopt one or several architectural patterns as strategies for system organization. …
The classic that bootstrapped the field of software architecture
Software Systems Architecture is a practitioner-oriented guide to designing and implementing effective architectures for information …
I've used this book for several years while teaching software architecture to master students in computer science at TU Delft. The book is based on extensive experience from the authors working for large IT organizations. The book encodes years of experience in a systematic set of (UML-like) diagrams reflecting the basic premises of the book: Software systems are built to meet architectural properties desired by stakeholders, and are realized by means of viewpoints and crosscutting perspectives. The distance to the world of students is quite large, making it less suitable for teaching.
Test-Driven Development (TDD) is now an established technique for delivering better software faster. TDD is …
Great wisdom from the inventors of mock objects.
Our goto book when we built the first product in our start up back in the year 2000. An inspiration.
The year it appeared (in 1999) I presented a summary at CWI where I worked. A classic.
A concise summary describing how to properly use UML
These are the revised and illustrated notes of the Software Architecture lecture of the Master …
Strong and original take on software architecture. The writing is a transcript of actual lectures — the content would deserve a more carefully worded book though.
My favorite pattern book since 2000, grouping patterns into architectural, design, and code (idiom) level, covering layers, model-view controller, microkernel, proxy, and more. A bit dated of course, but still an inspirational read.