Presentation is loading. Please wait.

Presentation is loading. Please wait.

INTER-OPERABILITY IN THE EDUCATION SECTOR USING A SECTOR DATA MODEL DRIVEN METHODOLOGY.

Similar presentations


Presentation on theme: "INTER-OPERABILITY IN THE EDUCATION SECTOR USING A SECTOR DATA MODEL DRIVEN METHODOLOGY."— Presentation transcript:

1 INTER-OPERABILITY IN THE EDUCATION SECTOR USING A SECTOR DATA MODEL DRIVEN METHODOLOGY

2 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.

3 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

4 Why go there? A business perspective Andreas Kubisch – Senior Business Systems Analyst

5 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 …

6 The challenges Code Value Lists Versioning Data quality Message Validation Connectivity Vendor capability Model flexibility

7 What is an XML Schema? Wider Context of XML Schema Design Juerg Tschumperlin, DMS Data Management Solutions

8 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: Wider Context of XML Schema Design

9 What is an XML Schema? Example of XML Schema Diagram: (Extract) Wider Context of XML Schema Design

10 What is an XML Schema? Example of XML Schema Code: (Extract) Wider Context of XML Schema Design

11 What is an XML Instance Document? Example of XML Instance: (Extract) Wider Context of XML Schema Design

12 XML Instance: Validation against XML Schema Validates? Y = Process Instance Incoming Instance N = Return to Sender Wider Context of XML Schema Design

13 How are XML Schemas commonly developed? By standard-setting bodies: “off-the-shelf” or Custom-build to meet requirements. Wider Context of XML Schema Design

14 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) Wider Context of XML Schema Design

15 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 Wider Context of XML Schema Design 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)

16 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. Wider Context of XML Schema Design

17 Facts: The XML Schema Language is not to blame. The real culprit is how we develop schemas. Wider Context of XML Schema Design

18 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. ? Wider Context of XML Schema Design

19 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. Wider Context of XML Schema Design

20 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). Wider Context of XML Schema Design

21 Today’s presentation will show: MXV Transformation Methodology XML Schemas Custom Data Model feeds into derives Wider Context of XML Schema Design M odel-driven X ML V ocabulary Transformation Methodology ESDM Education Sector Data Model

22 22 ESDM Project Education Sector Data Model: History and Outcomes Alistair Betts, Summit Solutions Ltd

23 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

24 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

25 The Model Subject Areas 25

26 Agencies Consulted Career Services Teachers Council ERO NZQA TEC MOE 26

27 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

28 From Data Model to XML Schema Juerg Tschumperlin, D-M-S Data Management Solutions

29 Industry-independent overview: MXV Transformation Methodology XML Schemas Custom Data Model feeds into derives From Data Model to XML Schema

30 Education Sector overview: MXV Transformation Methodology XML Schemas Custom Data Model feeds into derives From Data Model to XML Schema ESL XML Schemas Education Sector Language ESDM Education Sector Data Model

31 From Data Model to XML Schema Tools Administrator Data Owners XML Schemas Custom Data Model MXV Transformation Methodology ESL XML Schemas Education Sector Language feeds into derives ESDM Education Sector Data Model Schema Consumers End-to-end tool support Main players Shared data understanding Documented in a single model Project Team Messaging Requirements

32 MXV Transformation Methodology ESL XML Schemas Education Sector Language ESDM Education Sector Data Model feeds into derives UTF-8 character encoding ISO Data Naming UN/CEFACT Unqualified Data Types Schema OASIS Universal Business Language Naming and Design Rules (UBL NDR 2) [adapted] W3C XML SchemaW3C XML URN Naming high NZ e-Gif compliance Standardised XML Schema - tag names and definitions - versioning - look and feel - across projects and organisations From Data Model to XML Schema

33 ESL XML Schemas Education Sector Language ESDM Education Sector Data Model equivalent expressions Derived XML Schemas: - UML and XML in sync - Names match - Definitions cascade From Data Model to XML Schema

34 MXV Transformation Methodology ESL XML Schemas Education Sector Language ESDM Education Sector Data Model equivalent expressions XML Component Library populates is referenced by From Data Model to XML Schema

35 MXV Transformation Methodology ESL XML Schemas Education Sector Language ESDM Education Sector Data Model is referenced by populates UML data model Domain / Data Type Attribute Class Specialization 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 XML Component Library From Data Model to XML Schema OASIS UBL NDR-like component library Re-use of XML Schema components Tool supported Impact Analysis

36 MXV Transformation Methodology ESL XML Schemas Education Sector Language ESDM Education Sector Data Model feeds into derives From Data Model to XML Schema

