Selecting an Enterprise Architecture Framework_02!20!12v1.1

  • Upload
    casaka

  • View
    217

  • Download
    0

Embed Size (px)

Citation preview

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    1/15

    Enterprise ArchitectureExplaining the What, and Why of the EnterpriseArchitecture Frameworks

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    2/15

    The phrase Enterprise Architecture was first used in 1987 byJohn Zachman in an IBM Systems Journal article titled A

    Framework for Information Systems Architecture, which is all

    pretty academic.

    Intended to address two problems System complexity - organizations were spending more and

    more money building IT Systems

    Poor business alignment - organizations were finding it more

    and more difficult to keep increasingly expensive IT systemsaligned with business needs

    Enterprise Architecture Framework

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    3/15

    Dictionary: framework: n. 1) A structure for supporting or enclosingsomething else, especially a skeletal support used as the basis forsomething being constructed; 2) a simplifieddescription of acomplex entityor process (syn: model)

    EA Context: An EA framework is a model or outline that provides thelogical structure within which EA deliverables will be created andrelated to each other

    Intent of EA Framework: Provide a simplified context for the scope,analysis and structure of an enterprise and its components

    Examples: Zachman Framework for Enterprise Architecture, TOGAF,

    DODAF, MODAF, FEAF

    What is an EA Framework?

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    4/15

    There are many successful Enterprise Architecture Frameworksin use today can we benefit from this accumulation ofknowledge?

    Can we examine in detail the EA Frameworks of others?

    Do we have to reinvent the wheel?

    What reference materials are available?

    This is why TOGAF exists and is freely available.

    TOGAF is a framework a detailed method and set of

    supporting tools for developing an enterprise architecture.

    But where do you start?

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    5/15

    We use the framework to view and understand the enterprise. This view is actually made up of several views, (Business, Data,

    Application, and, Technology views.

    Our view of the enterprise is shaped by our perspective, as viewed from

    the role we play within the enterprise.

    The Value of Enterprise Architecture is in the Relationships

    Enterprise Architecture is more than a collection of the constituent

    architectures (Business, Data, Application, and Technology). The

    interrelationships among these architectures, and their joint properties,

    are essential to the Enterprise Architecture.

    What is an EA Framework?

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    6/15

    Business Manager or User

    an organizational

    structure

    collection of business

    services/processes

    Software Developer

    set of application

    functions

    collection of software

    systems or

    components

    Design or Build Engineer

    collection of

    infrastructure

    components and

    interfaces

    Enterprise Perspective

    I see the enterprise as a.

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    7/15

    So who is right?

    They are all right!

    EAs role is to organize all the views against a common EA framework so

    everyone can understand each others perspective.

    Providing the common language between the business and IT.

    Enterprise Perspective

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    8/15

    Where does TOGAF fit? TOGAF is a mature EA framework that provides organizations with a step by

    step method of creating an enterprise level architecture. It defines placeholders for defining things common to all organizations

    delivering services in an enterprise environment .

    Business architecture The strategy, governance and business processesgoverning how the business goes about its work

    Data architecture A definition of the organizations logical/physical data stores,

    meta data and management resources Application architecture Blueprints for how software systems interact with

    each other, are deployed and their relationships to business processes (mappedin the business architecture)

    Technology architectureThe assets of an organization used to deliver its ITcapabilities. Logical software models, hardware resources, support

    requirements, data/application capabilities etc. Includes things like networktopologies, comms, standards etc.

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    9/15

    Putting it all together

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    10/15

    Or maybe this.

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    11/15

    Benefits of Adopting TOGAF

    There are many benefits in adopting a standardizedarchitecture framework rather than rolling our own, here are

    but a few:

    reduced costs to maintained

    shorter ramp-up times

    readily available trained technical resources

    available ecosystem of standardized artifacts, and automation tools

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    12/15

    What if

    Another approach to evaluating the importance of EAFramework is by asking the question, What if we didnt have

    EA Framework?

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    13/15

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    14/15

    Questions?

  • 7/31/2019 Selecting an Enterprise Architecture Framework_02!20!12v1.1

    15/15

    Ok here is the TOGAF framework