Difference between revisions of "Reports Store Gateway scenarios for VME"
From D4Science Wiki
(→Scenarios) |
(→Scenarios) |
||
| Line 17: | Line 17: | ||
==Scenarios== | ==Scenarios== | ||
| − | Data entry actions are Create, Read, Update and Delete, so 4 in total. There are 5 scenarios (see below), with each 4 sub scenarios(see below. Total amount of scenarios is 4*5*4 = 80. | + | Data entry actions are Create, Read, Update and Delete, so 4 in total. There are 5 scenarios (see below), with each 4 sub scenarios(see below. Total amount of scenarios is 4*5*4 = 80.<br> |
One report manipulates these objects: | One report manipulates these objects: | ||
Revision as of 14:54, 4 November 2013
Introduction
This page describes the foreseen data entry scenarios for the iMarine Reports for the VME-DB project. This scenario will use the Reports-store-gateway
Data structure
One iMarine VME Report manipulates these objects:
- Vme
- SpecificMeasure
- Profile
Then there 4 RefReports:
- GeneralMeasure
- InformationSource
- FisheryAreasHistory
- VmesHistory
Scenarios
Data entry actions are Create, Read, Update and Delete, so 4 in total. There are 5 scenarios (see below), with each 4 sub scenarios(see below. Total amount of scenarios is 4*5*4 = 80.
One report manipulates these objects:
- Vme (V)
- SpecificMeasure(SM)
- Profile(P)
|
Scenario |
V 2010 |
V 2011 |
SM 2009 |
SM 2010 |
SM 2012 |
P 2010 |
P 2011 |
P 2012 |
|
1 |
* |
|
* |
|
|
* |
|
|
|
2 |
* |
|
|
* |
|
|
* |
|
|
3 |
* |
|
|
|
* |
|
|
* |
|
4 |
* |
* |
* |
* |
* |
* |
* |
* |
Each of these objects is a RefReport:
- GeneralMeasure (GM)
- InformationSource (IS)
- FisheryAreasHistory (FH)
- VmesHistory (VH)
|
Subscenario |
GM 2009 |
IS 2010 |
FH 2011 |
VH 2012 |
|
1 |
* |
|
|
|
|
2 |
|
* |
|
|
|
3 |
|
|
* |
|
|
4 |
|
|
|
* |
|
5 |
* |
* |
* |
* |
Resources
- See also Reports-store-gateway
