Hi,
I’m looking for a solution to be able to store my Capella models within git in a way that avoids having the same model conflicted all the time. I’ve read the Wiki and it’s mostly concerning Teams for Capella.
For some internal reasons getting Teams for Capella isn’t possible right now, so I was wondering if there is a way to have a large integration model, with multiple smaller models that are referenced by the larger, integration model? This would partially solve the issue.
Any other suggestions very welcome
Thanks in advance
M
Not quite sure of your use case. Are you looking for:
an advanced version control (variants/options & branches management)?
a multi-user model edition?
complexity management by splitting large model in sub models?
etc.
Anyway, of course, you can imagine tinkering with things. The great classics are playing with Git, System/sub-systems and/or diff/merge.
If ‘reconciliation’ are uncommon, this might work (nevertheless keeping your fingers crossed in the process).
However, if your use case is related to collaborative model edition, I’m afraid there is no (serious) alternative to Team for Capella.
Feel free to contact me privately. I’ll be happy to discuss your needs and better understand what’s preventing you from using Team for Capella.
What you are suggesting is absolutely possible using Git. This is something I have experience of doing and works well, even without Teams for Capella even for “larger” teams.
By breaking the model up with smaller models, pulled into one larger integration model allows you to break your users up over multiple models thus ensuring that you only have “one/fewer” person per model.
It does depend on how integrated your system is and how much coupling there is between your sub-systems as to how many people need to work in the integration model(s).
Working with Git/DevOps is a must when working with this way as model corruption/people making mistakes is more likely.
Please also feel free to reach out to me privately.
Hi Samuel,
Thanks for your response. To address your points;
I’m not looking for advanced version control, we have our own internal git strategies including branching and development processes.
My problem is more related to the limitations of version controlling a single model when it is a binary file. Git sees this as one file, even though it may be broken down into many components or sub systems. I was seeking an alternative to having one large model and wanted to know if there’s a way to break down a large model (one file) into smaller models (multiple files) and integrate them together in another file - this would be the integration model.
This would allow better collaboration and avoid conflicts (or most of them) without Teams
This is exactly what I’m after. I would like a way to break up a larger model into smaller models (files) and reference them in an integration model
I can’t find the private message functionality on here… maybe because I’ve only just created my account!
Would be keen to chat more about this and how you’ve implemented it if that’s ok.
The xml-files of capella (.aird . capella) are text-files for git - comparable and even on a text-basis mergeable (not really advisable).
You can divide the model into many smaller parts by fragmentation. Getting two files (.airdfragment . capellafragment) for each fragment.
E.g. if you have a fragment for LA and a fragment for PA two persons can work idependantly work on them.
You can make the fragments as small as you want.
This is a very relevant thread for me as well. Currently, I am using VCS (Git) but have been thinking to use sss to achieve some higher degree of granularity and easily share information. I would really like to have more information regarding SSS and git to clear some of my doubts. Therefore, incase there is any source available online or experiences shared by users then it will be of great help to me! Thanks