An Introduction to TOGAF

An Overview TOGAF (The Open Group Architecture Framework)
September 2008 – <onSite in Rome>
1

Agenda

Overview of EA Overview of TOGAF

TOGAF v8
Value of TOGAF Comparison with ADM TOGAF v9

Copyright © 2008 Accenture All Rights Reserved.

Overview of Enterprise Architecture
An Enterprise Architecture supports the business by providing the fundamental technology and process structure for an IT strategy. This in turn makes IT a responsive asset for a successful modern business strategy.
Enterprise: Collection of organisations that share common set of goals • Government agency • Part of a corporation • Corporation Large corporations comprise multiple enterprises May be an ―Extended enterprise‖ Including partners, suppliers and customers Drivers: Laws and regulations • Clinger-Cohen Act (US Information Technology Management Reform Act 1996) • EU Directives on the Award of Public Contracts • Sarbanes-Oxley • • • • • More extended enterprises More co-operative IT operations Greater publicity to failures Increase in litigation Audit requirements Architecture: Fundamental organisation of something, embodied in Its components, their relationships to each other and the environment, And the principles governing its design and evolution

Why Enterprise Architecture?
A good Enterprise Architecture enables you to achieve the right balance between IT efficiency and business innovation.

 Effective management and exploitation of information through IT is key to business success  Good information management = competitive advantage  Current IT systems do not really meet the needs of business

• Fragmented, duplicated • Poorly understood • Not responsive to change
 Investment in Information Technology

• Focused on system maintenance • Tactical developments rather than a strategic plan

Enterprise view of capabilities required to execute strategy

Individual Capability Blueprints

Levels of Architecture The levels of Architecture consist of the Business Architecture. Source: The Open Group. Architecting the Enterprise . Information Systems Architecture and Technology Architecture.

who is responsible for them. who is involved and who is accountable? • Value creation through monitoring. and feedback • Increased visibility supporting internal processes and external parties‘ requirements .The importance of Governance The adoption of governance into TOGAF aligns the framework with current business best practice and also ensures a level of visibility.  An Enterprise Architecture is only as good as the decision making framework that is established around it ‖governance‖ framework  The Governance Framework depends on a clear authority structure and the right participants Benefits: • Increased transparency of accountability. monitoring. and informed delegation of authority • Controlled risk management • Protection of the existing asset base through maximising re-use of existing architectural components • Proactive control. concept. evaluation. and component re-use across all organisational business units Governance: Governance looks at the way in which decisions are made. measuring. guidance. and management mechanisms • Process. and control that will support all architecture stakeholder requirements and obligations.

. and make certain that the architecture selected allows for future growth in response to the needs of the business.Architecture Framework Using an architecture framework will speed up and simplify architecture development. ensure more complete coverage of the designed solution.  It should contain a set of tools and provide a common vocabulary.  It should describe a method for designing an information system in terms of a set of building blocks.  It should also include a list of recommended standards and compliant products that can be used to implement the building blocks. and for showing how the building blocks fit together.  An architecture framework is a toolkit which can be used for developing a broad range of different architectures.

Agenda Overview of EA Overview of TOGAF TOGAF v8 Value of TOGAF Comparison with ADM TOGAF v9 Copyright © 2008 Accenture All Rights Reserved. .

TOGAF consists of 3 main parts: 1. The TOGAF Resource Base: a set of resources: guidelines. architecture descriptions. proven method for developing an IT Enterprise Architecture that meets the needs of your business.The Components of TOGAF A set of methods and tools for developing a broad range of different IT architectures.  The key to TOGAF is the Architecture Development Method (ADM) — a reliable. The Enterprise Continuum: a ‗‗virtual repository‘‘ of all the architecture assets: models. 3. evaluate. The TOGAF Architecture Development Method (ADM): explains how to derive an organisation-specific Enterprise Architecture that addresses business requirements. . background information to help the architect in the use of the ADM. It enables you to design. and build the right architecture for your organisation.  TOGAF is an architecture framework — The Open Group Architecture Framework. 2. patterns. templates. etc.

