January 14, 2006

Batch Processing

Three rules of batch interface design that should never be neglected:
1) ensure that the same file can never be sent twice
2) ensure that a new file can never overlay a file that has not been processed.
3) ensure there is a way to verify what was sent, when and how often.

It seems common sense, but unfortunately common sense is not all that common at times.

Posted by Elyse at January 14, 2006 6:45 AM
Comments

#2 doesn't seem so common to me; care to expand on it?

thx,
eokyere

Posted by: eokyere at January 14, 2006 9:52 AM

4) Use error trapping and logging so you know when something went wrong.

Posted by: Gus at January 14, 2006 8:22 PM

Oh, Elyse, you touch on subjects dear to my heart... fwiw, we depend on a combination of unique file names, human driven SOP's and tape backup...

I was attempting to reply to you 'Shits and giggles' post, but it was, um, rejected...

Elyse, Elyse, Elyse....

Stumbled across this posting because my co-worker just used the term, 'For Shits and Giggles', in relation to a health insurance interface that we are coding...

Interesting musings, fwiw, I have found that inducing original thinking (IT-wise) in the health care industry is kinda like changing the direction of a moving freight train...

Perhaps I should work on more 'Stunning' language.

Gary

Posted by: Gary Isabusyguy at January 18, 2006 1:30 PM