RE: (ROSE) RE:

[Gornik, Davor]

Nagesh,   Some comments to 1: I would rather like the property on the generalization association. This is the only place that has knowledge of the parent and the child. If you place it in the child, like I assume your suggestion is, you could get problems if you decide to insert a class in the inheritance for example.       Regards,   Davor Gornik Rational Software   +1(425)497-4091 [EMAIL PROTECTED]   -----Original Message----- From: Hsia, John [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 12:17 PM To: 'Nagesh HR'; [EMAIL PROTECTED] Subject: (ROSE) RE:   Some comments below ...   -----Original Message----- From: Nagesh HR [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 10:45 PM To: [EMAIL PROTECTED] Cc: Hsia, John Subject:   Hi All         We are having our own Add-in, that converts the Rose Model to Database model. We are facing some problems with respect to REI, and its usage.          Each class is mapped to Table in Database, and each properties into column.  We have customized Add-in property for RoseAttribute called "ColumnSeqNo", based on this value the table column structure will be defined.         With respect to abstract base class(ABC) concept,  we will not have the Table for the base class, and all its properties will be part of the derived class table.  In this case, all the ABC properties will be listed along with derived class properties for specifying column sequence no. In our example, if Employee is ABC, then all its properties will be made part of Manager as well as Doctor. For all practical purposes, the ABC properties will be treated as if they were defined for derived class. So, for the same ABC property, there could be different ColumnSeqNo in different derived classes.   Please find the example in the Attachment The problems are : 1. How to persist same ABCs property's different ColumnSeqNo information for different derived classes in .mdl/.cat file.         with respect the diagram in the example,                 As Employee class is ABC, hence all its properties will be part of Manager class and as well as Doctor class. Here, Employee class will not have Table, and the derived classes Doctor, and Manager will have Tables.                 The EmpNo attribute in Employee class will be column in Manager Table as well as in Doctor Table, but the  column ordering for EmpNo may be different in Manager Table to that of Doctor Table. But EmpNo RoseAttribute's Addin property ColumnSeqNo can take only one value. How to have the different ColumnSeqNo's for different derived classes                         One of Our Approach to solve the above problem is                 a) have another addin RoseClass property say "BaseColumnSeqNos".  In derived class, we will store concatenated string for each base attribute "<BaseAttribute:ColumnSeqNo>"             Is any better approach ???                         2. How to suppress specific attributes from class diagram view ?? Rose provides only SuppressAttributes API which will suppress all attributes. Jhsia: No programmatic equivalent to the Edit/Compartment menu item 3. How to make customised Add-In property non-editable in the RoseView, but should be able to modify programmatically ?? Jhsia: Define your properties in a different tool and make that tool invisible (roseapp.currentmodel.defaultproperties.setToolVisibility() 4. How to hide any particular / All customised properties for specific classes ?? jhsia: You could do it by segregating the properties in a different set but nothing prevents the user from switching sets. <<RoseForum.jpg>>   Any Suggestions / Solutions / Help is welcome Thanks and Regards Nagesh H R