LicEnciado En ciEncias De La Computacion

FEA PMO Action, FEA Practice Guidance: analysis

Juan Avila

Version 1.2

24-25 February 2012

FEA PMO Action, FEA Practice Guidance: analysis version: JUAN AVILA 1.2

Date: 31/03/2012

Historical Review
Date 14/FEB/2012 Version 1.0 Description Document Analysis: FEA PMO Action, FEA Practice Guidance Document Analysis: FEA PMO Action, FEA Practice Guidance Document Analysis: FEA PMOAction, FEA Practice Guidance Author Juan R. Avila Ruiz

21/FEB/2012

1.1

Juan R. Avila Ruiz

23/FEB/2012

1.2

Juan R. Avila Ruiz

Page 2 of 23

FEA PMO Action, FEA Practice Guidance: analysis version: JUAN AVILA 1.2

Date: 31/03/2012

Index

1.KEY ISSUES 2. DETAILED ANALYSIS
2.1 What is Enterprise Architecture? What is FEA? 2.2 The relevance of enterprise architecture2.3 E-government citizen-centered 2.4 Evolve the FEA to Drive results 2.5 Develop and Evolve the Lines of Business and Other Collaborative Opportunities 2.6 Measuring EA Value with the EA Assessment Program 2.7 Enterprise Architecture Transition Strategy

4  4 
4  8  10  11  14  15  16 

3.Assessing these key issues if they are applied to Mexican Federal and State government organizations4.CONCLUSIONS 5.RECOMMENDATIONS 6 BIBLIOGRAPHY

17  19  21  23 

Page 3 of 23

FEA PMO Action, FEA Practice Guidance: analysis version: JUAN AVILA 1.2

Date: 31/03/2012

1.

KEY ISSUES
     E-government citizen-centered Evolve the FEA to Drive results Develop and Evolve the Lines of Business and Other Collaborative Opportunities Measuring EA Value with the EA Assessment ProgramEnterprise Architecture Transition Strategy

2.

DETAILED ANALYSIS 2.1 What is Enterprise Architecture? What is FEA?

The enterprise architecture describes the company as a coherent structure. The Architecture documents the current status of the organization, the desired state and the gap between them. The system architecture model should not be seen as a capsule. The characteristics of thearchitecture must have been the result of business analysis to determine which depart Systems Strategy. Systems Strategy The systems approach uses four perspectives to reduce the gap between business needs and technology. These views describe the processes required to achieve corporate goals.  Business.

Page 4 of 23

FEA PMO Action, FEA Practice Guidance: analysis version: JUAN AVILA 1.2Date: 31/03/2012

 Information.   Applications. Technology.

Each perspective describes the current state, future state and the gap between them. The goal is to make effective strategic decisions in the area of information technology. It is important not to forget that technology is only a subsystem of the system known as a business. It is very important that the general direction coordinateall the factors and resources involved in the system. The degree of success will be achieved to the extent that these factors interact and resources appropriately. Like any process, the systems approach can be measured and controlled, the improvement in the process of implementing solutions for the business is one of the benefits of seeing the strategy as a flow or process. At the end you have abasis for the technological processes, so the knowledge is incorporated into the business. This methodology meets the goal of aligning technology to business needs. Companies participating in the market in many ways taking into account the objectives, policies, and the triple constraint (time, cost, scope) that frame your business as your IT projects. Although sometimes the subject to understandbasic aspects of the mission and vision happen to be "covered" at all but without a clear focus and a clear relationship between what is proposed, which is planned and what is done. This is part of what justifies the need to define an enterprise architecture and thus have

Page 5 of 23

FEA PMO Action, FEA Practice Guidance: analysis version: JUAN AVILA 1.2

Date: 31/03/2012

the basis to...