ASMG-OMG Day 11-02-04 (OntGov).ppt


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

ASMG-OMG Day 11-02-04 (OntGov).ppt

  1. 1. Ontario: MDA in Provincial Government David Wallace Corporate Chief Technology Officer Management Board Secretariat Office of the Corporate Chief Information Officer February 2004
  2. 2. Agenda <ul><li>Background </li></ul><ul><li>Challenges </li></ul><ul><li>Current position on MDA </li></ul><ul><li>Next steps </li></ul>
  3. 3. Elements of Architecture <ul><li>Models, diagrams, charts, narratives, cross references, blueprints,… </li></ul><ul><li>Of: </li></ul><ul><ul><li>- A “Business” (an enterprise) </li></ul></ul><ul><ul><li>- along with </li></ul></ul><ul><ul><ul><li>the data and information the “business” needs </li></ul></ul></ul><ul><ul><li>- along with </li></ul></ul><ul><ul><ul><li>the manual processes and automated applications, to support the “business” and manage its data </li></ul></ul></ul><ul><ul><li>- along with </li></ul></ul><ul><ul><ul><li>deployment in a “technology” platform </li></ul></ul></ul><ul><ul><li>- taken into consideration </li></ul></ul><ul><ul><ul><li>security, access protections & privacy </li></ul></ul></ul>
  4. 4. A need to classify the elements <ul><li>A number of ways to do it... </li></ul>
  5. 5. A useful simple classification would be... <ul><li>What How Where Who When Why </li></ul><ul><li>From six different perspectives: </li></ul><ul><li>Planner (Contextual) </li></ul><ul><li>Owner (Owner) </li></ul><ul><li>Designer (Logical) </li></ul><ul><li>Builder (Physical) </li></ul><ul><li>Sub-Contractor (Out-of-Context) </li></ul><ul><li>The functioning Enterprise itself </li></ul>
  6. 6. And is... <ul><li>The Zachman Framework </li></ul>Copyright - John A. Zachman, Zachman International
  7. 7. Background I&IT Strategy EIA Project Phase 2 Centre of Excellence Project 1998 1998-1999 1999-2000 2000-2001 2001-2002 Architecture Assessment 2002-2003 2003-2004 Enterprise I&IT Architecture (EIA) Project Phase 1 Programs & Services, Information Modeling Handbook, Adaptive Infrastructure Checklist & Guidebook
  8. 8. Background <ul><li>Foundation Documents </li></ul><ul><ul><li>Enterprise Architecture Processes & Methods Handbook </li></ul></ul><ul><ul><li>Information Modeling Handbook </li></ul></ul><ul><ul><li>Defining Programs & Services in the OPS </li></ul></ul><ul><ul><li>Checklist & Checklist Guidebook </li></ul></ul>
  9. 9. Architecture Governance Deputy Ministers’ Committee on Transformation of the OPS I & IT Executive Leadership Council Proposed E-Government Council (ESD Planning) Architecture Review Board Architecture Core Team Cluster Architecture Review Board Cluster Architecture Core Team Cluster Domain Architecture Teams IT Standards Council Cluster CIO Cluster Projects (Change Initiatives) Information Technology Application Security Business Domain Architecture Team Leads Corporate Architecture & Infrastructure Projects
  10. 10. Challenges <ul><li>Involve the right parties </li></ul><ul><li>Consistency of usage (what level to target) </li></ul><ul><li>Ongoing need to demonstrate value </li></ul><ul><li>Life inside the Tower of Babel without a repository </li></ul><ul><li>When you can not mandate a single customization of one systems development methodology, how do you ensure that you get what you need? </li></ul><ul><li>How do we pull together an effective architecture review? </li></ul><ul><li>How do we establish enterprise architecture methodologies that apply well across jurisdictions and/or different companies? </li></ul><ul><li>How do we get both business line owners and systems developers to understand and be involved in architecture? </li></ul>
  11. 11. There are many challenges... <ul><li>The balance between defining the practice of architecture in our organizations and supporting/QA-ing projects. </li></ul><ul><li>Representing the business in their own terms </li></ul><ul><li>Providing views appropriate for Application/Project focus and views appropriate for an Integrated/Federated focus </li></ul><ul><li>Leveraging cross-enterprise opportunities </li></ul>
  12. 12. Direction <ul><li>Growing maturity with iterative development </li></ul><ul><li>Many variations of development methodologies </li></ul><ul><li>The common thread: UML </li></ul><ul><li>Repository </li></ul><ul><li>Our goal is to define enterprise architecture using UML to meet the challenge of... </li></ul>
  13. 13. Ontario’s Transformation Agenda Service Delivery Connecting Government & Citizens Building Internal Capacity Partnerships Privacy & Access Security Information Management Infrastructure Government and cross-jurisdictional collaboration to drive social development, economic competitiveness and regulatory harmonization Develop enterprise management systems and approaches that drive more value from investments, e.g., legacy renewal, back office reengineering, horizontal funding, project management and internal capacity building Integrated, cross-jurisdictional service delivery through multiple channels that is customer-focused, seamless and convenient Connecting government and citizens through increased transparency and citizen engagement opportunities Applying IM & IT in a comprehensive way to all functions of government
  14. 14. Implications Of Seamless e-Government <ul><li>A Transformation Of Service Delivery </li></ul><ul><ul><li>Transforming from “stove-piped” service to a horizontal, integrated service delivery supply chain (included within the ISD mandate). </li></ul></ul><ul><ul><li>Adaptation of customer care model to enable baseline of seamless, 24 x 7 customer care </li></ul></ul><ul><ul><li>Adaptation of change management models to accommodate 24 x 7 and the complexity implicit in integrated services. </li></ul></ul><ul><li>A Transformation Of The “Infrastructure” </li></ul><ul><ul><li>The OPS I&IT Strategy envisages enterprise-wide common services and the reuse enterprise-wide common components. </li></ul></ul><ul><ul><li>Need to adapt I&IT workflow to accommodate corporate and cluster roles and new relationships with service providers and program areas. </li></ul></ul>
  15. 15. Model Driven Architecture <ul><li>These transformations are taking place in an </li></ul><ul><li>environment that demands an MDA approach: </li></ul><ul><ul><li>E-Business and E-Government </li></ul></ul><ul><ul><li>Distributed systems </li></ul></ul><ul><ul><li>Heterogeneous platforms and languages </li></ul></ul><ul><ul><li>Legacy and open source and new code and off-the-shelf </li></ul></ul><ul><ul><li>A need for inter-jurisdictional connectivity </li></ul></ul><ul><ul><li>Wireless devices </li></ul></ul><ul><ul><li>Privacy and security </li></ul></ul><ul><ul><li>XML, Web Services </li></ul></ul><ul><ul><li>Financial constraints </li></ul></ul>
  16. 16. Unified Modeling Language <ul><li>UML enabled by XMI provides a common language for business and systems specification </li></ul><ul><li>A Government of Ontario Standard </li></ul><ul><li>We will much more fully exploit its use for specifying of the business of government: </li></ul><ul><ul><li>A well-defined business architecture at the government program level to inform and guide automation design (Platform-Independent Model) </li></ul></ul><ul><ul><li>A well-defined business architecture at the enterprise level to inform and guide planning, program design and assessment (Computation-Independent Model) </li></ul></ul>
  17. 17. The MOF <ul><li>The OMG architecture for metadata in the Model Object Facility (MOF) Specification informed and guided the creation of The Ontario Public Service Conceptual Data Model. </li></ul><ul><li>The Conceptual Data Model is a high-level view of the information requirements of the Government of Ontario. </li></ul><ul><li>Provides uniform definitions of important entities and rules </li></ul><ul><li>Intended for OPS business staff </li></ul><ul><li>Enhances communication with I&IT staff </li></ul>
  18. 18. MDA Tool support <ul><li>Currently the transformation from business architecture to system design is manual </li></ul><ul><li>The promise of maturing software tools in support of MDA: </li></ul><ul><ul><li>Business and business requirement specification is truly isolated from technology </li></ul></ul><ul><ul><li>Mapping of a platform independent model to a specific middleware technology using OMG mappings </li></ul></ul><ul><ul><li>Partial generation of code - raising the level of abstraction </li></ul></ul><ul><ul><li>Facilitates redeployment on new technology </li></ul></ul><ul><ul><li>Business requirements and technology evolve separately, a viewpoint encouraged by Zachman Framework </li></ul></ul>
  19. 19. Zachman Framework <ul><li>Model Driven Architecture and the Zachman Framework are compatible </li></ul><ul><ul><li>Computation-Independent Model Row 2 Model </li></ul></ul><ul><ul><li>Platform-Independent Model Row 3 Model </li></ul></ul><ul><ul><li>Platform-Specific Model Row 4 Model </li></ul></ul>The Ontario Government classifies its business and system specifications (artifacts) using the Zachman Framework.
  20. 20. Technical Standards Strategy <ul><li>Focus: The adoption of open industry standards </li></ul><ul><li>To facilitate : </li></ul><ul><ul><li>government services across jurisdictions </li></ul></ul><ul><ul><li>alternative delivery channels </li></ul></ul><ul><ul><li>utilizing a broad range of technologies </li></ul></ul><ul><ul><li>providing better access to government services </li></ul></ul><ul><ul><li>the interoperability necessary for e-government services (interconnected, web-enabled and mobile) </li></ul></ul>
  21. 21. Summary <ul><li>Ontario’s transformation agenda is ambitious </li></ul><ul><li>Open standards are key to this agenda </li></ul><ul><li>Collaboration with the federal and municipal governments is crucial for e-Government </li></ul><ul><li>Effective collaboration will require the degree of flexibility with technology that an MDA-approach can provide </li></ul>