Software modelisation

Arcadia
1

Hi,
I need in the physical architecture to modelise Thread and Process.
I’m note sure if i shall use Node PC or Behavior PC.

Any one has an idea ? An explanation
Thank

2

In your context:

  • Node PC (Physical Component): represents a physical execution platform (e.g., a CPU core, a microcontroller, or a board). It’s used for structural representation of the hardware.
  • Behavior PC (Behavioral Physical Component): used to represent software artifacts deployed onto hardware, such as threads, processes, or executables. It carries behavioral aspects and can be allocated to Node PCs.
3

I recommend to define also extensions for Behavior PC with PVMT to specify resource requirements for the SW component.
As an example I am using this approach for systems deployed to a Kubernetes cluster, defining pod replicas, ram and cpu limits

  • spec.resources.limits.cpu
  • spec.resources.limits.memory
  • spec.resources.requests.cpu
  • spec.resources.requests.memory

This approach makes it possible to gather system needs in model reports generated with Python4Capella.

4

Thank for your answers.

5

Thank for the idea.
Effectivly it can be a good idea.
For the moment i don’tuse PVMT and i’m not familiar with it.

6

Please find attached a sample of property value definition for HW/SW components.

pa.vpd (9.4 KB)

It could be enlarged to cover more use cases.