inter-operability in the education sector using a sector data model driven methodology

INTER-OPERABILITYIN THE EDUCATION SECTOR

USING ASECTOR DATA MODEL DRIVEN

METHODOLOGY

Introduction

Robyn Smits, Senior Manager, Sector Services, Ministry of Education

• During 2008 SSC, Standards NZ and a number of agencies worked together on developing 3 sets of guidelines for governing XML inter-operability.

• We recognised the need to share information on how different agencies are approaching the development and standardisation of XML messaging.

• We wanted to include vendors, technical/IT people and those in the business of data management/business intelligence.

XML Seminar Agenda

• Introduction

• Background

• Wider Context of XML Schema Design

• Developing the Education Sector Data Model (ESDM)

• From Data Model to XML Schemas

• Lessons Learnt

• Questions

Why go there?

A business perspective

Andreas Kubisch – Senior Business Systems Analyst

The journey so far

Hand coded Schemas:• Early notification• asTTle integration (EDUCTF)

No Schema:• E-Returns

ESDM derived Schemas:• ENROL Integration (3 message pairs)• SMS-LMS Integration (9 messages)• Student Record Transfer (6 messages)

more to come …

The challenges

• Code Value Lists

• Versioning

• Data quality

• Message Validation

• Connectivity

• Vendor capability

• Model flexibility

• What is an XML Schema?

Wider Context ofXML Schema Design

Juerg Tschumperlin, DMS Data Management Solutions

What is an XML Schema?

• A schema is a way to describe and validate data in an XML environment.

• A schema is a model for describing the structure of information.

• XML Schema (XSD) is a recommendation of the W3C.Source: EPA:

http://www.epa.gov/webservices/glossary.htm



Example of XML Schema Diagram: (Extract)



Example of XML Schema Code: (Extract)


What is an XML Instance Document?

Example of XML Instance: (Extract)


XML Instance: Validation against XML Schema

Validates?Y = Process Instance

Incoming Instance

N = Return to Sender


How are XML Schemas commonly developed?

• By standard-setting bodies: “off-the-shelf”

or

• Custom-build to meet requirements.


How are custom XML Schemas developed?Usually• Project-based, and

Hand-coded

OR• Project-based, and

Generated from- database structure, or

- application program code, or

- XML Schema model (1 stand-alone model per schema)


Conventional schema development creates serious issues:

- XML tag name variations, and

- data misinterpretation, and

- data quality issues, and

- schema look and feel variations, and

- schema versioning variations, and

- schema re-use variations

- schema maintenance nightmare


How are custom XML Schemas developed?Usually• Project-based, and

Hand-coded

OR• Project-based, and

Generated from- database structure, or

- application program code, or

- XML Schema model (1 stand-alone model per schema)

Fact:

Most organisations having developed custom XML Schemas came

to realise that;

• Neither interoperability nor data quality has improved,

• Master XML Schemas are scattered and hard to find,

• Schema maintenance is unsustainable,

• Unmanaged re-use / versioning is an operational risk.


Facts:

The XML Schema Language is not to blame.

The real culprit is how we develop schemas.


The challenge:

How can we develop XML Schemas that are;• semantically consistent,• syntactically standardised,• consistent across projects and organisations,

and hence improve;• semantic interoperability,• data quality,• operational robustness,• sustainable change management.

?


Today’s presentation will show:

Our early work in XML Schema development in the school sector:

• Using a data model-driven approach,

• Producing derived and generated XML Schemas,

• Which adhere to, + the single messaging data model, and

+ several global and NZ e-Gif standards

• With a centralised schema administration.


The presented solution is also:

A generic XML Schema development approach

for creating standardised custom schemas:

• Suitable for any industry,

• Suitable for messaging between organisations.

• Suitable for integrating in-house applications (EAI).


Today’s presentation will show:

MXV Transformation Methodology

XML Schemas

Custom Data Model

feeds into

derives


Model-driven XML Vocabulary Transformation Methodology

ESDMEducation Sector Data Model

22

ESDM Project

Education Sector Data Model:History and Outcomes

Alistair Betts, Summit Solutions Ltd

Purpose of ESDM

“To produce a sector data model that defines shared sector data so that sector participants can

provide, manage, access and understand the data.”

