Confusions about software development, maintenance, and support

I haven't written a blog for a long time. I have been doing maintenance work in the company for nearly a year. I have little technical skills and have learned a lot about human experience and problem handling, but this is not what I like. It also brings me a lot of confusion. It is obviously development, and the most writeable is notCodeInstead, they answer questions about each customer every day.

This is probably the case. The company has taken over a large project from its headquarters for more than 10 years. It should have been developing a new version, but this project has been ruined by countless people in the past 10 years, there are a bunch of problems with code and functions. Due to insufficient staff (AlAs ~~~ I have been recruiting people. Every month, I talk about people coming next month, but it's almost half a year since we haven't seen them.) and the new features are not the focus of customers, so our work has gradually become software maintenance. Next, let's talk about what maintenance should do.

1. Maintenance of correctness
Correction refers to an error that has occurred in the system development phase and has not been found in the system test phase. In this respect, the maintenance workload accounts for 17% of the total maintenance workload ~ 21%. Some of the errors found do not affect the normal operation of the system. maintenance can be performed at any time. Some errors are very important and even affect the normal operation of the entire system, its maintenance work must be planned, modified, and reviewed and controlled.
2. Adaptive Maintenance
Is to instruct the corridor to use software to adapt to changes in information technology and management needs. The maintenance workload accounts for 18% of the total maintenance workload ~ 25%. The current price of computer hardware is declining. various types of system software have never been poor, and people often need to upgrade the system to improve the system hardware environment and operating environment; the constant changes in the external market environment and management requirements of enterprises also enable managers at all levels to constantly propose new information requirements. These factors will lead to adaptive maintenance work. The maintenance work should also be carried out in a planned and step-by-step manner like system development.
3. Excellent Maintenance
This is a modification made to expand functions and improve performance. It mainly refers to the addition of some features and performance features that are not specified in the system analysis and design phase for existing software systems. These functions are necessary to improve the system functions. In addition, it includes processing efficiency and writingProgramIn this respect, maintenance accounts for 50% of the overall maintenance work ~ 60%, a large proportion, is also an important aspect related to the quality of system development. In addition to planned and step-by-step maintenance, you must add relevant documents to the previous documents.
4. Preventive Maintenance
In order to improve the reliability and maintainability of application software, in order to adapt to future changes in the software and hardware environment, new preventive functions should be proactively added so that the application system can adapt to various changes without being eliminated. For example, you can change the dedicated report function to generate a general report to adapt to future report format changes. The maintenance workload accounts for about 4% of the total maintenance workload.

Let's talk about what I am doing and how to handle the problems raised by customers every day. We have a support team, but in addition to strong language skills, most of the other questions cannot be solved, looking at one problem after another every day, it's really strange that there are problems all over the world. I suddenly wondered whether I was development, maintenance, or support. I felt that I was (20% of development, 40% of maintenance, 40% of support ), the leaders said that this is to cultivate the language capabilities of our developers. Let's talk about whether your company is the same.