Publisher: O'Reilly, 2005, 332 pages
Keywords: Information Systems
Business process modeling (BPM) provides a platform that enables process, domain, and technical experts to communicate and build applications. In Essential Business Process Modeling, Michael Havey, experienced architect and integration expert, explains clearly and concisely the concepts and standards surrounding BPM and provides examples of the technology in action. In addition to practical information and examples for architects, this book includes an introduction to BPM, allowing project managers and enterprise architects to come up to speed.
In this book, Havey explains everything you need to know about BPM, including:
Essential Business Process Modeling teaches you how to develop examples of process-oriented applications using free tools that can be run on an average PC or laptop. You'll also learn about BPM design patterns and best practices, as well as some underlying theory. The best way to model processes within an enterprise is with BPM, and the best way to navigate BPM is with this valuable book.
This is definetly not for the practicing manager, nor for any business person, as it is filled with jargon, technical information, references to different "standards" etc.
It includes syntaxical descriptions, sometimes in pseudo-languages and long listings in XML.
As a technical person, I find it too lightweight, as there is never any depth in the discussions, which are also flawed from time to time (transaction processing don't seem to be the authors forte).
As a former standards person, I see it as a project to try to dazzle the environment with a lot of abbrevations and pseudo-standards. It doesn't have to be presented like this in the real standards world, this is a choice of the author, and where he fails miserably.
My impression after having read this book, is that BPM should fail miserably, due to confusing "standards", nomenclature confusion, low theoretical treshhold, limited practical experience of the few practitioners and badly written software. Fortunately, I know this is not the overall case, but it is the impression puts forward.
In other words, it is not even well-written, and contains a lot of bull.