Enterprise Architecture

{{post_terms.hashtags}}

Re-thinking Enterprise Architecture Using Systems and Complexity Approaches

This article looks at the issues currently confronting enterprise architects and the challenges posed when extending EA to be the architecture of the enterprise rather than just its information technology. It describes the contribution that Systems Practice and other disciplines can make to Enterprise Architecture (EA), and considers how the Cynefin sense-making framework can be used to help indicate which are the most appropriate types of approach.

Tactical Enterprise Architecture: Challenges to Building a Strategic Program

Enterprise Architecture (EA) is widely accepted as a strategic practice, focused on building a definition of future state and then managing a business and technology roadmap to help get there. The young EA program however, is often expected to contribute immediate benefits to the organization before an enterprise strategic vision or the long term roadmap has been defined. While engaged in building the solid foundations of an EA program, the Chief Architect will need to be sensitive to two distinctly different management expectations. The EA program must first be visionary, leading their management teams towards an integrated and enterprise view of business, information and technology architecture. Second, the program must also be flexible enough to manage tactical issues thrust upon them, and find ways to work those solutions into the longer term end-state architecture.

An Enterprise Abstraction Approach: Viewing Enterprise Architecture Through Natural Language Constructs

This article introduces an approach to define an Enterprise Architecture (EA) that aims to get closer to the abstraction level of the business side of an organization. Named as Enterprise Abstraction Aproach (EAA), the approach stems its roots from ontology engineering, business rules approach and business process engineering and aims to define business view of EA through natural language contructs. The approach also suggests to define domain ontology of the information view of an EA. By extending the business ontology definition towards information and technology views of EA, the approach aims to define a semantic mapping accross self-contained domain ontologies that pertain to different views of an enterprise, achieving a 360-degree view of the enterprise through a unified language.

Geographic Information Systems in Public Sector Enterprise Architectures: Issues and Challenges

Geographic information systems (GIS) are widespread at the federal, state and local levels. Data sharing is important because the ultimate power of a GIS is its ability to graphically present layers of data from multiple unrelated disciplines to create new information that allows people to answer questions. GIS have traditionally been built on standalone, stove-piped systems that present considerable difficulties to enterprise architects for several reasons. Although there are standard exchange formats for individual data types, there is a lack of federally-mandated standards for overall GIS data sets. This paper will discuss the efforts and associated challenges at federal, state and local levels to develop and implement GIS enterprise architecture frameworks, standards and enterprise architectures in order to better manage geospatial data. It presents the U.S. Census Bureau as an example of how the federal government is pursuing data sharing efforts with local government agencies, and provides examples of state and local government organizations that are implementing GIS into their enterprise architectures. It also discusses the impact of web technologies on the GIS industry and the differing opinions of the GIS industry on these technologies.

When Enterprise Architecture Meets Government: An Institutional Case Study Analysis

This study investigates the systemic challenges facing enterprise architecture programs in government. Drawing upon the institutional theory lens from the political science field, a Danish case study is used to explore why public agencies implement enterprise architecture programs and the challenges they face when governing these programs at different levels (vertically) and different functions (horizontally) of government. The analysis shows that enterprise architecture is not just a technical issue, as economic and political facts are equally important when establishing interoperable e-government services. The findings suggest that implementing enterprise architectures in government challenges the way information systems are organized and governed in public agencies. Interoperability challenges in government arise because there is no overall coordination of different information systems initiatives in the public sector and because public organization have no economic and/or immediate political incentives to share data and business functionality with other organizations in their enterprise architecture programs.

Providing Deep Business Value: A Supply Chain Case Study

Enterprise Architecture (EA), born in the private sector under fractured proprietary process methodologies, has matured into a serious discipline thanks to the funding strengths of the Federal Government and the dedication of many practitioners. Application of this systems engineering discipline has come about under the shadow of a federally-induced mandate, but with mixed results. The United States Office of Management and Budget’s primary focus on Information Technology (IT) has results in an inappropriate association of EA as an “IT thing” and has caused EA to lose credibility among business leadership. The author argues that EA can be about more than IT and more than a necessary evil. It can actually provide deep business value and provide a structure for breaking down and managing complex problem. From personal experience in applying EA to a private sector e-commerce solution for supply chain management, the author presents elements of an e-business approach that others can leverage to help craft an operational EA that generates more than expensive shelf-ware. EA can become crucial in day-to-day operations and can be used within executive ranks to drive business decisions.