After you have considered an “enterprise” as a specific “business undertaking”—a set of related business activities aimed at some common goal, viewed the overall enterprise architecture (EA) of an organization as a collection of EAs, and developed the individual EAs, you can focus on EA integration. This step is aimed at ensuring that the separate EAs do not result in duplicate data or duplicate IT systems supporting different enterprises within the organization. As an example, consider the following diagram illustrating the EAs for several "enterprises" such as financial management, customer relationship management, human resource management, and the core enterprise (this is what the organization really knows how to do well):
The diagram shows the component architectures—business, data, application, and technology—for each enterprise. The two areas where the potential for EA integration should be most evident are the data and technology areas. Even though you might use commercial off-the-shelf (COTS) IT solutions to implement some of these EAs such as customer relationship management and human resource management, you would want to ensure that any data such as customer information or employee information is not duplicated. That would be an example of EA integration at the data level. Similarly, you would want to consolidate the hardware and software platforms and the network so that all EA implementations can share the infrastructure. The exact details of how you achieve EA integration depend on the details of the EAs and the strategy you want to employ. For example, you could have common data in a single database that multiple applications access or you might decide to define Web Services that manage the data and any application that needs the common data access it through specific services. No matter how you accomplish it, the key point is that after developing of the component EAs for an organization, you need to go through the EA integration step to ensure that you don't end up with what we call "stovepiped" systems and business practices.
Tags: enterprise architecture EA integration COTS stovepiped SOA service
Recent Comments