Back | |
Why should Ripose be used? | Read with Acrobat |
In light of articles in several magazines, organisations are going to be hard pressed to rapidly verify that the designs their data
modellers have produced will provide the results their
users require.
One article that may be of interest was called '1995: The Year of Shattered Illusions'. In it Ms Christine Comaford reports that only 16% of software projects were considered successful. In addition almost US$167 billion was spent on software projects with a mammoth US$140 billion being thrown away on cancelled and problematic projects. Designing and implementing large software projects looks to be very much a hit and miss affair. With all the amazing software tools and methodologies about, why is this so? To understand the problem, it may be necessary to examine some of the alternatives to finding solutions to the strategic planning, system architecture and data base design problems? |
Some of the most popular
alternatives are:
How does Ripose measure up against these approaches? Please contact us for our white paper on the comparisons of most of the above techniques with the Ripose Technique. Note that the above list is not exhaustive. Then
see the conclusion. |