It is only for class diagramming at this time, however that is the main usage of UML in this class. My design is currently only set up to operate by typing in smalltalk code. Any confilcts with the diagram should accept the descriptions below as the authority. This is useful for not showing some parts of the design at times, as it can be collapsed. This a representation of a class for UML class diagramming.
Later attributes become objects.
But text at first for simplicity messages- list of all messages that the class will have. Same situation as attributes. You start to make a your classes, then you make the relationships between them. Add all of the classes to a system, call form on that subsystem, and Voila, you will get a form of the entire system, layed out with a minimum of line overlap, proximity of classes in a subsystem and no occlution of lines or imporant symbols. Any subsystem that is collapsed will instead be represented as a small icon about the size of a class.