One of the biggest reasons there is so much bad software is that business schools pump out people who have been led to believe that the ability to draw diagrams is an acceptable substitute for the ability to read a line of code or assess a technical standard.
One prominent victim of this phenomenon is the whole area around enterprise architecture. Gartner calls it:
...the process of translating business vision and strategy into effective enterprise change by creating, communicating and improving the key requirements, principles and models that describe the enterprise's future state and enable its evolution
It's a clear enough definition and - as with everything Gartner - it doesn't help anyone accomplish much of anything. Not counting the dubious objective of creating a market for MBA graduates.
Here is my alternative definition of Enterprise Architecture. You are free to use this definition for any purpose, especially if you intend to tattoo it on your CIO's backside:
The systems we are responsible for are legion, they are heterogeneous, they are wicked, and they conspire. We wield the autocratic staff of Enterprise Architecture and it sheds light and builds highways (and occasionally bike paths). It fosters empathy for the whole in the heart of each subsystem.