|
CBDI Service Oriented Architecture Practice Portal
Independent Guidance for Service Architecture and Engineering
|
|
|
|
||
|
|||
 |
| Report Summary |
| Title: | Editorial: EA for SOA? | ||
| Author: | David Sprott | ||
| Publication Date: | 17 October 2007 | ||
| Report Type: | Journal | ||
| Report Class: | Editorial | ||
| Abstract: | I observe renewed interest in Enterprise Architecture (EA). There is considerable debate about how EA and SOA relate to each other. Yet EA has been around for years; who hasn’t come across the Zachman Framework or TOGAF? So are we looking to augment EA with SOA concepts, or is there a more profound change that needs to take place? | ||
| Backgrounder: | There are many pitfalls in EA for the unwary. For example: Current Architecture Death March - In any large enterprise there’s a vast amount of detail needed to document the AS-IS architecture and it’s a gargantuan task equivalent to trying bring architectural order to a municipal rubbish dump. Technical Reference Model (TRM) Stagnation – Many organizations initiate their TRM as an inventory exercise. Then quickly grandfather existing technologies as standard. This is effective at stopping technology product proliferation but its benefits end there and there are many potential problems with this approach. EA Compliance Becomes a Barrier - Many organizations find it difficult to measure the value of their EA programs and are reluctant to empower them to govern. This is because most EA programs that are immature establish compliance standards without going through the difficult task of enabling compliance. | ||
| Report Size: | 2 pages | ||
| Report Access Type: |
|
||
| Available for separate purchase | Single copies of recent CBDI Journals may be purchased | ||
| Login |
|
| © Everware-CBDI Inc 1999-2008 |   
|
Home