Model management

[pearms]

Is there a best practices doc or tutorial for model/diagram management somewhere that I'm missing?  I'd like to know the best way to manage my modeling diagrams and objects as I move through all design phases.  I understand the package structures, and that every project will have it's own flavor of model management but it seems like I'm reinventing the wheel here and this must have been done a million times before.  Any info would be appreciated.

To give an example of the scope of what I'm after:
1.  Does it make sense to organize domain models by use case or some other package scheme?
2.  We've pulled well-used domain objects into a 'common' package but it still seems a little clunky - is there a better way of handling this?
3.  Do you partition your diagram types or combine them into the same package,  eg. activity and state?

Let me know if this is not clear and I can provide other examples.  Thanks in advance.

[Jan ´Bary´ Glas]

That is all based on methodology you use. EA is a tool with some enhencements for some methodologies, but is open to anything you find or invent.
There are two main approches views according to WHO works within the package and WHAT is in the package. The former I would call "EA traditional" and the later may be called use case driven/aspect oriented/domain related or so.

Both have pros and contras.

[kwasposer]

I still try to find the best fitting methodolgy in package management of my sysml Model.

In order not to have many elements on one diagram, I created a sub-ProductTree bdd.
So clicking on one component A (block) in the bdd; i jump to the ProductTree bdd of this component A with all its parts.

But than I wanted to create an IBD of the component A. This will create a new link to the IBD and my link to the bdd Product tree is not available anymore.

How do you manage to have several sub diagrams of one component, like ibd, bdd, sd....?

[qwerty]

This is a post from 2007. It's not a zombie. It's dead.

q.