Hi, all.
I found a difference about the CommunicationMean between the OCB and OAB diagrams, which is that the CommunicationMean object in the OCB diagram cannot use the “delete from diagram” command, whether in synchronous or unsynchronous states.
I am currently creating an OCB diagram, due to this problem, I have to use an OAB diagram. Does anyone know why or how to use the “delete from diagram” command in the OCB diagram for the CommunicationMean.
It is worth noting that in the OCB diagram, the “delete from diagram” command can be used for operational actor object, and in the OAB diagram, the command can be used for both operational actor and CommunicationMean objects.
Thank you for your reply.
Hiding the elements doesn’t solve our needs, because they’ll still be there when we need to derive the CommunicationMean object from the OCB diagram.
Not sure why you cannot delete from diagram in this case, probably that should be a feature request.
Nevertheless, I don’t get why Hiding does not fit your need. Can you clarify what you mean when you say “when we need to derive the CommunicationMean object from the OCB diagram”?
Stephane
Thank you for your reply.
Firstly, I cannot delete from diagram in this case, but I don’t think it’s just that this is an isolated case, it looks like this is a shared problem.
Secondly, I’d like to clearly explain what I mean. Briefly, I first constructed an OCB diagram ([OCB] Operational Capabilities), which may contain comprehensive elements such as OA1, OA2, CommunicationMean 1 and CommunicationMean 2. Then I cloned the diagram, to form the diagram Clone of [OCB] Operational Capabilities, and only wanted to present some of the elements, e.g. not to present CommunicationMean 1. At this point I would have liked to use the “delete from diagram” command, but at the moment I can only use the “Hide Element” command (as in Figure 1). Finally, I used the Python4Capella plugin to export the CommunicationMean in these two diagrams to compare the differences, and found that the diagram of [OCB] Operational Capabilities will show CommunicationMean 1 and CommunicationMean 2 (Figure 2), while hiding the element achieves the same result as I wanted, which is to show only CommunicationMean 2 (Figure 3). I would have thought that the “delete from diagram” command would be possible, but it seems that the “Hide Element” command is also feasible.@ haage
The script: #diagram_name = “[OCB] Operational Capabilities”
diagram_name = “Clone of [OCB] Operational Capabilities”
for diag in JavaList(org.eclipse.sirius.business.api.dialect.DialectManager.INSTANCE.getAllRepresentationDescriptors(model.session),Diagram):
if diag.get_name() == diagram_name:
for comp in diag.get_represented_elements():
if isinstance(comp, CommunicationMean):
print(comp.get_name())
Hi Luke,
Yes, I confirm that the delete from diagram seems to be not available on the OCB for communication means, and this is probably a missing feature.
Glad to read that hiding the element does the job for you.
Stephane
While studying the Arcadia documentation, I’ve been considering the distinction between OCB and COC diagrams. It appears that the key difference for the user lies in the fact that COC diagrams do not depict “Medium Communication” links between actors and entities, unlike OCB diagrams.
As for the rationale behind including these links in the rest of the modeling process, it remains somewhat unclear to me. Indeed, in functional analysis, we emphasize connections between functions using OAIB and SDFB diagrams, as well as LDFB and PDFB.
Therefore, what are the benefits of including these “communication” links? How do they contribute to enriching lower levels of modeling? Could this approach potentially confuse newcomers?
Thanks.
I believe the COC diagrams are rarely used. They are supposed to be “a diagram centered on one specific capability” whereas the OCB depicts multiple capabilities. But I reckon you can create as many OCB as you want and display the Capabilities you want in it, as well as adding other Capabilities in one COC. So you can live without them…
One of the difference is where these diagrams are stored: A COC is stored under the capability it is focusing on, the OCBs are stored at the root of the OC folder.
As for the “Communication Mean” links: you may indeed think they are not useful but:
First, they can be useful at the OA level to get a better understanding of the context in which the system is going to be used
Second, when you go down to the SA, you are actually adding your system of interest in the picture. By doing so, you are going to define the boundaries of your system (which functions are in the system and which are out). And so, it may happen that a communication mean between 2 system actors may be impacted now that the SOI enters the picture
Just as a very short illustration of what I mean, here is a very basic example of an OA architecture and how the communication means is going to be impacted when the system is added at the SA level:
But I suppose that this does not have a great influence on the functional analysis process itself, as it has more to do with defining the interfaces between the system and its actors.
Hello, thank you very much for your response. I will thoroughly assess the transition possibilities between the levels using the “Communication means” to evaluate their utility within the process.
