-
Notifications
You must be signed in to change notification settings - Fork 20
Secondary tools for data, function and requirement management
This page concerns activities of WP7 T7.2 and is dedicated to the evaluation of tools for data, function and requirement management activities.
Planning is available on the main page.
- Capturing and editing of textual requirements (both plain text and rich text)
- Annotating requirements with arbitrary typed attributes
- Traceability between and within requirements and model elements (both formal and informal), as well as other elements (e.g. external documents)
- Change Management
- Traceability Analysis
The following table contents the proposed means and tools to evaluate for this benchmark :
| Contact | Formalism / Tool | Link with primary means or tools | Data management | Requirement management | Function management | Repository management | Functionnal architecture |
|---|---|---|---|---|---|---|---|
| Uwe Steinke (SIEMENS) | SCADE Suite | SCADE | ? | X | ? | ? | ? |
| Matthias Güdemann (Systerel) | Rodin + plugins (ProR, ProB, SMT solvers, IUML,...) | Event B | X | X | X | ? | ? |
| Jan Welte (TU-BS) | Goal Structuring Notation (GSN) | Assurance Case Editor (ACEdit) | ? | X | ? | ? | ? |
| Alexandre Ginisty (All4tec) | MaTeLo (Model Based Testing tool based on Markov Chains) | UML/SysML (Papyrus) | ? | X | ? | ? | ? |
| Michael Jastram (Formal Mind) | Eclipse ProR | any EMF based: Papyrus, Event-B, ERTMSFormalSpecs, EA-Bridge exists | ? | X | ? | ? | ? |
| Jonas Helming (EclipseSource) | Eclipse EMFStore | Model Repository for versioning EMF model instances | ? | X | ? | ? | ? |
| Jonas Helming (EclipseSource) | Eclipse EMF Client Platform | UI Toolkit for tools based on EMF model instances | ? | X | ? | ? | ? |
Who is volunteer to propose means and tools to evaluate ?
TODO
Some of the proposed tools have already been evaluated in the context of the primary tool chain. To reduce the effort of the benchmarking activities, those tools can use SUBSET-026-3, ISSUE : 3.3.0, 3.5 Management of Radio Communication.
Tools that are being evaluated for the first time in this context will use a different case study (see below). This will make the benchmark more meaningful and increase the potential for reuse.
Using two different case studies is less than optimal, but we think that this is a good balance between effort spent and result gained.
Marc Behrens suggested:
The classic challenge for the version management and requirements system is
§ 6 (Management of older Version Systems - several subfunctions initiated inside other functions beside management of version (BL2/ BL3))
If you want to start with a requirements management tool-evaluation I would propose to start building up a version/ configuration management system based on the chapter enabling e.g. a BL3 Train to understand BL2 tracks. This can be later integrated into the results of the other streams and be a benefit to them.
An entity relationship diagram is on-going work for SSRS activities, and will start with the following section of Subset-026:
- § 4.5.2.1 (Functions within Table to start with)
- § 5.1 to 5.19 (Processes excluding 5.6, 5.9 5.19)
- § 6 (Management of older Version Systems - several subfunctions initiated inside other functions beside management of version (BL2/ BL3))
- § 7 & 8 (Work on CH7 is already done By Siemens)
The evaluation can follow the same plan.
This activity can jump at a high priority level due to the urgency of SSRS activities. See (https://github.com/openETCS/model-evaluation/wiki/Secondary-Tools-Analyses) and (https://github.com/openETCS/model-evaluation/wiki/Benchmark-of-means-and-tools-for-SSRS-activities)
Other ideas ?
An open repository to store the models is available: management means and tools.