Grooming of Manage Levels And Modes : Analysis

[MariellePetitDoche]

For the analysis and design of this item the following tasks are planned:

• [ ] Document Analysis Results
• [ ] Create SysML architectural model
• [ ] Document links between SysML model and SRS (ProR-Tool)
• [ ] Definition of Input Ports (Data Dictionary)
• [ ] Definition of Output Ports (Data Dictionary)
• [ ] Definition of internal types and data
• [ ] Document links between SRS data types
• [ ] Transfer model to Scade
• [ ] Transfer model to B
• [ ] Review

[BaseliyosJacob]

Dear Marielle,

we are working at the moment on the same workscope. @BerndHekele has the status of the work. Would be great if you can align with him.

Furthermore i am working at the moment on the table § 4.8.3 and § 4.8.4. We should avoid double work.

Furthermore we are working at the moment on

• [ ] Document Analysis Results
• [ ] Create SysML architectural model
• [ ] Definition of Input Ports (Data Dictionary)
• [ ] Definition of Output Ports (Data Dictionary)

Please avoid double work.

[MariellePetitDoche]

Baseliyos,

it is dammage, I clearly said we are going to work on this subject at Bruxels to avoid double work, and we have already put a SysML model on github. Before to start, I spent a lot of time to check github documents and issues and I did no see any reference or issue on your work.

[mahlmann]

Dear @MariellePetitDoche , dear @BaseliyosJacob ,

I am not sure if this is really double work -- only if @BaseliyosJacob is going to provide a SysML model in the end.

Moreover, note that §4.8.3 and §4.8.4 is part of the function Select Useable Info, which is assigned to me currently ( #19 #24 ). However, since the first iteration of work does not deal with level and mode changes the functionality of Select Useable Info is very limited for the moment.

[BaseliyosJacob]

Dear Marielle, i just checked your model and it seems to be complementary to our work since i am working on a high level breakdown: See screenshot

We should merge your work to our work process to avoid double work. Furthermore i have started with a descripttion to Manage levels and mode. Should i send it you?

@mahlmann i just started to announce packages and messages to the table §4.8.3 and §4.8.4. Do you see a conflict? Is there any double work. If not you can just merge it.

[mahlmann]

@BaseliyosJacob I am not sure what is meant by announcing packages to tables. If this is about identifying the radio messages and balise telegrams which are relevant for the types of messages described in the tables, then note that @VNuhaan has done quite some work on that. He created an excel document to capture the connection of the message types and actual messages. To the best of my knowledge this document is not on github so far.

However, this is getting of topic and I don't wan't to hijack @MariellePetitDoche 's original issue.

[MariellePetitDoche]

@BaseliyosJacob: "Furthermore i have started with a descripttion to Manage levels and mode. Should i send it you?" Yes It can be useful.

I agree Peter : §4.8.3 and §4.8.4 concern "Select Useable Info" And I do not take care on them. I am only concrens by the requirements which allow to compute levels and modes i.e:

• §4.4 (mainly definitions, but some requirements are linked to §4.5 and 4.8),
• §4.6 entirely
• §5.4 to §5.13
• §5.19

In my mind the other sections of §4 and 5 do not concern management of modes and levels but other function (mangament of DMI, balises informations,...)

It will be nice to allocate to the architecture the relevant § of SRS.