UC:Use cases: Difference between revisions
[checked revision] | [checked revision] |
(→List) |
|||
(20 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{navi}} | {{navi}} | ||
{{head|Use cases}} | |||
In this page you learn what is a '''use case''' | 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. | 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?== | ==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. | <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. | ||
Line 12: | Line 13: | ||
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. | 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|View/edit list on the separate source page]]. | |||
{{:UC:Use cases/table}} | |||
===How to interpret the status=== | |||
<div style="writing-mode: tb-rl;"></div> | |||
{|class="wikitable" | |||
!rowspan=2| !!Status!!Description!!colspan=5|participation | |||
|- | |||
! !! !!<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== | ==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== | ==References== | ||
<div id="*">[[#t*|*]] http://www. | <div id="*">[[#t*|*]] {{external|http://www.engr.sjsu.edu/fayad/current.courses/cmpe202-Fall2009/docs/lecture2/CmpE202-Use-Cases-3.pdf}}</div> |
Revision as of 16:33, 15 March 2019
| ||||||||
|
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 Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases – Category:Use cases by company
List
View/edit list on the separate source page.
|
- REDIRECT Template:UC:Use cases/table
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 currant 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.