23

Scope

• Logical Model of Shared Sector Data

• Data Custodianship responsibilities

• Methodology for use

• Report of Findings

• Review of Data Modelling tools(Ministry of Education only)

24

The Model Subject Areas

25

Agencies Consulted

• Career Services

• Teachers Council

• ERO

• NZQA

• TEC

• MOE

26

Creating a message

How do we go about creating a message using this methodology?

1. Is it a sector message?

2. Map requirements to model & mock up messages

3. Approve changes to ESDM via data dictionary

4. Update ESDM model

5. Create new draft message schemas

6. Model & message approval

7. Final changes and release to specification status

27

From Data Model to XML Schema


Juerg Tschumperlin, D-M-S Data Management Solutions

Industry-independent overview:


XML Schemas

Custom Data Model

feeds into

derives


Education Sector overview:


XML Schemas

Custom Data Model

feeds into

derives


ESL XML SchemasEducation Sector Language



Tools

Administrator

Data Owners

XML Schemas

Custom Data Model



feeds into

derives

ESDMEducation Sector Data Model Schema

Consumers

End-to-end tool support

Main players

Shared data underst

anding

Documented in

a single m

odel

Project Team

Project Team

Messaging Requirements

Messaging Requirements




feeds into

derives

UTF-8 character encoding

ISO 11179-5 Data Naming

UN/CEFACT Unqualified Data Types Schema

OASIS Universal Business Language Naming and Design Rules (UBL NDR 2) [adapted]

W3C XML Schema W3C XML

URN Naming

high NZ e-G

if complia

nce

Standardise

d XML S

chema

- tag names a

nd definitio

ns

- versi

oning

- look a

nd feel

- acro

ss pro

jects and org

anisatio

ns




equivalent expressions

Derived X

ML Sch

emas:

- UML and X

ML in sy

nc

- Names m

atch

- Defin

itions c

ascade





equivalent expressions

XML Component Library

populates

is referenced by





is referenced by

populates

UML data model

Domain / Data Type

Attribute

ClassSpecialization

Association

XML Schema Component Library Modules:

- UDT UN/CEFACT Unqualified Data Types (read-only)

- QDT Qualified Data Types

- CBC Common Basic Components

- CAC Common Aggregate Components



OASIS UBL NDR-like component libraryRe-use of XML Schema componentsTool supported Impact Analysis




feeds into

derives


MXV Transformation MethodologyStandards

UML Modelling




Concepts Tools

W3C XML Schema W3C XMLModel-driven Architecture

Semantic Vocabulary(aka Ontology)

Sybase PowerDesigner

D-M-S MXV Productivity Tools (optional)

Change Management Process


Data Owners



feeds into

generates

Administrator

SchemaConsumers

XML Schemas


Data Owners

Custom Data Model SchemaConsumersMXV Transformation Methodology

Standards

UML Modelling




Concepts Tools

W3C XML Schema W3C XMLModel-driven Architecture

Semantic Vocabulary(aka Ontology)

Sybase PowerDesigner

D-M-S MXV Productivity Tools (optional)

Change Management ProcessPortable so

lution fo

r deve

loping custo

m semantic

XML standards

Suitable fo

r any i

ndustry

Suitable fo

r mess

aging between organisa

tions

Suitable fo

r mess

aging between in

-house applica

tions (

EAI)

MXV Tools:PD = Sybase PowerDesigner DMS = MXV Productivity Tools

Administrator

MXV Tool Support

XML Schemas

Custom Data Model


XML Schemas

feeds into

generates

Custom Data Model

Migrate to Specification (DMS)

XML Schema Modelling (PD)

Clone an XML View (DMS)

UML Modelling (PD)

Create New Model Version (DMS)

Check NDR Naming and Design Rules Compliance (DMS)

Automatically populate the XML Component Library (DMS)

Check completeness of XML Component Library (DMS)

UML to XML Schema Impact Analysis (PD)

Create Delivery Package (DMS)

XML Schema Generator (PD & DMS)

Reliable schema quality

Fast turn-around time


Further Opportunities

1) Extensions (optional)

XML Schemas

Custom Data Model

XML Schemas

feeds into

generates

Custom Data Model



Extension Organisation A

