[logseq-plugin-git:commit] 2025-06-19T17:22:26.455Z
This commit is contained in:
Binary file not shown.
@@ -0,0 +1,66 @@
|
||||
{:highlights [{:id #uuid "684fbd0a-e948-4f25-9fd4-4ca045edad83",
|
||||
:page 1,
|
||||
:position {:bounding {:x1 486.5487976074219,
|
||||
:y1 498.4389343261719,
|
||||
:x2 601.209716796875,
|
||||
:y2 634.2398681640625,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966},
|
||||
:rects ({:x1 486.5487976074219,
|
||||
:y1 498.4389343261719,
|
||||
:x2 601.209716796875,
|
||||
:y2 511.5842590332031,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 512.5199584960938,
|
||||
:x2 600.4761962890625,
|
||||
:y2 525.665283203125,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 526.931884765625,
|
||||
:x2 504.9493713378906,
|
||||
:y2 540.0772705078125,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 543.8770751953125,
|
||||
:x2 600.4428100585938,
|
||||
:y2 557.0223999023438,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 558.277587890625,
|
||||
:x2 533.0376586914062,
|
||||
:y2 571.4229736328125,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 572.8036499023438,
|
||||
:x2 574.1879272460938,
|
||||
:y2 585.9490356445312,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 587.2156372070312,
|
||||
:x2 528.8746948242188,
|
||||
:y2 600.3609619140625,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 604.1493530273438,
|
||||
:x2 574.6978759765625,
|
||||
:y2 617.2947387695312,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}
|
||||
{:x1 486.5487976074219,
|
||||
:y1 621.0945434570312,
|
||||
:x2 569.527099609375,
|
||||
:y2 634.2398681640625,
|
||||
:width 777.9999999999999,
|
||||
:height 1100.4935483870966}),
|
||||
:page 1},
|
||||
:content {:text "Introduzione al dominio applicativo “Generative AI”: Large Language Models e loro uso nell'ingegneria del software(area Informatica)(Davide Di Ruscio"},
|
||||
:properties {:color "green"}}],
|
||||
:extra {:page 1}}
|
||||
Binary file not shown.
@@ -1 +1 @@
|
||||
{:highlights [], :extra {:page 10}}
|
||||
{:highlights [], :extra {:page 7}}
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 170 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 116 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 177 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 312 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 59 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 58 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 77 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 236 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 280 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 250 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 292 KiB |
@@ -2978,7 +2978,9 @@ This paper investigates the conceptual and technical feasibility of a new softwa
|
||||
\par
|
||||
8E5M8QKA\{"readingTime":\{"page":12,"data":\{"0":530,"1":1430,"2":1400,"3":1140,"4":450,"5":240,"6":330,"7":210,"8":250,"9":50\}\}\}
|
||||
\par
|
||||
9G4B4RYG\{"readingTime":\{"page":477,"data":\{"0":10,"2":10,"3":20,"4":10,"7":20,"14":10,"17":140,"18":40,"19":10,"20":40,"21":30,"22":10,"25":220,"26":180,"27":140,"28":110,"29":40,"30":40,"31":340,"32":250,"33":80,"399":10,"400":20\}\}\}
|
||||
9F5F2G9D\{"readingTime":\{"page":8,"data":\{"0":50\}\}\}
|
||||
\par
|
||||
9G4B4RYG\{"readingTime":\{"page":477,"data":\{"0":20,"2":10,"3":20,"4":10,"7":20,"14":10,"17":140,"18":40,"19":10,"20":40,"21":30,"22":10,"25":220,"26":180,"27":140,"28":110,"29":40,"30":40,"31":340,"32":250,"33":90,"34":300,"35":340,"36":490,"37":220,"38":400,"39":230,"40":80,"399":10,"400":20\}\}\}
|
||||
\par
|
||||
9QF9CWEH\{"readingTime":\{"page":44,"data":\{"0":30\}\}\}
|
||||
\par
|
||||
@@ -2986,6 +2988,8 @@ This paper investigates the conceptual and technical feasibility of a new softwa
|
||||
\par
|
||||
9VTMURYV\{"readingTime":\{"page":9,"data":\{"3":10\}\}\}
|
||||
\par
|
||||
66AQQ5ZI\{"readingTime":\{"page":4,"data":\{"0":430,"1":680,"2":780,"3":490\}\}\}
|
||||
\par
|
||||
78JSCZMI\{"readingTime":\{"page":12,"data":\{"0":810,"1":1060,"2":440,"3":610,"4":430,"5":520,"6":760,"7":220,"8":430,"9":500,"10":200\}\}\}
|
||||
\par
|
||||
836S4XI5\{"readingTime":\{"page":79,"data":\{"0":20,"3":10,"9":10,"12":10,"13":10\}\}\}
|
||||
@@ -3052,7 +3056,7 @@ PSRA6HK6\{"readingTime":\{"page":76,"data":\{"0":10\}\}\}
|
||||
\par
|
||||
RUKHUVV6\{"readingTime":\{"page":58,"data":\{"1":160,"11":10,"25":10,"39":10,"44":10,"45":20,"46":20,"51":30,"52":10\}\}\}
|
||||
\par
|
||||
SJH2XINQ\{"readingTime":\{"page":80,"data":\{"0":100,"1":150,"2":120,"3":30,"4":40,"5":10,"6":10,"8":10,"11":10,"15":10,"18":10,"21":10,"22":50,"23":50,"24":20,"25":50,"26":210,"27":20,"31":10,"32":10,"33":10,"34":10,"37":10,"39":10\}\}\}
|
||||
SJH2XINQ\{"readingTime":\{"page":80,"data":\{"0":120,"1":180,"2":130,"3":50,"4":40,"5":20,"6":10,"7":20,"8":30,"11":20,"12":10,"15":10,"17":10,"18":10,"19":20,"21":20,"22":90,"23":50,"24":20,"25":50,"26":210,"27":20,"28":10,"29":80,"31":10,"32":10,"33":30,"34":80,"37":20,"38":20,"39":120,"40":30,"41":80,"45":10,"49":10,"52":10,"57":10\}\}\}
|
||||
\par
|
||||
TK8XNYNL\{"readingTime":\{"page":15,"data":\{"0":10,"1":10\}\}\}
|
||||
\par
|
||||
@@ -3425,6 +3429,15 @@ TL;DR
|
||||
Analysis reveals that PLBART learns program syntax, style, logical flow, and style that are crucial to program semantics and thus excels even with limited annotations, and outperforms or rivals state-of-the-art models.}
|
||||
}
|
||||
|
||||
@online{AIAgentCapabilities,
|
||||
title = {{{AI Agent Capabilities Periodic Table}}},
|
||||
url = {https://www.digitaltwinconsortium.org/initiatives/ai-agent-capabilities-periodic-table/},
|
||||
urldate = {2025-06-19},
|
||||
abstract = {The AI Agent Capability Table enables scalable, ethical, and intelligent AI-twin integration across platforms and industries.},
|
||||
langid = {american},
|
||||
organization = {Digital Twin Consortium}
|
||||
}
|
||||
|
||||
@online{AiAgenticAgents,
|
||||
title = {\#ai \#agentic \#agents \#opensource \#rag \#mcp | {{Eduardo Ordax}} | 60 Commenti},
|
||||
url = {https://www.linkedin.com/posts/eordax_ai-agentic-agents-activity-7328742367086227456-6T2P},
|
||||
@@ -5186,7 +5199,8 @@ The definitions, architecture, fundamental technologies, and applications of IoT
|
||||
publisher = {Packt Publishing},
|
||||
location = {Birmingham},
|
||||
abstract = {Go beyond foundational LangChain documentation with detailed coverage of LangGraph interfaces, design patterns for building AI agents, and scalable architectures used in production--ideal for Python developers building GenAI applications Key Features Bridge the gap between prototype and production with robust LangGraph agent architectures Apply enterprise-grade practices for testing, observability, and monitoring Build specialized agents for software development and data analysis Purchase of the print or Kindle book includes a free PDF eBook Book Description This second edition tackles the biggest challenge facing companies in AI today: moving from prototypes to production. Fully updated to reflect the latest developments in the LangChain ecosystem, it captures how modern AI systems are developed, deployed, and scaled in enterprise environments. This edition places a strong focus on multi-agent architectures, robust LangGraph workflows, and advanced retrieval-augmented generation (RAG) pipelines. You'll explore design patterns for building agentic systems, with practical implementations of multi-agent setups for complex tasks. The book guides you through reasoning techniques such as Tree-of -Thoughts, structured generation, and agent handoffs--complete with error handling examples. Expanded chapters on testing, evaluation, and deployment address the demands of modern LLM applications, showing you how to design secure, compliant AI systems with built-in safeguards and responsible development principles. This edition also expands RAG coverage with guidance on hybrid search, re-ranking, and fact-checking pipelines to enhance output accuracy. Whether you're extending existing workflows or architecting multi-agent systems from scratch, this book provides the technical depth and practical instruction needed to design LLM applications ready for success in production environments. What you will learn Design and implement multi-agent systems using LangGraph Implement testing strategies that identify issues before deployment Deploy observability and monitoring solutions for production environments Build agentic RAG systems with re-ranking capabilities Architect scalable, production-ready AI agents using LangGraph and MCP Work with the latest LLMs and providers like Google Gemini, Anthropic, Mistral, DeepSeek, and OpenAI's o3-mini Design secure, compliant AI systems aligned with modern ethical practices Who this book is for This book is for developers, researchers, and anyone looking to learn more about LangChain and LangGraph. With a strong emphasis on enterprise deployment patterns, it's especially valuable for teams implementing LLM solutions at scale. While the first edition focused on individual developers, this updated edition expands its reach to support engineering teams and decision-makers working on enterprise-scale LLM strategies. A basic understanding of Python is required, and familiarity with machine learning will help you get the most out of this book},
|
||||
langid = {english}
|
||||
langid = {english},
|
||||
keywords = {LOGSEQ}
|
||||
}
|
||||
|
||||
@article{augusteijnNeuralNetworkClassification2002,
|
||||
@@ -29145,6 +29159,8 @@ An effective optimization approach, which integrated the probabilistic surrogate
|
||||
shorttitle = {Management of {{Self-Admitted Technical Debt}} Using {{Machine Learning}}},
|
||||
author = {Li, Yikun},
|
||||
date = {2024-04-23},
|
||||
eprint = {11370/0212b8bb-b0af-481d-9f17-a943d0356a90},
|
||||
eprinttype = {hdl},
|
||||
institution = {University of Groningen},
|
||||
doi = {10.33612/diss.972242960},
|
||||
langid = {english}
|
||||
@@ -29342,7 +29358,7 @@ Comment: 7 pages, 3 figures, IEEE conference format}
|
||||
title = {Proposed Title: {{IoT-native}} Software Engineering},
|
||||
author = {Li, Zheng and O’Brien, Liam and Yang, Ye and Gorton, Ian},
|
||||
langid = {english},
|
||||
note = {{$<$}!-- ~== For your convenience, this form can be processed by EasyChair ~== automatically. You can fill out this form offline and then upload it ~== to EasyChair. Several review forms can be uploaded simultaneously. ~== You can modify your reviews as many times as you want. ~== ~== When filling out the review form please mind the following rules: ~== ~== (1) Blocks such as this are comments. EasyChair will ignore them. ~== ~ ~ Do not write any text into these blocks as it will be ignored. ~== ~ ~ You can add comments to the review form or remove them. ~== (2) Write only into the tags where instructed. Do not modify any ~== ~ ~ tags and attributes, or the review will become unusable and will ~== ~ ~ be rejected by EasyChair. ~--{$><$}review id=":7075322::3424433" ~ ~ ~ ~submission="35" ~ ~ ~ ~title="IoT-native Software Engineering" ~ ~ ~ ~authors="Zheng Li, ~ ~ ~ ~ ~ ~ ~ ~ Liam O'Brien, ~ ~ ~ ~ ~ ~ ~ ~ Ye Yang, ~ ~ ~ ~ ~ ~ ~ ~ Ian Gorton" ~ ~ ~ ~pc\_member="Davide Di Ruscio"{$><$}field id="611399" name="SCORE: Overall evaluation of the submitted document"{$>$} ~{$<$}!-- ~ ~== This field defines the "proposal overall quality". ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 3 Accept ~ ~== 2 Borderline ~ ~== 1 Reject ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}!-- ~ ~ Additional Scores ~ ~ --{$><$}field id="611401" name="TOPIC Rating (1-100)"{$>$} ~{$<$}!-- ~ ~== This field represents the importance of the TOPIC presented ~ ~== (independently from the proposal quality) ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 5 (81-100) Strong TOPIC that definitively should be published. ~ ~== 4 (61-80) Interesting TOPIC that most likely will generate interest; ~ ~== 3 (41-60) Potentially a good TOPIC; ~ ~== 2 (21-40) Weak TOPIC; ~ ~== 1 (1-20) Very weak TOPIC that should not be published; ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}field id="611402" name="Is the Topic relevant and timely?"{$>$} ~{$<$}!-- ~ ~== Please describe if the topic is of importance for the IEEE SW ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 2 Yes ~ ~== 1 Not ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}field id="611403" name="Do you expect this theme issue to attract an adequate number of submissions?"{$>$} ~{$<$}!-- ~ ~== Please describe if the guest editors are supposed to be able to ~ ~== attract an adequate ({$>>$}10) number of submissions. ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 3 I expect a high number of submissions. ~ ~== 2 I expect a proper number of submissions; ~ ~== 1 I expect a limited number of submissions; ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}!-- ~ ~ Review ~ ~ --{$><$}field id="611405" name="Review"{$>$} ~{$<$}!-- ~ ~== Please provide a detailed review, including justification for your ~ ~== scores. This field is required. ~ ~--{$>$} ~{$<$}text required="required"{$>$} ~{$<$}!-- ~ ~== Enter the text for the field ~ ~== ~ Review ~ ~== below. This field is required. ~ ~--{$>$}The proposal is too broad. It aims at covering "any aspect of IoT-native Software Engineering", which is risky. For instance, proponents should decide if they want to elicit empirical studies or experience reports. In any case, I don't think pure empirical studies can be appropriate for this venue especially considering the length of typical IEEE Software papers. Overall, it is not clear the need that the proponents aim to fill. ~{$<$}/text{$><$}/field{$><$}field id="611406" name="Confidential remarks for the board members"{$>$} ~{$<$}!-- ~ ~== If you wish to add any remarks intended only for board members ~ ~== please write them below. These remarks will only be seen by the ~ ~== board members having access to reviews for this submission. They ~ ~== will not be sent to the authors. This field is optional. ~ ~--{$>$} ~{$<$}text optional="optional"{$>$} ~{$<$}!-- ~ ~== Enter the text for the field ~ ~== ~ Confidential remarks for the board members ~ ~== below. This field is optional. ~ ~--{$>$} ~{$<$}/text{$><$}/field{$><$}reviewer{$>$} ~{$<$}!-- ~ ~== If the review was written by (or with the help from) a subreviewer ~ ~== different from the PC member in charge, add information about ~ ~== the subreviewer below. Write subreviewer's first name, last name ~ ~== and email between the tags below. ~ ~--{$>$} ~{$<$}first\_name{$>$} ~{$<$}/first\_name{$>$} ~{$<$}last\_name{$>$} ~ {$<$}/last\_name{$>$} ~{$<$}email{$>$} ~{$<$}/email{$><$}/reviewer{$><$}/review{$>$}}
|
||||
note = {\texttt{{$<$}!-- ~== For your convenience, this form can be processed by EasyChair ~== automatically. You can fill out this form offline and then upload it ~== to EasyChair. Several review forms can be uploaded simultaneously. ~== You can modify your reviews as many times as you want. ~== ~== When filling out the review form please mind the following rules: ~== ~== (1) Blocks such as this are comments. EasyChair will ignore them. ~== ~ ~ Do not write any text into these blocks as it will be ignored. ~== ~ ~ You can add comments to the review form or remove them. ~== (2) Write only into the tags where instructed. Do not modify any ~== ~ ~ tags and attributes, or the review will become unusable and will ~== ~ ~ be rejected by EasyChair. ~--{$><$}review id=":7075322::3424433" ~ ~ ~ ~submission="35" ~ ~ ~ ~title="IoT-native Software Engineering" ~ ~ ~ ~authors="Zheng Li, ~ ~ ~ ~ ~ ~ ~ ~ Liam O'Brien, ~ ~ ~ ~ ~ ~ ~ ~ Ye Yang, ~ ~ ~ ~ ~ ~ ~ ~ Ian Gorton" ~ ~ ~ ~pc\_member="Davide Di Ruscio"{$><$}field id="611399" name="SCORE: Overall evaluation of the submitted document"{$>$} ~{$<$}!-- ~ ~== This field defines the "proposal overall quality". ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 3 Accept ~ ~== 2 Borderline ~ ~== 1 Reject ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}!-- ~ ~ Additional Scores ~ ~ --{$><$}field id="611401" name="TOPIC Rating (1-100)"{$>$} ~{$<$}!-- ~ ~== This field represents the importance of the TOPIC presented ~ ~== (independently from the proposal quality) ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 5 (81-100) Strong TOPIC that definitively should be published. ~ ~== 4 (61-80) Interesting TOPIC that most likely will generate interest; ~ ~== 3 (41-60) Potentially a good TOPIC; ~ ~== 2 (21-40) Weak TOPIC; ~ ~== 1 (1-20) Very weak TOPIC that should not be published; ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}field id="611402" name="Is the Topic relevant and timely?"{$>$} ~{$<$}!-- ~ ~== Please describe if the topic is of importance for the IEEE SW ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 2 Yes ~ ~== 1 Not ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}field id="611403" name="Do you expect this theme issue to attract an adequate number of submissions?"{$>$} ~{$<$}!-- ~ ~== Please describe if the guest editors are supposed to be able to ~ ~== attract an adequate ({$>>$}10) number of submissions. ~ ~--{$>$} ~{$<$}score{$>$} ~{$<$}!-- ~ ~== Select your choice from the options below and write its number below, ~ ~== before the {$<$}/score{$>$} tag. ~ ~== ~ ~== 3 I expect a high number of submissions. ~ ~== 2 I expect a proper number of submissions; ~ ~== 1 I expect a limited number of submissions; ~ ~--{$>$} ~ ~ ~{$<$}/score{$><$}/field{$><$}!-- ~ ~ Review ~ ~ --{$><$}field id="611405" name="Review"{$>$} ~{$<$}!-- ~ ~== Please provide a detailed review, including justification for your ~ ~== scores. This field is required. ~ ~--{$>$} ~{$<$}text required="required"{$>$} ~{$<$}!-- ~ ~== Enter the text for the field ~ ~== ~ Review ~ ~== below. This field is required. ~ ~--{$>$}The proposal is too broad. It aims at covering "any aspect of IoT-native Software Engineering", which is risky. For instance, proponents should decide if they want to elicit empirical studies or experience reports. In any case, I don't think pure empirical studies can be appropriate for this venue especially considering the length of typical IEEE Software papers. Overall, it is not clear the need that the proponents aim to fill. ~{$<$}/text{$><$}/field{$><$}field id="611406" name="Confidential remarks for the board members"{$>$} ~{$<$}!-- ~ ~== If you wish to add any remarks intended only for board members ~ ~== please write them below. These remarks will only be seen by the ~ ~== board members having access to reviews for this submission. They ~ ~== will not be sent to the authors. This field is optional. ~ ~--{$>$} ~{$<$}text optional="optional"{$>$} ~{$<$}!-- ~ ~== Enter the text for the field ~ ~== ~ Confidential remarks for the board members ~ ~== below. This field is optional. ~ ~--{$>$} ~{$<$}/text{$><$}/field{$><$}reviewer{$>$} ~{$<$}!-- ~ ~== If the review was written by (or with the help from) a subreviewer ~ ~== different from the PC member in charge, add information about ~ ~== the subreviewer below. Write subreviewer's first name, last name ~ ~== and email between the tags below. ~ ~--{$>$} ~{$<$}first\_name{$>$} ~{$<$}/first\_name{$>$} ~{$<$}last\_name{$>$} ~ {$<$}/last\_name{$>$} ~{$<$}email{$>$} ~{$<$}/email{$><$}/reviewer{$><$}/review{$>$}}}
|
||||
}
|
||||
|
||||
@article{liSystematicMappingStudy2015,
|
||||
@@ -34276,6 +34292,154 @@ And then add a Detailed Comments section to report the notets that contain issue
|
||||
langid = {english}
|
||||
}
|
||||
|
||||
@article{muctadirModelConsistencyManagement,
|
||||
title = {Model {{Consistency Management}} of a {{Brewery Digital Twin}}},
|
||||
author = {Muctadir, Hossain Muhammad and Liao, Yanyifan and Cleophas, Loek},
|
||||
abstract = {Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services. VEs are typically model-based software systems that incorporate a variety of multi-domain, multi-tool models that are essential throughout the DT’s lifecycle. Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT. In this paper, we present a case study on consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production.},
|
||||
langid = {english},
|
||||
note = {\section{Annotazioni\\
|
||||
(16/6/2025, 23:22:43)}
|
||||
|
||||
\par
|
||||
- “Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services.” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT.” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production” (Muctadir et al., p. 1) \#a28ae5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “model inconsistencies during the DT lifecycle are frequent and have a major impact on DT functionality” (Muctadir et al., p. 1) \#e56eee\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “effective consistency management method for DT models.” (Muctadir et al., p. 1) \#a28ae5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “conceptual framework to address the challenges of consistency management for DT models.” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “In this paper, we further evaluate the framework with a DT from the bio-chemical domain.” (Muctadir et al., p. 1) \#a28ae5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “We manage the consistency of the VE comprising four models, which are essential for delivering two services associated with predicting and controlling alcohol production.” (Muctadir et al., p. 1) \#e56eee\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “Section II reviews research on model consistency management” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “microbrewery” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “consistency management approaches into three categories” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “proof-theorybased” (Muctadir et al., p. 1) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “synchronization-based” (Muctadir et al., p. 1) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “rule-based” (Muctadir et al., p. 1) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “derivation of consistency from axioms and theorems.” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “extensive manual definition of transformation rules and become increasingly difficult to manage in heterogeneous or large-scale system” (Muctadir et al., p. 1) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “entities and their relationships required to facilitate the development of systems that can effectively maintain model consistency by addressing specific requirements.” (Muctadir et al., p. 2) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “5D DT architecture proposed by Tao et al. [24].” (Muctadir et al., p. 2) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “(1) Physical Entity (PE)” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “(2) Virtual Entity (VE)” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “chemical kinetics model” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “thermal dynamics model” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “heat transfer model” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “control model” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “Services” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “Production prediction” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “production control” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “PE sends monitoring data and receives control signals, beer flavor and physical attributes dictate VE model parameters, and the remaining VE data are model states” (Muctadir et al., p. 2) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “a) Read and extract model data:” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “b) Store the extracted data:” (Muctadir et al., p. 2) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “ConsistencyRules” (Muctadir et al., p. 2) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “c) Evaluate consistency rules:” (Muctadir et al., p. 3) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “d) Manage consistency rule relevancy” (Muctadir et al., p. 3) \#2ea8e5\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “VE of the brewery DT” (Muctadir et al., p. 3) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “CommonModelStructure” (Muctadir et al., p. 3) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “the second ensures correct connectivity with the thermal dynamics model.” (Muctadir et al., p. 3) \#ffd400\\
|
||||
\mkbibemph{What does it mean "ensures". How connectivity is ensured? }
|
||||
\par
|
||||
- “If a rule’s condition is violated, the associated error message is shown.” (Muctadir et al., p. 3) \#ffd400\\
|
||||
\mkbibemph{ANd then? WHo is the main intended user of the approach. What are the conditions to use the consistency management? What's the supported development of runtime environments that are required to enable the usage of the consistency management system? }
|
||||
\par
|
||||
- “The checker mentioned previously enables us to preserve this structure” (Muctadir et al., p. 3) \#5fb236\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “Discussion on results” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{What results? I undertand it's a short paper, however the paper is not effective in stressing the novelties of the proposed approach. What's the novelty? Is it the consistency language? is it the engine? Authors should distill what are the main ingredientes of the proposed approach. The paper presents an overview of the consistency mangenent systems consisting of different classes and interfaces. The presentation of the consistency managemtn rule is not effective in stressing what are the cases that existing approaches cannot support and that instead the proposed approach can do. }
|
||||
\par
|
||||
- “In the case study presented in Section IV-B, we demonstrate the practical implementation and advantages of the consistency management framework (cf. Section IV-A) for the microbrewery DT.” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “Furthermore, it supports the structured management of consistency rules, with integrated checkers to ensure that these rules remain well organized and continuously aligned with the evolving DT models.” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{The paper presents some ideas, by sketching essentially a class diagram of the consistency management system. What's the novel aspects of the proposed system? }
|
||||
\par
|
||||
- “b) Future work: Similar to the case studies presented in [3] implementing the consistency management framework,” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{WHat's the difference of the consistency management presented in this paper and that of [3]? }
|
||||
\par
|
||||
- “[3]” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “the framework’s relevance, practicality, and usability for a more complex system continue to be an area for further research.” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{ }
|
||||
\par
|
||||
- “For this purpose, we implement a consistency management framework designed specifically to manage the consistency of DT models.” (Muctadir et al., p. 4) \#ffd400\\
|
||||
\mkbibemph{The strenghts and the limitations of the framework are not clearly stated. }
|
||||
\par
|
||||
- “This provides a strong indication of the usefulness and applicability of the framework for DTs developed within the biochemical domain.” (Muctadir et al., p. 4) \#5fb236\\
|
||||
\mkbibemph{ }}
|
||||
}
|
||||
|
||||
@incollection{mullerAutonomicComputingNow2009,
|
||||
title = {Autonomic {{Computing Now You See It}}, {{Now You Don}}’t},
|
||||
booktitle = {Software {{Engineering}}},
|
||||
@@ -37897,6 +38061,13 @@ Google's monolithic repository provides a common source of truth for tens of tho
|
||||
langid = {english}
|
||||
}
|
||||
|
||||
@article{pretelAgentDesignPattern,
|
||||
title = {An Agent Design Pattern Catalogue for the Entanglement of {{Digital Twins}}},
|
||||
author = {Pretel, Elena and Navarro, Elena and López-Jaquero, Víctor and González, Pascual and Dustdar, Schahram},
|
||||
abstract = {The entanglement property is an essential property of Digital Twins (DTs), enabling seamless interaction between the physical twin and its DT. Despite the increasing adoption of MultiAgent Systems (MAS) in DT development, there is a lack of structured guidance on how agent design can support different levels of entanglement. This paper addresses this gap by proposing a catalogue of agent design patterns tailored to support weak, simple, and strong entanglement in DTs. Each pattern is aligned with established design patterns in MAS literature. A decision model is also introduced to guide practitioners in selecting appropriate patterns based on the essential aspects of entanglement: connectivity, promptness, and association. The proposed patterns and model were applied in a real-world case study involving the design of a DT to manage study sessions for children with ADHD, demonstrating their effectiveness and practical value. The results support the feasibility and utility of our catalogue of design patterns for the entanglement of the DT.},
|
||||
langid = {english}
|
||||
}
|
||||
|
||||
@inproceedings{Pretschner05,
|
||||
title = {One Evaluation of Model-Based Testing and Its Automation},
|
||||
booktitle = {Proc. 27th {{Int}}. {{Conf}}. {{Softw}}. {{Eng}}.},
|
||||
@@ -49774,6 +49945,12 @@ A taxonomy of tool-related considerations is presented, based on industry data,
|
||||
keywords = {source\_mobile}
|
||||
}
|
||||
|
||||
@online{WhyMachineLearning,
|
||||
title = {Why Do {{Machine Learning Notebooks Crash}}? {{An Empirical Study}} on {{Public Python Jupyter Notebooks}}},
|
||||
url = {https://www.computer.org/csdl/journal/ts/5555/01/11022755/27fzlMGbues},
|
||||
urldate = {2025-06-15}
|
||||
}
|
||||
|
||||
@incollection{Wilcoxon1992,
|
||||
title = {Individual Comparisons by Ranking Methods},
|
||||
booktitle = {Breakthroughs in Statistics: {{Methodology}} and Distribution},
|
||||
@@ -50284,12 +50461,12 @@ This paper proposes TagCombine, an automatic tag recommendation method which ana
|
||||
@online{xiaoFoundationsLargeLanguage2025,
|
||||
title = {Foundations of {{Large Language Models}}},
|
||||
author = {Xiao, Tong and Zhu, Jingbo},
|
||||
date = {2025-01-16},
|
||||
date = {2025-06-15},
|
||||
eprint = {2501.09223},
|
||||
eprinttype = {arXiv},
|
||||
eprintclass = {cs},
|
||||
doi = {10.48550/arXiv.2501.09223},
|
||||
abstract = {This is a book about large language models. As indicated by the title, it primarily focuses on foundational concepts rather than comprehensive coverage of all cutting-edge technologies. The book is structured into four main chapters, each exploring a key area: pre-training, generative models, prompting techniques, and alignment methods. It is intended for college students, professionals, and practitioners in natural language processing and related fields, and can serve as a reference for anyone interested in large language models.},
|
||||
abstract = {This is a book about large language models. As indicated by the title, it primarily focuses on foundational concepts rather than comprehensive coverage of all cutting-edge technologies. The book is structured into five main chapters, each exploring a key area: pre-training, generative models, prompting, alignment, and inference. It is intended for college students, professionals, and practitioners in natural language processing and related fields, and can serve as a reference for anyone interested in large language models.},
|
||||
langid = {english},
|
||||
pubstate = {prepublished},
|
||||
keywords = {/unread,Computer Science - Artificial Intelligence,Computer Science - Computation and Language,Computer Science - Machine Learning}
|
||||
|
||||
Reference in New Issue
Block a user