Software products never grow old, or fade away. The designs, their patterns and the ideas embodied in them are carried over and over again for a long time. In this presentation we explore the venues of immortalizing the software systems and the intellectual components they are made up of. We argue that such indestructible systems must embody crucial application ideas and functions but also exemplify user oriented architectural forms that personify ease of use, crash free operations, and user maintainable and /or maintenance free within the specified constraints. We approach the issue by recognizing the implicit fact that a software malfunction is a disaster, however small it is. Based on our previous studies in disaster hardening systems, we apply the ideas used in preventing and mitigating disasters to the methods of designing and developing software systems. We show the mutual commonality as well as areas where methods used in one can be carried over effectively into the other.