1. How should I represent a VB property in a UML static class diagram? I am learning UML (and VB for that matter) and am now doing a UML diagram using MS Visio.
As I see it I can call a property an attribute or an operation or ...
2. Shopuld a class implementing a base class be depicted as implementing an interface, or inheriting from a base class? VISO does not seem to cheat and let me have data
in an interface. But VB seems to only offer implementation of a class for inheritance.