Demo Script (final Itea Review)

[jastram]

We need to elaborate on the demo script, as decided at the Munich Workshop. Please provide your comments below, and updated the script directly here in the description.

• Launch the tool
• Show Subset-26: Appearance, automatically created links and metadata, etc. (Work from Moritz)
  • Show Chapter 3
• Show the System Model (created with Scade System, opens with Papyrus)
  • openETCS_EVC | ETCS_OBU | F2_ETCS_Kernel
  • Double clicking F2_ETCS_Kernel will open 13 sub-diagrams, here you might want to either continue with
  • ETCS_Kernel F2.1 | F2.1 Manage_TracksideInformation_Integration
  • or:
  • ETCS_Kernel F2.8 | F2.8 ProvidePositionReport
• SKIPPED: Show enriched Traceability (ReqCycle)
• Video: Show Fault Tree with Safety Framework
  • TODO Soundtrack for Video
• Conclude: Go back to slides, show download slide

[morido]

Show Subset-26: Appearance, automatically created links and metadata, etc. (Work from Moritz)

Do you want me to provide an update to those files which make them pass ProR's new ReqIF-validator? Or are you ok with the status quo?

[janWelte]

Dear Moritz,

If you have new files, which could be used and just plugged it would be great to use them.

Do you already have the files?

Vest regards

Jan

