Navigation
  • Home
  • Recent
  • Most Active
  • Popular
  • Blog
  • Credits
  • RSS
  •   Interaction
  • Register
  • Statistics
  •   Help
  • Suggestions
  • Contact Us
  • How to Edit
  • Help



  • [Edit]


    Enterprise architecture is the practice of applying a comprehensive and rigorous method for describing a current and/or future structure and behavior for an organization's processes, information systems, personnel and organizational sub-units, so that they align with the organization's core goals and strategic direction. Although often associated strictly with information technology, it relates more broadly to the practice of business optimization in that it addresses business architecture, performance management and process architecture as well.

    Enterprise architecture is becoming a common practice within the U.S. Federal Government to inform the Capital Planning and Investment Control (CPIC) process. The Federal Enterprise Architecture (FEA) reference models serve as a framework to guide Federal Agencies in the development of their architectures. The primary purpose of creating an enterprise architecture is to ensure that business strategy and IT investments are aligned. As such, enterprise architecture allows traceability from the business strategy down to the underlying technology.

    Companies such as BP, Intel and Volkswagen AG also have applied enterprise architecture to improve their business architectures as well as to improve business performance and productivity.


        Enterprise architecture
            Enterprise architecture methodology
            Relationship to other IT disciplines
            Enterprise architecture frameworks
            Certification of information, enterprise and IT architects
            More information
            Published examples of enterprise architecture

    top

    Enterprise architecture methodology

    The practice of enterprise architecture involves developing an architecture framework to describe a series of "current", "intermediate" and "target" reference architectures and applying them to align change within the enterprise. These frameworks detail all relevant structure within the organization including business, applications, technology and data. This framework will provide a rigorous taxonomy and ontology that clearly identifies what processes a business performs and detailed information about how those processes are executed. The end product is a set of artifacts that describe in varying degrees of detail exactly what and
    how a business operates and what resources are required. These artifacts are often graphical.

    Given these descriptions whose levels of detail will vary according to affordability and other practical considerations decision makers can make informed decisions about where to invest resources, where to realign organizational goals and processes and what policies and procedures will support core missions or business functions.

    A strong enterprise architecture process helps to answer basic questions like:

      Is the current architecture supporting and adding value to the organization?
      How might an architecture be modified so that it adds more value to the organization?
      Based on what we know about what the organization wants to accomplish in the future, will the current architecture support or hinder that?

    A value-based approach to implementing an enterprise architecture is recommended in order to realize quick wins, most notably when the team is first being formed. An analysis of key questions as listed above that provide the most value in your organization should lead your enterprise architecture team towards their highest priority tasks. Teams that spend too much time documenting without providing real value to decision makers will be at risk of being disbanded.

    Implementing enterprise architecture generally starts with documenting the organization's strategy and goals.

    The architecture process addresses documenting and understanding the discrete enterprise structural components, typically within the following four categories:
      Business:
        Strategy maps, goals, corporate policies
        Organization cycles, periods and timing
        Suppliers of hardware, software, and services
      Applications:
        Applications and software inventories and diagrams
        Interfaces between applications - that is: events, messages and data flows
      Information:
        Meta data
        Data models: conceptual, logical, and physical
      Technical:
        Hardware, platforms, and hosting: servers, and where they are kept
        Operating System
        Infrastructure software: Application servers, DBMS, etc...

    Wherever possible, all of the above should be related explicitly to the organization's strategy, goals, and operations for planning and decision-making needs. The enterprise architecture is most useful when documenting the current state of the technical components listed above, as well as an ideal-world desired future state (Reference Architecture) and finally a "Target" future state which is the result of tradeoffs and compromises vs. the ideal state. Special software is available and becoming increasingly mature to handle the complex task of mapping the enterprise structure.

    Such exhaustive mapping of IT dependencies has notable overlaps with both Metadata in the general IT sense, and with the ITIL concept of the Configuration Management Database. Maintaining the accuracy of such data can be a significant challenge. The use of a CMDB solutions are for managing the current state effectively, while the longer term planning of enterprise architecture tools and practice is employed for corporate project and strategic planning exercises.

    Governance is the key process to keep organizational changes on target for meeting articulated goals and strategies defining the future state of the enterprise. Governance can be applied in various strengths from strongly enforced policies, to more subtle means such as the agreement and declaration of IT principles.

    Enterprise architecture requires appropriate positioning in the organization to be successful. One such analogy of city-planning is often referenced for enterprise architecture groups. A common issue for groups that are granted too much authority is becoming known as an "Ivory Tower" group, alienating the teams involved in following architectural governance. A combination of federated and a small Enterprise team can be the most successful implementation with a focus on democratic vs. authoritarian team involvement.

    An intermediate outcome of implementing an enterprise architecture process is a comprehensive inventory of business strategy, business processes, organizational charts, technical inventories, system and interface diagrams, and network topologies, and the explicit relationships between them. The inventories and diagrams are tools to support decision making at all levels of the organization. It is key that the information remain current to be relevant and useful, a process must exist to keep the information "evergreen."

    The organization must design and implement processes that ensures continual movement from the current state to the future state, keeping the details current. The future state planning will generally be a combination of one or more:
      Closing gaps that are present between the current organization strategy and the ability of the IT organization to support it
      Closing gaps that are present between the desired future organization strategy and the ability of the IT organization to support it
      Necessary upgrades and replacements that must be made to the IT infrastructure using lifecycle management practices for infrastructure and technologies employed, to address ever changing regulatory requirements, and other initiatives not driven explicitly by any single team in the organization's functional management. One such example is Service Oriented Architecture, an ideal candidate for enterprise architecture team leadership.

    top

    Relationship to other IT disciplines
    Enterprise architecture is a key component of the Information technology governance process at any organization of significant size. More and more companies are implementing a formal enterprise architecture process to support the governance and management of IT. However, as noted in the opening paragraph of this article it ideally relates more broadly to the practice of business optimization in that it addresses business architecture, performance management and process architecture as well. Enterprise architecture is also related to Performance Engineering, IT portfolio management and Metadata in the enterprise IT sense.

    top

    Enterprise architecture frameworks

      Zero Delta Framework & Integrated Methodology *.

    top

    Certification of information, enterprise and IT architects

    top

    More information
      Training and Certification combined is the most effective way to create productive EA Practitioners. The FEAC Institute is tool neutral and Framework agnostic. It has available FEAF and DoDAF Executive, 3-Day, 5 Day workshops and has the premier Certification program consisting of 5 quarter courses the fifth being a practicum where the students build part of an EA, taught in mixed mode utilizing face to face instructions and an electronic classroom *
      The information exchange area of the Institute For Enterprise Architecture Developments is delivering information about: EA standards, methods, tools, best practices, presentations, publications, certification, books, links, etc. More info about Enterprise Architecture
      The US Government has mandated the use of a formal Enterprise Architecture process for all federal agencies with the Clinger-Cohen act of 1996.
      Enterprise architecture can be seen as overly prescriptive and academic; agile approaches are proposed by some.
      Several Enterprise Architecture software tools exist to document and facilitate Enterprise Architects. More info about EA Tools
      For managing complexity of Enterprise Architecture and for a possible service oriented design, clustering may be a valuable approach developed by the ea builder research project: ea-builder.de.
      EABOK - The Guide to the Enterprise Architecture Body of Knowledge - provides a guide to EA in the context of legislative and strategic business requirements.
      * The EA architecture is best delivered by practitioners with hands-on knowledge and application in EA, BPR, and DoDAF. Wizdom has in-depth experience in EA standards, and provides EA/DoDAF books, training, EA software tools, and support: More information about Wizdom EA

    top

    Published examples of enterprise architecture
      US FEA - Federal Enterprise Architecture reference models, which include XML formats for EA reference model data transfer




     
    Search more:
     

       
    Source Privacy License Download Contact Us Atlas
    Scientus.org Dictionary (Yet Another Wiki) RC : 1.39
    This article is licensed under the GNU Free Documentation License [copyleft]. It uses material from the Wikipedia article "Enterprise architecture". link