Checkpoints: Design Model
- Does the Logical View section of the Software Architecture Document provide a
comprehensive picture of the services of different packages?
- Does it provide a comprehensive picture of the services of the architecturally
significant classes and their objects and mechanisms?
- Can you find similar structural solutions that can be used more widely in the problem
domain?
- Are there more than ~15 "important or architecturally significant" classes or
subsystems?
- Are there more than seven layers?
- Are the names of the packages descriptive?
- Does the package description match with the responsibilities of contained classes?
- Do the publicly visible classes of the package provide a single, logically consistent
set of services?
- Do the import dependencies correspond to the relationships between the contained
classes?
- Do the classes contained in a package belong there according to the criteria for the
package division?
- Are the classes in the packages related functionally?
- Do there exist classes or collaborations of classes within a package which can be
separated into an independent package?
- Is the ratio between the number of packages and the number of
classes appropriate? For example, 5 packages and 1,000 classes is probably a sign of that
something is wrong.
| |
|