esdm 15: making our shared sector model meet real messaging needs

Education Sector Data Model ESDM version 15:

Making our shared sector model meet real messaging

needs January 26 2011

Agenda

Introduction / Background Recent History of ESDM SRT: The newest implementation of ESDM SRT: A look inside the SRT delivery

package MXV Tool Suite Lessons Learnt Q & A

Introduction / Background

Paul Seiler, Ministry of Education

Recent History of ESDM

Juerg Tschumperlin, D-M-S Data Management Solutions


extension

CSDM V1 (2006)

Education Sector Data Model

ESDM V12 (2005)

ESDM V14 (2009)evolved into

CSDM V2CSDM V3

CSDM V4

Compulsory Sector Data Model

CSDM V5 (2010)

extension

ESDM V15 (2011)merged into

ESDM V14 (2009)279 classes / 345

attributes

CSDM V1 (2006)

ESDM V12 (2005)269 classes / 360

attributes

evolved into

CSDM V2CSDM V3

CSDM V4

CSDM V5 (2010)265 classes / 173

attributes

extension

ESDM V15 (2011)568 classes / 609

attributes

merged into


ESDM is evo

lving

ESDM grows f

ast enough to

meet

project

timefra

mes

SRT Student Record Transfer:

The newest implementation of the Education Sector Data Model

(ESDM)


SRT: ESDM’s newest implementationGeneric Model-driven XML Vocabulary Design:

MXV Transformation Methodology

XML Delivery Packages

Custom Data Model

feeds into

derives

XML Delivery Packages

Custom Data Model

SRT: ESDM’s newest implementation

Model-driven XML Vocabulary Design in the Education Sector:


Education Sector Language

ESL XML Delivery Packages

ESDMEducation Sector Data

Model

feeds into

derivesSince 2006:

21 delivery packages / 60 schemas)




ESDM V15Education Sector Data

Model

equivalent expressions

The methodolgy e

nsure

s:

- XML sc

hemas deriv

ed from E

SDM

- Names m

atch

- Defin

itions c

ascade

- Tech

nical s

tandards c

ompliance

- Ove

r 300 re

usable X

ML component v

iews

Value Validation: (Optional delivery package add-on)

A standardised methodology for validating values in an XML instance

Using OASIS Genericode © formatfor defining code value lists

Using OASIS Context Value Association © format for associating code value lists with XML schemas

Using ISO Schematron © formatfor defining more complex business constraints

Generates one run-time Stylesheet for platform-independent validation


2) Value Validation (2-pass)

Diagram courtesy of www.CraneSoftwrights.com

SRT: ESDM’s newest implementationValue Validation: (Optional delivery package add-

on)

Value Validation: (Optional delivery package add-on)


Tools

Custom Data Model

XML Schemas

feeds into

generates

ESDM V15


XML Value Validation skeletons

generates

Value Valid

ation is

integra

ted into M

XV

SRT: A look inside the delivery package

Andreas Kubisch, Ministry of Education

Much more than just a schema!

Self-contained

Fully versioned – whole package as well as individual components

Fully tested

Basic structure:

1. \cl - Content validation files Individual components GC, SCH and CVA Assembled XSL – includes all of the above Batch files to run validation of sample messages

2. \val - Java based Saxon validator

3. \xml - Populated Sample messages

4. \xsd – Structural Validation Files Schemas and Libraries Documentation files

Using the schema

Only 3 components required for prod useXSL + XSD + Libraries

Additional documentation essential for implementation

Multiple concurrent versions of same message are possible

MXV Tool Suite


MXV Tools:PD = Sybase PowerDesigner ® DMS = MXV Plugins from Data Management Solutions© for PowerDesigner

Administrator

MXV Tool Suite

XML Schemas

Custom Data Model




feeds into

generates

ESDM V15

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

Key success factors

XML Schemas

Custom Data Model




feeds into

generates

ESDM V151. Analyse data requirements well

(messaging has a long life span)

2. Utilise ESDM by evolving it as required

(messaging project by messaging project)

3. Utilise MXV for uniform delivery packages

(uniformity fosters buy-in creates pay-back)

Lessons Learnt

Andreas Kubisch, Ministry of Education

A consistent approach to creating XML payloads is essential While the methodology is rightly complex – using the

schemas is not Vendors will benefit from extra help SMS vendors are now used to it and can see the benefits The X stands for extensible The earlier validation happens the better Trust but verify There is more to messaging than the payload messages The difficulty is not getting what you want – it is knowing

what you want i.e certainty about requirements = quick turn around on schema package

A consistent approach to maintaining “official” code value lists is required – incl versioning

More information on SRT and ESDM is available:SRT Delivery Package & ESDM V15 (snapshot Jan 2011)

http://tech.groups.yahoo.com/group/data-sharing-framework/files/Student%20Record%20Transfer%20%28Optional%29/

Also available on CD

BrochureModel-driven Semantic Interoperability: Education Sector Case Study

MXV Demo CDModel-driven XML Vocabulary: 1 hr demo video showing MXV in action

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

Questions?

Contacts

Paul Seiler, MoESMS Services Manager [email protected]

Andreas Kubisch, MoEBusiness Analyst, SMS Services [email protected]

Juerg Tschumperlin ESL / MXV Methodology, MXV Tools, Customisation and [email protected] www.d-m-s.co.nz

Thank you

for your

time and

attendance

esdm 15: making our shared sector model meet real messaging needs

Documents

recent history of esdm

xml instance

xml payloads

esdm v14

esdm v15 mxv tools

attributesextension

shared sector model

data requirements