Enterprise Architecture

1. Definition of Enterprise Architecture Framework:

The books defines EA Framework as “a set of assumptions, concepts, values, and practices that constitutes a way of looking at enterprise reality via views on (architectural) models. It offers a fundamental structure, serving as a scaffold for developing, maintaining, and using EA”. The Wikipedia provides a shorter definition stating that EA Framework defines how to create and use an enterprise architecture. I like the second definition because it is shorter, but it needs some development to be fully understood.

Using these two definitions as a base I would say that EA Framework helps in developing roadmaps and architecture solutions that will help in the in the alignment of business and IT strategy. These frameworks serve as a guide during the architecture development process.

In a simpler way, it is like a blueprint that needs to be followed to achieve the desired goals.[pic 1]

1. Discuss the meaning and opportunity for the Maturity Model: A Maturity Model is a model that can be represented in a table which can be used to evaluate different areas or processes of the whole enterprise or individual projects, allowing to visually know which areas can improve and which ones are in the target level.

It can also be defined as “a way to develop and refine an organization's processes.”

The following table is an example of functions/capabilities and the different maturity levels and where they rank: [pic 2]

1. What benefits does SOA offer to EA? What risks are involved and how do you propose to mitigate them?  

SOA can help us link all of our services to facilitate the work and results for everyone in the enterprise. What needs to be done can be done by a human, either everything done by a singles person, or everything done by a group of people. Or, a product from a service oriented company can be used to handle tasks, thus reducing costs and/or time, both really valuable things in a business. This is a big benefit, having an architecture rather than isolated applications. If all services are connected it is easier to work closer with customers and suppliers. And since the company is not necessarily handling this services by itself, they can count the required software, or service, will always be updated and prepared for future challenges.

But there are also some risks involved. One of the biggest and most important to consider is a potential information breach if it is not properly safeguarded. But this risk can be minimized by storing the most sensitive information “in house” instead of relying in thirdparty services. Adding of course all the security measures to ensure all information is protected.

[pic 3]

1. Describe EIA and the role & responsibilities of an enterprise architect:  Although in class we discussed that the title of “Enterprise Information Architect” does not exist per se, a search on the internet showed me that some companies or universities do have EIA as an available position, and reading these job openings gives a good example of what an EI Architect responsibilities are.

According to what I have read an enterprise information architect is responsible for guiding the research, planning, definition, refinement and implementation of the enterprise information architecture; ensures, via plans, policies, principles, models, standards, technologies, and processes that information is treated as a strategic asset whereby the integration of data can deliver value and help align business priorities and technology. An EI architect also has to work closely with the leaders in the business and technology areas to understand the business challenges and know how to act.