|
The software design
correctly model less than
60% of the functionality
specified in the
requirements document.
The system design might
be organized into a set of
components, but (1) most
of the components are not
cohesive or loosely
coupled together, OR (2)
the system is designed as
one meta component OR
(3) t he systemÂs design
hampers
expanding/enhancing the
system's capabilities.
|
The software design
correctly model at least
60% of the functionality
specified in the
requirements document.
The system design is
organized into a set of
components. Most of the
components are cohesive
and loosely coupled
together. The system is
designed to include some
hooks and mechanisms to
accommodate new
components or subsystems
for expanding/enhancing
the capabilities.
|
The software design
correctly model at least
80% of the functionality
specified in the
requirements
document. The system
design is organized
into a set of cohesive
and loosely coupled
components. The
system is designed to
include hooks and
mechanisms for
expanding/enhancing
the systemÂs
capabilities.
|