- Project tools
- Nightly builds of docs
- The ArgoUML Project
- Using ArgoUML
- How do I...
|Over 500 more tools...
Critics concerning generalization and specialization in
The current version of ArgoUML has the following critics
in this category.
15.16.2. Remove <class>'s Circular
Suggestion that a class inherits from itself, through a
chain of generalizations, which is not permitted.
This critic is marked inactive by default in the
current release of ArgoUML (the only one so marked). It
will not trigger unless made active.
15.16.4. Remove final keyword or remove subclasses
Suggestion that a class that is final has
specializations, which is not permitted in UML.
15.16.5. Illegal Generalization
Suggestion that there is a generalization between
model elements of different UML metaclasses, which is not
It is not clear that such a generalization can be
created within ArgoUML. It probably indicates that the
diagram was created by loading a corrupt project, with an
XMI file describing such a generalization, possibly created
by a tool other than ArgoUML.
15.16.6. Remove Unneeded Realizes from <class>
Suggestion that the specified class has a realization
relationship both directly and indirectly to the same
interface (by realization from two interfaces, one of which
is a generalization of the other for example). Good design
deprecates such duplication.
15.16.7. Define Concrete (Sub)Class
Suggestion that a class is abstract with no concrete
subclasses, and so can never be realized.
15.16.8. Define Class to Implement <interface>
Suggestion that the interface referred to has no
influence on the running system, since it is never
implemented by a class.