Object oriented approach to post-delivery syndrome

Traditionally, software is developed by using the waterfall model. It is also known as structured development. The decomposition in structured development is based on functions. The development phases, namely, analysis, design and implementation are sequential. Maintenance is not thought of until the software is delivered to the end user. It is a general scenario that by the time software is delivered the requirements have changed or the technology has advanced. The customer is in a fix; she cannot use it or throw it due to the investment made on it. This potential obsolescence and the need for immediate maintenance is called post-delivery syndrome. This report identifies the causes for post-delivery syndrome in the traditional method and then discusses how the impact of post-delivery syndrome is reduced in object-oriented development.<>