A Pragmatic Guide to Business Process Modelling |
 |
 click here for more details, find new or used items |
Jon Holt
|
|
Pages: 240 (Paperback)
ISBN: 1902505662
Pub: British Computer Society
Pub date: 2005-09-26
Amazon.co.uk Sales Rank: 12340
Reader Reviews:
An excellent guide to process modelling! (0/0 people found this helpful)
John Holt has presented thoroughly all that surrounds the notion of business process modelling. The first two chapters of the book smoothly introduce the reader to a range of basic concepts for business process modelling. The remaining chapters are solely dedicated in detailed descriptions of UML and its different process views.
There are numerous diagrams which clearly depict the level of detail to which process modelling should be done. The sixth and final chapter of the book describes a case study applying the material presented throughout the book. I believe that was a great idea from the author's point of view, since process modelling is not an art that can be tought without practical examples at hand. It made things a lot easier to understand.
I would highly recommend the book to all IT professionals involved with process modelling activities within their organisation.
UML v. Other Notations - a Question of Purpose (8/9 people found this helpful)
I think the debate about using UML v. other notations or methods should be considered from the point of view of what is the purpose and objectives of your modelling. If you are developing process models for a process improvement type initiative, where diagrams need to be shared and reviewed by a large audience of non-technical business users, then UML, in my experience, is probably not the right approach.
UML is an excellent approach when it comes to systems / software engineering, system architecture design and requirements management; but not as a method for sharing and communicating business process models across the organisation.
A more easy to understand notation will be much more effective, and it seems that BPMN has now become a well established approach for this purpose. Additionally, I think that the fact that the OMG chose to develop the BPMN standard in addition to UML speaks for itself (as you may know, the Object Management Group - OMG, is responsible for the development of both standards). Therefore, in my opinion the approach offered in the book is more suitable for technical analysts not for people running a business focused process modelling initiative.
However, I do agree with the author's key point about the fact that in order to fully understand the process complexities there is a need to document more then just the process flow (conduct a 360 modelling, but which comes more under the domain of Enterprise Architecture not purely process modelling).
Furthermore, various process modelling tools today do offer the ability to easily capture many additional dimensions then just simple flow diagrams. I found the approach advocated by Ian Gotts in his book "Common Approach, Uncommon results" highly effective for getting organisations to document their processes and gain the benefits from doing so.
Don't be fooled by the title (3/4 people found this helpful)
I bought this while studying for the British Computer Society exam on process modelling - expecting a good practical book like many other BCS publications. Instead what the book provides is a somewhat esoteric / academic mediation on the nature of business process models, expressed (sometimes in a rather contrived way) through UML.
It might be interesting, I may come back to it - but it certainly wasn't going to help me though my exam so it went on the bookshelf. If you are looking for a practical hands on guide - as the title implies - look elsewhere.
To join in the mini-debate here of course you can use ULM for business process modeling. I have been doing so for 10 years, and no business users don't run a mile - they find use case and activity diagrams immensely useful and practical tools in expresing busines process.
I just don't think this is a particulalry helpful book on using UML with business people, try UML Xtra-Light by Milan Kratochvil and Barry McGibbon instead.
Buisness Process Modelling - why not? (3/4 people found this helpful)
Why not use UML for business process modeling? No reason what so ever, as long as the modeling language fits your purpose. With tools such as Rhapsody and EA, UML may help you accomplish a suitable solution. For systems architecture, modeling and requirements gathering UML is very well supported.
However there are usually more than one path to a solution, dont be blinkered.
UML for business modeling - lets not go there! (4/7 people found this helpful)
I bought this book being a business modeling junkie, with close to 20 years experience.
My biggest issue is that UML CAN be used for business process modeling but the key word here is "business". UML, despite all the protestations to the contrary, is a IT techie thing and most business people/business analysts run a mile from it.
BPMN is the de facto standard for business process modeling. Yes it is flawed and lacks a meta model-soon to be addressed. But given that the OMG now "own" both UML and BPMN then hopefully these flaws will be addressed and sorted out.
Maybe a future edition of this book replacing UML for BPMN may fill a need in the market place but as it stands, UML for business process modeling - don't go there. The BCS should know better!
Similar Products
Writing Better Requirements
Writing Effective Use Cases (Crystal Series for Software Development)
Business Process Management: A Rigorous Approach
Essential Business Process Modeling
Categories
Amazon.co.uk places this book into the following categories:
Books -> Subjects -> Business, Finance & Law -> Management -> General AAS
Books -> Refinements -> Language (feature_browse-bin) -> English
Books -> Refinements -> Age (feature_two_browse-bin)
Books -> Refinements -> Format (binding_browse-bin) -> Paperback
Books -> Refinements -> Condition (condition-type)