As the Spring Festival is coming, the new project has to start. The current tasks have two parts: the maintenance of the old system and the design of the new system. Because time is very tight, the manpower is not rich, so how to balance these two parts are critical. And for the design of the new system, there is a good technical reserve. There is a good technical guarantee for the implementation of the new project. Many things prepared for the new system need to choose in the maintenance stage of the old system. . I think, if the whole transition will be very smooth, but if it is not smooth, many programs or techniques should be re-defined.
Analyze the current old system, the main problem I think this point:
The design style is not uniform. The design is particularly serious, this is mainly because the project is time when the project is started is too nervous, and it is a simple module division. Personal written different frameworks according to their own modules, and organize it. Although there is a common abstraction, but Some modules are not completely turned over because they are more independent, so it is difficult to join some things. I have been considering whether I have to give them over. Also consider. There is also a typical part of
Query section. At that time, the system did not know how many times. Although the project is coming over, but it is said that there is no need to leave anything, so as a system that has a high requirements for the query. Say, how to put a query part of a common thing, the ideal state is AOP, it is a urgent task. With this, at least the control, performance of the paging, the processing of the log will be very perfect, and the maintenance is also very simple. Other also included
Logs, transactions, system management modules, performance counts need to be resolved.
interface style. Because the module is done, it is done from the previous one. The result is that the interface of the front desk is not the same in addition to the renewal of the background business logic. I especially envious of Java, J2EE, well-made a good architecture can be a good company, and each other. And .NET this kind of RAD is difficult to achieve such an effect, including itself, I also wrote a lot of Struts to get things, it is not practical, it is obviously violated .Net's original intention, so it is still from this point. Project management angle to control. I also hope that I have independent a person in the new system to do various interfaces, so you can maximize uniform and optimized strengths. But I have to consider that once the human is loses how to cultivate the second person. So in the transition stage of the new and old system, the old system has a new UI requirement, so I have to solve this unified problem from the mechanism. After all, if it is a pure subjective problem, whether it is a basic requirement of an architecture, so I am going to start from the UI and gradually reach the architecture. At present, the UI section I am preparing to abstract the interface elements used in the system, do some simple behaviors and features of the package, so that every interface element that uses is from one place, so unity will be affirmative. The cost of maintenance will be very small, and it is not easy to move.
Multi-language part. It should be said that many languages should be much, it should be said that it is very mature because there is no forced processing when the old system starts, which causses many tips to die in the system, and the terms are irregular. Therefore, it is a special vocabulary to collect in the concept of professional vocabulary.
