asmg-omg day 11-02-04 (ontgov).ppt

www.cio.gov.on.ca

Ontario:Ontario: MDA in Provincial GovernmentMDA in Provincial Government

David WallaceCorporate Chief Technology Officer

Management Board SecretariatOffice of the Corporate Chief Information Officer

February 2004

Queen’s Printer for Ontario

2Agenda

• Background• Challenges• Current position on MDA• Next steps


3Elements of Architecture

Models, diagrams, charts, narratives, cross references, blueprints,…

Of:

- A “Business” (an enterprise)

- along with

• the data and information the “business” needs

- along with

• the manual processes and automated applications, to support the “business” and manage its data

- along with

• deployment in a “technology” platform

- taken into consideration

• security, access protections & privacy


4A need to classify the elements

• A number of ways to do it...


5A useful simple classification would be...

What How Where Who When Why

From six different perspectives:Planner (Contextual)Owner (Owner)Designer (Logical)Builder (Physical)Sub-Contractor (Out-of-Context)The functioning Enterprise itself


6And is...

The Zachman Framework

Copyright - John A. Zachman, Zachman International


7Background

I&ITStrategy

EIA ProjectPhase 2

Centre of ExcellenceProject

1998

1998-1999

1999-2000

2000-2001

2001-2002

ArchitectureAssessment

2002-2003

2003-2004

Enterprise I&IT Architecture (EIA)

Project Phase 1

Programs & Services, InformationModeling Handbook,Adaptive Infrastructure

Checklist &Guidebook


8Background

Foundation Documents

– Enterprise Architecture Processes & Methods Handbook

– Information Modeling Handbook– Defining Programs & Services in the OPS– Checklist & Checklist Guidebook


9Architecture 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)

Info

rmati

on

Tech

nolo

gy

Applic

ati

on

Secu

rity

Busi

ness

Domain Architecture Team Leads

Corporate Architecture & Infrastructure

Projects


10Challenges

• Involve the right parties• Consistency of usage (what level to target)• Ongoing need to demonstrate value• Life inside the Tower of Babel without a repository• When you can not mandate a single customization of one

systems development methodology, how do you ensure that you get what you need?

• How do we pull together an effective architecture review?• How do we establish enterprise architecture methodologies

that apply well across jurisdictions and/or different companies?

• How do we get both business line owners and systems developers to understand and be involved in architecture?


11There are many challenges...

• The balance between defining the practice of architecture in our organizations and supporting/QA-ing projects.

• Representing the business in their own terms• Providing views appropriate for Application/Project focus and views

appropriate for an Integrated/Federated focus• Leveraging cross-enterprise opportunities

•

•

•


12Direction

• Growing maturity with iterative development

• Many variations of development methodologies

• The common thread: UML

• Repository

• Our goal is to define enterprise architecture using UML to meet the challenge of...


13Ontario’s Transformation Agenda

Service Delivery

Connecting Government &

Citizens

Building Internal Capacity

Partnerships

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

Applying IM & IT in a comprehensive way to all functions of government


14Implications Of Seamless e-Government

• A Transformation Of Service Delivery– Transforming from “stove-piped” service to a horizontal,

integrated service delivery supply chain (included within the ISD mandate).

– Adaptation of customer care model to enable baseline of seamless, 24 x 7 customer care

– Adaptation of change management models to accommodate 24 x 7 and the complexity implicit in integrated services.

• A Transformation Of The “Infrastructure”– The OPS I&IT Strategy envisages enterprise-wide common

services and the reuse enterprise-wide common components.– Need to adapt I&IT workflow to accommodate corporate and

cluster roles and new relationships with service providers and program areas.


15Model Driven Architecture

These transformations are taking place in anenvironment that demands an MDA approach:

– E-Business and E-Government– Distributed systems– Heterogeneous platforms and languages– Legacy and open source and new code and off-the-shelf– A need for inter-jurisdictional connectivity– Wireless devices– Privacy and security– XML, Web Services– Financial constraints


16Unified Modeling Language

• UML enabled by XMI provides a common language for business and systems specification

• A Government of Ontario Standard• We will much more fully exploit its use for specifying

of the business of government:– A well-defined business architecture at the government

program level to inform and guide automation design (Platform-Independent Model)

– A well-defined business architecture at the enterprise level to inform and guide planning, program design and assessment(Computation-Independent Model)


17The MOF

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.

The Conceptual Data Model is a high-level view of the information requirements of the Government of Ontario.

• Provides uniform definitions of important entities and rules

• Intended for OPS business staff

• Enhances communication with I&IT staff


18MDA Tool support

• Currently the transformation from business architecture to system design is manual

• The promise of maturing software tools in support of MDA:– Business and business requirement specification is truly

isolated from technology– Mapping of a platform independent model to a specific

middleware technology using OMG mappings– Partial generation of code - raising the level of

abstraction– Facilitates redeployment on new technology– Business requirements and technology evolve

separately, a viewpoint encouraged by Zachman Framework


19Zachman Framework

• Model Driven Architecture and the Zachman Framework are compatible– Computation-Independent Model Row 2 Model– Platform-Independent Model Row 3 Model– Platform-Specific Model Row 4 Model

The Ontario Government classifies its business and system specifications (artifacts) using the Zachman Framework.


20Technical Standards Strategy

• Focus: The adoption of open industry standards

• To facilitate:– government services across jurisdictions– alternative delivery channels– utilizing a broad range of technologies– providing better access to government services– the interoperability necessary for e-government services

(interconnected, web-enabled and mobile)


21Summary

• Ontario’s transformation agenda is ambitious • Open standards are key to this agenda• Collaboration with the federal and municipal

governments is crucial for e-Government• Effective collaboration will require the degree of

flexibility with technology that an MDA-approach can provide