Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Tech Meeting 2015 07 1@CEAList
Contents
Present
- Matthieu Perin (CEA List)
- Nataliya Yakymets (CEA List)
- Jonathan Dumont (All4tec)
- Anne-Catherine Vie (All4tec)
Minutes
Objectives
Working on ESF Profile from ESF MetaModel.
Decide on ESF mechanism for lifecycle (creation, typing, linking).
Meeting
Decision D1 ESFProperties stereotypes will extend DataType Metaclass
Proposition P1 ESFBehaviourObject should have at least State to comply with FailureMode idea. A solution might be to rely on ActivityNode and Vertex.
Proposition P2 ESFBehaviourObject should extend some typing UML Element, maybe Classifier ?
Question Q1 Are the ESFSafetyConcepts are Types or Instances?
Proposition P4 The ESFSafetyConcepts are Instances !
Proposition P5 The ESFSafetyConcepts could extend Class
Proposition P6 A first Process example (using some norms & analysis) should be proposed short after first release.
Proposition P7 Add dependency links between profiles that need them.
Decision D2 The ESFProperties should be Typing ELement because they will be used to type things used by concepts.
Decision D3 the ESFBehaviouralObjects should be Typing Element not because of users, but to help Tooling (types could be different but with similar use!)!