Unexpected behavior on Iterative Transitions

Capella
1

Hello,

I’m a new user using Capella 6.1

I learned a lot in the past few weeks. But currently I’m stuck on some strange behavior of Capella.

According, the Capella User Manual (chapter Iterative Transitions) a transition from OA to SA should only consider elements which are not already linked (justified) to the model in the upper (OA) level.

This works pretty fine for a while. When adding some operational activities in OA and performing a Functional Transition, only the new added operational activities are transitioned and will appear in SA.

But after a lot of iterative transitions, the behavior changes. After then all Operational Activity (also Activites already linked/realized) are transitioned. This result in duplicates of the already transitioned System Functions. Even after getting rid of all the data in the System Analysis (elements and realization links) this strange/wrong behavior can not be fixed.

Seems that somehow, I crashed the model.

Is this behavior already known?
Is there a way to clean-up my Model?

Thank you for your response

Markus

1 Like
2

Well, it does not look good, but it is going to be difficult to reproduce the problem unless you’re willing to raise a bugzilla on the Capella project and provide an example model and a scenario to reproduce the issue.
What I have heard from experimented users on large project as that in general, they don’t use the while transition. A given user, with its own scope of responsibility, would select only the items (let’s say functions) he is working on/responsible of and transition them by right-clicking on them from the project explorer.

Stephane

1 Like
3

Hello,
thank you for your fast response. Since I am not sure if its an user error, I do not want to raise an issue.
So, I will play around a little bit and come back if my problem still exists.

Markus

4

Hello Markus,

I think I have the same problem. How did you solve it ? or Have you never faced with same problem again?

Beytullah

5

Hello Beytullah,

Unfortunately I couldn’t solve the problem. As I only do an evaluation, I can live with it. But it is annoying.
I will try to provide some good/bad example an will raise an issue as Stephane proposed.

Markus

6

Hello again,

We forwarded the problem to our PLM crew. If any solution comes up, I will update the topic.

Beytullah

7

I experienced the same problem and posted about it a few days ago Message link.

(I did not see Marcus’ post at that time).

I submitted an issue report on GitHub, but got no response.

8

In my experience, even if I do a selective transitioning, it may still pick a few duplicates along the way.

I tried to control that by selecting what gets transitioned (in the left pane). I am having a harder and harder time to control the model that way. Following a transition, I search the model for the new duplicates to delete them.

9

Hi all,

I’ve encountered the same issue (iterative transitions leading to duplicates).

I managed to find the cause through comparison of several models showing or not the issue: in my case, the problem came from the fact that the realization link ([Operational Analysis Realization]) between the System Analysis and Operational Analysis layers had been deleted.
I recreated it directly in the .modeller file (I work with 4.5.2 version of Capella) and it solved the problem.

So, if you encounter this problem:

  • first, check the presence or not of this realization link between layers ([Operational Analysis Realization], [System Analysis Realization], …). You can check it through the project explorer (ensure that the “Trace” filter is not active) or by clicking on the target layer of the transition and checking in its properties, in expert tab, if the “Allocated Architecture” property is filled with the source layer (it should be, if not this is the cause)
  • then recreate this link manually (directly in the .modeller/.capella file): create a new project and get the [xxx Realization] link from its .modeller/.capella file, copy/paste it at same place in your model file, set the source and target layers ids with the ones from your model

This issue can occur very easily when the “Trace” filter is deactivated:

  • the “Prevent deletion of Project, System Engineering, Block Architecture, Internal Structure” option (in Window/Preferences/Capella/Delete) does not prevent from the deletion of these realization links
  • the undo does not allow to recover from an accidental deletion
  • these links can not be created through the Add Capella Element menu
  • and the Repair function does not detect/correct this issue

I work with the 4.5.2 version of Capella and don’t know if at least the prevention of deletion of realization links between layers (Operational Analysis, System Analysis, …) or between root items (Root Operational Activity, Root System Function, …) has been implemented in further versions. It could be useful if not the case…

Stéphane

2 Likes