Multiple Customers have asked me if there is a Rhapsody Modeling Guide. I have to disappoint them, there is no such thing. perhaps we can, as a community, create something.If you post propositions here, I will gather them and publish them regularly.

Walter

===============================================Who is General Failure and why is he reading my drive?

To start this very usefull thread going I will post two practices that we use:What we have found useful is, that there is an overall object model diagram for every package and an object model diagram called include for every class, as presented bellow:

Legend:OMD : Object Model DiagramPoint 1: "sample_pkg_buildtime_overview": has on it all entities (classes, files, singleton objects) that interact with each other in this package. Point 2: "sample_pkg_runtime_overview": has on it all runtime entities (objects, singleton objects) that need to be created at build time; this one is optional if one uses dynamical allocation. Point 3: "includes" OMD : has on it all entities (classes, files, objects) that need to "see" each other. we connect all standard libraries (stdio.h, string.h, etc) and other dependencies via "usage" stereotype. This way one can graphically see what are the dependencies.