files and package organization

[Bebert]

Hi,
I'm on important projet for me and how can I organize my files and package ?
Use case and deployment are on the root
I see 2 ways for the another; by type of diagram : State, activity, domain model...
Or by business package
What do you think ?
thank's

[AndyJ]

Because of the size and complexity of the current project, we have separate packages for each team (business areas mainly, but also some system functionality teams i.e. Integration).

Within those packages we've added Business Process Model, Domain Model, Requirements Model, Use Case Model, etc. as required.

It doesn't matter much where something is, you can always find it with search.

 

Andy

[qwerty]

It doesn't matter much where something is, you can always find it with search.

Though some sort of structure will definitely help :-)

Anyhow, there is no common rule on how to structure a project. Over the year I have seen that most of my projects are best served with a CIM/PIM/PSM structure (I also describe that in my EA for the BA book). This way the project is focused on abstraction levels which in most cases is a good approach.

q.

[Uffe]

I usually recommend structuring a project by content type, which often-but-not-always coincides with the teams on a development project. Structuring by diagram type is to me just nonsense, the equivalent of dividing a Word document into chapters based on which font is used.

So there'd be a root node each for
- Business analysis
- Requirements analysis
- High-level design
- Detailed design
- Implementation
- Deployment
- Testing

In general, any connectors between these main branches are traces and realizations from lower-down branches to higher-up ones.

The structure within each branch would also follow the same dependency rules, so the structure within your detailed design package would depend on the result you've arrived at in your high-level design.

HTH,


/Uffe