Thank you for providing more information on your day-to-day ORM needs. The reason that I asked is that we (my company Viev Pty Ltd) is making reasonable progress with our ORM tool, 'Richmond'.
Our vision is to have a tool which, while supporting ORM v2.0, will be quite dissimilar to nORMa, in that we tie 'Use Cases', 'Subject Areas' and 'Projects' to ORM diagrams. So an 'Enterprise' may have many 'Subject Areas' may have many 'Projects', may have many 'Pages' (of ORM diagrams/Use Case Diagrams).
An ORM diagram 'authorised' (by authorised users) at the 'Enterprise' level is persistent at all levels, but at any level you may bring up whatever 'fragment' of an ORM diagram that you want to look at - by just dropping the items on the page and letting the tool self-assemble the ORM diagram.
We get around the problem of having persistent models accross 'pages' by using a relational database.
Anyway, it's early days yet (we started 2 months ago), but here is a small and simplistic video of where we are at:
In essense, we have a vision for 'drill down' capability and having different views of the same thing.
Of course, 'experimentation' and 'prototyping' is just as easy within nORMa, but just copying/pasting a .orm file and showing/modifying whatever it is you want to include/exclude....Viev's vision is that once you have agreed to a model at (say) the 'project' level....you can migrate it 'upwards' to the 'Subject Area' and finally the 'Enterprise' level, each with successively higher persistence throughout the Enterprise.
We're targeting business/systems analysts, enterprise architects and developers alike, with an understanding that there is fluidity until an Enterprise Architect/Busines Owner approves a design concept.
Of course, we offer no reward for suggestions (like Microsoft), but we forge for informtaion and are not affraid to ask. ;) Customer is king.