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: Reverse engineering interfaces
Topic Summary:
Created On: 10-Oct-2006 06:48
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-2006 06:48
User is offline View Users Profile Print this message


Leonid Ryzhyk

Posts: 10
Joined: 27-Sep-2006

I am designing a system that contains a mix of hand-written and automatically generated code. The system constitutes an extensible framework that can be customised by users. It defines a bunch of interfaces that users have to implement. As a fact of life, some of the users will work in the Rhapsody environment, while others will work directly in C++.

Consequently, I want to define interfaces in hand-written C++ to make them more human-readable, and use them from Rhapsody as external elements. This works ok except that reverse engineered interfaces appear as regular classes, rather than interfaces in Rhapsody, which means that I can't use them for example to describe port contracts. I can manually change the stereotype to <<interface>>, but then if I modify the interface in C++ and import it to the model again, it overrides my setting.

So, my question is: Is there a way to tell Rhapsody to treat a class as an interface during reverse engineering? And if not, is there a way to use classes instead of interfaces in port contracts?
Report this to a Moderator Report this to a Moderator
 13-Oct-2006 21:47
User is offline View Users Profile Print this message


Jan Diep

Posts: 18
Joined: 31-May-2005

Do you reverse engineer after the new changes, or roundtrip? I would think that once you've set up the classes/interfaces in Rhapsody, auto generate the code... that as long as you edit the classes between the //#[ and //#] markers, I would think when you roundtrip the changes in, it wouldn't change the stereotype. (I know this works when I choose a customized stereotype, but never actually tried it for interfaces, but it should do the same thing).
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.