- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
Introduction to Business Architecture Paperback – Jul 22 2009
Special Offers and Product Promotions
Frequently Bought Together
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
1: Introduction to Business Architecture. 2: What Is Business Architecture Comprised Of? 3: How To Get There. 4: When Are We Done? 5: Representational Languages for Your Business Architecture. 6: Frameworks. 7: Understanding Your Business. 8: Practical Uses for Your Business Architecture.
About the Author
Chris Reynolds has been consulting in the IT industry for over 15 years, and has been doing business design work for over 20 years. He has performed business architecture work for wholesale and logistics companies, manufacturers, telecom companies, and financial institutions.
Inside This Book(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
Most Helpful Customer Reviews on Amazon.com (beta)
There was no mention of Business Capability Models (one of the main tools of the trade!), there were only very basic graphics that weren't helpful, and way too much text and lack of meaningful diagrams and examples of real business architecture in practice.
One example of repetition that I find in the book is Chapter 11 Representational Languages. While the chapter does discusses the available languages, it also discusses, one again, what should be included in each view. The author previously provided this information when discussing each view earlier in the book.
This is just one example of repetition. You can find plenty more examples throughout the book. The above example also highlights my concerns with structure.
The diagrams provided in the book appear to be thrown together in a haphazard manner with little or no concern for style or clarity. His BPMN diagrams, a powerful modeling language he trivialized, border on unreadable. They would make a great example of how not to put a model together.
I still have many questions, questions I feel this book should have answered since it is an introductory book. I could not in his conscience recommend this book to anyone.