UC:Use case example
| The name of the use case Subschema: Demoschema | |||
| |||
| For general information on use cases see UC:Use cases |
This page should be considered as an annex to the guides of the section use-cases (link to the railML® website). If inconsistencies are found, then guides of the section use-cases (link to the railML® website) have higher priority.
Use case / Anwendungsfall
This section should be used for a header or introduction. The headline is made with Template: UC title (type {{UC title}})
Description / Beschreibung
What is the application behind the use case? Which data in general is required? Which kind of tool/application provides this data? Who usually consumes it? Which data is not included (if not obvious)? Define the boundaries of the use case and the relevant data.
Data Flows and Interfaces / Datenflüsse und Schnittstellen
Which data flows exist? How often is data exchanged? What is the granularity? How does it change over time, if it does at all? Diagrams/images would be helpful to visualize the dataflow.
Dependent railML® domains / Abhängige railML®-Domänen
Please describe what domains of railML the use case is dependent upon if any, e.g. infrastructure, timetable, rolling stock, interlocking. Please also clarify if this dependency is essential for the use case or considered optional.
Characterizing Data / Charakterisierung der Daten
Please describe what data is exchanged for the use case. What is part and what is not part of the data exchange. What level of detail is usually included. On what does this level of detail depend. This description is usually the starting point for the next level of determining a more formalized and detailed table of the domain elements necessary for the use case. This description may also reference other existing use cases.
Sub-use cases / Teil - Usecases
Are there any partial use cases distinguished, which build on each other?