Kaiser Software falling down.
LA Times reports "Kaiser has aches, pains going digital: Patients' welfare is at stake in the electronic effort, experts say."
Like any big software project, it's never easy to replace an existing system, be it manual/paper system or software [mainframe] system. Either way, the problem is always with the software people: the architects and business analysts since their understand of the requirements are never complete and always behind the curve plus the programmers learn new things in the process of coding and want to do things better [and should be done so that it will be easier to maintain in the future]. Even something as small as web programming can take an inordinate more time than estimated, as we're finding out with my current work.
Copyright, 2007, DannyHSDad, All Rights Reserved.
Like any big software project, it's never easy to replace an existing system, be it manual/paper system or software [mainframe] system. Either way, the problem is always with the software people: the architects and business analysts since their understand of the requirements are never complete and always behind the curve plus the programmers learn new things in the process of coding and want to do things better [and should be done so that it will be easier to maintain in the future]. Even something as small as web programming can take an inordinate more time than estimated, as we're finding out with my current work.
Copyright, 2007, DannyHSDad, All Rights Reserved.
Labels: business analysis, programming, project management, risks, software architecture
posted by DannyHSDad at
7:50 AM
