Zurück zu Willert.de

Modeling Guide

Rhapsody Model or Codegeneration topics

Modeling Guide

Postby wvdheiden » May 26th, 2014, 7:56 pm

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.

Who is General Failure and why is he reading my drive?
User avatar
Posts: 52
Joined: October 5th, 2007, 10:31 am
Location: Hellendoorn, the Netherlands
Company: Willert Software Tools GmbH

Re: Modeling Guide

Postby Ursanio » July 7th, 2014, 6:59 pm

Hi guys,

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:

----|--> Object model diagrams
---------|-->sample_pkg_buildtime_overview (point 1)
---------|-->sample_pkg_runtime_overview (point 2)
------------|-->object model diagrams
-------------------|-->includes (look at point 3)

OMD : Object Model Diagram
Point 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.

Best Regards

Posts: 9
Joined: October 2nd, 2013, 9:40 am

Return to Modelling with Rhapsody

Who is online

Users browsing this forum: No registered users and 1 guest