• Manual De Contabilidade Basica

Current view of the Zachman Framework.The Zachman Framework is an for, which provides a formal and highly structured way of and defining an enterprise. It consists of a two dimensional classification matrix based on the intersection of six communication questions (What, Where, When, Why, Who and How) with six rows according to transformations.The Zachman Framework is not a in that it does not imply any specific method or process for collecting, managing, or using the information that it describes. The Framework is named after its creator, who first developed the concept in the 1980s at. It has been updated several times since.The Zachman “Framework” is a for organizing architectural artifacts (in other words, design documents, specifications, and models) that takes into account both whom the artifact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed. Contents. OverviewThe term “Zachman Framework” has multiple meanings.

It can refer to any of the frameworks proposed by:. The initial framework, named A Framework for Information Systems Architecture, by John Zachman published in an 1987 article in the IBM Systems journal. The Zachman Framework for Enterprise Architecture, an update of the 1987 original in the 1990s extended and renamed. One of the later versions of the Zachman Framework, offered by Zachman International as industry standard. Collage of Zachman Frameworks as presented in several books on Enterprise Architecture from 1997 to 2005.In other sources the Zachman Framework is introduced as a framework, originated by and named after John Zachman, represented in numerous ways, see image. This framework is explained as, for example:. a to organize and analyze,.

a framework for enterprise architecture. a system, or classification scheme. a matrix, often in a 6×6 matrix format. a two-dimensional or an analytic model.

a two-dimensional schema, used to organize the detailed representations of the enterprise.Beside the frameworks developed by John Zachman numerous extensions and or applications have been developed, which are also sometimes called Zachman Frameworks.The Zachman Framework summarizes a collection of involved in enterprise architecture. These perspectives are represented in a two-dimensional matrix that defines along the rows the type of and with the columns the aspects of the architecture. The framework does not define a methodology for an architecture. Rather, the matrix is a template that must be filled in by the goals/rules, processes, material, roles, locations, and events specifically required by the organization. Further modeling by mapping between columns in the framework identifies gaps in the documented state of the organization.The framework is a simple and logical structure for classifying and organizing the descriptive of an enterprise.

It is significant to both the of the enterprise, and the actors involved in the development of enterprise systems. While there is not order of priority for the columns of the Framework, the top-down order of the rows is significant to the alignment of business concepts and the actual physical enterprise. The level of detail in the Framework is a function of each cell (and not the rows). When done by IT the lower level of focus is on, however it can apply equally to physical material (ball valves, piping, transformers, fuse boxes for example) and the associated physical processes, roles, locations etc. Related to those items.

HistoryIn the 1980s had been involved at IBM in the development of (BSP), a method for analyzing, defining and designing an of organizations. In 1982 Zachman had already concluded that these analyses could reach far beyond automating and managing data into the realms of strategic business planning and management science in general. It may be employed in the (in that time considered more esoteric) areas of enterprise architecture, data-driven systems design, data classification criteria, and more. Information Systems Architecture Framework. Simple example of the 1992 Framework.In the 1987 article “A Framework for Information Systems Architecture” Zachman noted that the term “architecture” was used loosely by information systems professionals, and meant different things to planners, designers, programmers, communication specialists, and others.

In searching for an objective, independent basis upon which to develop a framework for information systems architecture, Zachman looked at the field of classical, and a variety of complex engineering projects in industry. He saw a similar approach and concluded that architectures exist on many levels and involves at least three perspectives: raw material or, function of processes, and location or networks.The Information Systems Architecture is designed to be a for organizing architecture models. It provides a synoptic view of the models needed for enterprise architecture. Information Systems Architecture does not define in detail what the models should contain, it does not enforce the modeling language used for each model, and it does not propose a method for creating these models.

Extension and formalizationIn the 1992 article “Extending and Formalizing the Framework for Information Systems Architecture” and John Zachman present the framework and its recent extensions and show how it can be formalized in the notation of conceptual graphs. Also in 1992.

John Zachman’s co-author John Sowa proposed the additions of the Scope perspective of the ‘planner’ (bounding lists common to the enterprise and its environment) and the Detailed Representation perspective of the ‘sub-contractor’ (being the out of context vendor solution components). The Who, When and Why columns were brought into public view, the notion of the four levels of metaframeworks and a depiction of integration associations across the perspectives were all outlined in the paper. Keri Anderson Healey assisted by creating a model of the models (the framework metamodel) which was also included in the article.

The Veterans Affairs Zachman Framework with an explanation of its rows.In the 1997 Zachman Framework the rows are described as follows:. Planner’s View (Scope) – The first architectural sketch is a “” or, which depicts in gross terms the size, shape, partial relationships, and basic purpose of the final structure.

It corresponds to an executive summary for a planner or investor who wants an overview or estimate of the scope of the system, what it would cost, and how it would relate to the general environment in which it will operate. Owner’s View ( or ) – Next are the architect’s drawings that depict the final building from the perspective of the owner, who will have to live with it in the daily routines of business. They correspond to the enterprise (business) models, which constitute the designs of the business and show the business entities and processes and how they relate. Designer’s View (Information Systems Model) – The architect’s plans are the translation of the drawings into detail requirements representations from the designer’s perspective.

