Architecture and Patterns for IT Service Management, Resource Planning, and Governance: Making Shoes for the Cobbler's Children

In software engineering, a design pattern is a general solution to a common problem . A design pattern isn t a finished design that can be transformed directly into [program] code; it is a description or template for how to solve a problem that can be used in many different situations.
Wikipedia [212.]
The concept of patterns, originating in building architecture and city planning, [213.] has been applied in computing for almost two decades. This book also uses a pattern language, but it does so at a higher level than the software engineering pattern literature; patterns of process, organization, data sourcing and flow, and human motivation are discussed. [214.]
[212.] Wikipedia contributors, Design Pattern (Computer Science), Wikipedia: The Free Encyclopedia, en.wikipedia.org/wiki/Design_ pattern_%28computer_science%29 (accessed July 17, 2006).
[213.] (Alexander, Ishikawa et al. 1977)
[214.] In this sense, the material is at the same level as some of the antipatterns work (see Further Reading at the end of Chapter 5). It s perhaps ironic that only negative antipatterns have been identified for IT management, and no positive pattern literature at this level is apparent. (Hopefully, this book will stimulate further work in this area.)
Integrated IT management is an emerging field, and this book takes some liberty in using the term pattern, which typically implies known uses. Some of these patterns are known to be used, but I do not wish to identify the companies there would be many complications in doing so. Others are inferred from considering...