37 MXV Transformation Methodology From Data Model to XML Schema

38 MXV Transformation Methodology Standards UML Modelling ISO Data Naming UN/CEFACT Unqualified Data Types Schema OASIS Universal Business Language Naming and Design Rules (UBL NDR 2) [adapted] ConceptsTools W3C XML SchemaW3C XMLModel-driven Architecture Semantic Vocabulary (aka Ontology) Sybase PowerDesigner D-M-S MXV Productivity Tools (optional) Change Management Process From Data Model to XML Schema

39 Data Owners ESL XML Schemas Education Sector Language ESDM Education Sector Data Model feeds into generates Administrator Schema Consumers XML Schemas From Data Model to XML Schema Data Owners Custom Data Model Schema Consumers MXV Transformation Methodology Standards UML Modelling ISO Data Naming UN/CEFACT Unqualified Data Types Schema OASIS Universal Business Language Naming and Design Rules (UBL NDR 2) [adapted] ConceptsTools W3C XML SchemaW3C XMLModel-driven Architecture Semantic Vocabulary (aka Ontology) Sybase PowerDesigner D-M-S MXV Productivity Tools (optional) Change Management Process Portable solution for developing custom semantic XML standards Suitable for any industry Suitable for messaging between organisations Suitable for messaging between in-house applications (EAI)

40 MXV Tools: PD = Sybase PowerDesigner DMS = MXV Productivity Tools Administrator MXV Tool Support XML Schemas Custom Data Model MXV Transformation Methodology 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 From Data Model to XML Schema

41 Further Opportunities 1) Extensions (optional) XML Schemas Custom Data Model XML Schemas feeds into generates Custom Data Model MXV Transformation Methodology XML Component Library Extension Organisation A Extension Organisation C Shared Data of Organisation A, B and C Extension Organisation A Extension Organisation C In-house Schema of Organisation A Extensible From Data Model to XML Schema

42 Further Opportunities: 2) Value Validation (optional) A standard methodology for validating values in an XML instance Using OASIS Genericode format for defining code value lists Using OASIS Context Value Association format for associating XML schemas to code value lists Using ISO Schematron format for defining more complex business constraints Generates one run-time Stylesheet for platform-independent validation From Data Model to XML Schema

43 Further Opportunities: 2) Value Validation (optional 2-pass) Diagram courtesy of From Data Model to XML Schema

44 Tools Further Opportunities: 2) Value Validation (optional) Custom Data Model XML Schemas feeds into generates Custom Data Model MXV Transformation Methodology XML Value Validation skeletons generates Integrated Value Validation From Data Model to XML Schema

45 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 Web links (incl. MXV Trial Download) From Data Model to XML Schema

46 Credits and References Standards UML Unified Modelling Languagehttp://www.uml.org/http://www.uml.org/ W3C XML 1.0http://www.w3.org/TR/1998/REC-xml http://www.w3.org/TR/1998/REC-xml W3C XML Schemahttp://www.w3.org/XML/Schema#devhttp://www.w3.org/XML/Schema#dev ISO/IEC Part 4 Data Element Naming UN/CEFACT Unqualified Data Types Schema OASIS UBL NDR New Zealand Education Sector Language eroperability.pdf OASIS Genericode and OASIS Context Value Association ISO Schematronhttp://standards.iso.org/ittf/PubliclyAvailableStandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableStandards/index.html W3C XSLT Tools Modelling Sybase PowerDesignerhttp://www.sybase.com/products/modelingdevelopment/powerdesignerhttp://www.sybase.com/products/modelingdevelopment/powerdesigner XML Value Validation Crane Softwrights Schematron Implementation of OASIS context/value association files Crane Softwrights Genericode and context/value association files rendering stylesheets ISO Schematron to XSLT skeleton

47 Lessons Learnt Robyn Smits, Ministry of Education

48 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

49 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.

50 Questions ?

51 The verdict It delivers: Standardised messages, Powerful validation options. But it requires: Requires whole organisation commitment, and Schema creation is complex.

52 Feel free to contact us Robyn Smits, MoE Senior Manager Sector Services Andreas Kubisch, MoE Senior Business Systems Analyst, Interoperability Team Alistair Betts, Summit Solutions ESDM Data Modeller, ESL Schema Developer Juerg Tschumperlin ESL / MXV Methodology, MXV Tools, Customisation and Implementation Thank you for your time and attendance


Download ppt "INTER-OPERABILITY IN THE EDUCATION SECTOR USING A SECTOR DATA MODEL DRIVEN METHODOLOGY."

Similar presentations


Ads by Google