Great video! Thank you so much. I have a related question. At minute 8:47 you show the Copy Data with Sync screen with relationships "derived from" and "related to" on the Jama Connect Side. But these properties are not really how Jama presents requirements relationships. Did you specifically create item types or pick lists in Jama to allow you to have those relationships translated directly to CATIA Magic?
@@MBSEExecution Thank you for the follow up. When you are on that Copy Data with Sync, it seems that the relationships "derived from" and "related to" were already created in the past. Could you also show the step where you create those? Seems to be not so obvious, I don't manage to make that link.
I really thought they would be implementing a good approach for really linking artifacts between the tools. This is just a marginal improvement against the existing copy/sync capability CATIA magic offers for DOORS classic for example. It does not allow for having a single source of truth and creates chaos in terms of config management, how can I ensure a good change process if the changes can come from different tools? OSLC links would at least preserve the SSoT at the same time that allows you to se linked artifacts.
Hello, thank you for the feedback. This is the most popular integration method for Doors too. Also Doors and Jama integrations are the most popular ones from hundreds available. You can limit synchronization to one direction in DataHub. Also you can forbid editing of requirements in SysML with iser permisssions e.g. Have dedicated project just for requirements synchronization which would be used in main modeling project as read only. In general requirements are important elements in SysML so not to have them would require different capabilites to work compleately different in the tool e.g. Report generation, requirement verification through simulation, query engine, validation, change tracking. Requirenents are input into SE and output of SE so they are part of SysML. When we synch them with external tool we do not trat SysML req as master but as limited proxy.
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
Great video! Thank you so much. I have a related question. At minute 8:47 you show the Copy Data with Sync screen with relationships "derived from" and "related to" on the Jama Connect Side. But these properties are not really how Jama presents requirements relationships. Did you specifically create item types or pick lists in Jama to allow you to have those relationships translated directly to CATIA Magic?
Thank you for the feedback. Good question. Let me check!
@@MBSEExecution Thanks for checking! Looking forward for your reply.
@@alexoaktube Sorry for slow response. Those are Jama relation types / names we used same in our integration: Derived from, Related To, Traced By.
@@MBSEExecution Thank you for the follow up. When you are on that Copy Data with Sync, it seems that the relationships "derived from" and "related to" were already created in the past. Could you also show the step where you create those? Seems to be not so obvious, I don't manage to make that link.
I really thought they would be implementing a good approach for really linking artifacts between the tools. This is just a marginal improvement against the existing copy/sync capability CATIA magic offers for DOORS classic for example. It does not allow for having a single source of truth and creates chaos in terms of config management, how can I ensure a good change process if the changes can come from different tools? OSLC links would at least preserve the SSoT at the same time that allows you to se linked artifacts.
Hello, thank you for the feedback. This is the most popular integration method for Doors too. Also Doors and Jama integrations are the most popular ones from hundreds available. You can limit synchronization to one direction in DataHub. Also you can forbid editing of requirements in SysML with iser permisssions e.g. Have dedicated project just for requirements synchronization which would be used in main modeling project as read only. In general requirements are important elements in SysML so not to have them would require different capabilites to work compleately different in the tool e.g. Report generation, requirement verification through simulation, query engine, validation, change tracking. Requirenents are input into SE and output of SE so they are part of SysML. When we synch them with external tool we do not trat SysML req as master but as limited proxy.
Very good video. Thanks.
Thank you!
Good video