Architecture Principles: The Cornerstones of Enterprise Architecture (The Enterprise Engineering Series)

Architecture Principles: The Cornerstones of Enterprise Architecture (The Enterprise Engineering Series)

Danny Greefhorst

Language: English

Pages: 197

ISBN: 3642202780

Format: PDF / Kindle (mobi) / ePub

Enterprises, from small to large, evolve continuously. As a result, their structures are transformed and extended continuously. Without some means of control, such changes are bound to lead to an overly complex, uncoordinated and heterogeneous environment that is hard to manage and hard to adapt to future changes. Enterprise architecture principles provide a means to direct transformations of enterprises. As a consequence, architecture principles should be seen as the cornerstones of any architecture.

In this book, Greefhorst and Proper focus on the role of architecture principles. They provide both a theoretical and a practical perspective on architecture principles. The theoretical perspective involves a brief survey of the general concept of principle as well as an analysis of different flavors of principles. Architecture principles are regarded as a specific class of normative principles that direct the design of an enterprise, from the definition of its business to its supporting IT. The practical perspective on architecture principles is concerned with an approach to the formulation of architecture principles, as well as their actual use in organizations. To illustrate their use in practice, several real-life cases are discussed, an application of architecture principles in TOGAF is included, and a catalogue of example architecture principles is provided.

With this broad coverage, the authors target students and researchers specializing in enterprise architecture or business information systems, as well as practitioners who want to understand the foundations underlying their practical daily work.

Optimization Techniques for Solving Complex Problems (Wiley Series on Parallel and Distributed Computing)

Probabilistics Search for Tracking Targets: Theory and Modern Applications

Lecture Notes in Computer Science, Volume 7833, Evolutionary Computation, Machine Learning and Data Mining in Bioinformatics: 11th European Conference, EvoBIO 2013, Vienna, Austria, April 3-5, 2013. Proceedings

Python Network Programming Cookbook

Computer Organization and Design: The Hardware/Software Interface (5th Edition)

















evolution also explicitly refers to the role of principles in guiding the design and evolution of systems. Models are generally understood to be purposeful abstractions of (some relevant part of) reality (Falkenberg et al. 1998). Models can be used to represent systems, and actually can be regarded as systems themselves. For example, Apostel (1960) defines a model as a system representing another system: “any subject using a system A that is neither directly nor indirectly interacting with a

the gap between high-level strategic intents and concrete designs. Chapter 3 A Conceptual Framework for Principles Abstract This chapter provides the theoretical core of this book. It is concerned with a conceptual framework for architecture principles and related concepts. It starts by providing some historical background to the concept of principle. We will distinguish between scientific principles that describe laws or facts of nature, and normative principles that start as fundamental

abstraction. Nature of the information The nature of the information included in the architecture description. Representation The way architectural information is represented. Since these dimensions are applicable to architectural descriptions, they also apply to architecture principles which are part of them. In the context of this book we have applied these dimensions to the concept of architecture principles. In order to better understand the various dimensions in architecture principles, a

Norms add specification details to credos, making them specific and measurable. 4.2.5 Stakeholder Dimension This dimension uses the stakeholders that are addressed as primary criterion. Stakeholders are typically only interested in certain parts of the architecture (views). Defining descriptions for specific stakeholders was the intention of the Zachman perspectives dimension. However, in the Zachman framework the stakeholders dimension is equivalent to the detail level dimension. In a lot of

applications require their own data, and using a separate environment prevents polluting the operational data. Implications: • A data warehouse environment is created that is loaded periodically. • Reports are not based on current data, but on data that have been loaded some time earlier. A.25 Applications Have a Common Look-and-Feel Type of information: application Quality attributes: usability Rationale: • Inconsistency leads to a lower productivity and irritation of users. • A consistent user

Download sample