IPDA PDAP | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012 | Pag. 1 IPDA PDAP UML for Extensions Jesus Salgado ESA/PSA 12/07/2012

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 2 PDAP Extensions –During last IPDA meeting 4 different extensions were identified: –Spectral extension –Time support extension –FlyBy extension –Geometrical Extension –First step was to identify the possible data model extensions to plug them inside the Core PDAP UML model

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 3 UML problems –In the process of creation of these extensions, some questions were raised: –Do we need new specifications for this? Metadata added looks minimal –How to solve multiple inheritance? –How to integrate all the extensions in a single UML? –How to create a UML easily extendable? –Is this UML in line with PDS4?

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 4 PDAP standard UML

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 5 Metadata added per extension: Spectral UML –Spectral data looks a good candidate for a product extension –It looks not so present in planetary data than in astrophysics. More 2D tables than spectral data itself –It appears in two places with the current UML: Flyby products and MapProjected products could be spectra –Spectral (energy) axis support could be also needed for, e.g., images so the support for the spectra axis is more general

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 6 Metadata added per extension: Time support –After initial analysis from our French colleagues, not too many metadata should be added to provide time support within PDAP –Time ranges support for queries and time axis support for products –Qualifier is needed to define the system of reference where this time values are applicable

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 7 Metadata added per extension: Flyby products –Flyby products are different from standard products due to spacecraft orbit position and orientation –This is defined within Spice kernels –Suggestion to add a link to the spice kernel + some orientation angles and position

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 8 Questions 2/3/4: A UML proposal

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 9 Data structures minimodel

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 10 Time Support extension

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 11 Flyby extension

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 12 Spectral Extension

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 13 Questions for discussion –Is this approach a possible simplification or it makes the UML more complex? –Do we need to explore this into the different extensions? –Do we need a single PDAP document or one core + extensions (new metadata justifies new specifications? –How is this related with PDS4? Other planetary DMs?

IPDA PDAP UML proposal | Jesus Salgado | ESAC | 12 July 2012 | IPDA meeting Bangalore 2012| Pag. 14 THANK YOU Jesus Salgado IPDA PDAP UML for extensions