Is there a Metamodel or Ontology for ARCADIA?

There’s a nice little diagram on the Arcadia datasheet. It shows what looks like Operational Activities, mapped to System Functions, Mapped to Logical Functions, deployed on Logical Components, etc. But it’s too vague, too incomplete, and not well-labelled.

Is there a better ontology view that describes the relationship between viewpoints or between classes/elements in the ontology? A bigger, more detailed one that might convey much more information to someone new to this, but something that will fit on an A3/A4 page?

There doesn’t seem to be anything like this in the Arcadia Reference documentation. I’m finding systems engineers painstakingly creating their own diagrams of Arcadia in Visio, to conceptualise and try to communicate the workflow, in terms of the different diagrams and their horizontal/vertical relationships. But surely this is a waste of time and something like this already exists?

1 Like

The complete ontology is described in @Jean-Luc_Voirin’s book.

But you can also check out @HelderCastro’s website. He’s produced some very useful and easy to consume information. I’d start here Understanding what is the MBSE Arcadia method » HCSC Engineering Ltd.

In Python4Capella there is a “simplified Metamodell” - perhaps you can find some information there
https://github.com/labs4capella/python4capella#capella-simplified-metamodel-of-python-for-capella

It is also possible to get the full Metamodell of Capella from the Capella source ecore model.

Hi,

There is a some documentation of the current metamodel here:
Metamodel · eclipse-capella/capella Wiki · GitHub

Regards

1 Like

This example from Helder Castro is the closest thing I’ve found to what I’m looking for:

I agree that an Arcadia metamodel should be provided by the authors with the Arcadia methodology definition and training.