1 / 7

A few lessons learnt from data modeling

A few lessons learnt from data modeling. Data Model Working Group , M.Louys , IVOA Interop Pune, Oct 2011. Different purposes for Data models . Core information VOResource VODataService STC Photometry Data product oriented + Protocols Spectral DM  concepts

bly
Download Presentation

A few lessons learnt from data modeling

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. A few lessons learnt from data modeling Data Model Working Group , M.Louys, IVOA Interop Pune, Oct 2011

  2. Different purposes for Data models Core information VOResource VODataService STC Photometry Data product oriented + Protocols Spectral DM  concepts SSA re-uses the concepts and add more for query parameters and access SSLDM  SLAP

  3. Data model life cycle: first step Use-case oriented separate data models Good to start and get practice Helps to identify the core concepts and define the vocabulary Needs some iterations to converge and be robust Needs implementations to adjust to use-cases in practice and not only the primary specification Provides a patchy map of how our DMs cover the domain field Caveat : avoid overlap of DMs : one major concept should be in only one model

  4. Data model life cycle: second step Refactoring Identify reusable parts Identify abstract properties or roles Re-organise the concepts Fill the gaps e.g : Spectral DM and side models : SED, Timeseries Characterisation 2.0 need to access to external products ( resolution maps, sensitivity maps, etc.)

  5. Not yetmodeled Complex observations • Considervarious possible aggregations • Other efforts pointing to this : DCP ontology • Consider the way the user proceeds • Need for intermediatepreview data • Codes used in analysis of data • Other use cases ?

  6. The other approach Top-down from domain model down to physical data model Followed by the SimDM Gives a more uniform coverage of the needs Feasible for a rather homogeneous application domain Applicable with few contributors

  7. Conclusion Having a completeviewinvolvesbothapproach Appliedmodels Abstract view Explore specification Organise the overalldetailsarchitechure multiple iterations in a reasonnable time

More Related