Discussion #2336
Discussion #2318: MIWP-6 - Identification and documentation of use cases for Registries and Registers
Use Case F Linking the registers/registries with the underlying UML models
| Status: | New | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  Christian Ansorge |
Description
| Name | Linking the registers/registries with the underlying UML models |
| Primary Actor | INSPIRE Data Provider |
| Goal |
Provide simple pipeline/methodology/tools to ensure live link between UML models and registers/registries publishing their content. In case underlying UML models are changed this change should be easily reflected into the register/s and their systems. |
| System under consideration |
* Systems for the domain/national UML models managements. (e.g. SVN, Enterprise architect) * Systems for presenting and harvesting of the registers built on top of the underlying UML models. (e.g.Registers, Registries) |
| Importance | high |
| Description |
Considering the current nature and environment where INSPIRE UML model is maintained, this should contain guidance, how to link existing national and domain exchange UML models to registers/registries as well as how to establishing the links towards INSPIRE UML model available via SVN repository in case of INSPIRE national and domain extensions. |
| Pre-Condition | Existence of national and domain specific UML models |
| Post-Condition | Availabiltiy of the national and domain specific UML models, or INSPIRE model extensions content via Register/s, or Registires. |
| Step 1 |
Data provider would like to provide more efficient human and machine readable interface to national or domain specific UML model or extension of INSPIRE UML model. |
| Step 2 | Data provider is following the instructions, methodology or using the tools/s allowing provision of the national or domain specific UML model or extension of INSPIRE UML model. |
| Step 3 | The link between the model and register/registry is established and able to reflect the changes in the UML model based on agreed versioning. |
History
#1
Updated by Michael Lutz almost 6 years ago
- Tracker changed from Bug to Discussion
- Project changed from Re3gistry development & testing to MIWP-6: Registers
- Parent task set to #2318