S/W Maintance

I think S/W Maintance is very important. And It's more difficult than development. I have fixed and added function on the S/Ws which are developed by me. But I seem that many people think developing S/W is difficult and important. So there is tendency to think about maintance insignificantly. But the cost of maintance is very high.

Most of the clients frequently request something which will be fixed and added. And then an officer assigned will have to take it. But the requests are infinite and never ending. And they are sometimes changed. For example, A client says "I want to use a function like this.". And then maintance officer will add function. And the client will sometimes say a few days after "I want to change the function. I tried to use it. However, I think that it and what I want are different."

If above events are frequently occured, maintance will become annoying work. So I think some people who work for S/W company must take the high cost of maintance into consideration. That's because they can't have only to put blame on clients. And developers have to think for convenient maintance when they work. Let us say, documentation, naming method, modulization, and so on.

Anyway, I wrote this article because I have been stressed for maintance. I hope that developers win public recognition.