What Greg says may be true in eventuality but there are ways to "head off
part the problem at the pass". The Life Cycle Model is one aspect. The
protptyping iterative model is one LCM very applicable to the MUMPS
environment. Another aspect is dealing with the full landscape and paying
attention to the key principal processes that constitute any LCM. Check
http://www.swebok.org . The Requirements Engineering Process that deals
with the conceptual content is key and its involvement of the beneficiary
stakeholders. This involvement reveals the cognitive processing element in
the "business processes" and this aspect is manytimes left out through
fovcussing on the technologic details. Neither MUMPS nor VistA needs to
suffer from these defects but can involve all of the key stakeholders and
do reasonably well. THat challenge though is still before us.
On Sun, 13 Nov 2005, Nancy Anthracite wrote:
OK, just so you know, I read it.
On Saturday 12 November 2005 07:52 pm, Gregory Woodhouse wrote:
This does have anything specifically to do with medical information
systems in general or VistA in particular, so feel free to stop
reading now, if you wish. But it does have to do with the quality of
software in general, and so is related (albeit indirectly) to
healthcare informatics, and to VistA.
A well known statistic in the computer industry is that 75% of
projects fail -- and that's only the beginning of the story when it
comes to issues of software cost and quality.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
