TOGAF V91 M12 Views and Viewpoints

Embed Size (px)

Citation preview

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    1/37

    Copy

    Copyright TOGAF is a registered trademark of The Open Group.

    The Open Group is a registered trademark and Boundaryless Information Flow

    is a trademark of The Open Group.

    Lesson 12Views and ViewpointsTOGAF 9.1

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    2/37

    Copy

    Views and

    Viewpoints

    TOGAF is a registered trademark

    of The Open Group in the United

    States and other countries

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    3/37

    Copy

    To understand the concepts of views and viewpoints

    To understand the role of Architecture Views

    To introduce some TOGAF resources

    By the end of thislesson, you will beable:

    Objectives

    Sour

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    4/37

    Copy

    System

    Stakeholders

    Concerns

    View

    Viewpoint

    Concepts and Definitions

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    5/37

    Copy

    A system is a collection of components organized to accomplish a specific functio

    System

    Source: SGI

    Source: IONA

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    6/37Copy

    Stakeholders

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    7/37Copy

    Concerns

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    8/37Copy

    A view is a representation of a system from the perspective of a related set of co

    An architect creates architecture models. A view consists of parts of these arc

    chosen to show stakeholders that their concerns are being met.

    View

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    9/37Copy

    A viewpoint defines the perspective from which a view is taken.

    It defines how to construct and use a view, the information needed, the mode

    expressing and analysing it and a rationale for these choices (Example: Describ

    intended audience of the view).

    Viewpoint

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    10/37Copy

    Source: IEEE Std 1471

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    11/37Copy

    The architect uses views and viewpoints in phases A to D to develop architecture

    (business, data, application, technology).

    A view is what you see. A viewpoint is where you are looking from, the vantag

    perspective that determines what you see

    Every view has an associated viewpoint that describes it, at least implicitly.

    Viewpoints are generic, and can be stored in libraries for reuse. A view is alwa

    architecture for which it is created.

    Views and Viewpoints

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    12/37Copy

    Architecture view is a representation of an overall architecture with meaning to o

    stakeholders in the system. For example:

    A building architect might create wiring diagrams, floor plans, and elevations t

    facets of a building to its different stakeholders (electricians, owners, planning

    An enterprise architect might create physical and security views of an IT system

    What is an Architecture View?

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    13/37Copy

    A Simple Example of a Viewpoint

    Viewpoint Element Description

    Stakeholders Management Board, CEO

    Concerns Show the top-level relationships between geographical sit

    functions

    Modeling technique Nested boxes diagram.

    Outer boxes = locations;

    Inner boxes = business functions.Semantics of nesting = functions performed in the locatio

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    14/37Copy

    A Simple Example of a View

    Off-siteOff-site

    IT Infrastructure

    BurlingtonBurlington

    Management

    ReadingReading San FranciscoSan Francisco Dynamic/ VirtualDynamic/ Virtual Home OfficesHome Offices

    Management Management Management

    Out-sourcedOut-sourced

    PR

    Legal

    Event Management

    HR HR HR

    Finance

    Enterprise Architecture

    IT Development

    IT Support

    Program Management Program Management

    Miscellaneous

    Sales

    Program Management

    Research

    Desktop Support

    MarketingMarketing

    Event Management

    Program Management Program Management

    Event Management

    IT Development

    Figure 1: Example View - The Open Group Business Domains in 2008

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    15/37Copy

    The choice of which particular architecture views to develop is one of the key de

    architect has to make.

    The architect has a responsibility for ensuring:

    the completeness of the architecture; and

    o does it address all the concerns of its stakeholders?

    the integrity of the architecture.

    o

    can the views be connected to each other?o can the conflicting concerns be reconciled?

    o what trade-offs have been made (e.g. between security and performance)

    Developing Views in the ADM

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    16/37Copy

    The pilot has one view of the system, the air traffic controller has another. Neithe

    the whole system. The perspective of each stakeholder constrains how they see t

    Name some elements in the pilots view not viewed by the controller

    Name some elements in the controllers view not viewed by the pilot

    Name some shared elements

    ExerciseViews and Viewpoints for a Simple Airport System

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    17/37Copy

    Describe 2 viewpoints for this system.

    Why is using viewpoints helpful?

    ExerciseViews and Viewpoints for a Simple Airport System

    Th Vi C i P

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    18/37Copy

    Refer any existing libraries of viewpoints.

    Select key stakeholders.

    Analyse stakeholders concerns and document them.

    Select appropriate viewpoints (based on the stakeholders and their concerns)

    Generate views of the system using the selected viewpoints as templates.

    The View Creation Process

    B fit

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    19/37

    Copy

    Ensures less work for the architects. The viewpoints have already been define

    can be created faster.

    Ensures better comprehensibility for stakeholders as the viewpoints are famili

    Ensures greater confidence in the validity of the views as their viewpoints hav

    record.

    Benefits

    Th Vi C ti P

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    20/37

    Copy

    If no libraries of viewpoints exist then:

    select key stakeholders;

    analyse stakeholders concerns and document them;

    develop new viewpoints (based on the stakeholders and their concerns); and

    generate views of the system using the new viewpoints as templates.

    Alternatively create an ad hoc view and then consider whether a generalized form

    viewpoint should be defined explicitly and saved.

    The View Creation Process

    Using TOGAF Artifacts

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    21/37

    Copy

    TOGAF includes an example set of recommended artifacts that can be adopted, e

    combined to produce architecture views.

    The three classes of artifacts defined are:

    Catalogs

    Matrices

    Diagrams

    Using TOGAF Artifacts

    Catalogs

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    22/37

    Copy

    Catalogs are lists of building blocks of a specific type, or of related types.

    For example:

    Principles Catalog created in the Preliminary Phase

    Organization/Actor Catalog created in Phase B

    Driver/Goal/Objective Catalog

    Catalogs

    Matrices

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    23/37

    Copy

    Matrices show the relationships between building blocks of specific types. Matric

    represent list-based rather than graphical-based relationships.

    For example: The Stakeholder Map Matrix created in Phase A

    Matrices

    Stakeholder Map Matrix

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    24/37

    Copy

    Stakeholder Map Matrix

    Diagrams

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    25/37

    Copy

    Diagrams represent building blocks in a rich and visual way. It is especially suited

    communication.

    Example:

    Value Chain diagram created in Phase A

    Business footprint diagram created in Phase B

    Diagrams

    Example Business Footprint Diagram

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    26/37

    Copy

    Example Business Footprint Diagram

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    27/37

    C

    Preliminary Phase

    Principles catalog

    Phase A, Architecture Vision

    Requirements Management

    Phase B, Business Architecture

    Organization/Actor catalog

    Driver/Goal/Objective catalog

    Role catalog Business Service/Function catalog

    Location catalog

    Process/Event/Control/Product catalog

    Contract/Measure catalog

    Business Interaction matrix

    Actor/Role matrix

    Business Footprint diagram

    Business Service/Information diagram

    Functional Decomposition diagram

    Product Lifecycle diagram

    Goal/Objective/Service diagram

    Business Use-Case diagram

    Organization Decomposition diagram Process Flow diagram

    Event diagram

    Phase C, Data

    Architecture

    Data Entity/Data

    Component catalog Data Entity/Business

    Function matrix

    Application/Data matrix

    Logical Data diagram

    Data Dissemination

    diagram

    Data Security diagram

    Class Hierarchy

    diagram

    Data Migration diagram

    Data Lifecycle diagram

    Phase C, Application

    Architecture

    Application Portfolio catalog

    Interface catalog Application/Organization matrix

    Role/Application matrix

    Application/Function matrix

    Application Interaction matrix

    Application Communication

    diagram

    Application and User Location

    diagram

    Application Use-Case diagram

    Enterprise Manageability

    diagram

    Process/Application Realization

    diagram Software Engineering diagram

    Application Migration diagram

    Software Distribution diagram

    Ph

    Phase E. Opportunities & Solutions

    Project Context diagram

    Benefits diagram

    Recommended Architecture Views

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    28/37

    C

    Recommended Architecture Views

    Business Architecture View

    Enterprise Security View

    Software Engineering View

    System Engineering View

    Communications Engineering

    View

    Data Flow View

    Enterprise Manageability View

    Acquirer View

    Summary

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    29/37

    C

    In general, TOGAF embraces the concepts and definit

    2007, specifically those that guide the development o

    view actionable. Such as selecting key stakeholders, aconcerns, and documenting them, and understanding

    deal with those concerns.

    The language used to depict the view is the viewpoint

    architecture concepts from different perspectives, inc

    interfaces, and allocation of services critical to the vie

    Summary

    Summary (contd )

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    30/37

    C

    When applying TOGAF a number of tailoring steps should

    The viewpoints provided should be customized to crea

    architecture views that ensure all stakeholder concern new viewpoints and views should be created to addre

    Summary (contd.)

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    31/37

    C

    Quiz

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    32/37

    Copy

    QUIZ

    a.

    b.

    c.

    d.

    e.

    Views and viewpoints are used by an architect to capture or model t

    system architecture. Which of the following statements is true?1

    Different stakeholders always share the same views

    Some views do not have associated viewpoints

    A viewpoint is the perspective of an individual stakeholder

    A view is the perspective of an individual stakeholder

    Views and viewpoints are rarely used in TOGAF

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    33/37

    Copy

    a.

    b.

    c.

    d.

    QUIZ

    e.

    Different stakeholders always share the same views

    Some views do not have associated viewpoints

    A viewpoint is the perspective of an individual stakeholder

    A view is the perspective of an individual stakeholder

    Views and viewpoints are used by an architect to capture or model t

    system architecture. Which of the following statements is true?1

    Answer: d.

    Views and viewpoints are rarely used in TOGAF

    Exercises

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    34/37

    Copy

    Select a scenario (i.e. a business problem) from your own organization.

    Identify two stakeholders (i.e. human actors) and their place in the business m

    State the views and viewpoints for each stakeholder.

    Exercises

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    35/37

    Copy

    A Vehicle Licensing Bureau has the following stakeholders: licensing authority, ind

    tax authority, car insurance firms, vehicle roadworthiness authority, and law enfo

    Identify two stakeholders (i.e. human actors) and their place in the business m State the views and viewpoints for each stakeholder.

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    36/37

    Copy

    Views and

    Viewpoints

    TOGAF is a registered trademark

    of The Open Group in the United

    States and other countries

  • 7/25/2019 TOGAF V91 M12 Views and Viewpoints

    37/37

    Copy

    Copyright TOGAF is a registered trademark of The Open Group.

    The Open Group is a registered trademark and Boundaryless Information Flow

    is a trademark of The Open Group.

    Thank You