They correspond to the system model designed by a systems analyst who must determine the data elements, logical process flows, and functions that represent business entities and processes. Builder’s View (Technology Model) – The contractor must redraw the architect’s plans to represent the builder’s perspective, with sufficient detail to understand the constraints of tools, technology, and materials. The builder’s plans correspond to the technology models, which must adapt the information systems model to the details of the programming languages, input/output (I/O) devices, or other required supporting technology. Subcontractor View (Detailed Specifications) – Subcontractors work from shop plans that specify the details of parts or subsections. These correspond to the detailed specifications that are given to programmers who code individual modules without being concerned with the overall context or structure of the system.

Manual De Contabilidade Basica

Alternatively, they could represent the detailed requirements for various, or components of modular systems software being procured and implemented rather than built. Actual System View or The Functioning Enterprise Focus of ColumnsIn summary, each perspective focuses attention on the same fundamental questions, then answers those questions from that viewpoint, creating different descriptive representations (i.e., models), which translate from higher to lower perspectives.

The basic model for the focus (or product abstraction) remains constant. The basic model of each column is uniquely defined, yet related across and down the matrix. In addition, the six categories of enterprise architecture components, and the underlying interrogatives that they answer, form the columns of the Zachman Framework and these are:. The data description — What. The function description — How.

The Network description — Where. The people description — Who.

The time description — When. The motivation description — WhyIn Zachman’s opinion, the single factor that makes his framework unique is that each element on either axis of the matrix is explicitly distinguishable from all the other elements on that axis. The representations in each cell of the matrix are not merely successive levels of increasing detail, but actually are different representations — different in context, meaning, motivation, and use.

Because each of the elements on either axis is explicitly different from the others, it is possible to define precisely what belongs in each cell. Models of CellsThe kinds of models or architectural descriptive representations are made explicit at the intersections of the rows and columns. An intersection is referred to as a cell. Because a cell is created by the intersection of a perspective and a focus, each is distinctive and unique.

Since each cell is distinctive and unique, the contents of the cell are normalized and explicit per the perspective’s focus.The cell descriptions in the table itself uses general language for a specific set of targets. Below the focus of each cell in this particular Zachman Framework is. Current view of the Zachman Framework. Example of Zachman Framework Rules.The framework comes with a set of rules:. Rule 1 The columns have no order: The columns are interchangeable but cannot be reduced or created. Rule 2 Each column has a simple generic model: Every column can have its own meta-model. Rule 3 The basic model of each column must be unique: The basic model of each column, the relationship objects and the structure of it is unique.

Each relationship object is interdependent but the representation objective is unique. Rule 4 Each row describes a distinct, unique perspective: Each row describes the view of a particular business group and is unique to it. All rows are usually present in most hierarchical organizations.

Rule 5 Each cell is unique: The combination of 2,3 & 4 must produce unique cells where each cell represents a particular case. TEAF Work Products for EA Direction, Description, and Accomplishment.Other sources:. The TEAF matrix is called a customization sample, see, p. 22 Standards based on the Zachman FrameworkZachman Framework is also used as a framework to describe standards, for example standards for healthcare and healthcare information system. Each cell of the framework contains such a series of standards for healthcare and healthcare information system. Mapping other frameworksAnother application of the Zachman Framework is as reference model for other enterprise architectures, see for example these four:. Mapping a part of the, 2007.Other examples:. Analysis of the as a Process,.

How the (MDA) models used in software development map to the Zachman Framework. Mapping the IEC 62264 models onto the Zachman framework for analysing products information traceability. Mapping the Architecture Development Method (e.g. The methodology) to the Zachman Framework. Base for other enterprise architecture frameworksLess obvious are the ways the original Zachman framework has stimulated the development of other, such as in the, the AE, the DOE AE, and the:. 2003.

The (FEAF) is based on the Zachman Framework but only addresses the first three columns of Zachman, using slightly different names, and focuses in the top of the three rows. (see ) Example: One-VA Enterprise ArchitectureThe Zachman Framework methodology has for example been used by the (VA) to develop and maintain its One-VA Enterprise Architecture in 2001. This methodology required them to define all aspects of the VA enterprise from a business process, data, technical, location, personnel, and requirements perspective. The next step in implementing the Zachman methodology has been to define all functions related to each business process and identify associated data elements. Once identified, duplication of function and inconsistency in data definition can be identified. The hard job then followed to de-conflict the data definitions and resolve duplicative implementations of the same business function.

VA EA Meta-Model Cell Details Enlarged.This diagram has been incorporated within the VA-EA to provide a symbolic representation of the that VA used, to describe the One-VA Enterprise Architecture and to build an EA Repository without the use of Commercial EA Repository Software. The One-VA EA repository was developed using an within the Caliber-RM Software Product. Caliber-RM is intended to be used as a tool; not as an EA repository.However this tool permitted defining entities and relationships and for defining properties upon both entities and relationships, which made it sufficient for building an EA repository, considering the technology that was available in early 2003.