Document the tool chain Roadmap

[cecilebraun]

The tool chain needs an high level view of the goal to be achieved.

• Look at the document tool chain architecture as a starting point
• write the document
• launch the review

[cecilebraun]

First draft available here https://github.com/openETCS/toolchain/blob/master/T7.3/Roadmap/oetcs_roadmap.pdf
Will be continued with @srieger

[jastram]

Thanks for starting this! I just had a quick look at this. Here are my comments:

• I like that you organized the sections according to activities. The odd one out is 2.2.2 Papyrus, which is not an activity.
• Features should be quantifiable, i.e. we must know when we're done. For instance, we're done importing Subset-26 requirements, so why do you state "Partial"? Well, because we're not happy with the result yet. We should either make it more precise, or mark it as done and add a new Feature.
• Likewise, what does "requirement traceability" mean? We already have functioning requirement-requirement traceability, but not requirements-sysml or requirements-data dictionary traceability.
• Intuitively, I would expect a picture of the V-Diagram in this document (as this is a good way to pinpoint where the activities take place) and/or Cecile's Activity Diagram.
• How do you envision managing the priorities of features?

Thanks for your efforts - I believe that this will be a very important document.

[cecilebraun]

Thanks Michael for the remarks.
For the priorities I don't know yet. We will launch the discussion once the document is more complete.

[MariellePetitDoche]

IMHO, on figure 1 and §2.4, formal proof (as Frama-C or B-proof) and associated tools are missing.