UC:TT:UseCases: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(Transfer of use cases to discussion)
Line 19: Line 19:
* Betriebsleitsysteme/RBL (<font color="red">writer: INIT</font color>; <font color="red">reviewer: IVU</font color>)
* Betriebsleitsysteme/RBL (<font color="red">writer: INIT</font color>; <font color="red">reviewer: IVU</font color>)
* Dienstbildung Personal Jahresfahrplan (<font color="red">writer: INIT</font color>; <font color="red">reviewer: IVU</font color>)
* Dienstbildung Personal Jahresfahrplan (<font color="red">writer: INIT</font color>; <font color="red">reviewer: IVU</font color>)
* Disposition Fahrzeugeinsatz (<font color="red">writer: ???</font color>; <font color="red">reviewer: ???</font color>)
 
* Ergebnis Fahrplansimulation (<font color="red">writer: ???</font color>; <font color="red">reviewer: ???</font color>)


=== Glossary ===
=== Glossary ===

Revision as of 13:51, 29 September 2016

RailML Trademark RGB V2.png
XML Railway exchange format
https://railML.org
Latest release: 2.5
(September 1st, 2021)
 
Main Menu
 
Subschemas
XML tree
UML diagrams
Use cases
Versions & Changes

This page provides use cases specific to the TT-subschema. See Dev:Use cases to learn what a use case is, how to contribute to writing good railML®-Use Cases and where to find them in this wiki.

List of Use Cases

The following list provide links to the use cases related with the exchange of timetable data (TT schema):


Glossary

  • LTP = long term planning: the yearly timetable(s)
  • STP = short term planning: changes to the current production timetable up to the point that changes can be published to downstream systems (passenger information, train control, train operators, etc.)




Use cases, usecase, usescases