Enterprise Continuum The Enterprise Continuum provides a framework and context for the leveraging of relevant architecture assets in executing the ADM. Guides and supports Guides and supports Guides and supports Guides and supports Enterprise Continuum = Architecture Continuum + Solution Continuum .

Reference Models Technical Reference Model: Reference Models: Focuses on the application platform Integrated Information Infrastructure Reference Model:  A major challenge in any project is effective communication between all participants  Reference models create the common vocabulary and structure  Use of reference model(s) is essential to identify duplicate functionality and opportunities for infrastructure simplification Focuses on the flow of information at the application level .

Agenda Overview of EA Overview of TOGAF TOGAF v8 Value of TOGAF Comparison with ADM TOGAF v9 Copyright © 2008 Accenture All Rights Reserved. .

)  Version 8: • An overall structure and core method for enterprise architecture that can be filled out in future years. DoD Framework. FEAF.TOGAF 8 Scope and Goals TOGAF 8 scope covers the development of four related types of architecture: TOGAF 8 Goals:  Long-term: • An industry standard. (not TOGAF or…. not method – TOGAF and…. • ….usable in conjunction with frameworks having products relevant / specific to particular sectors. generic enterprise architecture method…. – Several frameworks have mindshare: • Zachman. Spewak. … – Almost all focus on products. . TEAF.

industry models. system models.The Enterprise Architecture Development Method The EA Development Method… for defining business needs and developing an architecture that meets those needs.…)  Decisions based on: • Competence / resource availability • Value accruing to the enterprise.  An iterative method  Each iteration = new decisions: • Enterprise coverage • Level of detail • Time horizon • Architecture asset re-use: – Previous ADM iterations other frameworks. . utilising the elements of TOGAF and other architectural assets available to the organisation.

Produce implementation roadmap Opportunities and Solutions Identify major implementation projects Technology Architecture Technology supporting the organisation .The Enterprise Architecture Development Method The Preliminary Framework and Principles sets the direction for the architecture as it prepare the organisation for a successful architecture project. In each case develop the baseline ―as is‖ and target ―to be‖ and analyse gaps Architecture Change Management Ensure that the architecture responds to the needs of the organisation Requirements Management Every stage of the project should be based on and validate business requirements Implementation Governance Ensure that the implementation project conforms to the architecture Business Architecture Develop architectures at 3 levels Migration Planning Information Systems Architecture Systems supporting the processes Analyse cost benefits and risk.

business goals. and business drivers . or reference to. or benefit from.Frameworks and Principles To ensure that everyone who will be involved in. this approach is committed to the success of the architectural process Objectives:  This phase prepares the organisation for a successful Enterprise Architecture project • • • • • • Understand business environment High level management commitment Agreement on scope of architecture activities Establish principles Establish governance structure Agree method Outputs:  This phase prepares the organisation for a successful Enterprise Architecture project  Framework definition  Architecture principles  Restatement of. business principles.

Architecture Principles  General rules and guidelines that support the way in which an organisation sets about fulfilling its mission • Enduring and seldom amended • Clearly related back to the business objectives  Value • As drivers for defining the functional and non-functional requirements • To provide a framework within which the enterprise can start to make conscious decisions about IT • As a guide to making choices • As an input to assessing both existing systems and the future directions .

expectations for this project • Required at the start of every architecture cycle  Validates business context  Creates Statement of Architecture work . and Architecture Vision  Develop Statement of Architecture Work and Secure Approval Outputs:  Approved Statement of Architecture Work  Refined statements of business goals and strategic drivers  Architecture principles  Architecture Vision • Sets scope. Business Requirements. Objectives:  Initiates one iteration of the architecture process Steps:  Establish the Project  Identify Business Goals and Business Drivers  Review Architecture Principles. constraints. including Business Principles  Define Scope  Define Constraints  Identify Stakeholders and Concerns.A) Architecture Vision The Architecture Vision is essentially the architect‘s ‗‗elevator pitch‘‘ — the key opportunity to sell the benefits of the proposed development to the decision-makers within the enterprise.

