Application livecycle completely respected

Today I had a discussion about fancy stuff you may buy, such as suvenirs, that will end in the trash after a few weeks.
Somebody said, that this was waste of resources.
So I argued, that this is the same as wasting software for marketing reasons (see this post).
“But this is just mental waste.”
No it’s not!
There is the energy to run the computer, the gas you use, when you drive to work, the engery for the servers you deploy it on, the energy to support the internet etc. etc.

The same mistake often appears, when speaking about the application livecycle of software or any other kind of product.


There are lots of parts not considered, when defining application livecycles.

Who thinks about the disposal, when installing custom software on a server.
Maybe you have legal commitment to store customers data for 10 years. This means, that you may not just uninstall software and delete the database.

Who cares about the support, after the period of a guarantee has expired? I’m sure your customer will not buy one more single line of code from you, if you are not able to fix the software after that.

As you can see in the following picture from realtech, the application livecycle stops, when the application is deployed and running:

Application livecycle management of realtech


There are thousands of scenarios, what could happen to your software or, what your customer could expect from you. Of course, it might be too expensive to define a process for every possibile state of the application livecycle. But at least you should identify it and its risks.

Most of these cases will be the same for every product again. So as you identify it and write it down, you can just apply it to new projects. And with a bit of luck you can even suprise the customer in a positive way, when you present it to him.
Maybe it is not the best idea, to speak about the disposal of a software he recently buyed. But as you present your support process after the guarantee has expired, you demonstrate that you thought about allmost every need he will propably have in the future.


Whenever you think about a product / application livecycle, it is worth trying to think about further states (or even backward), than those you already know.

Leave a Reply

Your email address will not be published. Required fields are marked *