|
|
Line 1: |
Line 1: |
| {{UseCase|TT||title=Adopt vehicle working scheduling to timetable changes|CO=1|IS=1|RS=1|reporter=IVU}} | | {{mirror}} |
| | |
| {{UC title}}
| |
| Adopt vehicle working scheduling to timetable changes; {{Deu|Umlauf an Jahresfahrplan anpassen }}
| |
| | |
| {{UC description}}
| |
| The importing system holds timetable and vehicle working data. A change in the timetable shall be imported.
| |
| | |
| {{UC flows}}
| |
| The import may be performed manually via a file based interface, or online via a message (SOAP) based interface.
| |
| | |
| {{UC interference}}
| |
| * Common
| |
| * Infrastructure
| |
| * Rolling stock
| |
| | |
| {{UC data}}
| |
| | |
| {{UC update}}
| |
| * could be daily
| |
| | |
| {{UC complexity}}
| |
| | |
| * small (single train run)
| |
| | |
| {{UC focus}}
| |
| | |
| * any
| |
| | |
| {{UC elements|TT}}
| |
| | |
| * 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.
| |