Let's say I have an older system / structure that shows a little age, but will soon be used much more than it was before. This is a web application in which there wasn’t much common code in it, so I suggested that in the long run it would be less than a person-hour of effort to rebuild it using a more promising code, in order to reduce it (I owned an outdated system for some time and I think that this is true). Keep in mind that the architecture of an outdated system ultimately requires a lot of problems and TLC: I don’t care if it’s not “beautiful” or written “correctly” if it works, but it doesn’t “just work” like it is right now. I already did rewrites before successfully with a similar system, and it looks like the credentials that are open to me do this,if I suggest it right.
So now I need to sell this idea. In the previous system that I mentioned, I successfully rewrote not formal, but simple time, but this has a direct impact on the project timeline if I spend some time rewriting. This means that I know my things better. Before formally justifying the complete rewriting, I would like to get ideas on how to convey it.
Immediately I need to, of course, review the rewriting, but after that it is fuzzy. This will help to have numbers confirming maintenance costs and savings after rewriting, but it is difficult to evaluate. Anything else?
Chris source
share