Linky, linky.
Quote:
When he investigated the cause, he discovered that one part of the website had created so much “cookie†tracking data that it appeared to exceed the site’s capacity to accept his login information. That’s the mark of a fractured development team.
Quote:
Campbell, whose company has a contract worth a possible total of more than $200 million for its work on the system, noted than an end-to-end test conducted within two weeks of the launch caused the system to crash. She said it was up to CMS to decide on proceeding with the rollout.
Quote:
He and Campbell blamed a decision by CMS within two weeks of the launch to require users to fully register in order to browse for health insurance products, instead of being able to get information anonymously, as originally planned.
While the technical change to require registration was easy, the result was a much greater burden on the system that it failed to handle, Slavitt and Campbell said.
While the technical change to require registration was easy, the result was a much greater burden on the system that it failed to handle, Slavitt and Campbell said.
So, I admittedly know very little about software coding, as in I'm happy to parse a text file and extract information in a timely fashion. Still it seemed odd you'd have several different parts of the website contracted out to many different companies, like it's a pretty big potential problem. I mean, given the scope of what they're trying to do and everything I can see why one would do that, but that's an awful lot to stitch together in the end. I can't imagine keeping communication flowing well between the groups was easy.
Anyone who knows more about putting together a website (or just punching out random bits of computer code) like this care to share thoughts on the project, perhaps offer perspective?
I know we have computer people 'round these parts.
Edited, Oct 24th 2013 12:22pm by someproteinguy