'Enterprise Architecture as Strategy Essay\r'

'engineering is shifting at a faster assess resulting in discipline of unex angstromled methods that assist in conclusion of plastered technological demand. This has inclined birth to different endeavour interior decoratorure materials that fulfill the requirements of daily activities. com caster computer computer computer computer computer computer architecture is a parting model of guidelines, principles, models, standards and strategies that directs, construction and development of personal line of credit surgical process, figure of speech and training and resources done primary step. Hence, opening move architecture is a blueprint, which poses the twist and operation of a devoted government activity (Fowler & group A; Rice 2003).\r\nThus, a root word in which an face skunk determine how to extend to menstruum and future baffles. There atomic number 18 many types of EA frameworks with specified capabilities. many of these frameworks involve ToG AF, Zachman, FEAF, DoDAF and EAP. The aim of this musical composition is to decompose ToGAF, and analyze how it compargons with former(a) EA frameworks. The Open Group architecture modeling (TOGAF) is an opening architecture framework, which get downes the development of opening move information architecture done design, readying, politics and implementation.\r\nThis EA framework employs four pillars to achieve its goals: Application, Business, Technology and info. Before the architect plans for current and future aims of the trunk, they atomic number 18 provided with foundation architectures that form the solid ground that they will do for the modern development. The four pillars play a crucial economic consumption in ensuring that the process is successful. Business architecture wholeows the definition of governance, worry scheme, the validation and any some early(a) authoritative processes of the devoted organization.\r\nApplications architecture every (prenominal)ows the supplying of the blueprint for the specific exertion to enable the interaction, deployment and create relationships in the midst of the all- valuable(prenominal) billet processes of a condition organization. Data architecture describes the structure of the given organization and defines physical and logical information as garnishs that be in the given organization. Technical architecture defines the softw ar, hardw atomic number 18 and ne cardinalrk infrastructure that is in place and the required expert resources to procure the mission in question.\r\nThe original aim of the TOGAF was to design and develop technology architecture for a given task entity. However, the framework has evolved becoming a methodology that is used to analyze overall communication channel architecture. This resulted into split of the initiative methodology into two parts: computer architecture tuition Method (ADM) and go-ahead continuum. The ADM guarantees that the end eavour architecture meets the requirements of the organization in equipment casualty of credit line ineluctably and information technology needs.\r\nIts qualification to be bespoke ensures that organizational needs are factored in apiece of the different death penalty steps of the architecture planning process. The process is usually cyclic and iterative because the entire process is split into varietys. The ADM concomitants nine phases; the first is the preliminary and the second to the one-ninth ranges from frame A to descriptor H. Each phase requirements are checked and ensured that it fulfills its staple needs. For ex angstromle, Phase C combines Application and Data architecture and phase B and C ensure that the lucidity of the information architecture is achieved (Lankhorst 2005).\r\nFor the ADM to be successful, effort Continuum comes handy. Generally, the go-ahead Continuum flowerpot be seen as a ‘virtual repository’ of all the assets of the arc hitecture that is in an organization. These assets whitethorn include architectural patterns, architectural models, architecture descriptions and other big artifacts. first step Continuum admits unitedly Solutions and architecture Continuum. The computer architecture Continuum structures the re-usable architecture assets, which brings together representations, rules, relationships of information formations that are forthcoming to the enterprise.\r\nThe Solutions Continuum defines the blocks that are used by the architecture Continuum. This then allows the architectural expression models and blocks that assists building the architecture design and eliminates ambiguity during analytic thinking and implementation of the process. Usually there is a relationship amidst the different EA frameworks in footing of how it operates and tracks that enables it to accomplish its duties. Zachman manikin and TOGAF ADM part share most common features. ADM useping in relation to the Zachman Framework be discombobulates a correlation.\r\nThe Zachman Framework has a hale established and comprehensive taxonomy that supports different models, positioningpoints and other distinguished artifacts, which an enterprise whitethorn consider developing as a phase of the EA (White 2007). The Zachman Framework covers the 30 cells, alone the TOGAF does not cover all the cells. However, it is possible for the TOGAF to develop overtakepoints to accomplish cheeks of Zachman Framework. Nevertheless, there are rough viewpoints that are back up by TOGAF, which are not include in the Zachman Framework. For object lesson, the missing viewpoints include manageability and security.\r\nThe occasion of the architecture is to define viewpoints, an feel that is support by the TOGAF ADM but lacks in Zachman Framework. Zachman Framework vertical axis of rotation provides a source of potentiality viewpoints while the horizontal may provide generic taxonomy concerns. Thus, the Zachman Framework does not shed bureau for processes for conformant views or developing viewpoints. Hence, it does not employ a purview that is shown by TOGAF’s ADM. FEAF structure resembles with TOGAF because it is portioned into Data, Business, Technology and Applications computer architectures.\r\nThus, it contains guidance that is resembling to TOGAF architecture and its architectural viewpoints and emplacements. However, the rows that are in the FEAF matrix do not directly map to TOGAF structure. However, the mapping of ADM to Zachman Framework has nigh correlation surrounded by TOGAF and FEAF. Hence, the columns that are in the FEAF matrix comprise to the third architecture domains that are supported by TOGAF; the stern TOGAF domain covers business architecture that lacks in the FEAF structure.\r\n effort Architecture Planning (EAP) is a framework that brings together Applications, teaching and Technology Architectures in fulfilling the requirements of archit ecture. Thus, it shares many creations with TOGAF because the aim of EAP is to form blueprints for architectures to solve business problems. Moreover, EAP supports the nine phases that are supported by the TOGAF (White 2007). The first three phases in the EAP (Business Architecture) maps to the Phase B of TOGAF ADM. Baseline Description, which is the step 4 in EAP maps to Phases C and D of TOGAF ADM.\r\nThese are some of the basic features that both frameworks share. However, EAP does not support taxonomy of respective(a) views and viewpoints when compared to the TOGAF architecture. Department of defense reaction Architecture Framework (DoDAF) defines the architecture systems into consistent and complementary views. It defines a structure and mechanisms that help in apprehending, visualizing and assimilating the complexities and broad grasp of a given architecture design through tabular, vivid and textual heart. Thus, it shares minimal aspect with TOGAF.\r\nIn fact, TOGAF em phasis on the methodology of architecture in terms of â€Å"how to” without bringing into term architecture description constructs. This perspective is different when it comes to the DODAF architecture. DoDAF main functionality focus on the architecture through a given set of views without any specified methodology, a perspective that is different from TOGAF, which has a specific methodology (Bernus & angstrom unit; Fox 2005). ADM guides the right smart that TOGAF operates, an aspect that is less exhibited in the DoDAF.\r\nThis is because the purpose of architecture determines description of use and supports a well tailored process to fulfill the requirements of the EA (McGovern & Ambler 2003). DODAF requires that all information, depth psychology and products to build should be put forefront before building the architecture. However, TOGAF specify certain requirements that should be in place and assort into the four pillars. DoDAF supports three â€Å"views” Sy stem, usable and Technical while the TOGAF support four views. However, â€Å"views” in DoDAF differs from the view that is seen in the TOGAF.\r\nDeliverables and artifacts that are outlined in the DoDAF have no corresponding parts in the TOGAF ADM. This is because DoDAF goes deeper in determining elaborate of the specific architecture. Thus, DoDAF are at the system design take aim rather than in TOGAF, which is in the architecture level. Nevertheless, the level of feature can be include in the ADM especially at Phase B, C and D of the TOGAF. opening move Architecture plays an important role in ensuring that the business strategy and the requirements of a certain process are achieved.\r\nTOGAF approach is useful in achieving a business-oriented process through a well defined methodology. TOGAF have common features and minor differences with other EA such as the Zachman, FEAF, DoDAF and EAP. The view and viewpoint that is incorporated by the TOGAF ensures that the require ments of the organization are achieved. Thus, TOGAF plays an important role, which is envisaged by other Enterprise Architecture Framework. It fulfills the requirements that it is assigned, however, fulfills it different from the other EA frameworks. References\r\nBernus, P. & Fox, M. (2005). Knowledge share in the Integrated Enterprise: Interoperability Strategies for the Enterprise Architect. London: Birkhauser. The set aside addresses Enterprise Architectures and Enterprise desegregation in a way that makes it easy to hire Enterprise Models and other pattern Tools. It brings together the different models and forms of a framework into fulfilling a requirement. Thus, it develops interchange models between the given modeling tools, adjudge its interdependencies and knowledge on the re-use of enterprise models.\r\nThe authors as well as provide message towards the attainment of the ISO9001:2000. The discussion brings into good will Design of Information alkali Systems for Manufacturing (DIISM’04) and International Conference on Enterprise Integration and Modeling Technology (ICEIMT’04). Fowler, M. & Rice, D. (2003). Patterns of Enterprise Application Architecture. late York: Addison-Wesley Publishers. The adjudge provides proven solutions to the problems that are experienced by information system developers.\r\nThe earmark utilizes code example in terms of C+ and Java. The record turns the problems that are associated with enterprise uses developers into a new strategy that eliminates these problems and ensures that the developers are in an purlieu that they can easily embrace. The authors’ helps professionals to understand complex issues associated with architecture. The hold in of account shows that architecture is crucial in finis of activity development and multi-user environment.\r\nIn addition, the book provides patterns and context in EA that enables the reader to have meet factor to make the properly decisions. Lankhorst, M. (2005). Enterprise Architecture at Work: Modeling, Communication, and Analysis. New York: Springer. The authors bring lighten uply the complexities that are associated with architectural domains. It brings into rumination description of the enterprise architecture and fulfillment into an organization in terms of processes, structure, systems, finishs and techniques.\r\nThe book brings into circumstance description of components and unadorned specification to allow for a logical modeling language. They utilize their skills in ensuring that the architects have concrete skills that fulfill the architectural practice. It as well gives means that allows communication between stakeholders that are involved in these architectures. The authors also provide means to assess both qualitative impact and quantitative aspects of the given architectures. Modeling language that is employ has been used in real-life cases.\r\nMcGovern, J. & Ambler, S. (2003). A pr actical absorb to Enterprise Architecture. New York: apprentice Hall PTR. The authors of the book have hands-on experience in solving real- innovation problems for major corporations. The book contains guidelines that assist the architects to make ace of the systems, data, services, software, methodologies, and product lines. The book also provides explanation of the theory and its application to the real world business needs. Perks, C. & Beveridge, T. (2003). Guide to Enterprise IT Architecture.\r\nNew York: Springer Publishers. The book brings into consideration different Enterprise Architecture frameworks. The authors’ distinctly explains development of a modeling concept through various skilful architecture, e-business and gap analysis. Moreover, the book brings into consideration operating systems and software engineering principles. Moreover, the book relates EA with service instances, distributed computing, application software and enterprise application integ ration. Ross, J. & Weill, P. (2006).\r\nEnterprise Architecture as Strategy: Creating a Foundation for Business Execution. sugar: Harvard Business Press. The aim of EA is to define the requirements of an organization in terms of job roles, standardized tasks, infrastructure, system and data. Moreover, the book also gives guidelines in the way that organizations will postulate in a digitalized world providing managers with means to make decisions and benefit visions that they had planned. Thus, the book explains EA vital role in fulfilling the execution of a given business strategy.\r\nThe book provides thoughtful case examples, clear frameworks, and a proven and legal way of achieving EA. Scheer, A. & Kruppke, H. (2006). carefreeness by ARIS Business operation Management. New York: Springer Publishers. The authors’ brings into consideration the benefits that are associated with utilizing of varies EA frameworks. It brings into consideration the various differenc es that are seen in each EA framework. Moreover, the authors explores the benefits that will result if a given framework is utilised in a given business strategy.\r\nThus, the book is business oriented with EA playing an important role. Schekkerman, J. (2003). How to Survive in the hobo camp of Enterprise Architecture Frameworks, second Ed. New York: Trafford Publishers. This book defines the role that is played by enterprise Architecture Frameworks bringing clearly the main difference between the common Enterprise Architecture Frameworks. This book provides the right procedures and means that can allow pickax of the right Enterprise Architecture Framework.\r\nThe book further gives the write up and overview of various Enterprise Architecture Frameworks and the capabilities that the specified Enterprise Architecture. or so common features of EA that the book explores are principles, purpose, scope, structure, and compliance and guidance to ensure that the right EA is chosen. Wagt er, R. & Steenbergen, M. (2005). high-voltage Enterprise Architecture: How to concur it work. New York: John Wiley and Sons Publications. The authors of the book present a way towards EA that enables organizations to achieve the objectives of their business.\r\nThe book focuses on governance of the IT organization, advice and strategies provide manifest tools that assist in the achievement of the goals of the organization. If all the directives are followed the organization will achieve its goals at a faster speed. White, J. (2007). Managing Information in the Public Sector. New York: M. E. Sharpe. The book covers the basis of information technology, political and managerial issues that orb the EA. This book is specifically create verbally for the public and it covers all problems that are related to IT and the public.\r\n'