Business Modeling With UML: Business Patterns at Work

I'm not much a reader; however, this book is an excellent resource and handy. Useful for assisting in times when you feel like you've come upon a wall.

I've found this very helpful.

One of the weaknesses of the Unified Modelling Language is its relatively limited support for modelling at the Enterprise level, especially to accurately model business processes. The UML purists believe that everything should be reduced to Use Cases, while these authors recognise that much more is necessary.The book covers five quite distinct topics:1. An introduction to business modelling and UML, explaining the problems the authors want to help solve, and describing each of the relevant techniques of UML,2. A proposal for a group of extensions to UML (using that language's own established extensibility mechanisms) so that that it can better model business processes,3. A description of the variety of views and models which will be required to establish a comprehensive understanding of the business, or at least part of it,4. A repository of "business patterns", which you can use to model the business,5. A comprehensive worked example.Each of these is quite detailed. In particular, the book contains probably the best introduction to the Object Constraint Language (OCL), and its use to model business rules, that I have read anywhere. The sections on how to do business modelling are also very good, as are the introductions to the relevant UML techniques.The "Eriksson-Penker extensions for business modelling" are important because several UML-based case tools have now implemented them as an emerging standard for business process modelling with UML. If you want to fully understand how these work, this is the book to read.The business patterns are more of a "curates egg". Some are extremely useful, and others innovative which could easily solve your problems where there is an accurate match. That said, some are less good and seem to state the obvious, although with patterns it is always difficult to know if you are judging some harshly simply because you are so familiar with them and other readers will get more value. Some of the pattern explanations are a bit repetitive, and the "examples" often sound very artificial, but overall they are useful, and a single one which solves a real business modelling problem for you will justify the rest.At over 400 pages, some of which is occasionally slightly slow and ponderous this is not an ideal book to read from cover to cover. But it is definitely one to study, focusing on whichever topic is most relevant to you at any time, and I can happily recommend it.

Sometime ago I have been wondering if somebody will try to bridge the gap between business modeling (the one used by consultants) and software engineering. It would certainly make it easier for people to understand and explain business operations.This book is an application of the UML into the realm of business modeling. It is very good in the sense that it explains and goes through the patterns that form business models. The introduction on UML is pretty short and concise, so if you are new to it try using "Applying UML..." book to get an introduction. Be prepared to sit down and spend some time reading, since the material can be a little bit daunting to try to understand and remember all the patterns available. Overall, I wish I had this book for Systems Analysis instead of the outdated software engineering books that we used.

While I didn't really enjoy UML Toolkit I do enjoy this book. The presentation and writing styles are same between books however, which are very structured and easy to follow however.This book does a wonderful job of discussing the "design patterns" around the activities of a business, this is it's strength. While I haven't yet mapped these out in UML to a business I think they can stand on their own outside of UML. UML just makes the flow more understandable.Overall the design patterns are enough to recommend it. Very novel and useful!

I am looking for a book that would be able to flesh out proper business processes utilizing well defined modeling language/framework. Although UML is extremely useful for software development, the author's work did make its case stand with me on UML's usefulness as business process modeling tool.The examples are too simplistic and the suggested modeling diagrams are far too cluterred for a business personel to understand.(Cluttered diagrams on a simple example) The book would be better if it had a growing case study and used real world examples and diagrams.

I enjoyed the concepts, and the book is actually very readable. But when it came time to start applying the techniques my tune changed a bit. If you are using a simple drawing tool (like Visio or similar) to render your UML diagrams, then this book may be helpful to you. If you are using a more sophisticated tool like Rational Rose, then I think you will have difficulty creating the necessary business extensions and stereotypes. (Is that a criticism of the book or of Rose - you decide).Another criticism is that the authors appear to have made themselves readily available for questions and additional info, but in fact this is not true in my case. Also the the URL that is provided on page xix (in the introduction), which is supposed to contain additional examples and articles is no longer available. I hate that! It appears as though the authors have left this book behind them, so perhaps you might as well to.If you are in the inception phase of a business modeling initiative and you are using Rational Rose, then I would not recommend attempting to apply the techniques in this book with that toolset.

This book covers many aspects of business modeling. Using the patterns to solve our problem domain.We can make some view of business, they are business vision view, business process, business structure, and business behaviour.Thanks to Eriksson-Penker Business Extension. We can simplify our complex business using this extension.

One of the weaknesses of the Unified Modelling Language is its relatively limited support for modelling at the Enterprise level, especially to accurately model business processes. The UML purists believe that everything should be reduced to Use Cases, while these authors recognise that much more is necessary.The book covers five quite distinct topics:1. An introduction to business modelling and UML, explaining the problems the authors want to help solve, and describing each of the relevant techniques of UML,2. A proposal for a group of extensions to UML (using that language's own established extensibility mechanisms) so that that it can better model business processes,3. A description of the variety of views and models which will be required to establish a comprehensive understanding of the business, or at least part of it,4. A repository of "business patterns", which you can use to model the business,5. A comprehensive worked example.Each of these is quite detailed. In particular, the book contains probably the best introduction to the Object Constraint Language (OCL), and its use to model business rules, that I have read anywhere. The sections on how to do business modelling are also very good, as are the introductions to the relevant UML techniques.The "Eriksson-Penker extensions for business modelling" are important because several UML-based case tools have now implemented them as an emerging standard for business process modelling with UML. If you want to fully understand how these work, this is the book to read.The business patterns are more of a "curates egg". Some are extremely useful, and others innovative which could easily solve your problems where there is an accurate match. That said, some are less good and seem to state the obvious, although with patterns it is always difficult to know if you are judging some harshly simply because you are so familiar with them and other readers will get more value. Some of the pattern explanations are a bit repetitive, and the "examples" often sound very artificial, but overall they are useful, and a single one which solves a real business modelling problem for you will justify the rest.At over 400 pages, some of which is occasionally slightly slow and ponderous this is not an ideal book to read from cover to cover. But it is definitely one to study, focusing on whichever topic is most relevant to you at any time, and I can happily recommend it.