Re: How do you ensure that data is not altered/corrupt

1. Have all invariants explicitly specified in the Business Requirements
document

2. If this issue is not caught in tests, then blame the QA  :)

@Joel Kalvesmaki,

A round-robin trip leading us exactly to the starting point is not a
guarantee that we followed the right course without deviations. Any errors
on the forward processing may be reversed by corresponding errors in the
reverse processing. We will only know for sure that the number of errors is
even ... and pray to all Gods that may or maynot exist that this even
number is 0.

Thanks,
Dimitre

On Fri, May 19, 2023 at 1:36b/AM Roger L Costello costello@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Hi Folks,
>
> In certain domains loss of life may occur if data is altered/corrupted in
> any way.
>
> Suppose you write an XSLT program which transforms this:
>
> <alt>12000 feet</alt>
>
> to this:
>
> <altitude>12000 feet</altitude>
>
> How do you ensure that the data -- 12000 feet -- was not altered/corrupted
> in the transformation?
>
> I have heard of people doing a hash on the data prior to the
> transformation, a hash on the data after the transformation, and then
> comparing the hashes. Is that what you would do when lives are on the line?
> What is your recommendation?
>
> /Roger