|
The relationship
between the choice of
classes and the rest of
the architecture is
unclear, and the
distribution of
functionality among the
classes seems
haphazard. The
classes do not seem to
support the proposed
architecture.
|
The models for the
classes (e.g., UML
diagrams), show that
class responsibilities are
not cleanly distributed
among classes and
functionality is duplicated
among some classes.
Either too few or too many
classes are used, but the
classes generally support
the proposed architecture
|
The models for the classes
(e.g., UML diagrams) show that
(1) individual classes exhibit (a)
strong cohesion, (b) a public
interface that is independent of
the class implementation, and c)
methods that represent a
natural behavioral interface, and
(2) the classes collectively
exhibit weak coupling among
themselves, and (3) the classes
and their interactions are
consistent with the other
architectural design models.
The number of classes is
appropriate.
|