Usually class diagrams like that occur early in texts about object oriented software. I deliberately put this figure towards the end of this text, because the inheritance view of a WeaveJ-based design is less important than the subsystem view.