User:RailML Coord Governance: Difference between revisions
(Pattern for railML 3 use cases for timetable added) |
(Copy & Paste errors from IS fixed; clarification for last segment added) |
||
| Line 48: | Line 48: | ||
*''tiny (attribute)'' | *''tiny (attribute)'' | ||
*''very small (element)'' | *''very small (element)'' | ||
*''small ( | *''small (single train run)'' | ||
*''big ( | *''big (line)'' | ||
*''huge (region)'' | *''huge (region)'' | ||
*''whole data set (network)'' | *''whole data set (detailed operational concept network)'' | ||
<u>Which views are represented by the data (focus)?</u> | <u>Which views are represented by the data (focus)?</u> | ||
| Line 64: | Line 64: | ||
*''...'' | *''...'' | ||
<u>Which specific | <u>Which specific timetable data do you expect to receive/send (elements)?</u> | ||
''Fill in your application-specific data structure elements, which you want to see modelled in railML 3.''<br> | ''Fill in your application-specific data structure elements, which you are using and want to see modelled in railML 3.''<br> | ||
''Please define | ''Please describe also structures which should be modeled in another way (so called "code refactoring") in railML 3''<br> | ||
''Attention: This is the most important part of this questionaire. Please define as detailed as possible, the length isn't limited here.'' | |||
Revision as of 11:26, 11 February 2015
Vasco Paul Kolmorgen
railML-Koordinator
Tel. +49 351 46676939
01069 Dresden
Germany / Deutschland /
Vorlage für railML® 3 use cases im timetable-Schema
Use case / Anwendungsfall / :
An expressive name in English; Ein aussagekräftiger Name in Deutsch;
Description / Beschreibung /
What is the application behind the use case? Which data are required? Who or which tool/application provides these data? Which data are not included (if not obvious)? Define the boundaries of the use case and the relevant data. (max. 200 words, English)
Data Flows and Interfaces / Datenflüsse und Schnittstellen /
Which data flows (from/to the use case application) exist? Which data and process interfaces exist?
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen /
- infrastructure
- rolling stock
- interlocking
- other ..............
Characterizing Data / Charakterisierung der Daten /
This section serves to specify the required data regarding certain aspects.
How often do the data change (update)?
- static (not changing)
- yearly
- regular changes
- monthly
- weekly
- daily
- realtime (seconds)
How big are the data fragments to be exchanged (complexity)?
- tiny (attribute)
- very small (element)
- small (single train run)
- big (line)
- huge (region)
- whole data set (detailed operational concept network)
Which views are represented by the data (focus)?
- Long term planning (eg. for infrastructure dimensioning)
- Mid term planning (eg. for yearly timetable disposition)
- Short term planning (eg. for trackworks)
- Real term planning (eg. for dispatching)
- Statistics
- Fare collection
- Passenger information
- ...
Which specific timetable data do you expect to receive/send (elements)?
Fill in your application-specific data structure elements, which you are using and want to see modelled in railML 3.
Please describe also structures which should be modeled in another way (so called "code refactoring") in railML 3
Attention: This is the most important part of this questionaire. Please define as detailed as possible, the length isn't limited here.