Abstract: Software aging process and preventive software rejuvenation policy were studied in this paper. Consumption of physical memory, which would not be released, caused by aging related bug, was considered as damage suffered by shocks and could be known by periodic tests, preventive software rejuvenation was done at the next test point when consumption of physical memory reaches a preventive rejuvenation value. Expected cost rate model and optimistic preventive rejuvenation value which minimizes expected cost rate was analytically derived. Simulation experiment shows the validity of the rejuvenation conditions.

Key words: Software aging, Software rejuvenation, Cumulative damage, Maintenance policy