1. AN ORGANISATION FOR A NATIONAL EARTH SCIENCE INFRASTRUCTURE PROGRAM Information modelling – tools Simon Cox

2. Overview A little more UML –Governance concerns, packaging and namespaces Hollow World interface Usage guidelines A few unavoidable details 2

3. UML structure diagrams

4. Class diagrams Show information objects, their properties and relationships } Class attributes } Class constraints Not shown – class operations Additional parent not shown Specialization Association Class stereotype Attribute stereotype Association-end role name Class

5. Package diagrams Dependencies & maintenance arrangements

6. Packaging is important Unit of governance UML Package = XML Namespace –If stereotyped «applicationSchema» 6

7. Object diagrams … can get busy very fast “Accidents in Legoland” Mostly useful in the analysis phase

8. Summary of UML structure diagrams Package –ownership (governance arrangements) –dependencies Class –the data model Objects –examples in action

9. HollowWorld

10. Hollow World template A template for designing application schemas in UML Contains key standards components –ISO 19100 Harmonized Model –OGC SWE Model –ISO 19136 stereotypes and tagged values –INSPIRE themes

11. Hollow World UI Access to standard/utility components Access to standard stereotypes

12. ISO Harmonized Model Key packages used for Application Schema design: –19103 – primitive types –19107 – geometry –19108 – temporal –19111 – coords –19115 – metadata –19123 – coverages –19136 – GML –19156 – O&M (go to EA live to explore)

13. Standard components: OGC Sensor Web Key packages used for Application Schema design: –SensorML –Observations & Measurements –SWE Common –SOS, SPS... (go to EA live to explore)

14. Elements from external standards Standard components are loaded from remote SVNs They are locked against modification by unauthorized users (i.e. mere application-schema designers!) –i.e. the tool enforces the governance arrangements Package your domain model separately

15. High level usage guidelines

16. Use of UML Informative - sketch or illustrate ideas –Ambler (Agile methodologies …) uses it mostly this way vs. Formal & complete –In order to feed a CASE tool For automatic implementation, the model must be complete –Everything required for implementation must be in either The model The rule for converting from model to implementation –UML == ‘graphical programming language’ Every comma counts, just like real programming

17. Be aware of the workflow Raw observations –E.g. temperature field, flow-rate history, density distribution, colour distribution (image) –i.e. evidence Interpolated/modelled properties –Geophysics, MetOcean –Results of simulations and process models, conditioned by observations –i.e. predictions, simulations, inversions ‘Real-world’ features –E.g. weather system, ore-body, forest, reef –i.e. result of interpretation Often useful to segregate these viewpoints into different packages

18. Be consistent about the abstraction level Conceptual - Domain semantics –Terminology as used by practitioners in the discipline not an abstraction from data management –‘Ore-body’, not ‘Table’ or ‘Polygon’ or ‘URI’ Don’t show identifier, key/keyref in the class model –these are implicit in the relationships Implementation –Shows implementation artefacts like ‘string’, ‘id’, ‘index’

19. Document as you go 19

20. More information For more detail: –https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlOutlinehttps://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlOutline –https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlGmlStereotypesAndTaggedVal ueshttps://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlGmlStereotypesAndTaggedVal ues –https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlGmlTestModelshttps://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlGmlTestModels

21. UML extensibility points

22. UML extensions Stereotypes –Extend the meta-model: –To create an additional class-of- [classes, associations, attributes]

23. UML Stereotypes «FeatureType»  standard properties & behaviour

24. Class stereotypes «FeatureType» –Domain class, instances have identity «Type» or none –Has identity, but not a feature; e.g. geometry, topology, temporal object, definition «DataType» –Just a data structure, no external identity, always inline «Union» –Ad-hoc choice «Enumeration» –Closed enumeration «Codelist» –Extensible enumeration

25. Package stereotypes «Application Schema» –independently governed package, separate XML namespace «Leaf» –Convenience package, no sub- packages, separate XSD document

26. UML extensions Stereotypes Tagged values –Embed information for specific implementation platforms –Doesn’t relate to the conceptual level

27. UML Tagged values

28. Tagged values for GML encoding Package –xsdDocument –xmlns –targetNamespace Class –noPropertyType –byValuePropertyType –asDictionary («codeList» only) –ownedBy (proposed) Attribute and association end –sequenceNumber –inlineOrByReference –estimatedProperty (proposed) https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/UmlGmlStereotypesAndTaggedValues

29. Acknowledgements SISS Project Sponsors: AuScope, ANDS and the ARCS Organisations are supported by the Australian Government through the National Collaborative Research Infrastructure Strategy Program and/or the Education Investment Fund (EIF) Super Science Initiative Workshop assistance provided by:

30. AN ORGANISATION FOR A NATIONAL EARTH SCIENCE INFRASTRUCTURE PROGRAM AuScope 2007-2011