GHINSU:   How does it help?

- Introduction
- Benefits to the target user
- Notes on software maintainance


Software testing and debugging is one of the most difficult and expensive parts of the software development process. Moreover, the difficulty of these tasks is in direct correlation with the size of the software code (and it can easily be suggested that the difficulty increases with a higher than proportional rate). The same is true for program understanding, and although not all software maintainance problems require complete program understanding, each one of them requires at least a limited knowledge of how the code works. It is therefore obvious that any effort for diminishing the complexity of the code is worth investigating into.

Benefits to the target user

The goal of our research is the development of a method and a tool that will help software engineers in the following tasks:
o Program understanding.
o Program testing and debugging.
o Software maintainance.
Elaborate more here !!!

Notes on software maintainance

Software maintainance is an expensive, demanding and ongoing process. Lientz and Swanson have reported that large organizations have devoted 50% of their total programming effort to maintaining existing systems. Boehm estimated that one US Air Force system cost $30 per instruction to develop and $4,000 per instruction to maintain over its lifetime.

These figures are perhaps exceptional; but on the average they seem to be between two and four times higher than the development costs for large embedded systems. Our aim is to reduce maintenance costs by increasing the maintainer's productivity.

Do we have any bibliography on that? Maybe we could add it here !!!

What next?

<A HREF=Contents     (o)></A>
<A HREF=What is Code Reduction?     (o)></A>
<A HREF=How does it work?

This page is maintained by Nikos Papaspyrou.
Please, feel free to send your comments, thoughts or suggestions to

Last updated: Monday May 15 1995, 12:05 EET DST.