It is not a dumb idea. Our product Atego Artisan Studio is built on a database for exactly the reasons that you mention. Otherwise working in groups becomes quite difficult.
From: sysml...@googlegroups.com [mailto:sysml...@googlegroups.com]
On Behalf Of Dieter Van Eessen
Sent: Sunday, April 07, 2013 11:27 AM
To: sysml...@googlegroups.com
Subject: [SysML Forum] UML/SysML in rdbms
Hello,
I've read some texts about whether to choose to store data in xml vs rdbms.
Flexibility seems to be nearly the only reason to do so: (eg, quote from stack overflow)
"The only reason, IMHO, to put XML in a database is if you need to interact, edit, or change the data with your project. If you are simply reading and using the XML Data, just throw it in a file."
Now I'm wondering: has an attempt be made to store uml/sysml models inside a rdbms? Would this increase possibilities for collaborative work? Topcased mentions in it's documentation that models are split into submodels which have to be locked/unlocked to enable
writing.
Could storing the model in an sql database improve possibilities for online view+documentation+collaboration? It might allow a more dynamic locking/unlocking of model elements on lower level and certain concepts/models could be made public/open source allowing
subscribed users to annotate and subscribed developers to update the model.... Or is this all just a foolish idea?
kind regards,
Dieter Van Eessen
--
--
You received this message because you are subscribed to the Google
Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com
To post to this group, send email to
sysml...@googlegroups.com
To unsubscribe from this group, send email to
sysmlforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "SysML Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
sysmlforum+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hello,
I've read some texts about whether to choose to store data in xml vs rdbms.
Flexibility seems to be nearly the only reason to do so: (eg, quote from stack overflow)
"The only reason, IMHO, to put XML in a database is if you need to interact, edit, or change the data with your project. If you are simply reading and using the XML Data, just throw it in a file."
Now I'm wondering: has an attempt be made to store uml/sysml models inside a rdbms? Would this increase possibilities for collaborative work? Topcased mentions in it's documentation that models are split into submodels which have to be locked/unlocked to enable writing.
Could storing the model in an sql database improve possibilities for online view+documentation+collaboration? It might allow a more dynamic locking/unlocking of model elements on lower level and certain concepts/models could be made public/open source allowing subscribed users to annotate and subscribed developers to update the model.... Or is this all just a foolish idea?
kind regards,
Dieter Van Eessen
Privacy
Maybe using svn or git to store models will be enough :)
> Do you know of any open source tools which use rdbm to store their models?
Christian Damus is currently porting the papyrus editors to support CDO <http://www.eclipse.org/cdo/>
Have a look at his blog <http://give-a-damus.blogspot.be>. AFAIK, the latest kepler developer and nightly builds (M6 or later) have support for CDO.
regards,
Klaas