UC:Use cases: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(head)
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{navi}}
{{mirror}}
{{head|Use cases}}
 
In this page you learn what is a '''use case''' and find a list of {{rml}} use cases.
 
While the emphasis of the {{rml}}-wiki lies in documenting single elements in a bottom-up approach, we also try to help users to capture the concepts of {{rml}} via [[Dev:Examples|examples]] and use cases in a top down approach.
 
==What is a use case?==
<div id="t*"></div>A use case can be defined as ''a single task, performed by the end user of a system, that has some useful outcome''[[#*|*]]. It is described as a list of steps (actions or events) to achieve this outcome.
 
A use case in terms of {{rml}} is an application of data exchange between at least two IT systems in the railway domain, where {{rml}} can be used as a format and language for the data to be exchanged. The aim of the use case description is to formulate requirements on the technical implementation of the data exchange.
 
What distinguishes a use case from an example is, that examples will typically consist of pieces of {{rml}}-code, whereas use cases will typically be formulated in natural language or ''Unified Modelling Language'' (UML). Examples are solutions to use cases.
 
=={{rml}} Use Cases==
===By category===
[[:category:Use case (CO)|CO Use Cases]] – [[:category:Use case (IL)|IL Use Cases]] – [[:category:Use case (IS)|IS Use Cases]] – [[:category:Use case (RS)|RS Use Cases]] – [[:category:Use case (TT)|TT Use Cases]] – [[:Category:Use cases by company]]
===List===
[[UC:Use cases/table|Highlight list]].
{{:UC:Use cases/table}}
===How to interpret the status===
<div style="writing-mode: tb-rl;"></div>
{|class="wikitable"
!rowspan=2|&nbsp;!!Status!!Description!!colspan=5|participation
|-
!&nbsp;!!&nbsp;!!<div style="writing-mode: tb-rl;font-size:70%">{{rml}} community</div>!!<div style="writing-mode: tb-rl;font-size:70%">reporting party</div>!!<div style="writing-mode: tb-rl;font-size:70%">{{rml}} scheme coordinator</div>!!<div style="writing-mode: tb-rl;font-size:70%">{{rml}} governance board</div>!!<div style="writing-mode: tb-rl;font-size:70%">{{rml}} scheme development group</div>
|-
|rowspan=3|<div style="writing-mode: tb-rl;font-size:70%">'''pre development'''</div>||''planned''
|the use case is planned, but there is no draft available by now; usually there will be no article about this use case in the wiki; Sometimes some basic ideas will be published
|style="text-align:center;"|×
|
|
|
|
|-
|''draft''
|a user has submitted a draft. Usually there will exist an article about the use case where you find the draft
|
|style="text-align:center;"|☒
|
|
|
|-
|''consolidated''
|the draft has been reviewed and accepted by the scheme coordinator
|style="text-align:center;"|×
|style="text-align:center;"|×
|style="text-align:center;"|☒
|
|style="text-align:center;"|×
|-
|rowspan=3|<div style="writing-mode: tb-rl;font-size:70%">'''development phase'''</div>||''requirements''
|the '''development phase''' begins with an assessment, if and how the {{rml}} schema has to be refined as to depict the use case
|style="text-align:center;"|×
|
|style="text-align:center;"|☒
|
|style="text-align:center;"|×
|-
|''model''
|the requirements of this use case have been implemented into the currant {{rml}} schema
|
|
|style="text-align:center;"|☒
|
|style="text-align:center;"|×
|-
|''finished''
|the use case has been completely implemented, documented and released
|
|
|style="text-align:center;"|×
|style="text-align:center;"|☒
|
|-
|
|''postponed''
|if an unfinished use case is not being barried further for several months, it will be listed as postponed
|
|
|style="text-align:center;"|☒
|
|
|-
!colspan="8"|×=participates — ☒=is responsible
|}
 
==How to contribute a use case==
Generally speaking, contributions to {{rml}} and this wiki are appreciated. For contributing use cases, please follow our [[dev:Use cases|UC guideline]].
 
==References==
<div id="*">[[#t*|*]] {{external|http://www.engr.sjsu.edu/fayad/current.courses/cmpe202-Fall2009/docs/lecture2/CmpE202-Use-Cases-3.pdf}}</div>

Latest revision as of 15:31, 3 February 2020

🗒️ This page is mirrored from page UC:Use cases in The railML® 3 wiki.
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

Use cases
 

In this page you learn what is a use case and find a list of railML® use cases.

While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up approach, we also try to help users to capture the concepts of railML® via examples and use cases in a top down approach.

What is a use case?

A use case can be defined as a single task, performed by the end user of a system, that has some useful outcome*. It is described as a list of steps (actions or events) to achieve this outcome.

A use case in terms of railML® is an application of data exchange between at least two IT systems in the railway domain, where railML® can be used as a format and language for the data to be exchanged. The aim of the use case description is to formulate requirements on the technical implementation of the data exchange.

What distinguishes a use case from an example is, that examples will typically consist of pieces of railML®-code, whereas use cases will typically be formulated in natural language or Unified Modelling Language (UML). Examples are solutions to use cases.

railML® Use Cases

By category

CO Use CasesIL Use CasesIS Use CasesRS Use CasesTT Use Cases

List of active use cases

View/edit list on the separate source page

Directing Subschema
Involved Subschemas
Implemented in railML® version
(lowest)
Implemented in railML® version
(highest)
Priority
Description (EN) Description (DE)
Abbreviation
Reported by Status
how to interpret the status
Edited
IL IS 3.1 3.2 X Interlocking module engineering data
(former: Interlocking engineering)
Stellwerksprojektierung IMED writer: Thales Germany model March 13th 2023 by User:RailML Coord Documentation
IS 3.1 3.2 X Network statement of an infrastructure manager Schie­nen­netz­be­nut­zungs­be­din­gun­gen eines Infrastrukturbetreibers NEST writer: Správa železnic (former: SŽDC) / ProRail / Bane NOR model March 13th 2023 by User:RailML Coord Documentation
IS RS 3.1 3.2 X RINF Reporting RINF Meldung RINR writer: SNCF Réseau merged into NEST March 13th 2023 by User:RailML Coord Documentation
IL IS 3.1 3.2 X Routes for timetable simulation
(former: Capacity operational simulation)
Fahrstrassen für Fahrplan simulieren
(ehemals: Leistungsfähigkeit Simulation)
RSIM writer: Jernbanedirektoratet / Bane NOR
(former: Jernbanedirektoratet Capacity Dpt)
model December 07th 2023 by User:RailML Orga Ontology
IS IL 3.1 3.2 X Schematic Track Plan Schematische Gleisplandarstellung SCTP writer: Jernbanedirektoratet / Bane NOR model February 13th 2023 by User:RailML Orga Ontology
IS TT, IL 3.2 3.2 X Integrated TMS Integriertes Verkehrsmanagement ITMS writer: Bombardier Transportation model February 13th 2023 by User:RailML Orga Ontology
TT IL, IS, RS 3.2 3.2 X Traffic Management Plan writer: Thales Germany model June 27th 2022 by User:RailML Coord Documentation
IS IL 3.2 3.2 X ETCS track net ETCS Streckenatlas ETCS writer: Thales Germany model June 12th 2023 by User:RailML Coord Infrastructure ETCS Streckenatlas
ETCS track net: Input for Detailed Design of ETCS Trackside ETCS Streckenatlas: Übergabe der allgemeingültigen Streckendateninformationen (vom Netzbetreiber an den Lieferanten) ETCS-a writer: Thales Germany model June 12th 2023 by User:RailML Coord Infrastructure |ETCS Streckenatlas
ETCS track net: Output of Detailed Design of ETCS Trackside ETCS Streckenatlas: Übergabe der Ergebnisdaten der Projektierung (vom Lieferanten an den Netzbetreiber) ETCS-b writer: Thales Germany model June 12th 2023 by User:RailML Coord Infrastructure
ETCS track net: Alignment on Topology and Properties of Trackside Equipment Before ETCS Balise Placement ETCS Streckenatlas: Aktualisierung der Streckendaten vor Balisengruppenplatzierung ETCS-c writer: Thales Germany model June 12th 2023 by User:RailML Coord Infrastructure
TT IS, RS 3.2 3.2 X Passenger information at stations Fahrgastinformation am Bahnhof writer: PSI Transcom (20. 05. 15);
reviewer: init
model March 13th 2023 by User:RailML Coord Documentation
TT IS, RS, IL 3.3 1 Run Time Calculation Input Data Eingangsdaten für die Fahrzeitrechnung RTCI writer: Jernbanedirektoratet / Bane NOR consolidated March 25th 2024 by User:RailML Coord Timetable
Run Time Calculation Input Data – Infrastructure properties Eingangsdaten für die Fahrzeitrechnung - Infrastruktur Eigenschaften RTCI-a writer: Jernbanedirektoratet draft
Run Time Calculation Input Data – Rolling stock properties Eingangsdaten für die Fahrzeitrechnung - Fahrzeug Eigenschaften RTCI-b writer: Jernbanedirektoratet draft
Run Time Calculation Input Data – Timetable properties Eingangsdaten für die Fahrzeitrechnung - Fahrplan Eigenschaften RTCI-c writer: Jernbanedirektoratet draft
TT IS, RS 3.3 1 Long Term Circulation Planning Langfristige Umlaufplanung LTCP reporter: IVU
writer & reviewer: TT developer group
draft December 04th 2023 by User:RailML Coord Documentation
TT IS, RS A timetable for a competition (call for proposals) Ausschreibungsfahrplan writer: iRFP (21. 05. 15);
reviewer: IVU Traffic Technologies (22. 09. 16)
consolidated March 13th 2023 by User:RailML Coord Documentation
TT IS, RS, CO Adopt vehicle working scheduling to timetable changes Umlauf an Jahresfahrplan anpassen writer: IVU Traffic Technologies (21. 05. 15);
reviewer: HaCon Ingenieurgesellschaft
consolidated June 27th 2022 by User:RailML Coord Documentation
TT RS, IS Duty planning and staff shifts Dienstplanung und Personalschichten SHFT writer: ÖBB Personenverkehr;
reviewer: init
consolidated July 18th 2022 by User:RailML Coord Documentation
TT IS, RS Exchange of formation data Austausch von Wagenreihungen/ Behängungsdaten writer: iRFP (21. 05. 15);
reviewer: IVU Traffic Technologies (22. 09. 16)
consolidated March 13th 2023 by User:RailML Coord Documentation
TT IS, IL, RS Long Term Strategic Timetabling Langfrist-Fahrplanerstellung LTST writer: SMA+Partner (22. 12. 16);
reviewer: HaCon Ingenieurgesellschaft (28. 6. 22)
consolidated July 18th 2022 by User:RailML Coord Timetable
TT IS, RS Timetable Information Fahrplanauskunft TINF writer: HaCon Ingenieurgesellschaft (13. 03. 15);
reviewer: IVU Traffic Technologies
consolidated, under revision March 13th 2023 by User:RailML Coord Documentation
IS 2 Track Geometry Gleisgeometrie TRGE writer: ÖBB Infrastruktur review June 27th 2022 by User:RailML Coord Documentation
IS TT, IL, RS 3 Asset status representation Darstellung des Infrastrukturzustands ASSR writer: DLR for IN2Rail project draft September 27th 2023 by User:RailML Orga Ontology
IS IL CAD for railway signaling CAD für Zugsignalisierung CASP writer: Railcomplete AS draft December 07th 2023 by User:RailML Orga Ontology
IS IL, TT, RS 3 Capacity Planning Kapazitätsplanung CAPL writer: Bane NOR (erstwhile: JBV) draft March 13th 2023 by User:RailML Coord Documentation
IS IL 3 Capture schematic visualisation information of track assets Erstellung schematischer Visualisierungs-Informationen von Schienenanlagen draft March 13th 2023 by User:RailML Coord Documentation
IS TT, RS 2 Driver Advisory System (DAS) Fahrerassistenzsystem DASY writer: Siemens Mobility Germany? draft March 13th 2023 by User:RailML Coord Documentation
IS IL, RS, TT Exchange of Logical Train Positions writer: Siemens Mobility Switzerland;
reviewer: ???
draft July 18th 2022 by User:RailML Coord Documentation
IS IL 3 Exchange of planning parameters for interlocking with suppliers Austausch von Planungsparametern für Stellwerke mit Her­stel­lern ISIL writer: IS draft March 13th 2023 by User:RailML Coord Documentation
IL IS, TT 4 Interlocking engineering for signalling Stellwerkstechnik für Signalisierung writer: Bane NOR (former: Jernbaneverket Signalling Dpt) draft March 13th 2023 by User:RailML Coord Documentation
IS RS 3 Maintenance Planning Wartungsplanung MAPL draft March 13th 2023 by User:RailML Coord Documentation
IS 3 NRE Reporting NRE Meldung NRER writer: ÖBB Infrastruktur draft March 13th 2023 by User:RailML Coord Documentation
IL IS 4 Operation and Control Betriebsführung draft March 13th 2023 by User:RailML Coord Documentation
RS IS, TT, IL Operational simulation Betriebssimulation draft March 13th 2023 by User:RailML Coord Documentation
TT IS, IL, RS Passenger information inside the train Fahrgastinformation im Zug writer: Interautomation (17. 01. 17);
reviewer: PSI Transcom and iRFP
draft June 27th 2022 by User:RailML Coord Documentation
IS RS, TT 2 Passenger Information System Fahrgast-Informationssystem PISY draft March 13th 2023 by User:RailML Coord Documentation
IS ? Posession Management Daten für Betra und Gleissperrungen POMA writer: Siemens Mobility Germany (10. 01. 22);
reviewer: HaCon Ingenieurgesellschaft
draft July 18th 2022 by User:RailML Coord Documentation
IS 3 Positioning and Map-Matching Positionierung und Kartenvergleich POSI draft March 13th 2023 by User:RailML Coord Documentation
IS 2 Railway Infrastructure Recording Erfassung der Schieneninfrastruktur ISRC writer: Bahnkonzept draft March 13th 2023 by User:RailML Coord Documentation
IS IL 3 Railway Simulation Laboratory Eisenbahnbetriebslabor RLAB writer: Czech Technical University Prague draft June 27th 2022 by User:RailML Coord Documentation
TT IS, RS Slot ordering Trassenbestellung writer: SMA+Partner (17. 09. 16);
reviewer: iRFP
draft March 13th 2023 by User:RailML Coord Documentation
IS 3 Speed directory Verzeichnis der zulässigen Geschwindigkeiten SPED writer: Bombardier Transportation draft March 13th 2023 by User:RailML Coord Documentation
TT IS TAF/TAP TSI requirements TAF/TAP TSI Anforderungen writer: ERA;
reviewer: Bahnkonzept
draft December 07th 2023 by User:RailML Coord Timetable
IS IL, TT, RS 3 Timetabling Fahrplanerstellung ISTT writer: ProRail draft March 13th 2023 by User:RailML Coord Documentation
IL IS Hardware and cable plan Aussenanlage und Kabelplan draft March 13th 2023 by User:RailML Coord Documentation
RS IS, TT Traction power supply simulation Simulation der Bahnstromversorgung draft March 13th 2023 by User:RailML Coord Documentation
IS Rail Inspection Data Schienenprüfdaten RIND reporter:DZSF & ZEDAS
writer:DZSF
draft December 04th 2023 by User:RailML Coord Documentation

 

List of inactive use cases

If you want to reactivate your inactive use case, write a post on the forum. For more information about use cases you can also follow our UC guideline.

Directing Subschema
Involved Subschemas
Implemented in railML® version
(lowest)
Implemented in railML® version
(highest)
Priority
Description (EN) Description (DE)
Abbreviation
Reported by Status
how to interpret the status
Reason
Why is this UC on hold?
TT ? Automatic Route Setting (ARS)
Automatic Train Supervision (ATS)
Zuglenkung writer: Toshiba Corporation?;
reviewer: PSI Transcom
postponed Currently no demand
IL ? 7 Data prepration for signalling Datenbereitstellung für Stellwerkssysteme DPRS writer: EULYNX postponed EULYNX withdrew from development
TT ? Operational simulation timetable Betriebssimulation Fahrplan writer: Open Track Railway Technology?;
reviewer: SMA+Partner
postponed Currently no demand
IS 9 Railway Infrastructure Visualisation Visualisierung von Schieneninfrastruktur ISVI postponed Only outdated version available
IL IS 5 Site preparation data for Signal Controlled Warning Systems Daten zur Standortvorbereitung für Rottenwarnsysteme SCWS writer: Thales Austria postponed Currently no demand

How to interpret the status

  Status Description participation
   
railML® community
reporting party
railML® scheme coordinator
railML® governance board
railML® scheme development group
pre development
planned the use case is planned, but there is no draft available by now; usually there will be no article about this use case in the wiki; Sometimes some basic ideas will be published ×
draft a user has submitted a draft. Usually there will exist an article about the use case where you find the draft
consolidated the draft has been reviewed and accepted by the scheme coordinator × × ×
development phase
requirements the development phase begins with an assessment, if and how the railML® schema has to be refined as to depict the use case × ×
model the requirements of this use case have been implemented into the current railML® schema ×
finished the use case has been completely implemented, documented and released ×
postponed if an unfinished use case is not being barried further for several months, it will be listed as postponed
×=participates — ☒=is responsible

How to contribute a use case

Generally speaking, contributions to railML® and this wiki are appreciated. For contributing use cases, please follow our UC guideline.

References