Conventions Used in This Book

Here are the conventions I use throughout this book:

  • I capitalize the names of patterns. In some chapters, the name of the pattern is the same as the name of a key component of the architecture. In general, the pattern name is capitalized, and the name of the component is not capitalized.
  • I abbreviate the names of many of the patterns discussed in Parts III and IV because they're quite long. Model-View-Controller, for example, becomes MVC. On the first use in a chapter, the whole name is spelled out, and the abbreviation is used thereafter.
  • When I introduce a new term, I put it in italics and define it shortly thereafter (often in parentheses).
  • I put web addresses in monofont so they stand out from the surrounding text. Note: When this book was printed, some web addresses may have needed to break across two lines of text. If that happened, rest assured that we haven't added extra characters (such as hyphens) to indicate the break. So, when using one of these web addresses, just type in exactly what you see in this book, pretending as though the line break doesn't exist.

Get Pattern-Oriented Software Architecture For Dummies now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.