|
Welcome | Company profile | Services | Products | Solutions | Resources |
|||
| Contact us | Feedback | Site map |
|
| Newsletter ... | June 2001 | ||
|
What took us so long ... The concept of Ripose was conceived in 1970 when Charles first realised that writing superior applications was just not good enough. He was continually asked to alter his applications to accommodate changes which were only revealed once a manager (responsible for the project) tested the application. Sometimes the problems were only revealed when other people used the application. He found that the cost of changing applications increased dramatically due to the number of people involved and the time they spent away from their daily activities. In addition, because the application specifications did not always reflect all management objectives, multiple releases had to be tested before a satisfactory solution was achieved. Sometimes, he found that someone else in another part of the organization was busy developing a similar application for a different set of managers using a different technology. As if this was not bad enough, just when he thought his solution was stable, changes in technology/management/direction occurred, forcing him to repeat almost the whole of the cycle again. Trying to develop a technique which would reduce the risks brought about by technology changes, reduce the lengthy design cycle, improve management efficiency (by eliminating redundant strategies) and reduce costs, were the goals Charles set out to achieve. |
It then took a further 10 years of research co-operating with associates and refinement to bring Ripose to where it is today.
These are some of the major changes:
Ripose implements the goals Charles set out to achieve all those years ago. You can now benefit from all this knowledge and experience. |
||
| Previous page | |||