1 / 52

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

INTER-OPERABILITY IN THE EDUCATION SECTOR USING A SECTOR DATA MODEL DRIVEN METHODOLOGY. During 2008 SSC, Standards NZ and a number of agencies worked together on developing 3 sets of guidelines for governing XML inter-operability.

aidan-patel
Télécharger la présentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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. Introduction Robyn Smits, Senior Manager, Sector Services, Ministry of Education

  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. Wider Context ofXML Schema Design • What is an XML Schema? Juerg Tschumperlin, DMS Data Management Solutions

  8. Wider Context ofXML Schema Design 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

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

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

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

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

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

  14. Wider Context ofXML Schema Design How are custom XML Schemas developed? Usually • Project-based, andHand-coded OR • Project-based, andGenerated from- database structure, or- application program code, or- XML Schema model(1 stand-alone model per schema)

  15. Wider Context ofXML Schema Design • How are custom XML Schemas developed? Usually • Project-based, andHand-coded OR • Project-based, andGenerated 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

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

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

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

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

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

  21. Today’s presentation will show: Wider Context ofXML Schema Design ESDMEducation Sector Data Model CustomData Model Model-driven XML Vocabulary Transformation Methodology MXV Transformation Methodology feeds into derives XML Schemas

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

  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? Is it a sector message? Map requirements to model & mock up messages Approve changes to ESDM via data dictionary Update ESDM model Create new draft message schemas Model & message approval Final changes and release to specification status 27

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

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

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

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

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

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

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

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

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

  37. From Data Model to XML Schema MXV Transformation Methodology

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

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

  40. MXV Tool Support From Data Model to XML Schema Administrator Custom Data Model Custom Data Model MXV Tools:PD = Sybase PowerDesigner DMS = MXV Productivity Tools UML Modelling (PD) Create New Model Version (DMS) Check NDR Naming and Design Rules Compliance (DMS) Automatically populate the XML Component Library (DMS) MXV Transformation Methodology Check completeness of XML Component Library (DMS) Reliable schema quality Fast turn-around time feeds into UML to XML Schema Impact Analysis (PD) XML Schema Modelling (PD) XML Schemas XML Schemas Migrate to Specification (DMS) Clone an XML View (DMS) generates XML Schema Generator (PD & DMS) Create Delivery Package (DMS)

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

  42. 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 From Data Model to XML Schema

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

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

  45. From Data Model to XML Schema 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)

  46. Credits and References Standards UML Unified Modelling Language http://www.uml.org/ W3C XML 1.0 http://www.w3.org/TR/1998/REC-xml-19980210 W3C XML Schema http://www.w3.org/XML/Schema#dev ISO/IEC 11179-5 Part 4 Data Element Naming http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35347 UN/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.html New Zealand Education Sector Language http://www.minedu.govt.nz/~/media/MinEdu/Files/EducationSectors/PrimarySecondary/Initiatives/ModelDrivenSemanticIn eroperability.pdf OASIS Genericode and OASIS Context Value Association http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=codelisthttp://www.genericode.org ISO Schematron http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html W3C XSLT http://www.w3.org/TR/xslt20/ Tools Modelling Sybase PowerDesigner http://www.sybase.com/products/modelingdevelopment/powerdesigner XML Value Validation Crane Softwrights Schematron Implementation of OASIS context/value association files http://www.cranesoftwrights.com Crane Softwrights Genericode and context/value association files rendering stylesheets http://www.cranesoftwrights.com ISO Schematron to XSLT skeleton http://www.schematron.com

  47. Lessons Learnt Robyn Smits, Ministry of Education Lessons Learnt

  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 ?

More Related