Presents: ObjectRoleModeling.com Thursday, September 09, 2010
  Search
Register Login
Forums
 
 

Note: To post to a thread, you must be logged in.

  Syndication  
   
  Forums Minimize  
 
 
ForumForumVisio for Enter...Visio for Enter...General Discuss...General Discuss...Splitting ORM diagrams??Splitting ORM diagrams??
Previous Previous
 
Next Next
New Post
 11/27/2005 3:27 PM
 

Is there any point in splitting ORM diagrams?

Would splitting make ERD generation quicker, or would it just complicate things?

At the moment I'm considering whether it would be worthwhile to split associated entities into their own files, but I don't want to do that until I've heard if it's worthwhile!

Any thoughts?

Cheers,

Martin.

New Post
 12/1/2005 5:24 AM
 
 Modified By Scot  on 12/1/2005 6:24:17 AM
MartinPlatt wrote

Is there any point in splitting ORM diagrams?

Would splitting make ERD generation quicker, or would it just complicate things?

At the moment I'm considering whether it would be worthwhile to split associated entities into their own files, but I don't want to do that until I've heard if it's worthwhile!



I don't know about performance, I suspect having multiple source models to one database model diagram would, if anything, slow down generation (as well as introduce all sorts of problems when source models share a given object type/fact type, use of abbreviations, keeping name changes, etc.).

The intention behind source models was to allow for multiple modelers to work on a project. The reality is that it wasn't implemented well and, in my opinion, is best avoided.

Scot.
Previous Previous
 
Next Next
ForumForumVisio for Enter...Visio for Enter...General Discuss...General Discuss...Splitting ORM diagrams??Splitting ORM diagrams??

 
 
© 2003 - 2009 Orthogonal Software Corporation. All rights reserved. Terms Of Use Privacy Statement