[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: TOSCA meta model
|
Attached are Philippeâs latest versions of various aspects of the TOSCA meta model. Thanks Philippe for putting these together. Paul, you had a question about âlayersâ in the model. Do these address your concerns? My main motivation with these diagrams is to create simple graphical representations that could help explain TOSCA concepts to new users in a simple to understand fashion. Please feel free to suggest ideas for simplifying these even more. Thanks, Chris From: Philippe Merle <philippe.merle@univ-lille.fr> Hi Chris, > would you mind if I share this with the TOSCA TC I have no problem to share this with the TC (as I would join it soon). I prepared other diagrams (see into the attached zip) to zoom on particular aspects of the object model. * TOSCA_2_0_csd03.[png|svg]: Full object model for TOSCA 2.0 csd 03 * ServiceTemplate_2_0_csd03.[png|svg]: Zoom on service template * TopologyTemplate_2_0_csd03.[png|svg]: Zoom on topology template * SubstitutionMapping_2_0_csd03.[png|svg]: Zoom on substitution mapping * ImperativeWorkflowDefinition_2_0_csd03.[png|svg]: Zoom on imperative workflow definition * Types_2_0_csd03.[png|svg]: Zoom on types I could produce other diagrams if needed, just say me what classes a new diagram should include. A+ Philippe De:
"Chris Lauwers" <lauwers@ubicity.com> Thanks Philippe, would you mind if I share this with the TOSCA TC Thanks, Chris From: Philippe Merle <philippe.merle@univ-lille.fr>
Hi Chris, Attached is a first complete version of the TOSCA class diagram. Following are changes against the previously sent first draft: * set type of dsl_definitions in ServiceTemplate * set type of mapping in ParameterDefinition * removed directives in RelationshipTemplate (introduced by an erroneous copy/paste :-( ) * removed ParameterMappingAssignment and added outputs in OperationAssignment and NotificationAssignment * completed NodeFilter, ConstraintClause, PropertyMapping, AttributeMapping, CapabilityMapping, RequirementMapping, EventFilter, ConditionClauseDefinition, ImperativeWorkflowDefinition * added PropertyFilter, PreconditionDefinition, WorkflowStepDefinition, DelegateActivityDefinition, SetStateActivityDefinition, CallOperationActivityDefinition, InlineActivityDefinition Any comments or suggestions? A+ Philippe De:
"Philippe Merle" <philippe.merle@univ-lille.fr> Hi Chris, Attached is a first class diagram for TOSCA 2.0 CSD 03. I tried to capture TOSCA concepts and their relationships, and hide grammatical details (e.g. short vs extended notation). Unfortunately the diagram is not so easy to read as TOSCA is not so simple to model.
Perhaps several diagrams could help to zoom on different parts of interests. There are still works to be done, annotated in orange in the diagram. What do you think about this first draft? A+ Philippe De:
"Philippe Merle" <philippe.merle@univ-lille.fr> Hi Chris, As the goal is only to document TOSCA, I would suggest to use PlantUML to generate class diagrams. We could also use a truly UML modeler but which ones to choose? I will draft a first class diagram quickly in order to start our discussion. A+ Philippe De:
"Chris Lauwers" <lauwers@ubicity.com> Thanks Philippe, Iâm interested in seeing your suggestions for how to generate such a class diagram (or improve the one I have in my blog). Thanks, Chris From: Philippe Merle <philippe.merle@univ-lille.fr>
Hi Chris, Ok for only a class diagram: this is simplier. A+ Philippe De:
"Chris Lauwers" <lauwers@ubicity.com> Thanks Philippe, at this point Iâm not as much interested in creating a âpureâ formal description of TOSCA. Instead, Iâm looking for a simple illustration of the various types of entities that can be defined in
the TOSCA language and how they relate (for example, types, definitions, refinements, templates, and instances/representations). Even in discussions with TOSCA experts, I continue to be surprised by how different peopleâs understanding is of some of the concepts
that I consider extremely basic. Anything we can do to create a common understanding and common terminology would be extremely helpful. Thanks, Chris From: Philippe Merle <philippe.merle@univ-lille.fr>
Hi Chris, This will be a good idea to add a metamodel to the TOSCA spec. I could help/work with you. UML could be one notation to express this metamodel. Other notations could be MOF or Ecore. Anyway, one important point is to clearly identify the goal of this metamodel, e.g., is it *just* to have a graphical class diagram that shows the TOSCA concepts, their properties, and the relations? Or does this metamodel go further away, e.g. capturing OCL constraints? A+ Philippe De:
"Chris Lauwers" <lauwers@ubicity.com> Hi Philippe, A couple of years ago, I made a very clumsy attempt at defining a TOSCA meta model in UML. You can find the idea here: http://blog.ubicity.com/2018/04/the-tosca-object-model.html This is likely incorrect based on my limited expertise with UML and because TOSCA itself isnât that well defined. Iâd love to create an updated/corrected version of this so we can include it in the spec. You input
would be greatly appreciated. Many thanks, Chris |
Attachment:
diagrams.zip
Description: diagrams.zip
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]