My Comment : World would be a a happy place to live.
I have come across a comment from software professionals that they know that some parts of their software oulived its utility. They would love to replace it with new parts but their business users would not allow it. Business users’ opinion is if they are not getting new functionality from software then they don’t want any change.
What if we have ‘Maintenance Check’ or ‘Overhauling” phases in our software life cycle? We allocate time and resources for maintenance check in our project plans. Qualifies Software Professionals would check software and see what parts are worn out or need oil and tuning. Worn software are removed with new, others are refactored and tuned.
Do I like paying for Car Service? No. Do I go for every car schedule to keep my car running? Yes. I think that it is a time to educate Business Users about Software servicing. They have choice to pay tens of thousand dollars for software servicing or million of dollars for software rewrite. Because Software System is going to die with
out service ultimately.
Till it happens, let us sneak changes as refactoring with next release.
Saturday, June 10, 2006
I was recently debugging Web Site functionality issue with a client. We were not able to reproduce the issues at our end. I saw that the c...
Survic has very nicely argued that database storage and retrieval is 80% ( I would say 70%) portion of application. Mocks ups, Screen Desig...
Petshop Architecture 4.0 I have used earlier Petshop Architecture. It left a mixed feeling. It was simple to start with but not extensible...
Architecture - client requires at least rudimentary skills in these areas. What is SOA? Benefits? SOA principles for WS? Name standard arc...