Talk:UC:IL:UseCases: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
(→‎Prioritization and Communication of IL uses cases: Sugesstion for expanding the table)
(Decision of IL conference call added)
Line 42: Line 42:
* [[tbd- IL:UC:SitePreparationDataForSignalControlledWarningSystems |Site preparation data for Signal Controlled Warning Systems (SCWS); {{Deu|Daten zur Standortvorbereitung für Rottenwarnsysteme}}]]
* [[tbd- IL:UC:SitePreparationDataForSignalControlledWarningSystems |Site preparation data for Signal Controlled Warning Systems (SCWS); {{Deu|Daten zur Standortvorbereitung für Rottenwarnsysteme}}]]
--[[User:Alain Jeanmaire|Alain Jeanmaire]] ([[User talk:Alain Jeanmaire|talk]]) 12:57, 29 August 2016 (CEST)
--[[User:Alain Jeanmaire|Alain Jeanmaire]] ([[User talk:Alain Jeanmaire|talk]]) 12:57, 29 August 2016 (CEST)
: I suggest to add a column with the reporter of the use case (EULYNX, Jernbaneverket, ...) and a column with the status of the use case (draft, discussed, consolidated, implemented, revised, ...).
: I suggest to add a column with the reporter of the use case (EULYNX, Jernbaneverket, ...) and a column with the status of the use case (draft, discussed, consolidated, implemented, revised, ...). --[[User:Vasco Paul Kolmorgen|Vasco Paul Kolmorgen]] ([[User talk:Vasco Paul Kolmorgen|talk]]) 21:37, 29 August 2016 (CEST)
: --[[User:Vasco Paul Kolmorgen|Vasco Paul Kolmorgen]] ([[User talk:Vasco Paul Kolmorgen|talk]]) 21:37, 29 August 2016 (CEST)
:: Agreed during the [https://www.railml.org/en/event-reader/railml-interlocking-status-telco-2016-09-06.html IL developers conference call] that this table shall be extended with an abbreviation column and used from now for priorisation and status follow up. --[[User:Coordination|Coordination]] ([[User talk:Coordination|talk]]) 15:12, 6 September 2016 (CEST)

Revision as of 15:12, 6 September 2016

Prioritization and Communication of IL uses cases

I propose to edit the use cases sorted as validated priorities That is (to be discussed and approbed before publishing): (below a trial as chart, and further below the original text version enriched

Priority Description (EN) Description (DE) Description (FR) Status
1 Data prepration for interlocking Datenbereitstellung für Stellwerkssysteme [[IL:UC:EulynxDataPreparationInterlocking|]] ongoing
2 Interlocking engineering for signalling Stellwerkstechnik für Signalisierung [[IL:UC:InterlockEngineeringForSignallingWithinJBV|]] tbc
3 Interlocking engineering Stellwerksprojektierung [[IL:UC:InterlockingEngineering|]] tbc
4 Example Example Example Example
5 Example Example Example Example
6 Example Example Example Example
tbd Example Example Example Example
tbd Example Example Example Example
tbd Example Example Example Example
tbd Example Example Example Example

I propose to edit the use cases sorted as validated priorities

That is (to be discussed and approbed before publishing):

The following list provides links to the use cases related with interlocking:

--Alain Jeanmaire (talk) 12:57, 29 August 2016 (CEST)

I suggest to add a column with the reporter of the use case (EULYNX, Jernbaneverket, ...) and a column with the status of the use case (draft, discussed, consolidated, implemented, revised, ...). --Vasco Paul Kolmorgen (talk) 21:37, 29 August 2016 (CEST)
Agreed during the IL developers conference call that this table shall be extended with an abbreviation column and used from now for priorisation and status follow up. --Coordination (talk) 15:12, 6 September 2016 (CEST)