Currently, the inheritance reference (which should actually be named superclass) is unidirectional. A TClass references its superclass if it has one but there's no efficient way to get the subclasses of a given class. But sadly, the refactorings pretty much depend on that.
Is it allowed to make that reference bidirectional or is that forbidden by "It is not allowed to make additional information available in the PG." in the case description? (I'd argue that this is no additional information but only a way to make existing information efficiently accessible.)
Currently, the
inheritance
reference (which should actually be namedsuperclass
) is unidirectional. ATClass
references its superclass if it has one but there's no efficient way to get the subclasses of a given class. But sadly, the refactorings pretty much depend on that.Is it allowed to make that reference bidirectional or is that forbidden by "It is not allowed to make additional information available in the PG." in the case description? (I'd argue that this is no additional information but only a way to make existing information efficiently accessible.)