I am the team lead for product develop group that specializes in both ATM networks (financial) and online EFT/ACH.. for a leading banking software company.
There are multiple fed districts with multiple feeder sites already in existance for the multiple switching/private networks that already handle the bulk of fed financial transaction work. The rest comes across private networks as singular batch files that maintain transactions in ACH/NACHA/EFT formats.
The fed take this stuff pretty seriously and have considerable experience. You can expect IP specific + encrypted + password authenticated verification systems.
I work for a financial/banking development company. We began a project a few months ago that takes all of our internal documentation (tech specs, user source, source descriptions, data library, design specs, database and client information) and builds an XML based library. Obviously we aren't rewriting all of our docs to meet a formalized XML standard, however we are attaching tag information on each document that categorizes and describes the document.
A standard for future specs (and whenever rewrites are required of old specs) is being drafted so that all documentation can be parsed and searched with the full power and blessed beauty that is XML!!
Slashdot Mirror
I am the team lead for product develop group that specializes in both ATM networks (financial) and online EFT/ACH.. for a leading banking software company.
There are multiple fed districts with multiple feeder sites already in existance for the multiple switching/private networks that already handle the bulk of fed financial transaction work. The rest comes across private networks as singular batch files that maintain transactions in ACH/NACHA/EFT formats.
The fed take this stuff pretty seriously and have considerable experience. You can expect IP specific + encrypted + password authenticated verification systems.
Jesus boy! I got a CS and an Anthropology degree! We are almost twins!
I work for a financial/banking development company. We began a project a few months ago that takes all of our internal documentation (tech specs, user source, source descriptions, data library, design specs, database and client information) and builds an XML based library. Obviously we aren't rewriting all of our docs to meet a formalized XML standard, however we are attaching tag information on each document that categorizes and describes the document.
A standard for future specs (and whenever rewrites are required of old specs) is being drafted so that all documentation can be parsed and searched with the full power and blessed beauty that is XML!!
GO UBERGEEKS!!