Root level documentation

[sargasso]

I know the project root node isn't a package but I know find that I neecd to include some "project level" documentation in a model.  Has anyone got any good ideas (short of creating a "Project" view which I dont whant to do.

tia
bruce

[thomaskilian]

Hi Bruce,
could you tell us, what kind of docu you want to have at that level. I know that you can (could?) move (at least diagram) objects to the top level. What else would you need?

[sargasso]

Cant move diagrams up anymore  

The project is "splitting" both in the software and team sense.  The new projects are aspects of the same product with different focuses (focii?).  One path is toward supporting multiple views of the application, i.e. the single UI will be replaced by several that address different actor viewpoints and responsibilities.  This path is architecturally oriented and while sharing a common requirements model and a common data tier with the core product it is focussed on the "next generation" app.  Another is involved in the (customer specific) support and evolution of the existing product and the final is involved in general product evolution.
I am looking for some way to describe general aspects of the models that these guys will now produce - and there will be several/many models especially in the first stream.  
The material is essentially textual and "undefined" - sort  of I want to have multiple embedded docs in the root node or at least some way to describe what this entire model is about.

bruce

[thomaskilian]

Hi Bruce,
I have some kind of Overview View where I put this stuff. This contains also the Default Diagram which opens when launching the repository. Starting from that view a new user can navigate to where he wants. I was inspired by a model from Damon Carr who calls this a 30.000 ft perspective.