Applications. • their relationships to each other and the environment.B) Business Architecture A knowledge of the Business Architecture is a prerequisite for architecture work in any other domain (Data. and is therefore the first architecture activity that needs to be undertaken. . Technology). Business Architecture:  The fundamental organisation of a business. • and the principles governing its design and evolution  Shows how the organisation meets it‘s business goals Steps: • Confirm context • Define baseline • Define target • Views are important • Validate • Requirements • Concerns • Gap analysis • Produce report Outputs: • Organisation structure • Business goals and objectives • Business functions • Business Services • Business processes • Business roles • Correlation of organisation and functions. embodied in • its business processes and people.

C) Information Systems Architecture Objectives:  The fundamental organisation of an IT system. or in parallel • • Theory suggests Data Architecture comes first Practical considerations may mean that starting with Application Systems may be more efficient Outputs: • Statement of Architecture Work • Baseline & Target Data Architecture • Baseline & Target Applications Architecture • Data and Application Architecture views  There will need to be some iteration to ensure consistency . Data or Applications First? • and the principles governing its design and evolution  Shows how the IT systems meets the business goals of the enterprise Steps: • Data Architecture • Applications Architecture  It is usually necessary to address both • Not always the case. embodied in • the major types of information and the application systems that process them • their relationships to each other and the environment. depending on project scope and constraints  May be developed in either order.

software and communications technology • their relationships to each other and the environment. embodied in • its hardware. Objectives:  The fundamental organisation of an IT System.D) Technology Architecture A Technology Architecture that will for m the basis of the following implementation work. • and the principles governing its design and evolution Steps: • Develop Baseline Technology Architecture Description • Develop Target Technology Architecture Outputs: • Statement of Architecture Work • Baseline Technology Architecture • Validated technology principles • Technology Architecture Report • Target Technology Architecture • Technology Architecture. gap report • Viewpoints addressing key stakeholder concerns • Views corresponding to the selected viewpoints Developing the Technology Architecture .

and benefits of the various projects  Identify the strategic parameters for change  Generate an overall implementation and migration strategy . and the toplevel projects to be undertaken in moving from the current environment to the target Objectives:  Decide on approach • Make v Buy v Re-Use • Outsource • COTS • Open Source  Assess priorities • Identify Key Business Drivers • Review Gap Analysis • Brainstorm Technical Requirements • Brainstorm Co-existence and Interoperability • Brainstorm Co-existence and Interoperability • Implementation and migration strategy • High-level Implementation Plan • Impact Analysis Steps: Outputs:  Identify the dependencies.E) Opportunities and Solutions Identifies the parameters of change. costs. the major phases along the way.

if appropriate) Objectives:    Cost/benefit analysis Risk assessment Technology roadmap . Key business drivers to be addressed that will also tend to dictate the sequence of implementation.F) Migration Approach The objective of the Migration Approach phase is to sort the various implementation projects into priority order. such as:     Reduction of costs Consolidation of services Ability to handle change A goal to have a minimum of ‗‗interim‘‘ solutions Steps: • Prioritise projects • Estimate resource requirements and availability • Perform cost/benefit assessment of the various migration projects • Perform risk assessment • Generate implementation roadmap • Document the Migration Plan Outputs: • Impact Analysis • Detailed Implementation Plan and Migration Plan • Including Architecture Implementation Contract.

G) Implementation Governance All the information for successful management of the various implementation projects is brought together. Objectives:  Defines architecture constraints on implementation projects • Architecture contract  Monitors implementation work for conformance Steps: Outputs: • Formulate Project Recommendation • Document Architecture Contract • Review Ongoing Implementation Governance and Architecture Compliance • Impact Analysis • Architecture Contract • The architecturecompliant implemented system .

H) Architecture Change Management This phase establishes an Architecture Change Management process for the new Enterprise Architecture baseline. Objectives:  Ensures that changes to the architecture are managed in a cohesive and architected way Establishes and supports the Enterprise Architecture to provide flexibility to evolve rapidly in response to changes in the technology or business environment Steps: • Monitor Technology Changes • Monitor Business Changes • Assess Changes and Development of Position to Act • Arrange Meeting of Architecture Board (or other governing council) Outputs: • Architecture updates • Changes to architecture framework and principles • New Request for Architecture Work  .

Agenda Overview of EA Overview of TOGAF TOGAF v8 Value of TOGAF Comparison with ADM TOGAF v9 Copyright © 2008 Accenture All Rights Reserved. .

