>3] Attribute/Property and Method/Operations are not deleted in either direction.

>Interestingly enough #3 is probably the easiest to implement, but to this point we have not done so by design to avoid breaking code. I will be doing an assesment of what is required to make all of these safe in the near future.

Thanks, Mark. I would say this is one of the biggest obstacles to making the engineering tool more than a "one-shot deal". You cannot continue to work on a class with the wizard once you have eliminated or renamed an operation or attribute. If you do, you must manually eliminate the properties/methods after engineering.

Perhaps you could warn the user, and show a list of all the properties and methods (or attributes and operations) which would be deleted, and require them to manually accept that this will happen. Additionally, perhaps you could create an 'undo' type functionality by saving the class library (or .uml file) in a temporary directory. If the user screwed up, they could restore the classlib or the .uml file.

Thanks,

David