Enterprise Architecture (EA) describes a framework or discipline whereby somebody or some group within an enterprise carefully designs the Technical Architecture and Solution Architecture around the business strategy, plans and needs of the Enterprise to effectively achieve it’s objectives.
The alternative and by far the most common scenario if for organisations to make isolated decisions about systems with a short term view and with no consideration of the longer term impact of that decision or of how all these pieces might fit together. This one practice, more than anything else leads to expensive low performing IT systems and failing projects. EA is traditionally the responsibility of an IT director or CIO, though gradually larger more forward thinking businesses are putting in place EA capabilities within their organisation with the responsibility for planning ahead with the business and transforming those business strategies and plans into technical architecture.
Well known frameworks include TOGAF, Zachman , DODAF and FEA
The “Explainned series” is planned to build into a trustworthy collection of explanations and commentaries that can be trusted to tell the story straight without any bias and attempt to make the subjects accessible to the layman. The latter is not always easy as some of these terms refer to genuinely complex subject matter, while others are simply too vague to pin down (there’s another word for that).
If you want an answer on something and you can’t find it easily, please use the comments section to just ask and I will apreciate not having to research the next topic.