Zachman Enterprise Architecture Framework Analysis - Essay Example

Zachman Enterprise Architecture Framework Analysis Introduction Zachman enterprise architecture framework canbe viewed as a formal perspective of analysing a modern enterprise in a homogenous structural approach. It seeks to explicitly conceptualize a given abstract of computerized/ custom program into theoretical data model, that is, from a scope perspective to an intrinsic operations perspective (Wout, 2010). It should be noted that the framework is not an ordinary model but more of a conceptual model, a composition of concepts, in that it exists in its applicability, mental synchronization and or personal/mind interpretations so as to guide the user to know, understand and where possible simulate the ideas in a practical situation (Raynard, 2000). Enterprise framework differs with structural/building framework in that as the building framework seeks to apply the laid out methodology, that is, to collect, manage and use information to achieve a prescribed/ designed model(s) to a tangible object, enterprise framework seeks to transform the abstract ideas, that is, intentions and semantics through designing documents, specifications, considerations of available models; without implying any specific and /or defined process. Therefore it can be viewed as a process to think, apply, re-apply, evaluate and solve problems through formalization and effective communication (Zachman & Geiger, 1997). With this in mind, we shall look at how Zachman’s enterprise architectural framework applies in reality by first understanding the types and scope of its architectural design. Types and Scope For conceptual enterprise architecture to be effective, there should explicitly define techniques to help individuals understand the represented system, it should convey the system details to the stakeholders, should provide a point of reference so as to simplify extractions of system specifications by designers and it should automatically and/or in a simplified manner, document the system for future reference and provide room for collaborations and implementation (Fishman & Selkow, 2003). For instance, it should first analyse the need for transformation within a given organizational process/intention or a phenomenon cross examine the available concepts to come up with a conceptual model and ideas to achieve the transformation. It should analyse the validation of the process, clearly show its specifications analysis and the simulation process. It should reflect accreditation, verifications of the perceived implementation and execution and finally outline the expected results and the impact (Uckelmann, 2012). The Zachman’s enterprise architecture is based on six core questions; what, how, where, who, when and why, which form basis of applications in the modern organization. To come up with stronger arguments and justifications to support the model, these questions are further analysed in different business perspectives such as the scope: which seeks to explain the contextual business activities, the business model: which is the evaluation of the conceptual nature of the organization and its stakeholders, the system model: which is the logical approach of the required transformation in line with the business needs, technology model: it represents the physical and the intended aspects by the transformers of the new phenomenon, detailed representations by other members of the transformation and finally the analysis of the functioning enterprise. The Scope/ Contextual Approach The planner tries to figure out: what content will the framework contain and/or the overall model represent? This call to ascertain and prioritize on all important business processes and what transformations can bring an impact. This may take course through the analysis of available data and the projected/intended goal. The planner then needs to ask how the conceptual model will be presented. This seeks to explain the functioning of the perceived model which can be achieved through intensive analysis of the core business processes or the activities it performs. Further, he needs to ask himself, who will be using or participating in the intended model? This calls for creative analysis of the business partners and their respective processes to ascertain the effectiveness of the transfer of the new architecture. In addition, he/ she need to ask, where is the intended model’s focus of observation? At this point, the planner needs to be conversant with the specific business organs and ascertain the impact of change within the networks. Later, he/ she need to ascertain when the model well fits the application with respect to the existing business cycles. Finally the planner needs to ask why the framework? This seeks to evaluate the motivational aspect of the framework towards the achievement of the business goals. Like for instance why this new model more effective in terms of time management, data management and /or profit maximization of the business with respect to existing one? Business Model/ Conceptual Approach This is conceptual thinking by the owner of the business on what; the specific aspects will this enterprise architecture will improve the business relationships and how it will affect the overall business entity, how; the introduction of the framework will impact business processes and how its functioning will be effected with the available resources, where; effecting of this new model impacts the logistic issues in the adaptability and linkages within the business network of customers and or suppliers, who; how the model will impact the existing employees’ organization and the corporate culture, when; how the effected model will coincide with the business cycles and fulfil the requirements of all stakeholders and finally why is the framework justified to bring the intended changes in the long run (Hay, 2003). System Model/Logical Approach This calls for the designer’s evaluation on what data and/or information to be included in development of the model, how will the framework transfer its intention to the needs of the business and how can overrides be solved without business interruptions and where will the system impact and by what volumes. In addition, the designers evaluate the applications of the new framework by analysing the human interface aspect of the model, its specific role and the deliverables, when is the appropriate time to implement and execute the new system and its overall processing cycle; and why it fit the business model in terms of rules and application more than the previous developed or designed models. Technology Model/Physical Approach This calls for the builders/ physical developer’s conceptual analysis/ decisions on what data to use in building the model, that is, to use regional or departmental data for construction, how their systems design will function with the computerised systems and/ or the planner’s provisions and where specifically will their designs impact on specific designer’s programs or the owner’s projected networks. Furthermore, they seek to simplify the architecture so as to enable presentation to capture the user’s interests and a simple interface, they define the control structure on when to launch, end the applications and/or execution platform in their product component cycle; and they clearly justify their design in terms of applications and the desired output. Detailed Representation/ Sub contraction Approach This approach seeks to present the overall performance of the enterprise architecture after the analysis and/or considerations from the business perspectives. It looks at the end products of each section like how the data has been defined, the fields included and the associated addresses; program functioning in terms of language statement or its controls; network architecture in terms of node-address and link protocols; security aspects to the users in terms of identity and respective jobs; timing definitions and the machine cycles and the rule specifications. Conclusion Zachman’s enterprise architecture framework details the conceptual thinking and evaluations by specific stakeholders of the enterprise framework development. This conceptual thinking can be pegged on the epistemological, economic, mental, scientific, metaphysical, logical, mathematical and statistical models which the stakeholders have used and applied in line with their roles to come up with specific ideas which can be applied to bring forth a methodology of constructing a tangible product and /or intangible process with great impacts in an organization. References Zachman, J. A., & Geiger, J. G. (1997). Data stores, data warehousing, and the Zachman Framework: Managing enterprise knowledge. New York: McGraw-Hill. Raynard, B. (2000). TOGAF: The Open Group Architecture Framework 100 success secrets : 100 most asked questions : the missing TOGAF guide on how to achieve and sustain superior enterprise architecture execution. S.l: s.n. Wout, J. (2010). The integrated architecture framework explained: Why, what, how. Heidelberg: Springer Uckelmann, D. (2012). Quantifying the value of RFID and the EPCglobal architecture framework in logistics. Berlin: Springer Fishman, N. & Selkow, W. (2003). Enterprise architecture using the Zachman Framework. Boston: Course Technology, a division of Thomson Learning Hay, D. C. (2003). Requirements analysis: From business views to architecture. Upper Saddle River, NJ: Prentice Hall PTR. Read More