- Taschenbuch: 292 Seiten
- Verlag: Wiley; Auflage: 1 (20. Dezember 2006)
- Sprache: Englisch
- ISBN-10: 0470027215
- ISBN-13: 978-0470027219
- Größe und/oder Gewicht: 19,1 x 1,7 x 23,7 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 971.561 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Business Rules Management and Service Oriented Architecture: A Pattern Language (Englisch) Taschenbuch – 20. Dezember 2006
|Neu ab||Gebraucht ab|
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Business rules management system (BRMS) is a software tool that works alongside enterprise IT applications. It enables enterprises to automate decision-making processes typically consisting of separate business rules authoring and rules execution applications. This proposed title brings together the following key ideas in modern enterprise system development best practice: the need for service-oriented architecture (SOA); how the former depends on component-based development (CBD); database-centred approaches to business rules (inc. GUIDES); knowledge-based approaches to business rules; and, using patterns to design and develop business rules management systems. Ian Graham is an industry consultant with over 20 years. He is recognized internationally as an authority on business modelling, object-oriented software development methods and expert systems. He has a significant public presence, being associated with both UK and international professional organizations, and is frequently quoted in the IT and financial press.
"SOAs and business rules are two of the hottest and most misunderstood topics in our industry. Graham's book does a very good job of explaining these concepts and presenting their symbiotic relationship to each other."
Author of "Universal Meta Data Model" and "Building and Managing the Meta Data Repository"
Universally recognized as the world's leading authority on Meta Data Management
Die hilfreichsten Kundenrezensionen auf Amazon.com
There is no orderly progression of concepts. There is no schematic, in pictures or words, of the knowledge that the reader is about to learn. It's just... I don't know. Partly a history of who said what about business rules since the 1980's, partly a rehash of OO, SOA and component concepts you can understand better by reading Wikipedia, and partly, perhaps mostly, a stream of conscious technical writing book thingie.
I read a lot of technical books. This one has very poor writing. If I knew a lot about business rules perhaps it would have been interesting. But, of course, that's not why I bought it.
Final complaint because I'm so irritated: why is there a caret over the 'o' in 'role' every time the word is used? Is the writer switching to French every time he uses that word? gggrrrrrrr
Ian builds on many of the basic methodology steps outlined in previous rules books (like Barbara von Halle's) and then adds a really interesting section (about a third of the book) or patterns for requirements, elicitation, development, writing and organizing business rules. While some are fairly straightforward it is still a nice set and an interesting approach very suited to a more flexible methodology (like agile or similar).
I enjoyed the book and if you are looking for an up to date book on rules and SOA this should be on your list.
As an enterprise architect I came across themes like architecture principles, SOA and business requirements. Business rules in relation to architecture is a much debated issue. So when I came to be involved in a Business Rules project for a customer, I decided to arm myself. What did the book deliver? Well:
- clear and pleasant writing style.
- answers to FAQ right from the preface.
- relate BR to SOA.
- functional and management perspective. Technology and concepts. Not too deep, not to hi-over.
- insight in leading products (be it anno 2007, but good enough for a benchmark).
- 42 (:-) solution patterns.
- a checklist for evaluating BRMS's.
Ähnliche Artikel finden