[logseq-plugin-git:commit] 2025-06-11T09:44:21.414Z
This commit is contained in:
+2
-67
@@ -4,72 +4,7 @@ boox-notes:: 
|
||||
- Abstract:
|
||||
- The notion of continuous software engineering extends practices like continuous integration to view the entire software development lifecycle as a continuous, interconnected flow of activities. At the same time, recent advances in large language models (LLMs) have revolutionized the way machines process natural language—language that plays a central role throughout software engineering, from requirements elicitation and design discussions to documentation.
|
||||
- In this talk, I will outline a vision for the role of models in continuous software engineering, focusing particularly on their use in design activities. I will argue that models will remain central to software engineering, even in an era of AI-assisted development, and explore what future design assistants might look like. One key capability of such assistants will be the ability to establish and use trace links between artifacts. I will present recent results showing how LLMs, combined with heuristic techniques, can achieve high precision and recall in this task.
|
||||
- Looking ahead, I will share our vision for how model-driven techniques can support more agile development of cyber-physical systems, and our ideas how LLMs can contribute to realizing the long-standing goal of model consistency. Finally, time permitting, I will also reflect on the use of LLMs in navigating software engineering literature and research data.
|
||||
- Notes
|
||||
- Cost-efficient modeling
|
||||
- automated extrection of models from other artefacts
|
||||
- Automated model consistency to enable cost-efficient evolution
|
||||
- Natural language as one view of the system to be keto consistent
|
||||
- NoRBERT for Requirements classification 2020
|
||||
- Models in Continuous Software ENgineering
|
||||
- At the beginning the ideal process was the waterfall one. But it seems does not work proprely in most cases. Specifications and implementations are inevitably interwined. This because:
|
||||
- hierarchical intertwinement: high-level design decisions inform lower-level requirements
|
||||
- technical feasibility: non-feasible requirements are useless
|
||||
- validation: what you see is what you require.
|
||||
- Iterative planning then!
|
||||
- {{renderer :mermaid_68493348-7f45-4787-95d3-54066d1c01fd, 3}}
|
||||
collapsed:: true
|
||||
- ```mermaid
|
||||
graph LR
|
||||
A[Learn] --> B[Plan]
|
||||
B --> C[Build]
|
||||
C --> A
|
||||
```
|
||||
- Agile manifesto, 2001
|
||||
- How to support cost-efficient modeling?
|
||||
- [[LLMs]]
|
||||
- some of the following slides can be exploited to prepare the slides for the [[Intervento PINKAMP]]
|
||||
- 
|
||||
-
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- {:height 398, :width 852}
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
-
|
||||
- 
|
||||
- This is related to [[Model Context Protocol (MCP)]] #LLMs #PROJECTS/MOSAICO #reading
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- A metascience study of the low-code scientific field - Jordi Cabot at [[STAF]] 2025
|
||||
- Can the low-code popularity to help the community grow?
|
||||
- Looking for win-win
|
||||
- [lens.org](https://www.lens.org/) has been used to collect articles
|
||||
- Nowadays there are more low-code papers than those using the MD* keywords
|
||||
- How can you be sure that arxiv papers are duplicates of papers published somewhere else? #question
|
||||
- Facts
|
||||
- Decline in the size of the modeling community
|
||||
- Low-code compensate that
|
||||
- Rebrand MODELS with Lowcode?
|
||||
- Becuase of the so different keywords like MDE/MDA/MBD/.,,, we look so fragmented
|
||||
- Majority of low-code papers are applications
|
||||
- Notes from [[Missione STAF 2025]] #todoist-task #STAF #ADMIN/MISSIONI #[[Attended Event]]
|
||||
-
|
||||
-
|
||||
-
|
||||
Reference in New Issue
Block a user