How not to fail in enterprise architecture
How not to fail in enterprise architecture
Common antipatterns and how to avoid them
About the Book
This anthology from the Tetradian weblog demonstrates the importance of discipline and formal rigour in architectures - and what happens if the discipline fails, or the rigour is absent.
This book includes about 35 posts and 70 images from the weblog. These posts are split into two groups:
- How Not To Fail: Concept-Critique - raises key questions about quality of formal-rigour, theory and discipline in current enterprise-architecture and beyond.
- How Not To Fail: Method-Critique - also raises key questions and concerns about quality and reliability of method in current enterprise-architecture and suchlike.
About the Author
Bundles that include this book
Table of Contents
- HOW NOT TO FAIL IN EA: INTRODUCTION
- HOW NOT TO FAIL IN EA: CONCEPT-CRITIQUE
- The dangers of ‘term-hijack’
- Magical-thinking and knowledge-management
- The absurdity of belief
- Intimations of hubris
- Round in circles on enterprise-architecture
- IT-centrism, business-centrism and business-architecture
- Skills-shortages and ‘the market’
- Showing my age, I guess…
- The over-certainties of certification
- On dubious definitions
- “Who will lead us out of our uncertainty?”
- If it’s not AE, it’s not EA
- Efficient, effective, convenient?
- “The history of enterprise architecture proves…”
-
Beware of ‘policy-based evidence’
- Implications for enterprise-architecture
- John Zachman and the curate’s egg
- Dump the BDAT-stack!
- HOW NOT TO FAIL IN EA: METHOD-CRITIQUE
- The autism of Enterprise Architecture?
- Whuffie, currency and the ‘ready-fire-aim’ syndrome
- How IT-centrism creeps into enterprise-architecture
- Broken
- Why broken?
- A bit more broken
-
Unbreaking
- Conflict: Engineers versus scientists
- Conflict: Stability versus agility
- Sometimes the small details do matter
- The stench of systemic decay
- Fail, to learn
- Spot the difference
- How architectures fail - 1: Architecture vs design
- How architectures fail - 2: Scope of action
- How architectures fail - 3: Constraints
- Why ‘engineering the enterprise’ doesn’t work
- Missing the point
-
Open Group, HERA and healthcare
- The good(ish)
- The bad(ish)
- The ugly (very)
- Real-world crosschecks
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
