I'm in the industry, so I have a little more background on this. They spent about 40M GBP building the system, and it's only been used for two years. It was (entirely?) outsourced to Accenture. Other reasons why the system sucks: It can only handle about 10,000 orders/second, and has latency numbers that are incredibly high (5 milliseconds+).
Looking at other exchanges, there are trading platforms that have been able to last 10+ years while scaling quite well.
TradElect was/is a project management and technical disaster.
Someone on TECHWR-L posted a link to this paper (under the paradoxical title "The Cupertino Effect"), which is about how Excel's autocorrect feature can corrupt statistical analysis of genetic data if/when Excel "makes the wrong assumption" about an entry based on how it looks:
I've seen far too much of the attitude around that programmers should write the documentation, because the programmers know the application best (as if that's a particularly good criterion by which to create documentation!), and IME that really only accomplishes two things: It makes your programmers (who'd rather be programming, quelle surprise) cranky, and it pisses off your user base, when the documentation reads like something that has been hacked together by someone who doesn't know the first thing or care a whit about documentation. Brilliant.
Now, if someone were serious about getting technical writing students involved in F/OSS projects, I'd recommend contacting these folks: Cooperative Education and Career Services at the University of Waterloo, and the Rhetoric and Professional Writing and Rhetoric and Communication Design programme people. They do co-ops at both the graduate and undergraduate levels in those programmes, and, at least when I was there, seem to be quite open to unconventional project ideas...
I sent her an angry e-mail because she'd managed to fill up my disk quota (and boy was that a royal PITA to clean up), and she said, "I don't know why you got all those copies. You should have only gotten three. It kept getting returned, so I tried sending it again." *headdesk headdesk headdesk*
I should probably also mention that she sent this message to about 20 people at the same time.
I really don't know what to do about a case like that. Perfessor Multigeek suggested locking her in a room with a computer and a bunch of reference materials and not letting her out until she'd learnt to program, but I'm not hopeful... Strangulation with a length of CAT-5 cable?
(Get your minds out of the gutter. The big ones, in this case, would be MS Word and FrameMaker...)