| MBSE [message #1857964] |
Wed, 08 March 2023 08:42  |
Eclipse User |
|
|
|
Hello ,
i have some questions about your MBSE tool PAPYRUS
- Is this tool interoperable with (jira, git, MFILES)
- Is it possible to export and import files and models in XML format
- Can we integrate requirements management tools like reqtify or DOORS or other traceability tools?
- What is the difference between your tool and capella/ arcadia why can i choose papyrus exactely ?
- can we find api to programme with (python vba ., java..)
- can we generate documents(word) , and EXCEL?
- is your tool collaboratif ? if yes What technique to protect and beware of conflicts when modifying a model?
- How much does it cost to train and support it per person /year?
I look forward to your reply.
Sincerely
|
|
|
| Re: MBSE [message #1857981 is a reply to message #1857964] |
Thu, 09 March 2023 05:17  |
| Eclipse User |
|
|
|
Having used both Eclipse Papyrus and Eclipse Capella I first focus on your question:
What is the difference between your tool and capella/ arcadia why can i choose papyrus exactly ?
First Eclipse Papyrus is a UML/SysML based modeling tool while Eclipse Capella is based on Arcadia. This has a lot of implications because both UML and SysML are notations but Arcadia is an architecture framework, a process model which comes with an own notation. As a consequence with Capella you are bound to the Arcadia process model. Using Papyrus you can use any architecture framework / process model (i.e. UAF, Harmony, SysMOD, OOSEM, ...)
Integrating the process model into the modeling tool has the advantage that the modeling tool can guide you creating your models. Capella features wizards that provide help creating your models and checking the integrity of your models. Papyrus being process model agnostic in principle cannot do this.
I really appreciate the Arcadia process model. It is well suited for the majority of engineering cases. But it has in my experience short comings when it comes to re-using models, designing systems of systems, structuring big models and collaboration.
On the other hand, with Papyrus you have complete freedom how to structure the model. You can use an architecture framework highly adapted to your needs. But this implies, prior to start modeling the modeling team should (at least I strongly advise so) commit on a model structure and document the model structure in a modeling guideline.
In this case freedom of choice on one hand can be a facilitator, on the other requires additional work.
In short whether to better use Papyrus (like any other UML/SysML tool) or Capella IMHO depends on the team which has to work with the tool and the systems to be engineered.
|
|
|
| Re: MBSE [message #1857984 is a reply to message #1857981] |
Thu, 09 March 2023 06:22 |
| Eclipse User |
|
|
|
... and now some answers to the rest of the questions.
- Is this tool interoperable with (jira, git, MFILES)
What does "interoperable" mean in this context?
Well, you can version Papyrus models with git and you can store a Papyrus project export as a file in m-files.
But in what way should Papyrus interact with Jira?
- Is it possible to export and import files and models in XML format
yes, Papyrus stores models in XML format by default
- Can we integrate requirements management tools like reqtify or DOORS or other traceability tools?
yes, using the SysML add-on you can import/export requirements in CSV format
- can we find api to programme with (python vba ., java..)
yes, for example via the UML2 Java API
- can we generate documents(word) , and EXCEL?
yes, at least Word, using the model2doc add-on you can generate Word documents.
- is your tool collaboratif ? if yes What technique to protect and beware of conflicts when modifying a model?
Papyrus provides two different mechanisms to faciilitate collaboration.
1. CDO - models are stored in a database. In this case each change of the model is a database transaction. In the case of applying a change resulting in a conflict the transaction will simply fail.
2. GIT, or any other source code versioning system - Papyrus can handle models split into sub-models. This facilitates collaboration. In this case it is up to the model structure to reduce the risk of conflicts. In the case a conflict occurs you can undo the change by undoing the commit causing the conflict.
- How much does it cost to train and support it per person /year?
Highly depends on the contents of the train and the support level.
What should the contents of the training be?
What should the support level be?
/Carsten
|
|
|
| Re: MBSE [message #1857985 is a reply to message #1857984] |
Thu, 09 March 2023 08:14 |
| Eclipse User |
|
|
|
Hello,
Thanks Carsten for your pertinent responses ;D. I will complete theses responses:
>- Is it possible to export and import files and models in XML format
Yes , it is possible. If the format is different , it is possible to program a model transformation.
- Can we integrate requirements management tools like reqtify or DOORS or other traceability tools?
yes , I done a proto if you export requirement into REQIF format. It exists a code inside our eclipse git
- can we find api to programme with (python vba ., java..)
yes with java you can also use pyhon if you use EASE framework
Patrick
|
|
|
Powered by
FUDForum. Page generated in 0.49523 seconds
Home