Mapper

Quality Assurance Information

Known Defects

Note that Mapper is still at the α-release stage. It is incomplete and only partially tested and documented, so it presumably has numerous defects in addition to those listed here. You might also wish to consult the list of fixed defects. These defects are listed in decreasing importance.

  1. Angle and Bearing constraints have a poor error function; they should be closer to quadratic away from the minimum. As it is, Mapper can not converge on the minimum if the initial guess is very poor.
  2. Mapper should use XML namespaces.
  3. Mapper should use the XML lang attribute.
  4. The configure script should check whether it can find the Xerces library.
  5. The test coverage report should have hyperlinks to the annotated source-code files.
  6. Doxygen should be run separately for the test driver programs.
  7. The validity of all XHTML should be automatically checked.
  8. The test coverage of inlined code should be measured and included in the sufficiency criteria.
  9. Tracing from the code to the high-level design should be recorded and checked.
  10. The spelling in documents should be automatically checked.
  11. Curves should be splines, rather than harmonics. This will integrate better with SVG, which uses only splines.
  12. Mapper has no installation instructions.
  13. The design patterns used should be documented.
  14. The required test coverage should also be in terms of branch coverage.
  15. Mapper should use an XML application for the high-level design.
  16. The documentation displays ugly $ signs produced by RCS.
  17. The Doxygen tags should use @ as the escape character, rather than \, for compatibility with Javadoc.
  18. The high-level design should be documented using UML.
  19. Mapper should follow the Unix naming convention and be called mapper (in lower case), rather than Mapper.
  20. Mapper should use a more recent version of Doxygen, and take advantage of its pre, post and invariant tags.
  21. The minimisation functions should also be tested with ill behaved functions.
  22. The XHTML pages do not provide a character encoding.
  23. Checking numerical results using a simple diff is unsatisfactory because of the possibility of rounding differences.

This documentation is still being written, and is therefore incomplete.
$Revision: 6.33 $ $Date: 2002/07/14 17:08:52 $