-----Ursprüngliche Nachricht-----
Von: Moritz Dorka [mailto:notifications@github.com]
Gesendet: Mittwoch, 2. Dezember 2015 23:10
An: openETCS/toolchain toolchain@noreply.github.com
Cc: Jan Welte j.Welte@tu-bs.de
Betreff: Re: [toolchain] Demo Script (final Itea Review) (#512)

Show Subset-26: Appearance, automatically created links and metadata, etc. (Work from Moritz)

Do you want me to provide an update to those files which make them pass ProR's new ReqIF-validator? Or are you ok with the status quo?

—
Reply to this email directly or view it on GitHub #512 (comment) . https://github.com/notifications/beacon/ACmA384YyC1NwklVwfsnmaPO7Y95UWbzks5pL2PIgaJpZM4Gs8Ii.gif

[morido]

@janWelte I don't have the files, yet. But I have the tool to generate them :)
So its just a matter of running the tool and uploading its output into my repo. I'll do it on the weekend and then get back to you, ok?

[janWelte]

That's great. Thanks a lot.

-----Ursprüngliche Nachricht-----
Von: Moritz Dorka [mailto:notifications@github.com]
Gesendet: Donnerstag, 3. Dezember 2015 12:50
An: openETCS/toolchain toolchain@noreply.github.com
Cc: Jan Welte j.Welte@tu-bs.de
Betreff: Re: [toolchain] Demo Script (final Itea Review) (#512)

@janWelte https://github.com/janWelte I don't have the files, yet. But I have the tool to generate them :)
So its just a matter of running the tool and uploading its output into my repo. I'll do it on the weekend and then get back to you, ok?

—
Reply to this email directly or view it on GitHub #512 (comment) . https://github.com/notifications/beacon/ACmA3-Y1MGMbBQNLKPvbfAJbieMQGKZNks5pMCPPgaJpZM4Gs8Ii.gif

[jastram]

@morido - that would be great. We're also fixing the problem with the images: One reason why Moritz wrote invalid links was that our HTML-Renderer did not process them correctly.

@iweigelt - can you please make sure that we fix RMF in time for this?

[morido]

can you please make sure that we fix RMF in time for this?

This does not seem to be done yet. Hence, it does not make sense to provide any new ReqIFs either. If you internally need files for testing, please get back to me. Otherwise, I will wait for the bugfix in ProR.

[iweigelt]

Hello Moritz,

i am already working on the fix. Can you provide me with the new files for testing, please.

Best,
Ingo

[morido]

Here is a version of chapter2 that passes the validator (except for two points regarding ProR's internals - perhaps somebody can give me a hint regarding those).
However, when displaying contents of the file ProR cannot find the linked PNGs.

chapter2.zip

[FrederiqueVallee]

Hello Michael,

We have been able to import the SysML model, to perform a safety analysis on it and to have some results.

For the review, I’ll be able to make a demo (on my machine) that shows :

1.   The papyrus model implemented into ESF,
   

2.   The way the safety analysis is performed,
   

3.   The fault tree that is generated,
   

4.   The test that is built from the fault tree and that demonstrates a safety weakness of the model (still under study because the SCADE model is constantly evolving - to be confirmed)
   

You could then execute (on your machine - I don’t have a SCADE license) the SCADE test on the SCADE model to show the results

Is it OK for you ?

cid:image001.png@01CEF00E.E223F9E0

Frédérique VALLEE
Directeur Général Adjoint

Fixe : +33 (0)1 78 85 81 43

Mobile : +33 (0)6 81 68 92 92

---

Immeuble Odyssée - Bât E - 2-12 rue du Chemin des Femmes - 91300 MASSY
http://www.all4tec.net/ www.all4tec.net

De : Michael Jastram [mailto:notifications@github.com]
Envoyé : mercredi 2 décembre 2015 09:22
À : openETCS/toolchain
Cc : FrederiqueVallee
Objet : [toolchain] Demo Script (final Itea Review) (#512)

We need to elaborate on the demo script, as decided at the Munich Workshop. Please provide your comments below, and updated the script directly here in the description.

• Launch the tool
• Show Subset-26: Appearance, automatically created links and metadata, etc. (Work from Moritz)
• TODO @janWelte https://github.com/janWelte : Which .reqif file to show?
• Show the System Model (created with Scade System, opens with Papyrus)
• TODO @janWelte https://github.com/janWelte : Which Model to open? Show enriched Traceability (ReqCycle)
• TODO @raphaelfaudou https://github.com/raphaelfaudou : Which steps to perform?
• Optional: Show Fault Tree with Safety Framework
• TODO @FrederiqueVallee https://github.com/FrederiqueVallee : Which steps to perform?
• Conclude: Go back to slides, show download slide

—
Reply to this email directly or view it on GitHub #512 .Image supprimée par l'expéditeur.

---

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[jastram]

Hi Frederique,

Is it OK for you ?

There are three problems with this: First, I don't have Scade on my machine either; second, I thought we decided against machine switching, due to the time constraints; and last, this sounds really extensive, considering how little time we have.

I would suggest the following: If you provide me with step by step instructions, I can show this as part of my demo. Alternatively, maybe it makes more sense to show this as part of WP4 - @MarcBehrens - what do you think?

[FrederiqueVallee]

Hello Michael,

Considering the time we have I think that it is not easy to show all the needed steps in a « pure demo » (switch needed between Scade system/ESF/Scade suite -> too long). What do you think if I prepare a video of less than 5 mn that you could launch on your PC?

Best regards,

Frédérique

De : Michael Jastram [mailto:notifications@github.com]
Envoyé : lundi 7 décembre 2015 21:15
À : openETCS/toolchain
Cc : FrederiqueVallee
Objet : Re: [toolchain] Demo Script (final Itea Review) (#512)

Hi Frederique,

Is it OK for you ?

There are three problems with this: First, I don't have Scade on my machine either; second, I thought we decided against machine switching, due to the time constraints; and last, this sounds really extensive, considering how little time we have.

I would suggest the following: If you provide me with step by step instructions, I can show this as part of my demo. Alternatively, maybe it makes more sense to show this as part of WP4 - @MarcBehrens https://github.com/MarcBehrens - what do you think?

—
Reply to this email directly or view it on GitHub #512 (comment) .Image supprimée par l'expéditeur.

---

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[jastram]

What do you think if I prepare a video of less than 5 mn that you could launch on your PC?

I think this is a great idea!

[janWelte]

Dear everyone,

the problem is that at the moment no file and model are set up already to be shown. This has to be done.

To do so the best case is using Chapter 3 and implementing the results for one modul block e.g. train positioning. Seconf option would be Level and Mode.

[FrederiqueVallee]

Dear Jan,

We have performed the safety analysis in the block “ProvidePositionReport” (ErrorManager – BuildSinglePostReport) in the SysML model that seems to be fine !

By the way could you remind me the name of the report in which François has to describe this analysis ?

Of course he has some problems to compile the corresponding function in the SCADE model (in that case the last test proposed in our demo could not be run).

Best regards,

FRV

De : Jan Welte [mailto:notifications@github.com]
Envoyé : mardi 8 décembre 2015 11:03
À : openETCS/toolchain
Cc : FrederiqueVallee
Objet : Re: [toolchain] Demo Script (final Itea Review) (#512)

Dear everyone,

the problem is that at the moment no file and model are set up already to be shown. This has to be done.

To do so the best case is using Chapter 3 and implementing the results for one modul block e.g. train positioning. Seconf option would be Level and Mode.

—
Reply to this email directly or view it on GitHub #512 (comment) .Image supprimée par l'expéditeur.

---

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus