[logseq-plugin-git:commit] 2025-12-27T19:07:25.270Z
This commit is contained in:
+137
-46
@@ -3,9 +3,13 @@ date:: [[13-07-2025]] - 16:57
|
||||
link:: https://univaq-my.sharepoint.com/:w:/g/personal/juri_dirocco_univaq_it/EQ-K23f6XrJPvu0NMEBJbwMB2mOKj0PTLNoPBrgOsUEeGQ?e=fSHI0E
|
||||
progress:: {{renderer :todomaster}}
|
||||
|
||||
- ### Tasks
|
||||
-
|
||||
- ### TASKS
|
||||
collapsed:: true
|
||||
- {{query (and [[SWEN Retreat 2025]] (task TODO DOING) (not [[GOALS-TODOIST]]) (not [[TODOIST-LOGSEQED]]))}}
|
||||
query-table:: true
|
||||
query-properties:: [:block]
|
||||
- ### Notes
|
||||
- 
|
||||
- ## First day [[15-07-2025]]
|
||||
collapsed:: true
|
||||
- ### Points for discussion
|
||||
@@ -41,47 +45,51 @@ progress:: {{renderer :todomaster}}
|
||||
- Discrimination of universities depending on their possibility of training/fine-tuning
|
||||
- Alfonso was suggesting to use Wikidata for generating domain models from textual descriptions
|
||||
- ## Second day [[16-07-2025]]
|
||||
- Topics of the groups
|
||||
- Green SW Engineering
|
||||
- Sustainabiolity
|
||||
- Simlation in federated digital twins
|
||||
- Cultural Heritage
|
||||
- RecSys
|
||||
- Multi-view Modeling
|
||||
- Reuse of LLM Agents for Software Engineering
|
||||
- Performance Analysis
|
||||
- Model
|
||||
- Code
|
||||
- NF Analysis for SW
|
||||
- AI Ops
|
||||
- Code execution and LLMs
|
||||
- Ethic for SW
|
||||
- MDE techniques + JJodel
|
||||
- CONCEPTS
|
||||
- System views
|
||||
- Pre deployment
|
||||
- Statics
|
||||
- Forward vs reverse engineering
|
||||
- Dynamics
|
||||
- Forward vs reverse engineering
|
||||
- Analysis
|
||||
- Predictive
|
||||
- Prescriptive
|
||||
- Simulation
|
||||
- It requires semantics
|
||||
- Post deployment
|
||||
- System Monitoring
|
||||
- System Adaptation
|
||||
- Supporting tools
|
||||
- Modeling environments
|
||||
- LLMs
|
||||
- To move from statics to dynamics
|
||||
- To support deployment (e.g., reconstruct the microservice architecture)
|
||||
- Configurations
|
||||
- Single agent
|
||||
- MAS workflows
|
||||
- e.g, design patterns for software architecture perspectives
|
||||
- WPs
|
||||
collapsed:: true
|
||||
- [SWEN Project - Google Docs](https://docs.google.com/document/d/1cvbufoeL0JcZKgHEUpy71P7677eE4UwQu_VAgLvgzwo/edit?tab=t.0)
|
||||
- Topics of the groups
|
||||
collapsed:: true
|
||||
- Green SW Engineering
|
||||
- Sustainabiolity
|
||||
- Simlation in federated digital twins
|
||||
- Cultural Heritage
|
||||
- RecSys
|
||||
- Multi-view Modeling
|
||||
- Reuse of LLM Agents for Software Engineering
|
||||
- Performance Analysis
|
||||
- Model
|
||||
- Code
|
||||
- NF Analysis for SW
|
||||
- AI Ops
|
||||
- Code execution and LLMs
|
||||
- Ethic for SW
|
||||
- MDE techniques + JJodel
|
||||
- CONCEPTS
|
||||
collapsed:: true
|
||||
- System views
|
||||
- Pre deployment
|
||||
- Statics
|
||||
- Forward vs reverse engineering
|
||||
- Dynamics
|
||||
- Forward vs reverse engineering
|
||||
- Analysis
|
||||
- Predictive
|
||||
- Prescriptive
|
||||
- Simulation
|
||||
- It requires semantics
|
||||
- Post deployment
|
||||
- System Monitoring
|
||||
- System Adaptation
|
||||
- Supporting tools
|
||||
- Modeling environments
|
||||
- LLMs
|
||||
- To move from statics to dynamics
|
||||
- To support deployment (e.g., reconstruct the microservice architecture)
|
||||
- Configurations
|
||||
- Single agent
|
||||
- MAS workflows
|
||||
- e.g, design patterns for software architecture perspectives
|
||||
- Workpackages
|
||||
- **WP1: Pre-deployment design and anlysis of software systems**
|
||||
- T1.1: Multi-dimensional non-functional analysis
|
||||
- T1.2: Multi-dimensional software architectures (e.s. green) (deps: T1.1)
|
||||
@@ -98,6 +106,89 @@ progress:: {{renderer :todomaster}}
|
||||
- **WP5: Impact**
|
||||
- Use case scenarios (Cultural heritage, Territorial monitoring)
|
||||
- Education
|
||||
-
|
||||
-
|
||||
-
|
||||
- Investigating the impact of code refactoing on perfomance and energy
|
||||
- Code refactoring vs software security and its impact on energy consumption
|
||||
- all the commits of the history are considered for the analysis
|
||||
- Martin Beseda - Steady-state detection in timeseries and stuff
|
||||
- Timeseries classification / hierarchical clustreing
|
||||
- Test case selection in collaboration with Dario Di Nucci
|
||||
- Quantum Computing for NISQ
|
||||
-
|
||||
- ## Third day [[17-07-2025]]
|
||||
- ### **SWEN Research Group Strategic Meeting**
|
||||
collapsed:: true
|
||||
- ##### Meeting Overview
|
||||
- The SWEN software engineering research group met to discuss strategic positioning within the university, administrative challenges with research funding, curriculum development around AI/LLM, and potential organizational structures to facilitate operations. The group focused on strengthening their influence in university governance while maintaining research excellence.
|
||||
- ##### University Politics and Positioning
|
||||
- The group acknowledged they need more strategic involvement in university politics to protect their interests:
|
||||
- Need for representation in key committees, particularly the Resources Commission
|
||||
- Discussion about potentially supporting a vice-director candidate from the SWEN group
|
||||
- Recognition that while research excellence is their priority, political engagement is necessary
|
||||
- Proposal to improve information sharing about university developments through a dedicated WhatsApp group
|
||||
- Concern about maintaining appropriate recognition despite administrative challenges
|
||||
- ##### Administrative Challenges and Solutions
|
||||
- Participants expressed significant frustration with administrative barriers to research:
|
||||
- Difficulty executing research contracts and efficiently using project funds
|
||||
- Challenge of maintaining staff continuity when projects end
|
||||
- Several organizational structures were discussed:
|
||||
- Creating a foundation or spin-off
|
||||
- Exploring examples from other universities (Bari, Salerno)
|
||||
- Investigating integration with existing entities like Vitality Foundation
|
||||
- Considering tax hubs for supporting open source projects
|
||||
- Agreement to coordinate sharing human resources across projects when possible
|
||||
- ##### Research Strategy and Visibility
|
||||
- The group discussed developing a comprehensive document/manifesto that:
|
||||
- Maps research competencies and potential synergies
|
||||
- Identifies resource requirements including PhD positions
|
||||
- Serves both internal coordination and external communication
|
||||
- Could be presented as an event for visibility
|
||||
- Would support funding applications in the post-PNRR era
|
||||
- ##### Education and Curriculum Development
|
||||
- With growing student interest in AI, the group discussed approaches to curriculum enhancement:
|
||||
- Incorporating AI/LLM content into existing software engineering courses
|
||||
- Creating dedicated courses on AI applications in software engineering
|
||||
- Leveraging a newly approved course in the EDIS program on LLM in Software Engineering
|
||||
- Concerns about securing computational resources (tokens) needed for these initiatives
|
||||
- Need to better communicate SWEN's relationship to AI to attract students
|
||||
- ##### International Collaboration
|
||||
- Potential bilateral agreement with ITU Vienna for a double degree program
|
||||
- Options in either software engineering or business informatics
|
||||
- Discussion about Green Deal program possibilities
|
||||
- Potential to host the ICT4Sustainability conference in L'Aquila in 2027
|
||||
- ##### Action Items
|
||||
- TODO Create a WhatsApp group for sharing information on university politics and governance
|
||||
- TODO Develop comprehensive document showcasing SWEN research topics and capabilities
|
||||
- TODO Incorporate AI/LLM content in curriculum by end of July
|
||||
- TODO Follow up on potential bilateral agreement with ITU Vienna
|
||||
- TODO Consider organizing ICT4Sustainability conference in L'Aquila 2027
|
||||
- TODO Establish better coordination for sharing resources across projects
|
||||
- TODO Gather data on SWEN's contribution to student enrollment to strengthen position in resource discussions
|
||||
- TODO Explore options for establishing an external entity to facilitate research operations
|
||||
- ### **Academic Group Planning Meeting**
|
||||
collapsed:: true
|
||||
- #### Meeting Overview
|
||||
- This meeting focused on finalizing a collaboration document, improving student engagement strategies, enhancing the group's visibility through various communication channels, and establishing better operational protocols. The discussion centered around how to attract more students and increase the group's presence both internally and externally.
|
||||
- #### Collaboration Document
|
||||
- The group is working on consolidating a document that outlines collaboration opportunities, responsibilities, and project details. This document needs to be finalized before the academic year begins.
|
||||
- TODO Finalize the collaboration document by mid-September (before classes start on September 22nd)
|
||||
- #### Student Engagement Initiatives
|
||||
- Participants discussed creating regular thesis presentation days to inform students about available bachelor's and master's thesis opportunities. This would include small gatherings where students could interact with faculty in a comfortable environment.
|
||||
- TODO Develop a proposal for thesis presentation days (once per semester)
|
||||
- TODO Create a process for publishing and promoting thesis opportunities
|
||||
- #### Communication Strategy
|
||||
- A significant portion of the meeting focused on improving the group's visibility through various communication channels:
|
||||
- **Booklet/Manifesto**: Creating a concise printed document highlighting the group's activities, projects, and opportunities that could be distributed to students and external partners.
|
||||
- **Social Media Presence**: Establishing a consistent presence across appropriate platforms with regular updates about achievements, publications, and activities.
|
||||
- **Website Improvements**: The current website was described as difficult to navigate, particularly for students.
|
||||
- **Brand Identity**: The need for consistent branding across all presentations, materials, and communications was emphasized.
|
||||
- TODO Develop a concise booklet/manifesto about the group's activities
|
||||
- TODO Create a social media strategy with differentiated content for different platforms
|
||||
- TODO Improve website navigation and user experience
|
||||
- TODO Establish consistent branding guidelines for presentations and materials
|
||||
- #### Operational Improvements
|
||||
- The group discussed the need for better protocols for internal communication and data sharing:
|
||||
- [ ] Develop a protocol for collecting and sharing important data and achievements
|
||||
- TODO Establish a process for regular updates to communication materials
|
||||
- #### Future Planning
|
||||
- The meeting concluded with plans for making this type of gathering a recurring event.
|
||||
- TODO Schedule the next meeting for mid-February (before the start of teaching)
|
||||
Reference in New Issue
Block a user