Enterprise Architecture Framework - Research Paper Example

Enterprise Architecture Framework Institute Table of Contents Table of Contents 2 Introduction 3 2- Enterprise Architecture Domains 4 3- EA vision and Benefits 6 3.1- Clarify Information technology investment decision-making 7 3.2- Accelerates system implementation 8 3.3- Enterprise Architecture offers Reduces system diversity 8 4- EA frameworks 8 4.1- DoDAF 8 4.2- MODAF 9 4.3- NATO 9 4.4- AGATE 10 4.5- DNDAF 10 5- Comparison between frameworks 11 6- EA Tools 12 7- Conclusion 13 8- Reference 13 1- Introduction Enterprise architecture provides the foundation to the higher administration planned for getting consistent, superior quality response from both complete functional data as well as of informational data improvement to respond their specific inquiries about the analysis of the company. The effective approach of architecture generally allows consistent, higher quality management of the diversity of business measures plus their essential strategies related to the business. So by means of an architecturally proposed system, the efficiency of the clients of the information system would probably augment for the reason of enhanced systems analysis as well as design of the system. An architected system will frequently provide a pervasive "appearance and experience" that makes the whole systems more identifiable and consequently make the systems simpler and rather easy to learn and use (Finneran). From the perspectives of a lot of people of the industry, there is nothing considered to be vital for the transactions of the business than the utilization of working descriptions. It could as well be presumed that nothing is extra isolated." An architectural method provides operational descriptions as a part of its extensive business terminology furthermore consequently help widespread establishment of business strategies and enforcement methods. Additionally, the enterprise architecture provides a deep understanding into business process improvement (equally in total quality management (or TQM) and/or re-engineering) by describing preliminary business procedural paradigm and makes the consequence reliance so significant to the development of business procedures and methodologies. Moreover, the enterprise architecture provides a useful technique to speak about the architecture mechanisms to the objectives of the business as well as specific goals to be achieved, therefore providing impending into the business inspiration in terms of both the data as well as procedures of the business (Finneran) and (wikipedia-1). An effectively managed enterprise architecture scheme looks for to support the handy information management transactions, to the level that is rather possible as well as gives assured utilization of metrics to efficiently estimate the quality as well as amount of both the business procedure plus the productivity supported for information technology. An enterprise architecture framework assembles cooperative techniques, tools, procedure standards, artifact descriptions, orientation models plus management carried out by the architects in the formation of specific elucidation of architectural enterprise (wikipedia-1) and (Finneran). So in this connection the current research covers a detailed analysis of some of the prominent characteristics and circumstances for the enterprise architecture framework, EA Domains, EA visualization and advantages, EA frameworks, framework evolution and EA Tools. This paper will assess and compare some of the main enterprise architecture frameworks and present a much closer look toward their contribution and implementation for an enhanced management and management of the corporation. 2- Enterprise Architecture Domains Generally a number of enterprise architecture frameworks don’t achieve something into an efficient performance of enterprise design into a number of applicable areas or "domains". In this scenario, according to the viewpoints of Spewak & Hill (1992), enterprise architecture practice is divided into two basic and important domains at level 2: that are "business modeling" along with "current systems and technology" in addition to three secondary domains at level 3: which are "application’s architecture", "data architecture", and "technology architecture". The last level of Spewaks enterprise architecture planning is the "methods" or "implementation" level, which is concerned with "how" to convey the enterprise to compete with the new and innovative paradigm (wikipedia-1), (Spewak and Hill) and (Finneran). The prominent TOGAF structure splits the application into three useful domains: "information systems architecture", "business architecture" and "technology architecture" as well as afterward subdivides the information systems design into "information architecture with "applications architecture" (wikipedia-1) and (Finneran). The strategic architecture model allows for a flexible severance up to ten domains including a lot of features of an enterprise from its goals and objectives in the course of its projects and programs related to its technology and software applications (wikipedia-1) and (Opengroup). The extrication of the performance into a numeral of domains allows enterprise architects to better explain an enterprise from a number of significant viewpoints. This application as well offers confidence with the support of a lot of individuals plus sanctions the practice as a whole to build high-quality exploitation of individual domain-specific proficiency and understanding. By adopting this technique, enterprise architects are capable to make sure a holistic elucidation is formed. The well-known plus most widespread 4 domains as well as their component parts are described as below (wikipedia-1), (Finneran) and (Spewak and Hill): Business domain is about the maps of business rules and guidelines, aspirations and objectives, business tactics, Operating Model. In this arrangement we can observe the functional disintegrations (for instance SADT, IDEF0), company potentials plus organizational paradigms that are expressed like enterprise / line of the company architecture. Information domain is about the business information architecture that provides a functionally related outlook on the exchange and flow of business and corporate information in a company. This domain holds and maintains the metadata that is the data that clearly clarifies data basic of our enterprise. In addition, the data models are the abstract expressed in an information domain for the purpose of supporting enterprise information architecture, both logical, and physical. Applications domain is about the application software diagrams and inventories, which have been expressed like academic / realistic or structure of enterprise / line of company architectures. This domain also characterizes the limitations among various applications such as messages, events and flows of data. Technology domain is about the inter-application intervene software or middleware. This domain is basically concerned with the settings and configuration of the application accomplishment and working structures comprising applications server status, operating systems, verification, permission settings, security systems, operating and monitoring systems. Operating system domain is about the infrastructure software that is developed by taking into account the requirement of DBMS (database management system) and application servers. This domain involves the programming languages, etc. that is expressed like company / line of company technology structural plan. 3- EA vision and Benefits The majority of businesses have been facing a lot of problems to clarify and handle the financial benefits of enterprise architecture. Additionally, numerous Governmental organizations are accepting enterprise architecture like the fraction of their renovation and E-Government tactics. A functionally related enterprise architecture technique is competent to carry many advantages to the organizations by relying on the focus of where to ascertain these advantages and profits. Even so enterprise architecture takes the basis planned for enterprise portfolio management, the ultimate corporate driver that has been designed for enterprise architecture. Each enterprise development is eventually explicated into profit or cost saving proposed for the business. Considering large management plus external stakeholders are the prime factors which matter a lot in this architecture. However, to evaluate the outcome of Enterprise Architecture achievements straightly at this economic gauge intensity is not possible. A profit tree would reveal that how a development is surged to an income or economy. Some of the main advantages of enterprise architecture are described below (Grigoriu) and (wikipedia-1): Decrease in replacement of platforms, policies in a multiplicity of divisions of the Enterprise Removal of hair ball relations in the course of integration Opening of modular services/borders Corporate technology values/standards Establishment of procedures arrangement to the company functional necessities Structures arrangement to the corporate strategic requirements Below I will summarize some of the main benefits of enterprise architecture regarding the defense areas (HUD): 3.1- Clarify Information technology investment decision-making EA application generally uses designs to improve the assessment of the proposed IT programs. These designs offer a general language that associates proposals of IT with the premeditated and pre-defined objectives of the department and significant tasks of the business. Our straightforward methodology offers managerial level personnel with a tactical, enterprise outlook of HUD’s assortment of IT (HUD) and (wikipedia-1). 3.2- Accelerates system implementation Enterprise architecture practice is concerned with the present strategies to boost up system design as well as improvement. In order to fulfill this purpose plans are operational documents since the plans describe introductory company procedures and practices, numerous elements of data, cross-cutting functions and standard coordination platforms. Blueprints are then utilized to validate requirements of prevalent system that mostly covers program regions, and helps to improve the way of communication among various program regions and technical personnel to better describe practice requirements (HUD) and (wikipedia-1). 3.3- Enterprise Architecture offers Reduces system diversity Enterprise architecture application employs plans to make overall working and operational environment efficient. Additionally, the EA supported plan describes basic procedures of the business, frequent data essentials, standard applications and various policies. Moreover, the standardization diminishes the quantity of IT products, lessens maintenance of system, expenditure, and simplicity in personnel training and learning (HUD) and (wikipedia-1). 4- EA frameworks 4.1- DoDAF The DoDaF (department of defense architecture framework) is a proposed illustration to business, the enterprise architecture, and structures design for balancing and consistent visions. The Department of Defense Architecture Framework describes a collection of useful objects that carry out system intended tasks for comprehending, envisaging as well as integrating the wide range and densities of a structural clarification in the form of grid of rows and columns, graphic or illustrative form and plain wording. It is specifically suitable for huge systems by means of complex incorporation and challenges of interoperability; also it appears to be exceptional in its usage of features acknowledged as "operational views" to the outdoor customers working domain in an effort to develop a structure that will work effectively (WikiPedia-2). 4.2- MODAF The British MODAF (British Ministry of Defense Architectural Framework) is an architectural structure that describes a standardized method of the performance of enterprise architecture, initially developed by the United Kingdom Ministry of Defense. In the beginning the idea of Ministry of Defense Architectural Framework was to provide diligence and arrangement to maintain the description as well as assimilation of the potential of Ministry of Defense tools, primarily in support of NEC (network enabled capability). In recent times Ministry of Defense has been effectively employing Ministry of Defense Architectural Framework to strengthen the utilization of the enterprise architecture procedure to detain the information about the company to better recognize and distinguish the procedures as well as resources that are necessary for the fulfillment of the idea expressed in the policy (WikiPedia-3). 4.3- NATO The NATO structural Framework is an enterprise architecture framework developed by the NATO imitative from the Department of Defense Architecture Framework enterprise architecture. At present the existing NATO C3 System Architecture Framework v2 (NAF v2), published by NATO in September 2004 presents great support and help on offering communication technology as well as information systems. Amendment 3 of the NAF or NATO Architecture Framework, circulated in year 2007, is almost impossible to differentiate to MODAF at its basis; however it extends the structure through accumulation of views proposed for the analysis of bandwidth, SOA and standard and plausible configurations and variations. NATO Architecture Framework employs the similar meta-model like MODAF. The meta-model is recognized in chapter 5 of the NATO Architecture Framework. Edition 3.1 of the NMM is the same as v1.2.003 of the Ministry of Defense Architectural Framework Meta-Model (WikiPedia-4). 4.4- AGATE Atelier de Gestion de lArchiTEcture des systèmes dinformation et de communication or AGATE is a structure designed for illustrating computer or communication structural architecture. It is encouraged by the DGA or Délégation Générale pour lArmement, the French administration association that performs development as well as evaluation programs planned for weapon systems and designed to serve the French forces. The whole DGA weapons as well as information technology system procurements are necessary to certify and identify their planned system architecture by means of the set of examinations approved in AGATE. AGATE is analogous to DoDAF, encouraged through U.S. Department of Defense (DoD) or Ministry of Defense Architectural Framework, supported through UK’s MoD or Ministry of Defense. Though, the reality that the AGATE orientation is simply obtainable in French appears to restrict it’s utilization to the French weapons acquisition structure (Wikipedia-5) 4.5- DNDAF The existing DNDAF V1.6 has been established to offer standard structural design framework planned for the sustained development and management of the DND/CF enterprise architecture. Additionally, the DNDAF provides an uninterrupted procedure to start out, apply, and maintain the jobs and responsibilities of DND/CF EA structure. In addition, a newest DNDAF V1.7 considerably increases the proceedings of this architecture and will be published in the near future. The DNDAF V1.6 identifies a standard technique as well as guidance in the effective utilization of supporting tools that have been designed for the improvement as well as detention of the DND/CF EA. The DNDAF V1.6 is divided into 4 levels (WikiPedia-6). 5- Comparison between frameworks This section provides a comparison and disparity of EA frameworks like DODAF 1.5, DODAF 2.0, MODAF 1.2, TOGAF 9 and NAF: MODAF is designed on the basis of DoDAF version 1 dimension, as well as it involves the major differences among MODAF, as illustrated by the MODAF Meta Model (M3) and the existing version of DoDAF. It is consistent that DoDAF appears to be in a state of progress that the contents of this section should not be taken as demonstrating substantial divergence as of the growing DoDAF (MOD.UK). The DoDAF or Department of Defense Architecture Framework, Edition 2.0 is the dominant, inclusive structure and abstract model that allows the development of architectures to help the capability of Department of Defense (DoD) administrators at the entire levels in order to formulate their important decisions more successfully through a planned distribution of information across the regions, Joint Capability Areas (JCAs), assignment, constituent, as well as various program limitations (DoDAF-V2.0 ). By means of these two classifications of frameworks there exists a group of objects, techniques and tools that are consequential. These are consequential on the established problem sets described previously. As these are resultant, the yield or production can be extremely different. All- Purpose structures (DoDAF-V2.0 ): Describes an open and reliable description of terms in the course of taxonomies as well as ontology. Disbeliever to managerial structure Low level procedure agnostic SDLC PMO Service Management Extremely configurable to businesses Area particular to EA Frameworks Regulatory leadership for Managerial structures Procedures Objects Typically deliver plenty of templates Plenty of real world instances 6- EA Tools This section presents a brief introduction of some of the main tools of the EA framework. Here I will discuss Sparx System and MagicDraw. Sparx Systems is an award winning UML 2.3 supported, team-based variety tools that is providing an atmosphere that holds and manages the complete product development lifecycle, by means of high-performance illustration tools which have been designed for the modeling of company, enterprise architecture, systems engineering, necessities of an organization, software arrangement, code development, testing and a great deal of more available options. This system is offering a complete tool for life cycle to put together our working members as well as take our common visualization into the life (Sparxsystems). MagicDraw is also an award-winning company procedure, structural design, software as well as system modeling tool with respect to the facilities of teamwork. This tool is designed for software analysts, business forecasters, QA engineers, programmers and documentation writers. Additionally, the MagicDraw software is a dynamic and flexible development tool which assists in the analysis as well as design of Object Oriented (OO) structures as well as databases. It gives the industrys most excellent ways of code engineering (by means of complete round-trip maintenance planned for C++, Java, CL (MSIL), C# as well as CORBA IDL programming languages), in addition to database representation modeling, DDL creation along with reverse engineering services (MagicDrawTM)& (Magicdraw). 7- Conclusion This paper has presented a deep analysis of some of the prominent characteristics and areas of deep consideration of the enterprise architecture framework (EA Framework). In this research I have also discussed the structure for enterprise architecture, enterprise architecture framework, EA domains, EA vision and benefits, EA frameworks, framework evolution and EA tools. I hope this paper will definitely provide a detailed analysis of major and considerable areas of the EA framework. 8- Reference DoDAF-V2.0 . "The DoDAF Architecture Framework Version 2.0." 2010. 09 10 2010 . Finneran, Tom. "Enterprise Architecture: What and Why?" 1998. 15 10 2010 . Grigoriu, Adrian. "Enterprise Architecture Matters." 2010 . 12 10 2010 . HUD. "Benefits of Enterprise Architecture ." 2010. 12 10 2010 . Magicdraw. "Commercial Plug-ins." 2010. 14 10 2010 . MagicDrawTM. "Introducing MagicDraw." 2010. 12 10 2010 . MOD.UK. "Relationship to DoDAF." 2010. 12 10 2010 . Opengroup. "The Open Group Architectural Framework (TOGAF) 8.1.1." 2009. 12 10 2010 . Sparxsystems. "Testimonials." 2010. 12 10 2010 . Spewak, Steven H and Steven C Hill. Enterprise Architecture Planning - Developing a Blueprint for Data Applications and Technology. John Wiley, 1992. wikipedia-1. "Enterprise architecture." 2010. 12 10 2010 . WikiPedia-2. "Department of Defense Architecture Framework." 2010. 14 10 2010 . WikiPedia-3. "Ministry of Defence Architectural Framework." 2010. 15 10 2010 . WikiPedia-4. "NATO Architecture Framework." 2010. 09 10 2010 . Wikipedia-5. "AGATE (architecture framework)." 2010. 07 10 2010 . WikiPedia-6. "DNDAF - Volume 1: Overview and Definitions." 2010. 10 10 2010 . Read More