UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
(Die Seite wurde neu angelegt: „'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:''' Adopt vehicle working scheduling to timetable changes; {{Deu|Umlauf an Jahresfahr…“)
 
No edit summary
Line 25: Line 25:
<u>How often do the data change (update)?</u>
<u>How often do the data change (update)?</u>


could be daily
* could be daily


<u>How big are the data fragments to be exchanged (complexity)?</u>
<u>How big are the data fragments to be exchanged (complexity)?</u>
Line 33: Line 33:
<u>Which views are represented by the data (focus)?</u>
<u>Which views are represented by the data (focus)?</u>


any
* any


<u>Which specific timetable data do you expect to receive/send (elements)?</u>
<u>Which specific timetable data do you expect to receive/send (elements)?</u>


see _Import complete timetable for vehicle working scheduling_
* see _Import complete timetable for vehicle working scheduling_


We describe different subtypes of the _adopt to timetable changes_ usecase.
We describe different subtypes of the _adopt to timetable changes_ usecase.

Revision as of 17:39, 21 May 2015

Use case / Anwendungsfall / :

Adopt vehicle working scheduling to timetable changes; Umlauf an Jahresfahrplan anpassen


Description / Beschreibung /

The importing system holds timetable and vehicle working data. A change in the timetable shall be imported.


Data Flows and Interfaces / Datenflüsse und Schnittstellen /

The import may be performed manually via a file based interface, or online via a message (SOAP) based interface.


Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen /

  • Common
  • Infrastructure
  • Rolling stock


Characterising Data / Charakterisierung der Daten /

How often do the data change (update)?

  • could be daily

How big are the data fragments to be exchanged (complexity)?

  • small (single train run)

Which views are represented by the data (focus)?

  • any

Which specific timetable data do you expect to receive/send (elements)?

  • see _Import complete timetable for vehicle working scheduling_

We describe different subtypes of the _adopt to timetable changes_ usecase.

Change train data (commercial or operational) in a given validity

Precondition:

  • Import data contains commercial train information with valid id and validity.
  • System holds data on a train with this id, and the validity of the train covers the validity change request.

Execution

  • The system splits the train into one with validity of the change request, and one with the remaining validity.
  • The changes are applied to the first train, according to the usecase in _Import complete timetable for vehicle working scheduling_.

Postcondition

  • The train is changed within the validity of the change request, and unchanged outside.

Change validity of a train

Precondition:

  • Import data contains commercial train information with valid id and validity.
  • System holds data on a train with this id

Execution:

  • The validity of the train is changed.