Enterprise Architecture .vs. Collection of Architectures in Enterprise
- 1,117 views
Enterprise Architecture (EA) is becoming popular in most private enterprises these days due to the practical needs in this era of IT, after its noticeable fading in public sectors. At this stage, the ...
Enterprise Architecture (EA) is becoming popular in most private enterprises these days due to the practical needs in this era of IT, after its noticeable fading in public sectors. At this stage, the lessons learned from public sectors could be very helpful to the EA adoption in both public and private sectors in moving forward.
We noticed that there is still no unified answer regarding to what is EA and what should be in it. It is not rare to see that so called “EA” is to use an EA tool and/or an EA repository to collect all type of “architecture” artifacts inside enterprise. These “architecture” artifacts are developed in different timeframes, cover different level of content details, and are created from different perspectives for different purpose. While a real EA should consist of “architecture” artifacts in concert by planning ahead with a designated purpose for each view. The level of details is good enough to convey intent and to serve the purpose, no more and no less.
This presentation will discuss the differences between enterprise architecture and a collection of architectures in enterprise. It’ll help to clarify the focus in each phase and stage of EA development (e.g. in TOGAF) to ensure successful EA adoptions in solutions, initiatives, programs, and projects.
- Total Views
- Views on SlideShare
- Embed Views