UC:Use case example

The name of the use case Subschema: Demoschema

(version(s) Demoversion)

For general information on use cases see UC:Use cases

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

This article shows and explains the structure of a good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases.

Please, describe the use case here. The headline is made with Template: UC description (type {{UC description}})

Data Flows and Interfaces / Datenflüsse und Schnittstellen

In this section the data flows should be drafted. The headline is made with Template: UC flows (type {{UC flows}})

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

Which data interferences are there? The headline is made with Template: UC interference (type {{UC interference}})

Characterizing Data / Charakterisierung der Daten

How can the data be characterized? Explain this in the following subsections. The headline is made with Template: UC data (type {{UC data}})

How often do the data change (update)?

How often are the data updated? Does this happen routinely? The headline is made with Template: UC update (type {{UC update}})

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

How complex is the exchanged data? The headline is made with Template: UC complexity (type {{UC complexity}})

Which views are represented by the data (focus)?

What is the focus of the data? How can the whole picture be described? The headline is made with Template: UC focus (type {{UC focus}})

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

Please list all elements that are part of the data in this use case. The headline is made with Template: UC elements (type {{UC elements}})