This is the first time The Open Group will host a conference in Washington D.C (July 16-20), which is convenient to me. The conference and my presentation info follow:
Enterprise Architecture vs. Collection of Architectures in Enterprise
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 will help to clarify the focus in each phase and stage of EA development (e.g. TOGAF®) to ensure successful EA adoptions in solutions, initiatives, programs, and projects.
Intended audience: enterprise architects, solution and system architecture, CIO/CTO, business segment leaders, program/project managers, etc.
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 will help to clarify the focus in each phase and stage of EA development (e.g. TOGAF®) to ensure successful EA adoptions in solutions, initiatives, programs, and projects.
Intended audience: enterprise architects, solution and system architecture, CIO/CTO, business segment leaders, program/project managers, etc.
Key takeaways:
1. The purposes of doing EA
2. The differences between EA and a collection of architectures in enterprise
3. The focus in each phase and stage of EA development (e.g. TOGAF) to ensure successful EA adoptions in solutions, initiatives, programs, and projects.
1. The purposes of doing EA
2. The differences between EA and a collection of architectures in enterprise
3. The focus in each phase and stage of EA development (e.g. TOGAF) to ensure successful EA adoptions in solutions, initiatives, programs, and projects.
No comments:
Post a Comment