Next: System and acceptance testing
Up: Features to be tested
Previous: Features to be tested
  Contents
The modules, classes and methods listed in Table 2 will be tested as independent modules. Software Design Specification
will be used as a reference material, i.e. the purpose of module testing is to test, whether the implemented modules comply with the SDS.
Acceptance testing for the DTW function library will be carried out at this phase. The requirements concerning the library can be found in
section 3.1.1 of the Software Requirements Specification. Table 2 contains the information, which requirement each function
of dtwlib.cpp
is supposed to fulfill. Acceptance testing will be done only to dtwlib
so there are no requirement codes for other
modules in the table.
Table 2:
List of modules functions for module testing
Source file |
Function |
Requirement code |
dtwlib.cpp |
DTAddTemplate |
D-01 |
|
DTDelTemplate |
D-02 |
|
DTCompareAll |
D-03 |
|
DTCompareOne |
D-04, P-01, P-02, P-04 |
|
DTGetTemplate |
D-05, P-02, P-02, P-04 |
|
DTFreeResources |
|
DTWFileIO.java |
openDataSet |
|
|
loadRecord |
|
|
closeDataSet |
|
|
loadTemplates |
|
|
saveTemplates |
|
|
loadObservation |
|
|
saveObservation |
|
|
saveLog |
|
DTWHorizontalPlotter.java |
setValues |
|
and DTWVerticalPlotter.java |
update |
|
|
paint |
|
DTWPathPlotter.java |
setValues |
|
|
initializePath |
|
|
update |
|
|
paint |
|
|
Next: System and acceptance testing
Up: Features to be tested
Previous: Features to be tested
  Contents
2002-03-19