1 / 18

Enterprise Architecture Methodology at KPMG

Enterprise Architecture Methodology at KPMG. David vun Kannon Manager, Financial Services Consulting KPMG LLP. Introduction. The Problem: “I spent $500 million on IT, and all I got was this lousy source code (ERP system, etc.)!”. Topics of Discussion. Overview of enterprise architecture

hue
Download Presentation

Enterprise Architecture Methodology at KPMG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Architecture Methodology at KPMG David vun Kannon Manager, Financial Services Consulting KPMG LLP

  2. Introduction • The Problem: “I spent $500 million on IT, and all I got was this lousy source code (ERP system, etc.)!”

  3. Topics of Discussion • Overview of enterprise architecture • Our model-driven approach • The relevance of XML

  4. Overview of Enterprise Architecture • Skyscrapers are not 10,000 doghouses stacked on top of each other. • 10K doghouses=10K siloed apps • No global planning or direction a function of the disconnect between IT and the business it supports.

  5. Enterprise Requirements • “You start coding, I’ll get the requirements.” NOT! • Cannot overemphasize the importance of design and requirements gathering • Exponentially less costly to fix mistakes at this stage.

  6. KPMG’s Model-Driven Approach • Capture requirements • Organise requirements • Operationalise requirements • Shadow Implementation to maintain relevance

  7. Leveraging the Requirements • Documentation • Code generation • Administrivia

  8. The Relevance of XML • UML is a visual language • No consistent API • Models are documents, not programs

  9. XMI – UML in XML • Part of OMG MOF initiative • A mechanically derived DTD • Goal is supporting interchange

  10. SimpleBank • A trivial model • A non-trivial script • Legacy up-translation

  11. What This Means • Separation of modeling and code generation • Choose the right tool for the job • Legacy support via up-translation to XMI

  12. XMI – Not Just For Interchange • Code Generation • Separating Modeling and CG • The relevance of XSL

  13. Code Generation • Traditional target of the object model’s class diagram • UI - HTML • Business Logic - Data structures, function stubs, directory and file structure in C++, Java, VB, etc. • Persistent Storage – SQL DDL • Targeted in isolation

  14. Separating Modeling from CG • Tools do one thing well • Don’t expect good code generation from a great modeler • More choices from unbundled tools

  15. The Relevance of XSLT • Tool appropriate to the task • Can quickly add new targets • Can tune the O-R mapping

  16. UML2SQL.XSL • Generates DDL for MS SQL Server • March draft XSLT and XT

  17. Next Steps • Tremendous opportunities in code generation • New targets – LDAP, DSML, UIML • New Sources – sequence diagrams, statecharts, • Cross tier coordination • The XML messaging vocabulary • Round trip engineering

  18. Next Steps • From static to dynamic system descriptions • Decorating the model with active metadata • Application instrumentation • Design For Change and the invalidated assumption

More Related