34 lines
1.6 KiB
Markdown
34 lines
1.6 KiB
Markdown
# 2020-12-21-Felicien-meeting
|
|
#people/felicien #meeting
|
|
|
|
Felicien presented an approach based on CHESSIoT to develop #IOT system.
|
|
|
|
It seems that the novelty is that it permits to model different concerns including hardware, communication, and software.
|
|
|
|
The code generation aspect is important but it should not be presented as the main novelty.
|
|
|
|
We need to stress why it is important to have a unique model (ChessIoT) which is then transformed to different models including ThingML specifications (see the figure below presented during the meeting ![[Pasted image 20201221151511.png]]
|
|
|
|
|
|
My main concerns are related to the following aspects:
|
|
|
|
*Concerning Hardware design metamodel*
|
|
- What are the related work?
|
|
- What's the novelty with respect to them?
|
|
|
|
*Concerning the software design metamodel*
|
|
- You need to stress what's new here
|
|
- [ThingML](https://github.com/TelluIoT/ThingML) seems to be very powerful
|
|
|
|
*Concerning the communication metamodel*
|
|
- What's the final usage here?
|
|
- Just to select the communication protocol at the software/hardware level, and then?
|
|
|
|
|
|
**The key here in my opinion is that you have different views linked together, thus e.g., you can link hardware components from the software view and vice-versa. Many analysis are disclosed. You should investigate this (e.g., dependability analysis, ...).**
|
|
|
|
|
|
*Concerning the tool demo*
|
|
- It is not clear what are the modeling components already available in Chess from those developed by you.
|
|
- Not all the elements are in the same location right?
|
|
- I see IoTGateway in one of your metamodel connected with the PhysicalEntity. They might be in different locations, isn't? |