Internal Meeting (25/7/2012)

When

Wednesday 25/07/2012, 09:00 - 13:00

Where

DEIS Cesena, via Venezia 52, Meeting Room, 2nd floor

Who (unordered list)

  1. Sara Montagna (SM)
  2. Andrea Omicini (AO)
  3. Danilo Pianini (DP)
  4. Mirko Viroli (MV)
  5. Ambra Molesini (AM)
  6. Marco Alberti (MA)
  7. Stefano Mariani with Sype (SM2)

Rough Agenda (Slots are about 15 min. for talk and 15 min. for discussion)

  • 9:20 - 10:00. MV: Contextualising T1.3 (i.e., SAPERE in Y3)
    • MV proposes to produce papers with scientific results of wide significance, and target the SAPERE context, e.g. also in Technical Reports   
    • AO commented positively about this approach, since generality cannot be sacrificed
  • 10:00 - 10:40. SM: Existing SAPERE applications and self-organisation approach
    • AO and MV commented about the fact that the methodology will both have a general section valid for all SAPERE systems, and a section specific for the SAPERE application at hand 
    • AO commented that identifying a detailed process (that SAPERE designers has to follow) that has wide generality is going to be very difficult
    • MV proposed to at least find a fair generalisation/abstraction of the methodological guidelines hidden in existing works and papers
    • SM argues that an important step of the methodology is to check to which extent a problem can be solved (at least partially) using existing (WP2) patterns 
    • MV proposed that the main role of Sara in WP1 in Y3 will be to act as sort of "collector" of existing guidelines, to interact with Ambra that will formalise the methodological guidelines
  • 10:40 - 12:30. AM: Early Draft on Methodology
    • AM said a complete survey will require more time, and should be spanned to next months, and proposes that only AOSE and coordination will appear in D1.4
    • MV proposed to increasingly write a TechReport
    • AM proposed that D1.4 will be quite general (survey, requirements, interactions with tools) and not propose guidelines yet 
    • MV proposed that D1.4 should make it very clear the shape (ingredients) that the final methodology will have. In general, practical hints for SAPERE designers will have to have a key role in the deliverable, though possibly long Technical Reports can detail how standards have been used to devise the methodology. 
    • AO and AM showed the proposed meta-model, and well-motivated it
    • MV proposed to start a subtask with the goal of reviewing the SAPERE meta-model: AM and SM will form the key of the group discussing these issues..
    • MV and AO will soon plan the activities towards the production of D1.4 
  • 12:30 - 12:45. MA: Analysis & prediction techniques for SAPERE
    • MA discusses the possibility of using MABLE modelchecker
    • MA discusses the possibility of using Data Mining 
    • MV noted that the Data Mining activity is related to the one on optimising system parameters, so they are both about AI-techniques used in conjunction with Alchemist 
  • 12.45 - 13.15. AO/SM: Expressiveness, middleware, simulations
    • AO argued that the expressiveness of SAPERE coordination model is a key scientific element of the project, and discussed some literature
    • MV reminds that a good deal of expressiveness concerns are relative to WP2
    • AO also briefly presented an alternative middleware fully supporting the model 
    • MV added that a different middleware, supporting semantic aspects, has also been * AO/SM: SAPERE, simulation, and the pervasive infrastructure
  • 13.15 - 13.30. DP: Alchemist: current state and ongoing development
    • DP explains the basics of Alchemist 
    • DP briefly discusses the plan for adding Approximate Stochastic Modelchecking
  • 13.30 - 13.40. MV: Brief discussion on formal proof results