Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.
SOA and Cloud computing does not replace EA. On the contrary, it has further recognize the critical of EA. SOA and Cloud computing can minimize the burden of technology, however, it does not free the …
SOA and Cloud computing does not replace EA. On the contrary, it has further recognize the critical of EA. SOA and Cloud computing can minimize the burden of technology, however, it does not free the organization from planning their SOA and cloud computing environment. The challenge of SOA and Cloud computing is how to define the appropriate services and determine the candidates for cloud computing. The SOA and Cloud computer subject matter experts can solve the technical problem but only the Enterprise architects can help an organization to plan for the SOA and Cloud computing. It is a matter of selecting the right services rather than how to design the services.
EA plans the Enterprise SOA and Cloud computing via the engineering of reuse and consolidation which is considered as a cross-cutting architecture approach rather than a derivative from the a top down architecture.
The exiting EA approach, evolved from application development, is basically a top down approach as shown in the NIST EA model. It is very difficult to understand EA just from the vertical approach of a top down or bottom up. Under the top down approach, there are many fundamental myths of EA.
. Confusion Reference model with reference architecture. Many EA experts can not tell the difference between reference model and reference architecture.
. SOA and Cloud computing is a bottom up approach.
. EA is nothing new but an enterprise scale solution architecture. Therefore all the solution architects can also wear the coat of Enterprise Architect.
This presentation suggests that EA contains multiple architecture disciplines. it consist not only the vertical top down architecture discipline but also the horizontal cross-cut architecture discipline and further the circular coherence architecture discipline.
Therefore, EA is not an enterprise scale application development, solution architect do not automatically become enterprise architect without additional discipline in horizontal and circular architecture.
Under the cross cutting architecture discipline, EA community can clearly distinguish that reference model is the tool to synchronize EA communication and learning from the right experience. Reference architectures are the architecture pattern and best practice.
The cross cutting architecture consist of the following components, It is very different discipline from the top down architecture.
The discipline to learn from the experience of the others
Reference models to learn the right experience of the other.
Engineering of reuse.
Engineering of consolidation.