jump to navigation

Enterprise Architecture August 10, 2012

Posted by 3562pittena in Enterprise Architecture.
trackback

I’ve learned a lot about Enterprise Architecture (EA) so far this lecture. My views on it in the beginning were skewed and I didn’t exactly know what it was. It’s still not 100% clear to me, but I don’t think it will be until I start putting what I’ve learned into practice (if that ever happens).What I have learned about EA is that it is an invaluable practice that should be used by all large corporations. There are many technologies that can support the EA process and having all the stakeholders agree on technologies is the best solution.

Having a common database is a good implementation for EA. Having one location for all of your data allows for easier integration of all the applications that need to get at that data. This allows for organization in the business (less applications/interfaces) as well as easier maintenance. Having a common database shows a maturing EA company. In the four stages of maturity given by Prof. Kaczmarek, it would be at least in the “Standardized Technology” stage.

COBRA is a standard defined by the Object Management Group (OMG). As wikipedia states, “CORBA enables separate pieces of software written in different languages and running on different computers to work with each other like a single application or set of services.” [1] Implementing something like COBRA would increase the EA maturity. It creates better integration and allows for different applications to access the same data. In the four stages of maturity, it would be at least in the “Standardized Technology” stage. As with any standardized technology, making it easy for everyone to interface with removes some of the complexity that can be put in it. In other words, some of the “cool” things that might be able to be done with a single programming language cannot be done using COBRA because it has to implement many different programming languages.

Web-services fall into the same category as COBRA. It defines an interface to some data or an application on a separate machine. It allows for easier integration and less applications in the company. This also falls under the stage of “Standardized Technology”

A Service-Oriented Architecture (SOA) is much like web services, but the entire architecture is all around these loosely coupled web services. The web services should be modular, granular, interoperable and reusable. Moving to a service-oriented architecture would move the maturity of the organization from the “Standardized Technology” state and into the “Optimized Core” state. The organization is moving to a high level business standard and that is why that move takes place.

When you start to get more and more mature, you start to have many different kinds of requests that are being sent over your SOA. An Enterprise Service Bus (ESB) is the model used to implement that interaction. Using SOA with and ESB is increasing the companies maturity. Depending on the use of the ESB, the company may be moved into the “Business Modularity” stage of maturity.

There are many different technologies that can be used to enhance a companies maturity in EA. A few were named here. Any time you can remove the necessity for separate applications and increase the integration of other applications, the maturity of the EA increases.

[1] Wikipedia contributors. “Common Object Request Broker Architecture.” Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 29 Jul. 2012. Web. 10 Aug. 2012.

Advertisements

Comments»

No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: