Pattern-Oriented Software Architecture For Dummies

Foolish Assumptions

I make some assumptions about who would read and benefit from this book. I don't expect that you're an expert in software architecture; in fact, I assume that you're pretty new to it. I do assume that you know something about writing software, however, and that you've already written some software. In particular, I assume that you've written software in some sort of team setting on a project bigger than a school project. From this experience, you'll have learned about designing with modules and components.

Because more software is changed, evolved, and maintained than written from scratch, I assume that you've experienced some software maintenance. Maintenance of someone else's (or even your own) code will have given you an understanding of the importance of modularity and good structure.

I don't assume that you're an expert in object-oriented design or any other particular design methods. The architectures in this book can be adapted to any paradigm you work in and are familiar with. Some familiarity with at least the basic terminology of objects, classes, and methods is assumed.