In this document, the author explains the zachman framework, where did it came from and the rules of how to implement it in the enterprise architecture. He defines the framework of enterprise architecture as a two dimensional classification scheme for descriptive representation of an enterprise. It was derived through observation descriptive representation of many different objects, for example: airplanes, buildings, ships and computers. Through looking at the descriptive representations, product descriptions and the engineering documentations it was observed that the complex products can be classified by the audience for which the artifacts was constructed. The author also mentioned the perspectives of the framework by being represented over the process of engineering and manufacturing of complex products. The descriptive representations of the product that are prepared over this process are designed to express concepts/constraints relevant to the various perspectives. He also showed the principle prespictives in this order: The Owner’s Perspective (Row 2), The Designer’s Perspective (Row 3), The Builder’s Perspective (Row 4), A Scope Perspective (Row 1), An Out-of-Context Perspective (Row 5). For the sixth row, the author described it as not architecture because it is not a representation, it is the actual thing. In the abstraction of the framework, there are things to be considered that relate to the object being described which are: What it is made of, how it works, Where the components are located relative to one another, who does what work, When do things happen relative to one another, why do things happen. The author chose the word abstractions for this dimension of the Framework because the object being described tends to be so complex that it is impossible to take into consideration all of the interrelationships of all the various components all at one time. For the rules of the framework, the author made seven rules that needs to be followed in implementing the framework. The first rule is do not add rows or columns to the framework. The author says that adding rows or columns to the framework would denormalize the classification scheme because, adding Rows or Columns would introduce redundancies or discontinuities. The second rule is each columns has a simple generic model. Which means the basic generic model of any one Column is very simple: the variable it represents as related to itself. The third rule each cell model specializes its Column’s generic model. The fourth rule is no meta concept can be classified into more than one cell, to make sure there is no redundancy. Fifth rule, do not create diagonal relationship between cells, because it can create a very confusing communication problem. Sixth rule, do not change the names of the rows or cells for the same reason in not adding new ones. The last rule says the logic is generic, recursive. The Framework is generic. It can be used to classify the descriptive representations of anything and therefore to analyze anything relative to its architectural composition. It is recursive. It can be used to analyze the architectural composition of itself.