Search results
Jump to navigation
Jump to search
- Dev:Use case example/old (category UC without specified reporter) (section Which views are represented by the data (focus)?)Template: UC focus (type {{UC focus}}) Please list all elements that are part of the data in this use case. The headline is made with Template: UC elements10 bytes (220 words) - 16:47, 4 December 2023
- eporter=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} For10 bytes (1,035 words) - 21:45, 23 January 2020
- UC:TT:SlotOrdering (category UC reported by SMA) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:SlotOrdering in The railML® 3 wiki.10 bytes (273 words) - 16:12, 3 February 2020
- UC:IL:HardwareAndCablePlan (category UC without specified reporter) (section Which views are represented by the data (focus)?)page UC:IL:HardwareAndCablePlan in The railML® 3 wiki.10 bytes (119 words) - 16:12, 3 February 2020
- UC:IS:RailwayInfrastructureVisualisation (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:RailwayInfrastructureVisualisation in The railML® 3 wiki.10 bytes (180 words) - 16:12, 3 February 2020
- UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets in The railML® 3 wiki.10 bytes (383 words) - 16:12, 3 February 2020
- UC:IS:Timetabling (category UC reported by ProRail) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:Timetabling in The railML® 3 wiki.10 bytes (343 words) - 16:12, 3 February 2020
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category UC reported by IS) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers in The railML® 3 wiki.10 bytes (367 words) - 16:12, 3 February 2020
- UC:TT:TimetableInformation (category UC reported by HaCon) (section Which views are represented by the data (focus)?)material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger information.10 bytes (751 words) - 16:12, 3 February 2020
- UC:TT:TAF/TAP TSI (category UC reported by ERA) (section Which views are represented by the data (focus)?)at least for 12 months after such data have expired." This use case will focus on the definition of the minimum requirements for passenger information.10 bytes (592 words) - 16:12, 3 February 2020
- UC:IS:Schematic Track Plan (category UC reported by JBD) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:Schematic Track Plan in The railML® 3 wiki.10 bytes (198 words) - 16:12, 3 February 2020
- UC:IS:Railway Simulation Laboratory (category UC reported by Czech Technical University in Prague (ČVUT)) (section Which views are represented by the data (focus)?)students with different railway issues). At present, our project is mainly focused to develop and implementing new technology of intelligent traffic system10 bytes (427 words) - 16:12, 3 February 2020
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category UC reported by Thales Austria) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IL:SitePreparationDataForSignalControlledWarningSystems in The railML® 3 wiki.10 bytes (571 words) - 16:12, 3 February 2020
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category UC reported by Jernbaneverket) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IL:InterlockEngineeringForSignallingWithinJBV in The railML® 3 wiki.10 bytes (558 words) - 16:12, 3 February 2020
- UC:TT:FGIInTrain (category UC reported by Interautomation) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:FGIInTrain in The railML® 3 wiki.10 bytes (677 words) - 16:12, 3 February 2020
- UC:IL:InterlockingEngineering (category UC without specified reporter) (section Which views are represented by the data (focus)?)etc) (origin: Railway regulations or other plain text requirements) The focus should be on data reliability because IL and IS data will be used for producing10 bytes (828 words) - 16:12, 3 February 2020
- UC:IS:MaintenancePlanning (category UC without specified reporter) (section Which views are represented by the data (focus)?)Maintenance Planning; Wartungsplanung The application focuses the transfer of infrastructure data from an asset management source system (e.g. DfA in Switzerland)10 bytes (133 words) - 16:12, 3 February 2020
- UC:IS:CADForRailwaySignaling (category UC reported by RailComplete) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:CADForRailwaySignaling in The railML® 3 wiki.10 bytes (127 words) - 16:12, 3 February 2020
- UC:IL:OperationAndControl (category UC without specified reporter) (section Which views are represented by the data (focus)?)from page UC:IL:OperationAndControl in The railML® 3 wiki.10 bytes (209 words) - 16:12, 3 February 2020
- UC:IS:NetworkStatement (category UC reported by SŽDC) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:NetworkStatement in The railML® 3 wiki.10 bytes (169 words) - 16:12, 3 February 2020