The Value of a Framework  Provides a practical starting point for an Architecture Project • • • • • • Avoids the initial panic when the scale of the task becomes apparent Systematic – ―Codified common sense‖ Captures what others have found to work in real life Baseline set of resources Foundation architecture in the Enterprise Continuum .

.Agenda Overview of EA Overview of TOGAF TOGAF v8 Value of TOGAF Comparison with ADM TOGAF v9 Copyright © 2008 Accenture All Rights Reserved.

Accenture Platform Accelerator etc. Organisation/Change management. Process architecture and IT Architectures. Accenture frameworks address non-IT architectures for Strategy.  Examples from the Accenture Delivery Suite (ADS)  Numerous sample deliverables and assets in the Knowledge Exchange • • Architecture Continuum Solutions Continuum III. Navitaire.Accenture has a number of frameworks for architecture and methods that relate to the TOGAF While TOGAF is restricted to IT architecture. II. Architecture development method Enterprise Continuum Accenture equivalent  Application architecture & technical architecture workstreams in Accenture Delivery Methods (ADM)  Business Integration Blueprint  Standard Architecture Frameworks  Industry specific assets like Architecture Reference model. Resources Notes: This comparison is deliberately incomplete and is only meant to aid in understanding the TOGAF *Accenture Communication Solutions . TOGAF I. ACS*.

Enterprise Architecture Framework: Methodology for EA Planning: 5 Deliver and Govern Iterate? Create Roadmap Refresh 3 Create Vision and Confirm Opportunities Diagnose Current Capabilities 4 Blueprint Future State 1 Launch Enterprise Architecture Initiative Copyright © 2008 Accenture All Rights Reserved.Enterprise Architecture Framework and EA Planning Methodology Accenture believes effective Enterprise Architecture is driven by Business and IT strategy. It links long-range strategy to day-to-day execution. 2 30 .

31 . Expectations and Concerns • Enterprise Architecture Project Approach • Project Plan • Prioritized Business Imperatives • Technology Imperatives • Technology Guiding Principles • Value & Issue Hypotheses Responsible: • Enterprise Architect Participating: • • • • • Business Architect Application Architect Information Architect Technical Architect Project Manager Copyright © 2008 Accenture All Rights Reserved. • Define technology imperatives. Inputs: • Statement of Work / Contract • Corporate/Business Mission Statement • Corporate/Business Vision Statement • Corporate/Business Values • Corporate/Business Strategy • Business Imperatives • IT Mission Statement • IT Vision Statement • IT Strategy • Inventory of ongoing and planned IT initiatives • Company Information – High level facts • Guiding Principles • Known Issues Deliverables: • Risk Mitigation Plan • Stakeholder Goals. Launch Enterprise Architecture Initiative Activity Confirm Scope. • Derive initial hypotheses on areas of pain and opportunities based on the technology imperatives.1. • Identify key business opportunities and capability challenges. Strategies and Imperatives Develop/Confirm Technology Imperatives and Guiding Principles Objectives: • Capture the project scope. Approach and Objectives Understand Business Context. approach and objectives with project sponsor to develop the project approach. • Define and prioritise key business imperatives.

