139 lines
8.5 KiB
Markdown
139 lines
8.5 KiB
Markdown
tags:: [[/unread]], [[#zotero]]
|
||
title:: @ICSOFT_2025_73
|
||
item-type:: [[document]]
|
||
original-title:: ICSOFT_2025_73
|
||
links:: [Local library](zotero://select/library/items/L7XRE7S5), [Web library](https://www.zotero.org/users/1039502/items/L7XRE7S5)
|
||
|
||
- ### Attachments
|
||
- [PDF](zotero://select/library/items/4X6W69N5) {{zotero-imported-file 4X6W69N5, "ICSOFT_2025_73.pdf"}}
|
||
- ### Notes
|
||
- # Annotazioni
|
||
(1/4/2025, 11:33:27)
|
||
|
||
- “IT Project Documentation Elements” (“ICSOFT_2025_73”, p. 1) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “Model Transformation Chai” (“ICSOFT_2025_73”, p. 1) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “define requirements, establish goals, and mitigate risks.” (“ICSOFT_2025_73”, p. 1) #a28ae5
|
||
* *
|
||
|
||
|
||
|
||
- “we proposed a model transformation chain to facilitate the generation of IT project artefacts, which are offered as a solution in last 5 years scientific papers” (“ICSOFT_2025_73”, p. 1) #a28ae5
|
||
* *
|
||
|
||
|
||
|
||
- “structured from the transformation chain more detailed representation.” (“ICSOFT_2025_73”, p. 1) #ff6666
|
||
* *
|
||
|
||
|
||
|
||
- “In the early stages of an IT project, well-structured documentation is particularly essential, as it guides stakeholders in defining requirements, establishing goals, and mitigating risks before implementation begins.” (“ICSOFT_2025_73”, p. 1) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “Furthermore, IT project documentation must adhere to established standards and best practices to ensure consistency, completeness, and usability across different stakeholders and project phases.” (“ICSOFT_2025_73”, p. 1) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “Compliance with standar” (“ICSOFT_2025_73”, p. 1) #ff6666
|
||
* *
|
||
|
||
|
||
|
||
- “By aligning documentation with recognized frameworks, organizations can improve collaboration, ensure regulatory compliance, and streamline project execution.” (“ICSOFT_2025_73”, p. 1) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “we introduced a model transformation chain designed to facilitate the generation of IT project artefacts” (“ICSOFT_2025_73”, p. 1) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “Solutions published in 133 studies offering IT project elements obtaining with principles of model-driven elements obtaining with principles of model-driven engineering, machine learning and generative engineering, machine learning and generative artificial intelligence, learning and generative artificial intelligence, as well as and generative artificial intelligence, as well as manual practices, artificial intelligence, as well as manual practices, were mapped into artefacts used in the initial stages were mapped into artefacts used in the initial stages of IT project identified in (Nikiforova et al., 2025a). of IT project identified in (Nikiforova et al., 2025a). This transformation chain provides a” (“ICSOFT_2025_73”, p. 1) #ffd400
|
||
*what kinds of solutions are you talking about? *
|
||
|
||
|
||
|
||
- “ensuring alignme” (“ICSOFT_2025_73”, p. 1) #ffd400
|
||
*how? what does it mean/imply from a technical point of view? *
|
||
|
||
|
||
|
||
- “This paper follows our previous work by focusing on the extraction and structuring of IT project on the extraction and structuring of IT project documentation elements as mapping of them into the documentation elements as mapping of them into the created model transformation chain. We explore the created model transformation chain. We explore the elements of documentation that can be derived, the elements of documentation that can be derived, the methodologies employed to extract relevant methodologies employed to extract relevant information, employed to extract relevant information, and the to extract relevant information, and the benefits extract relevant information, and the benefits of relevant information, and the benefits of integrating this information, and the benefits of integrating this approach into IT project management practices. approach into IT project management practices. Through this study, we aim to provide a systematic” (“ICSOFT_2025_73”, p. 2) #ffd400
|
||
*At this stage the goal of the paper is vaguous and general. What are the limitations and challenges that you want to address? *
|
||
|
||
|
||
|
||
- “Agile IT project life cycle and IT Project Management Plan project life cycle and IT Project Management Plan structure, which is used for mapping in the next structure, which is used for mapping in the next section. Section 4 specify the fragments of the sectio” (“ICSOFT_2025_73”, p. 2) #ffd400
|
||
*These are suddenly mentioned without any introduction! *
|
||
|
||
|
||
|
||
- “However, challenges such as contextual ambiguity challenges such as contextual ambiguity (AI and such as contextual ambiguity (AI and NLP-based as contextual ambiguity (AI and NLP-based techniques struggle to ambiguity (AI and NLP-based techniques struggle to fully understand context-dependent requirements), fully understand context-dependent requirements), domain-specific variations, and the need for domain-specific variations, and the need for large, labelled datasets make it difficult to achieve labelled datasets make it difficult to achieve fully automated and error-free documentation extraction. automated and error-free documentation extraction. Model-driven development (MDD) offers a” (“ICSOFT_2025_73”, p. 2) #ffd400
|
||
*I think there is some recent work employing LLMs for code generation. It is necessary to compare the proposed approach with some baseline (not necessarily based on LLMs) to highlight the novelty of what has been presented here. *
|
||
|
||
|
||
|
||
- “Automated tools such as Papyrus, MagicDraw, and Enterprise Architect facilitate the extraction of textual Enterprise Architect facilitate the extraction of textual documentation from models, reducing manual effort documentation from models, reducing manual effort and improving accuracy. However, different and improving accuracy. However, different documentation accuracy. However, different documentation tools and methodologies different documentation tools and methodologies often lack documentation tools and methodologies often lack seamless seamless integration. Ensuring” (“ICSOFT_2025_73”, p. 2) #ffd400
|
||
*These are old statements / tools. *
|
||
|
||
|
||
|
||
- “The primary goal is to capture the essence of the product and its goal is to capture the essence of the product and its intended value, rather than producing exhaustive intended value, rather than producing exhaustive documentation (Pasuksmit et al., 2021). This documentation (Pasuksmit et al., 2021). This approach” (“ICSOFT_2025_73”, p. 3) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “Key agile artefacts produced during these early stages include the product vision and roadmap” (“ICSOFT_2025_73”, p. 3) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “These artefacts are typically maintained in collaborative tools like Jira or Trello, allowing for continuous refinement and adaptation.” (“ICSOFT_2025_73”, p. 3) #ffd400
|
||
*???? *
|
||
|
||
|
||
|
||
- “MODEL TRANSFORMATION CHAIN FOR IT PROJECT INITIATION ARTEFACTS” (“ICSOFT_2025_73”, p. 4) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “In this article, we take and examine in more detail a fragment of this large chain that related to project documentation artefacts according to the IT Project Management Plan.” (“ICSOFT_2025_73”, p. 4) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “chain fragment for Scope Management” (“ICSOFT_2025_73”, p. 4) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “The rest of subsections demonstrates only transformation chain types” (“ICSOFT_2025_73”, p. 4) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “This transformation is performed manually” (“ICSOFT_2025_73”, p. 6) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “automation should be combined with manual work of stakeholders, where they select the corresponding use cases to be the user stories for implementation and prioritize them” (“ICSOFT_2025_73”, p. 6) #5fb236
|
||
* *
|
||
|
||
|
||
|
||
- “Obtaining consistent and well-structured IT project documentation is a continuous challenge for project managers and developers’ team due to the complexity and evolving nature of project artefacts.” (“ICSOFT_2025_73”, p. 7) #ffd400
|
||
*Indeed this is a relevant and difficult problem. However, the paper touches the problem in a generic an vaguous manner. Further than exploring some stepts of the required model refinements and transformation process, it's not clear e.g. how the mentioned transformations are actually implemented, orchestrated, chained. Chaining model transformations is critical problem and there are existing work that authors have not mentioned at all. * |