Beyond the Zachman framework: Problem-oriented system architecture

Abstract

The year 2012 marks the twenty-fifth anniversary of BA framework for information systems architecture,[ written by John Zachman and published in the IBM Systems Journal. The first part of this paper reviews the Zachman and similar frameworks and concludes that there are a number of limitations in the framework approach when applied to today's technology environment and business problems. These include the inability of the problem owner to properly describe a solution, the partitioning approach, and the decision-making processes in the context of uncertainty and change. The second part of this paper analyzes today's problems and allocates them to one of three classifications: tame, complex, and wicked, depending on the degree of certainty and stability of knowledge and decisions in both the problem and the solution domains. The final part outlines an approach to problem-solving and architecture development using techniques borrowed from cybernetics and control theory. It proposes that partitioning should be determined by the nature of the problem and potential solutions; that feedback loops should be implemented in order to control the process; that the architect should work across the business problem and solution spaces; and that decisions should be related to business value. The Zachman framework The Zachman framework describes the structure of a system architecture and processes for its development. This

Enterprise Architecture “As-Is” Analysis for Competitive Advantage

“…Nevertheless, the Zachman framework also has some significant drawback, such as no step-by-step procedure for creating a new architecture, which resulted lost in the architecting process [15]. Furthermore, there is a lack of analysis to validate either the proposed future architecture is improving the current architecture [16]. Therefore, it falls short at prescribing detailed solutions for enterprise problems and often implies solutions that are too idealistic and less realistic.…”

Conceptual Model of Enterprise Architecture Management

“…6,47,78 However, the external organizational environment is unpredictable and constantly changing with much faster pace. 79,80 For instance, Sauer and Willcocks 26 after surveying 97 executives report that half of them do not extend their plans beyond one year while many companies update their plans quarterly. Erder and Pureur 25 argue that even technology details might be unknown for several years ahead.…”

How Enterprise Architecture Formative Critical Success Facets Might Affect Enterprise Architecture Success: A Literature Analysis

“…A pilot title search with keywords "enterprise architecture" from 1990 through 2012 was conducted in a website 1 , where we can set our target database as the eight senior basket journals [23]. That test search got merely four relevant articles.…”

“…Enterprise architecture now is emerging as an enterprise problem-oriented discipline [1], and actually problem-finding is more concerned than problem-solving [2]. Though Enterprise architecture gains increasing attentions from both academics and practitioners, "we are far from establishing a solid empirical base for enterprise architecture" [3].…”