technology. financials and processes • Gain consensus on assessment findings with project sponsors and stakeholders resolving all points of contention Inputs: • Ongoing IT initiatives • Stakeholder Goals.g. surveys will be used to analyse application health. • Agree upon data collection techniques. Process and Information) Copyright © 2008 Accenture All Rights Reserved. etc. tools. organization. Expectations and Concerns • Enterprise Architecture Project Approach • Application Inventory • Existing Architecture documentation • IT Organization Chart • Existing Architecture documentation (Technology.2. * If available for given industry Deliverables: • Enterprise Architecture Assessment Pack • EA Project Approach • Current Capability Assessment Job Aids: • Technical Quality and Functional Quality Surveys • Data Collection Templates • Diagnostic Tools • Data Collection Checklist Responsible: • Enterprise Architect Participating: • Business Architect • Application Architect • Information Architect • Technical Architect • Project Manager 32 .) • Develop a point of view on the existing applications.. templates and surveys with project sponsor (e. Diagnose Current Capabilities Activity Prepare For Assessment Assess Current Capabilities Validate Capability and Environment Discovery Objectives: • Understand the assessment boundaries and availability of information. Application. information.

Create Vision and Confirm Opportunities Activity Create Vision Create Business Capability Blueprints Identify and Prioritize Opportunities Validate Opportunity Discovery Objectives: • Create a business capability blueprint that is a pictorial representation of the major future capabilities of the enterprise. It will be a key to identify and prioritize opportunities for change. • Identify high-level opportunities for change that directs the enterprise towards its business goals. It‘s design and organisation should be driven by an operating vision and the business and technology imperatives.3. Deliverables: • Operating Vision • Business Capability Blueprint • Opportunity Summary • Opportunity Definition • Opportunity Prioritization Matrix • Quick Win Opportunities Responsible: • Enterprise Architect Participating: • • • • • • Business Analyst Application Architect Technical Architect Capability Lead/SME Industry Lead/SME Project Manager 33 . It should be based on industry best practice and Accenture thought leadership. • Validate the opportunities with the client sponsor and stakeholders. and that is aligned with the business capability blueprint. The prioritisation of opportunities will be the basis for creating the future roadmap and plan for value realization at a later stage. Inputs: • Industry Best Practices • Accenture Thought Leadership • Business Imperatives • Technology Imperatives • Technology Guiding Principles • Current Capability Assessment Copyright © 2008 Accenture All Rights Reserved. and identify quick-wins. It will form the basis for the application and technology blueprints to be created at a later stage. Prioritise the list of opportunities.

Blueprint Future State Activity Summarize Blueprint Requirements Develop Blueprints Process Information Application Technology Validate Enterprise Architecture Objectives: • • • • • Comprehensively describe the EA model from multiple dimensions. Deliverables: • • • • • • Business Capability Blueprint Key Architecture Requirements Process Blueprint Information Blueprint Application Blueprint Technology Blueprints Inputs: • • • • • • Business Imperatives Technology Imperatives Technology Guiding Principles Opportunity Summary Current Capability Assessment Business Capability Blueprint Responsible: • Enterprise Architect Participating: • • • • • Business Architect Information Architect Application Architect Process Architect Technical Architect Copyright © 2008 Accenture All Rights Reserved.4. Describe the key characteristics of each of those dimensions Understand the linkages between all the model elements Enable consistent development of systems and solution in line with business imperatives Validate and gain consensus on all blueprints with sponsors and stakeholders. 34 .

Detailed Tasks Example Activity Develop Blueprints Process Information Application Technology Validate Enterprise Architecture Blueprint Future State Summarize Blueprint Requirements Develop Application Blueprints Task Identify and define applications Identify application building blocks Define application interactions & association Determine Application characteristics and styles Create application blueprint Objectives: • Describe the business application assets needed by the enterprise in support of its business imperatives and business capabilities • Provide a structure and form to organise and integrate the application assets to deliver specific service • Enable automation of business processes and organisational interactions with internal and external stakeholders • Enable the organisation to review its portfolio of business application investments and identify new investment areas that would enable the attainment of its business objectives. Copyright © 2008 Accenture All Rights Reserved. 35 .

What are the key technologies required to support the application? b. portal. etc) i. Is the user base of the application global or local? If it is global. Is it necessary for the application to be available 24 X 7 to its users? What are the operational hours for the application? g. Based on the functional characteristics. How often is the data refreshed for the application? Is it batch processes or is it real-time OLTP? h. and style (e.g. What are the key impact to the current architect as a result of introducing the new technology / application? c.g. Things to consider while going through this step are: a. 36 . should it have a thin client or a fat client? Or should the application be available from the internet to internal and external users? e.Task Detail – Develop Application Blueprints Develop Application Blueprints Task Identify and define applications Identify application building blocks Define application interactions & association Determine Application characteristics and styles Create application blueprint Detailed Task Steps: ►Determine Application characteristics and styles The purpose of this step to determine the characteristic. think about how it can meet the functional requirements of the business capability. both functional and technical. web services. Depending upon the user base of the application. batch. OLTP. determine the technical characteristics of the application. flat file. building blocks and application interaction information that was identified in the previous steps. XML. Are Service Level Agreements required for the application? Copyright © 2008 Accenture All Rights Reserved. What is the anticipated life span of the application? f. should application support multiple languages? d. How does the application tie up to the databases and other data sources identified in the information blueprint? What is the information exchange format (e. HTML. When determining the characteristic and style of an application. etc) of the application based on the capability requirements.

. Create Roadmap Activity Define and Integrate Opportunities into Initial Plan Develop Implementation Plans Validate Plans Finalize Business Case Objectives: • • • • • Develop roadmap or transition plan that defines the program necessary to implement the future state blueprints Derive a business case for the program and initiative to provide economic justification for all planned activities Create change management plans that will be required to startup.5. and navigate the roadmap Validate and gain consensus on Roadmap Deliverables with sponsors and stakeholders Transfer ownership of blueprints and roadmap to program managers that will drive the ensuing implementation Inputs: • • • • • • Business Capability Blueprint Process Blueprint Information Blueprint Technology Blueprints Application Blueprints Opportunity Summary Deliverables: • • • • • Program Roadmap Project List Project Plan Business Case Communication Plan Responsible: • Project Manager Participating: • • • • • • Enterprise Architect Business Architect Process Architect Information Architect Application Architect Technical Architect 37 Copyright © 2008 Accenture All Rights Reserved. govern.

.Agenda Overview of EA Overview of TOGAF TOGAF v8 Value of TOGAF Comparison with ADM TOGAF v9 Copyright © 2008 Accenture All Rights Reserved.

. • Architecture Value Realisation – use of enterprise architecture during normal operational services to realise the business benefits that were envisioned when the architecture was developed. • Architecture Management – management and governance of the enterprise architecture.Plans for TOGAF Version 9  Six domains: • Business Context – the enterprise context for EA work • Architecture Development – development of an enterprise architecture. • Business Transformation Planning – use of enterprise architecture to drive a program of change throughout the enterprise • Architecture Deployment – implementation of the enterprise architecture and the Transformation Plan. via the various projects in the Transformation Program. and the change in scope of the overall enterprise as it evolves over time.

ADM Mapping to TOGAF 9 .

:08 W 47547.90.:83088 '.

90.90 W :830882507.90.93 W W W W W :830887.79.:83088 $97..08 W %8843$9.9 %0.0/  .9437.3..7.5.9 !740.90.9.902039 !.9437.9 55.07 4579 ..9.3.039:70#98#0807.9 31472.90.

90.-908 '.9438.8.3/89.95574.943 !74.9.943.40.93 W :830887.94390.9430.43903943 35:98 W 343%39.%448 W .3.08 W $9.9 W 31472.79 W 8937.55.90.033/:897 0.9 !705. W !740.9:70880882039 !..36:08 9448 9025.3.08 -0:80/94.7432039 8.90.:2039. W 0.3.8 50.3.5.:2039..-0147..90.3.9.40.438038:843...3.943..08808 W .08 W &3/0789.90.7.3.9.07 -0.-908 .. W 55.90 .9:70/4.9 !.9..088.88088203913/3895740.9.95574.9433.943 W 700:543/.9 09.9..79..043900893.908.90.3/ 574.9 W !740..9 W %0.90.5.03947 W 8937.9$:7.5..89 #085438-0 W 390757807.3/90.3.344 55.40.90.04/074. .9 W 55.55.985438478..9438 31472.5.039:70#98#0807.9437.344 47.3/ 3.5.-9880882039 4-/8 W %0.3..90.880882039-4:3/. ":.9.3489..943 %0.543941.07  .-9.045.3/.9437.3/ 43.9:70/4.3480:77039.0738 W 390757807.943 W % 7.08 W .3/ 31472.0/ 1./.9.9.708.943 13.-94131472.80.3/8:7.-08 W 390757807.943%025.943 90.9:70!740..":...04/0787084.943 4579 .908 W .98543847 0  8:7.0895740.07.3/:3.4.70 47 880882039 88088 :77039 .. W :77039.5439841 .9430.

943.989003907578094.3/574790 455479:3908147.9090455479:3908990.-:83088.5.-9 880882039 4579 .90 '843 70...3442507.0398543847.3/.93901:9:7074.3.471:9:70.03-..039:7094:90..508 W :77039.94384:/-0/7.5.4.3//03916:.9 70.9./.07 -0./.38.34507.90.5.7.9.3442507.3/90-:83088.-9-:057399.04/078  35:98 W 3/:897089!7.08 W 70.:070.08 W %0..9 %0. 70.9. 38 %0574798.9..94341 455479:3908-090-.9.55..98.08 9 84:/-0-..039:70%4:9 0.943..5.943..843.70.93.30 9147290-..93 W W W W W W :830883./.94341902.039:70#98#0807.5.89 55.3/90.705708039.8814790.9.88147.90 55479:39 8.90.90789.0  W /0391 0./0785 W :830882507.8 .9/70.3/47.7/898-:830884.70.-9:05739 W 55479:39$:22./2.3/89.3147.90/.98.0.9 !.30/9 90-:83088..-08 W 507.344-:05739894-0.90.3 55479:3908 #085438-0 W 390757807.7 W 55479:39013943 W 55479:39!7479.3/43172 55479:3908 .5.90.0 W '.0455479:3908147.0/ 0.9.-9 :057398 /0391.97 W ":.79.80/433/:897-08957.5.9.08 W .3/9.309.3/5.5.90789.07.08 W %0..9 .90'843.-9-:05739 !747980908941455479:3908 ./0785 9-0.-90.3/ !74790 55479:3908 '.9437.-9084190039075780 9 8/083.5.5.947..93'843 W :83088.094/0391..3/90..9..344:/3 !73.90 :83088 .

$ 3/:8970./.

3.07  .$ !740.9.

943 %0.-08 W W W W W W :83088.7.0/08.9.90.9437.90 39075780 7.088:05739 31472.9024/00020398 3. :05739:9:70$9.-9:05739 #085438-0 W 390757807.43889039/0.3.9 !74.93 W W W W W :830887.90 0.08 %0.9.04/078 0.7 :77039..90.0/  .08 W W W W W 42570038.08-09003.90.088 $:22.79.7.419480/2038438 &3/0789.943:05739 55.344:057398 35:98 W W W W W W :830882507.5.90.3442507..9 31472.943:05739 %0...90.039:70#98#0807.9:70 .08 '.943 55..9.90.9:70#06:7020398 !74.90.-9880882039 :83088.9.-0.3/89.-9:05739 07.5.045203941889028.9 -0.90.9.7-09024/017422:950/2038438 08.0887.5.438038:843./.90789.9 4579 .90.70 :05739 #06:7020398 31472./.9 55.-:057398985438478..3.08 %0.9437.9 !.8410.7-0900.5..045:057398 !74.3/84:9433309-:830882507.07.3/.3/903.344 '.344:/3!73..508 55479:39$:22.9 %0.

943 %0.3/3907.0 W 3....88098300/0/-9003907578038:554794198-:83088 2507...90 39075780 7..08.9.943.884./.1.:942..09.943 -:05739 -0.55.9090.90.9439470.94:/03.320394198-:830884-0.3/09073.04/078 W 3.0/%.90 $:22.89.55. 807.8 /0391 ..943./0.9.3907.3/8908 70.943 -:/3 -4.5..3/14729447.9433.9438939073.943 55..38.-09047.8 .3//0130 . 89...9:70 :05739 :9:70 $9.943.08 4579 .098547914441-:83088.943:057398 %.04555.943 3907.70 :05739 #06:7020398 0.7.250 .8809894/0.-090.55.55.-0.08808...-908 W !74.94341-:83088574.0892039.8 0130 ..943 .9:70.55.943 0907230 55.9.088 31472...9438 /0391 .55.897:.9.3/-:83088.90 .07850.3/47.3//039130 3.344 '..380.7-090-:83088.38.9438 .039:70#98#0807.08920398.55.9 0.88.90789.99.0/  .045:057398 !74..70.08 W 08.

.3//0130 .04555.9433907..8 /0907230 9090.8 /0391 .. 09..9.55.9.9..-9706:7020398 -:/3-4.943:057398 0.943 -:/3 -4..34408706:70/948:5547990.3/90.08  %! -.7.438/07043974:988905.809..7.5.3.99490.90789.55.8$9058 ³090723055..55.943.:77039.3/890 0  5479.55..9438 /0391 .4:889058 03/090723390. 0.80/4390.7..884.9438 .3/8908 70.90 .7.90789.55..7.943...0/%.8/03910/390570...90789.706:70203984190-:83088. -491:3.....90..943 ..-4:949.7.04555.90789.3903090.7090025.943 -:05739 09.%..55.708:9413974/:.90789.344.90789. 0-807...55.943:057398 %..8 .3..943  %3894.943 93 .943-.9. ..9439. 4190.8 0130 .32009901:3...943 31472.943..7090090.8.80/43901:3.3....3/89041. .-9 ..9..3/.84190.943.943 - ..943 0907230 55.8.3/8908 %05:754804198890594/090723090.943 3907...70 .55.5.8..55.7.

943 1 8930.9434-..474.910  % 09.808..943  441903890/.94394-0.9438:554792:950.34190.00.9430.804190.  70$07.088.55.943 84:/9..943-:05739.55..55.943 .-.070020398706:70/14790.55.804190.9 0  1.08808478970.714790.0/  .0...9.3/4907/..574. 920 %!  4/40890.943..55.7017080/14790.9.039 784:/90.55...70904507.55.03947..55.-09498:8078.55.94390:59490/.3/09073..9.55.943 4579 .08/03910/39031472....94389-.90/1085.9..943-0 .301472.84:7. 890:807-.:8078 0 . 84:/.5..1.39.9890 31472.3:.9.93.9890..4:7814790.55...-017429039073099439073.1984-..08 / 0503/3:54390:807-..9.039:70#98#0807...

0887.0.9  4579 ./2.9.90./.90 55479:3908 39439.5 .9 31472.3.50./2.943:05739 %0.80147905747.5 '.0452502039..!.93 W W W W W W 390757807.54797.090038:32502039.909074.943!.9437.7 0.943147.90./.9437.943:057398 55479:39$:22.90.90.3 :83088.5.9 55.07..79.:891.0:83088.3 #085438-0 W !740..9!.3.3/3./2.9-0706:70/9489.90#4.230.5.-:83088.39.3 0.3810743078541-:057398.9 :830887.3/74.389435.9 %0.3..3/89.088..07.22.073 .9..90./2.438038:843#4.330/..38 3.3.094574.039:70#98#0807.943 35:98 W W W W W W :83088.9.-08 W W W W W !747.9.7.90.04/078 %7.088:05739 31472.020395.-9:05739 !74../2.-08985438478./2.344:057398 55.943!.04574.0789.9/01308905747.4342.9 !74.08 W W W W W 0.989 !740.3..79:5 4.90-:057398 07.2#4.302.9.5.38 './00.90. 70..9 0130.2.80 422:3.3/ 3907.90.3/.3/39.5 !740.9/7.0/ .90 !.908 70.7942502039901:9:7089.80 -0..389.07 !.5945747.

041 .039:70#98#0807.0/ . . 4579 .07.. '.78439 % .03/.:041%  425.041%  % .07.

4507..943 !747.807.0452039 /0.90.:0#0.9:700542039 2502039.089470.08 4.7.9070 03.!.381472.45041904.8430/0390..74:85740.9:70.04190039075780 .3038.98390%7.38147% '07843 $/42.90.90.9:70.3/90.90.38 W W W W W W :8308843909 90039075780.890.381472..9:7094/7.3/4.90.8.9:70.3.039075780.9:70'.3.381472.02039 2.7.3/ 90%7.3039075780.07920 .02039.8/0.045203941..943!.90.7.90.943 :8041039075780.4.333 :8041039075780.9:700.30974:4:990039075780 7.0450/ 7.07.0.943.9434190039075780.90.9:70 :83088%7.3 .90.7. 5747..7.4390914747 7.9:70/:73 3472.8090-:83088-0301989.2 7.943!.3.7.90.241.073.90.9:70 .

55394%  ..

Sign up to vote on this title
UsefulNot useful