Auto saved by Logseq

2025-06-02 17:15:13 +02:00
commit d9ea3d552d
6279 changed files with 711145 additions and 0 deletions
@@ -0,0 +1,15 @@
+#people/apurv #meeting
+
+Bisogna definire un framework concettuale per poter confrontare ed analizzare diverse #LCDP rispetto agli aspetti di workflow. Si e' quindi deciso di basare l'analisi considerando #BPMN e quindi rappresentare la BPMN-compliance delle varie piattaforme.
+
+
+L'idea e' ispirarsi a questo TSE paper:
+
+> [Bendraou. 2010. *A Comparison of Six UML-Based Languages for Software Process Modeling*](zotero://open-pdf/library/items/1_F4SIPPPV)
+
+
+
+
+Notion link: https://www.notion.so/LOWCOMOTE-e0a7af4d5d404b199109d62d5b6b3a27
+
+Parer in preparation https://www.overleaf.com/project/5fc09b98065e3c5aa6350497 #papersubmission #sourcecode
@@ -0,0 +1,34 @@
+# 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?
@@ -0,0 +1,27 @@
+#meeting
+
+---
+
+# **Call with Philip Langer Damiano Alfonso and Juri**
+Date: 2021-01-15
+Time: 16:28
+Attendend:  #attendance/online
+Project: #mdegroup
+People attended:  #people/alfonso #people/juri #people/damiano #externalpeople/phliplanger  
+
+---
+## Damiano presented some capabilities of the tool he is developing
+**Some notes below**
+
+** [Sprotty](https://github.com/eclipse/sprotty) is just to link metaclasses with SVG **
+So this means that if you want restrict the behaviour of the editor, you need to develop this. Sprotty does not have first class elements for doing this.
+
+** Co-evolution capabilities of the tool**
+Currently basic cases are supported to automatically evolve models according to operated metamodel changes.
+
+** Styling elements and add constraints to graphical elements **
+- There is a bidirectional relationship between the graphical position of the element and  model attributes.
+- It is possible to define rules involving different graphical elements.
+  ![[Pasted image 20210115164633.png]]
+- Philip suggested to apply the language to implement sequence diagram or even an editor for [Ladder](https://it.wikipedia.org/wiki/Ladder_diagram).
+- The opinion of Philippe is that connecting the editor with [GLSP (eclipse.org)](https://www.eclipse.org/glsp/) would not bring any benefit. It is instead important to link it with the [Model Server API](https://github.com/eclipse-emfcloud/emfcloud-modelserver)  and with the EMF ecosystem.
@@ -0,0 +1,31 @@
+# 2021-01-18-1035-Juri-Paper-MSR-with-Wimmer
+---
+tags:
+	- '#meetings'
+	  ---
+- # [[2021-01-18-1035-Juri-Paper-MSR-with-Wimmer]]
+  
+  **Date**: 2021-01-18
+  **Time**: 10:35
+  **Attendend**:  #attendance/online
+  **Project**: #PAPERS/msr11-dataset
+  **People attended**:  #people/juri 
+  _Celano: 🌫  -3°C_
+  
+  ---
+  Quick chat about the [[paper]] available o Overleaf [MSR2021 - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/5fec90e7f829ed1f031f7af8)
+  
+  ! [[file:///Pasted image 20210118103615.png]]
+	-
+	- Creare un dataset di JSON schema.
+	- {{embed [[HOME]]}}
+- 60.000 Json schema
+- visto i duplicati per identificarli e rimuoverlo. Ci sono circa 40.000 duplicati
+- I Json schema sono conformi a diversi draft di specifica (draft3, draft4, etc.)
+- Identificati errori
+	- Errori Parsing
+	- Errori di conformance rispetto allo schema
+	- *E' stato sviluppato un tool per fare questo: wrapper a 2 tool diversi (1 tool copre tre draft)*
+- Per quanto riguarda le statistiche
+	- Estrazioni di unigram per clustering (Juri sta lavorando su questo)
+	- Luca sta lavorando con MiniHive per calcolare un po di metriche simile al nostro MISE 2014
@@ -0,0 +1,19 @@
+type:: [[meeting]]
+
+- **Date**: 2021-01-21
+  **Time**: 11:26
+  **Attendend**: #attendance/online
+  **Project**:  #PROJECTS/CROSSMINER
+  **People attended**:  #people/PhuongNguyen 
+  _Celano: 🌦 +9°C_
+  
+  ---
+- Submit the ICSE NIER to the [Vision and Emerging Results - Evaluation and Assessment in Software Engineering (EASE) - ntnu.edu](https://www.ntnu.edu/ease2021/vision-and-emerging-results) track of EASE
+- Work on AML for API recommendations and work on counter measures (to be submitted to ASE)
+- Work on a journal paper like the research agenda mentioned at the end of [[Modeling and Artificial Intelligence]]
+	- Phuong suggested *Machine Learning and Deep Learning for Model-Driven Engineering: A Roadmap*
+- Talk with Alf about a web page maybe in GitHub about what we are doing to list all the tools
+- [x] Phuong asked me to have a look at the workshop proposal they are doing for EASE
+  	[EASE\_WS\_PROPOSAL/EASE\_WS\_PROPOSAL.pdf at master · MDEGroup/EASE\_WS\_PROPOSAL (github.com)](https://github.com/MDEGroup/EASE_WS_PROPOSAL/blob/master/EASE_WS_PROPOSAL.pdf)
+- [x] Write an email to Tommaso per il workshop [Want to host IIR 2020? - IIR 2019 | 10th Italian Information Retrieval Workshop (unipd.it)](https://iir2019.dei.unipd.it/about-iir/want-to-host-iir-2016/)
+- [x] Write an email to ICSE NIER Skype chat
@@ -0,0 +1,8 @@
+type::  #meeting
+date:: [[22-01-2021]]
+time:: 10:46
+people::  #people/alfonso #people/apurv
+
+- Presentation of the SOSYM paper about about BPMN vs Low-code
+- Problem with section 5.4 concerning the usability
+- We decided to model a workflow in BPMN and then use this as a reference workflow to show the characteristics of all the analyzed LCDPs
@@ -0,0 +1,22 @@
+---
+tags:
+  - '#meetings'
+created: 2021-01-28
+title: '2021-01-28-1410-Meeting-Ludovico'
+---
+
+**Date**: 2021-01-28
+**Time**: 14:10
+**Attendend**: #attendance/online 
+**Project**: #projects/edelta 
+**People attended**:  #people/ludovico
+
+---
+
+- # 2021-01-28-1410-Meeting-Ludovico
+- Stato sulla situazione di [Software: Practice and Experience 2021 (ParallelEvoEdelta) - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/5ff9f7ef6b716e6b2f044165)
+	- Abbiamo parlato della validation. L'idea è
+		- Fare analisi dipendenze dei metamodelli per stressare punto 1 di Fig.
+		- Prendere un sottoinsieme dei metamodelli considerati e generare i corrispondenti example.edelta
+			- Fare mutazioni del codice generato e ragionare sugli errori che potenzialmente si potrebbero ottenere.
+			- L'idea e' poter fare dei ragionamenti su precision and recall
@@ -0,0 +1,25 @@
+---
+tags:
+  - '#meetings'
+created: 2021-02-17
+title: '2021-02-17-0957-Meeting-Claudio-Juri'
+---
+
+- # 2021-02-17-0957-Meeting-Claudio-Juri
+  
+  **Date**: 2021-02-17
+  **Time**: 09:57
+  **Attendend**: #attendance/online 
+  **Project**: #PROJECTS/CROSSMINER 
+  **People attended**:  #people/juri #people/claudio  
+  
+  ---
+  
+  Next steps:
+- Feature diagram
+- Funzione standalone per usare l'approccio
+- Funziona di validazione
+- Generazione di check del dataset rispetto al modello specificato
+- Integrazione in Jupiter
+- Generazione API per poter usare il sistema generato come servizi
+	- Generazione specifica OpenAPI
@@ -0,0 +1,52 @@
+# 2021_01_16-1024-Meeting-Riccardo-Juri
+#meeting
+
+---
+# **202101161024-Meeting-Riccardo-Juri**
+Date: 2021-01-16
+Time: 10:24
+Attendend: #attendance/online
+Project:  #recsys #modeling 
+People attended:  #people/juri  #people/riccardo  
+
+---
+## Overview dell'approccio come presentato da Riccardo
+![[Pasted image 20210116102546.png]]
+
+Molto simile al paper [[AMMORE.pdf]]. La differenza è che la query viene generata automaticamente.
+## Overview dell'approccio proposto
+```mermaid
+graph TB
+
+
+ input(Metamodel being developed)
+ tool[Lucene-based tool]
+ output(OCL Statements)
+ rankingTool[Ranking tool]
+ rankingPolicy(Ranking policy)
+ rankedStatements(Ranked OCL Statements)
+
+
+ input-->tool
+ tool-->output
+ output-->rankingTool
+ rankingPolicy-->rankingTool
+ rankingTool-->rankedStatements
+```
+
+**User input**: It consists of the current metamodel being developed, which includes OCL statements 
+
+**Input of the approach**: It consists only of the metamodel being specified.
+
+**Lucene-based tool**: It retrieves:
+	1) metamodels that similar to the one given in input
+	2) The metamodels retrieved in 1) are used to retrieve OCL statements that can be used to complete the specification of the metamodel being developed.
+
+**Ranking tool**: It takes as input the retrieved OCL statements, a ranking policy, and it generates the ranked list of OCL statements.
+## Evaluation
+For the **Evaluation** we apply the following process:
+
+1) We create a dataset of metamodels containing OCL statements (this represents the GT)
+2) We remove from the dataset in 1) all the OCL statements
+3) We apply the approach on all the metamodels in 2) and compare the recommended OCL statements with those in the GT.
+	1) **Issue:** we need to identify the similarity function to be used for comparison.
@@ -0,0 +1,18 @@
+#meeting
+
+---
+
+- # **Aggiornamento lavoro Lowcode per RecSys**
+  Date: 2021-01-15
+  Time: 10:05
+  Attendend: #attendance/online 
+  Project: #PROJECTS/CROSSMINER 
+  People attended: #people/juri  #people/claudio  
+  
+  ---
+  
+  Metamodello
+  ![[Pasted image 20210115101251.png]]
+  
+  Esempio Modello
+  ![[Pasted image 20210115101915.png]]
@@ -0,0 +1,8 @@
+---
+tags:
+ - '#people/felicient'
+---
+
+# Presentazione Felicien a UAM
+
+- [ESR4: miso-UAM presentation - Google Slides](https://docs.google.com/presentation/d/1ZaIbxCdkHPL1FL81YN8bZGJxwDcv0_DvCokaoAThXkE/edit#slide=id.p1)
@@ -0,0 +1,8 @@
+---
+tags:
+ - '#people/arsene'
+---
+
+- [LOWCOMOTE ESR6 MONTHLY REPORT - Dec/Jan](https://docs.google.com/document/d/1Qm5kEW3AaxDzvxDqbAXpc3_CgmaqdNgpXqOsDOItwdg/edit)
+- [LOWCOMOTE ESR6 MONTHLY REPORT - Feb](https://docs.google.com/document/d/1LLTKcYleEcbOZS62eL_7zjjF7L9gaztPPMbS43x7TSc/edit)
+- [LOWCOMOTE ESR6 MONTHLY REPORT - May - Google Docs](https://docs.google.com/document/d/1XSZkTx7-1xH_Wn7Y6gWzd-KOtixCjSpLAXhfPmXeSSE/edit)
@@ -0,0 +1,10 @@
+---
+tags:
+ - '#people/apurv'
+---
+
+# RESEARCH REPORTS - APURV
+
+- [2021-02 LOWCOMOTE ESR15 MONTHLY REPORT.docx - Google Drive](https://drive.google.com/file/d/14oYpMu8zrm34rln1hQrT9rKb0-uw5-JD/view)
+- [2021-01 LOWCOMOTE ESR15 MONTHLY REPORT](https://drive.google.com/file/d/1LWV4V0ifb8pM85_1I4trMJA1EArw_C1h/view?usp=sharing)
+- [2020-12 LOWCOMOTE ESR15 MONTHLY REPORT](https://drive.google.com/file/d/1yBRnb_uQS78Ax_mrd8D4usMzZiXhrBx7/view)
@@ -0,0 +1,9 @@
+---
+tags:
+ - '#people/felicien'
+---
+
+# RESEARCH REPORTS - Felicien
+
+- [LOWCOMOTE ESR4 MONTHLY REPORT - JANUARY 2021 - davide.diruscio@gmail.com - Gmail (google.com)](https://mail.google.com/mail/u/0/#all/FMfcgxwLsKFQGNKrTHPWQLTgwwCXKnPC)
+- [[2021-03 LOWCOMOTE ESR4 MONTHLY REPORT.pdf]]