Hi all,
In your opinion, what is the best practise to model data? Class diagrams (CBD) or using properties values and its tool (PVMT)? By data modelling, I mean, the liquid between two components (temperature, pressure, flow, etc); output from a engine (power, consumption); the movement of an axis (speed, torque), etc…
Thanks in advance,
Miguel.
My impression would be (I may be wrong) that if you want to define the types of data that flow between functions, then CBDs with data linking to the Functional Exchanges/ports through Exchanges Items elements, enable you to generate your ICDs.
If what you’re looking for is actual data values, then PVMT may be more efficient.
Stephane
Hi,
As a complement, I would say if those items are exchanged, then they will be represented somehow by exchange item (EI). EI are to be detailed in elements typed by classes or details. All this is on CDB. PVMT is more for entity properties… But when these properties are exchanged, we are back to the first case: entities may own classes for instance, which represent the characteristics.
Use classes enables to have material that have several properties : nature/temperature/pressure/… or energies (Torque/speed; voltage/current/frequency; …)
Thierry
Thank both of you.
From my point of view, data modelling is the biggest unknown topic of using Capella/Arcadia. There is no enough information about how to model information/data. In addition, CBD diagram has many options, so there could be many possibilities to represent the same model.
We should keep talking about it in order to get a common methodology.
Miguel.
Not saying this is perfect but there is a dedicated section “Interfaces and Data Modeling in Capella” in the Capella documentation.
Stephane