Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: MikeWhatever on August 06, 2009, 03:12:38 am

Title: Keeping models tidy
Post by: MikeWhatever on August 06, 2009, 03:12:38 am

Starting a new (big!) project and want to keep it tidy. Would like to have diagrams at one level and entities needed for that diagram at a lower one, so that when you open up a package you don't get the diagram mixed in with all the classes etc in that diagram.

One way to do this is to create a package at the same level as the diagram (say "Supporting Classes") and stick all the classes etc in there. Problem is that this artificial package name then gets shown on diagrams as the owning package, which is misleading.

Is there a better way to do this, or other good ways of keeping things neat?

Thanks,
Mike.

Title: Re: Keeping models tidy
Post by: Uffe on August 06, 2009, 06:12:26 pm

Hi Mike, and welcome to the forum.

I am aware of no better way of doing it. However, I have just posted a feature request which I think is in part what you're after.
If you agree, please second the request.
http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1249546103

Cheers,

/Uffe

Title: Re: Keeping models tidy
Post by: bioform on August 08, 2009, 07:28:54 am

I usually have my classes in a domain model, and then my diagrams "underneath" the element that the diagram applies to...

Say: Customer, Order class types in the business domain model, and then my Use Case "overview" diagram under (owned by) the use case (e.g., Ship Order) That way the class types would appear on the diagram but would be grouped/organized under the business domain packages.

Did that make any sense?

I will ONLY keep a "element" owned by another element if it is not part of the business domain, but rather is supporting the element...

Example:

<<use case>> Ship Order
    <<diagram>> Overview
    <<diagram>> Domain View
    <<screen>> Ship Order UI
    <<requirement>> ....
         <<requirement>>...

Hope that helps?

David