Extension Organisation CShared Data of Organisation A, B and C

Extension Organisation A

Extension Organisation C

In-house Schema of Organisation A

Extensib

le


Further Opportunities:

2) Value Validation (optional)

A standard methodology for validating values in an XML instance

• Using OASIS Genericode formatfor defining code value lists

• Using OASIS Context Value Association format for associating XML schemas to code value lists

• Using ISO Schematron formatfor defining more complex business constraints

• Generates one run-time Stylesheet for platform-independent validation



2) Value Validation (optional 2-pass)

Diagram courtesy of www.CraneSoftwrights.com


Tools


2) Value Validation (optional)

Custom Data Model

XML Schemas

feeds into

generates

Custom Data Model


XML Value Validation skeletons

generates

Integrated V

alue Valid

ation


Further information available

Brochure• Model-driven Semantic Interoperability: Education Sector Case Study

Demo CD• Model-driven XML Vocabulary: 1 hr demo video showing MXV in action

SSC Object Registry Service• http://registry.e.govt.nz

Web links• http://www.d-m-s.co.nz/serv_xmlschema.htm (incl. MXV Trial Download)


Credits and References

StandardsUML Unified Modelling Language http://www.uml.org/W3C XML 1.0 http://www.w3.org/TR/1998/REC-xml-19980210W3C XML Schema http://www.w3.org/XML/Schema#devISO/IEC 11179-5 Part 4 Data Element Naminghttp://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35347UN/CEFACT Unqualified Data Types Schema http://www.unece.org/cefact/OASIS UBL NDR http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.htmlNew Zealand Education Sector Languagehttp://www.minedu.govt.nz/~/media/MinEdu/Files/EducationSectors/PrimarySecondary/Initiatives/ModelDrivenSemanticIneroperability.pdfOASIS Genericode and OASIS Context Value Association http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=codelist http://www.genericode.orgISO Schematron http://standards.iso.org/ittf/PubliclyAvailableStandards/index.htmlW3C XSLT http://www.w3.org/TR/xslt20/

ToolsModellingSybase PowerDesigner http://www.sybase.com/products/modelingdevelopment/powerdesignerXML Value ValidationCrane Softwrights Schematron Implementation of OASIS context/value association files http://www.cranesoftwrights.comCrane Softwrights Genericode and context/value association files rendering stylesheets http://www.cranesoftwrights.comISO Schematron to XSLT skeleton http://www.schematron.com

Lessons Learnt

Lessons Learnt

Robyn Smits, Ministry of Education

Lesson’s learnt

• Keys to success:– Well defined message requirements assessed early in

project lifecycle– Message mock-ups presented to subject matter experts

during requirements definition phase– Early confirmation of modeller interpretations & issues – Similarity of messages reduced time required to create

subsequent messages after first created– Stability of requirements meant little rework– Good project communications.

Engage your data modeler early

48

Lessons Learnt

• Accept interoperability as an ongoing subject matter.

• Ensure full business and IT management support.

• Allow for broad semantic model consensus.

• Expect consensus to be time consuming.

• Ensure long-term semantic model ownership.

• Evolving the data model keeps schema forward migrations simple.

• Avoid data model revolutions if possible.

• Keep administration centralised.

• Ascertain strong tool support before embarking.

• Except impact on business processes and processing.

• Expect impact on application development and testing.

• Interoperability attempts without IT governance are likely to fail.

• Plan for a cultural change.

• Don’t expect efficiency gains too soon.

• Manage the optimal component library release frequency.

Questions

?

The verdict

It delivers:

• Standardised messages,• Powerful validation options.

But it requires:

• Requires whole organisation commitment,

and• Schema creation is complex.

Feel free to contact us

• Robyn Smits, MoESenior Manager Sector Services

www.minedu.govt.nz

• Andreas Kubisch, MoESenior Business Systems Analyst, Interoperability Team

www.minedu.govt.nz

• Alistair Betts, Summit SolutionsESDM Data Modeller, ESL Schema Developer

www.summitsolutions.co.nz

• Juerg Tschumperlin ESL / MXV Methodology, MXV Tools, Customisation and Implementation

www.d-m-s.co.nz

Thank you

for your time

and

attendance

inter-operability in the education sector using a sector data model driven methodology

Documents