Defined behavior after errors
Define the behavior of your implementation in case of errors.
The next type of errors should be taken into consideration:
- the errors from "Errors" section of the specification. This mainly concerns the protocol specification.
- errors after reception of faulty artefacts from another implementation.
- errors when processing correct artefacts by your implementation
- errors during generation of faulty artefacts by your implementation
Erroneous data mapping
Verify that the user is consulted when incoming data from the central source can not be processed.
Input validation
Verify that the validation of user input is also applied for incoming data from the central source. If the validation fails, the data should be handled as erroneous data.
Transformation design
Verify that your transformation of central data is well-designed and documented. The design includes the restrictions the central data should apply to to be able to serve as input for the transformation.
All data that is not suitable for the transformation should be handled as erroneous data.
Server processing
Verify that the processing of erroneous data on a server (where there is no immediate user interaction) is logged, monitored and eventually presented to the user.
Logging
Verify that enough information about manipulation of central and local data is logged to enable later analysis of possible problems.