Upon performing my
research for a paper in my PADM 5322 class, I stumbled across an article about
how a combination of bad coding and bureaucracy is the problem with
healthcar.gov. There was a quote from a
programmer that stated, off the record of course, that the requirements were constantly
changing. Seeing how the programmers
were using the waterfall method, I can see how that creates issues. In a nutshell, the waterfall method begins
with the requirement process, and then move to coding, then move to testing, and
then releases an entire system. If there
was interference with this method (i.e. requirement changes), this would point
to political pressure. In addition to
tampering with the requirements, this article pointed to the timeframe the
developers were held to even though they insisted that the product was not
ready. This, again, points to political pressure. It would be beneficial, at least in the
aforementioned scenarios, for the government to allow the programmers to do
their job without constraints and with as static requirements as possible. Indeed, bureaucracy and bad coding make a
devastating tandem.
http://www.healthcareitnews.com/news/bad-code-bureaucracy-prove-toxic-combo-healthcaregov?single-page=true
No comments:
Post a Comment