Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic Rhapsody (steve huntington)
Decrease font size
Increase font size
Topic Title: Translation from SASD to UML
Topic Summary:
Created On: 10-Oct-2008 14:42
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 10-Oct-2008 14:42
User is offline View Users Profile Print this message


Jan Meyer

Posts: 3
Joined: 16-Jul-2008

Hello all,

we are trying to translate elements from SASD to UML. We are working on a concept that shows which elements can be used for the SASD elements. We see the problem that there are several possibilities in UML for the different SASD elements. A process can on one hand be a use case and on the other hand a class. So it is difficult to write an automatic translation tool to rhapsody.

So is anybody else working on this topic or has some experience with it?

Kind regards
Jan
Report this to a Moderator Report this to a Moderator
 13-Oct-2008 13:51
User is offline View Users Profile Print this message


Charlie Lane

Posts: 86
Joined: 16-Sep-2005

It depends what you're aiming to do.
If you're simply after a representation of the SASD design in Rhapsody, then I've done that --- I mapped processes to blocks with a <<process>> stereotype. Search in this forum for SASD and you'll find my notes, in the thread on creating OMDs via the API.
If you're aiming for a more sophisticated "proper UML" translation, then you will have to accept some re-engineering because SASD isn't object-oriented: I'd say that a process would become both a use case and one or more operations.
Your choice will take into account factors such as how much of the SASD design you need to alter once it is in a UML tool, how much is going to need re-engineering anyway and to what extent you can adopt a piecemeal approach using the old design+code until whole chunks are re-engineered.
Report this to a Moderator Report this to a Moderator
 13-Oct-2008 14:26
User is offline View Users Profile Print this message


Jan Meyer

Posts: 3
Joined: 16-Jul-2008

Hi Charly,
thanks for the reply. I found your notes about the representation of the SASD design in Rhapsody. It was quite interesting to read. But we are looking for a solution you mentioned with re-engineering. We have the problem that we have to add further functionality to existing models. Therefore we need a whole UML model because of consistency. We saw that we need some rules to translate the SASD elements to UML. But as you mentioned SASD is not object-oriented and you also have different possibilities to represent an SASD element in UML. A process can be a class or a use case .... We have tried to find such rules but we are not sure if we thaught about all variants that are possible. And so i ask if someone else have or had the same problems, so that we can exchange our knowledge

Kind regards
Jan
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic Rhapsody forum.
There are currently 1 users logged in.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.