Internal Meeting (23/01/2013)


Wednesday 23/01/2013, 09:00 - 13:00


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

Who (unordered list)

  1. Sara Montagna (SM)
  2. Danilo Pianini (DP)
  3. Mirko Viroli (MV)
  4. Ambra Molesini (AM)
  5. Stefano Mariani (SM2)


  • 09:30 - 10:00.
    • MV: presentation of goals of this and following meetings
    • AM: presentation of the main schema of the SAPERE methodology
  • 09:30 - 10:45. MV: Discussion and refinement of the Requirement Analysis and Analysis phases of the SAPERE Meta-Model
    • DP demands for an unambiguous definition of what the "Legacy Environment" should be interpreted as
      • MV and SM2 point out the definition of "Legacy Environment" as any HW/SW constraint existing in the environment where the SAPERE system should be deployed
    • SM suggests that some of the activities composing the Analysis phase can be over-detailed (e.g. the distinction between Goals and Tasks)
      • Final agreement is that it's better to detail every phase, then eventually drop some activity if unnecessary or trivial, for instance, by annotating some of the activities as "optional"
  • 10:45 - 11:00. Coffee break.
  • 11:00 - 13:00. AM: Discussion and Refinement of the Architectural Design Activities Diagram
    • SM highlights that the definition and design of a Role can depend on the requirements for the functioning of a given pattern, hence a Role can be defined as a consequence to the need for a given pattern
      • Final agreement is that such possibility is already given by both the SAPERE meta-model (SAPERE-Documentation, Figure 1.2) and the architectural design activities diagram (TR.WP1.2012.6, Figure 5), hence no changes have to be made upon any of the two
    • SM highlights that the instantiation of a Self-Organising Mechanism/Pattern may strongly depend on the instantiation of a Place as playing a precise Role manifesting as a fully-defined Annotation
      • Final agreement is that such possibility is already given by the SAPERE meta-model (SAPERE-Documentation, Figure 1.2) by navigating the associations from Self-Organising Mechanisms to Place as follows: a Self-Organising Mechanisms (e.g. a gradient) can strongly rely upon an Annotation (e.g. the source of the gradient) which play a precise Role (e.g. a POI) reified by an existing Place (e.g. where the POI is)