Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Inevitably, the authors devote a great deal of the book to business patterns--26 of them in all. However, these follow logically from the earlier chapters. As well as providing a basis for your own models these patterns illuminate and expand on the earlier explanatory material. Interestingly, one of the aims of Business Modeling With UML is to extend the usefulness of the technique from software engineers--by and for whom it was designed--to a range of business processes not necessarily directly concerned with programmatic information systems. In practice, it's hard to see a general manager sitting down to model processes in UML. UML itself requires a grasp of object oriented programming techniques you're unlikely to pick up by accident. However, this excellent book should help IT managers demonstrate how they can proactively contribute to a company's success instead of being seen as a low level resource called on only when a new accounting module is needed.--Steve Patient
The book makes a strong case for the advantages of modeling businesses in UML. With models, an organization can provide better software, define and implement new goals, and even decide whether to outsource certain operations. The Erickson-Penker Business Extensions for UML, invented by the authors and presented within the text, permit UML to document the entire business enterprise. This book shows how to model businesses, from business architecture to processes, business rules, and goals. Short case studies--for Web-centric and more traditional companies--are used to illustrate key concepts here.
Later sections of the book will perhaps take a little more background in software engineering to appreciate fully as the book presents a handful of business patterns, which offer reusable solutions to common problems (just like software patterns). The authors also look at how to leverage a business model to create better software.
In engineering, a new car is modeled and thoroughly tested on a computer before any physical prototype is ever built. As the authors point out, a business that has accurate models can test out new ideas cheaply and then adapt to changing market conditions quickly. This title makes a case that UML--a tool traditionally used by software developers--is ready to tackle the job. Read this notably informative and intelligent book to see the possible benefits of business modeling in UML for your organization. --Richard Dragan
Topics covered: Business modeling basics, UML notation and Erickson-Penker Business Extensions, class diagrams and powertypes, object diagrams, statecharts, activity diagrams and swimlanes, sequence and collaboration diagrams, collaboration and use case diagrams, component and deployment diagrams, stereotypes, business architectures, business processes, resources, goals, business rules, Object Constraint Language (OCL) and collections, business views and patterns, business goal allocation, business goal decomposition, business goal-problem, and software architectures
Tags(Was ist das?)Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte. |
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.
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.
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.
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
|