Quality information management system development problem
The quality information management system is a set of B / S applications developed by Swinglet as a B / S using Java language. During this year, during the system development, the basic framework and code writing method of the quality system have become more uncomfortable, and many practical issues are facing in the development process. This document only makes a summary on issues that occur during the current development process.
One. Unmanned upgrade maintenance
The Swinglet framework is very early, like a framework of the Java community, is an open source project, open source code, and users can use it at will, and then the Swinglet framework has gradually faded out the historical stage, the frame is in one. No one upgrade, such an embarrassment of unmanned maintenance. As a company, for the development project, it should neither chase new technologies, and should not be too conservative, and should choose very mature technology at the time, and gradually add new things, step by step. For this framework, there is currently no maintenance. The version of servlet.jar it must use is very low, and now the servlet.jar version has been updated to 3.0 or more, how is the downward compatibility of the version, there is a problem, this They are all unknown, and there are Tomcat servers closely related to servlet.jar; in addition, the old version of Servlet.jar continues to use new features in the new version. If you continue to use a Swinglet Framework in the project, then the company must upgrade and maintain its framework. If the current situation is concerned, it will not be lost.
two. Expedition is immature
Swinglet is actually packaged for servlets, but Swinglet's package is a servlet package, in essence, there is no reason to develop the old servlet program, but the Swinglet after the package makes us in writing procedures When you don't need to be as cumbersome when developing a servlet program, you don't need to print the HTML language to the page again, because all Swinglet has been packaged for us, but in fact, Swinglet has made it originally The things done on the page add to the complexity development of server-side program development. On the other hand, the Swinglet framework has also proposed an idea that affects later technology development - "server-side control", but this technology is not good in Swinglet, there are many frames to absorb this idea, in specific Implementing better, especially MS .NET, which is very good for programmer-oriented visual event driver development and server-side controls, can be said, truly reaching the Swinglet what I want to do, and no Do something.
three. Lack of information
Based on the first two reasons, there is naturally a shortage of information. A year ago, when you just join the quality project group, you can say that you don't understand Swinglet, almost completely searching for any point on Swinglet on the network, which can be said to have a painful. The lack of information and the difficulty of learning and in-depth, but from another aspect, a framework that is in unrequited upgrade, has fallen out of the historical stage, whether it is necessary to conduct in-depth research, I I think this problem is worth discretion.
four. Scalability difference
A excellent framework should have good scalability, accepting new things at any time, only such a framework has a strong vitality to continue to develop, mature and improve. Unfortunately, the Swinglet framework does not have this ability. During the development of quality system, especially in the development of the 9 quality system, I have thought that I have gradually added some mature things, just, I don't find the entry point. Fives. System performance and security
This is a system-level issue.
1. Swinglet is the management method of the user, and each user is allocated, the large amount of information owned by users, users, and users is placed. Threadlocal has proven to be very consuming, it is not recommended, while the core part of Swinglet is operating in this way, and consequences are low system performance, which is very easy to cause numerous complications. On the other hand, the idea of the Swinglet framework is to give almost all things to the server to run, like the JSP JavaBean's way, it will be too extreme, and it will affect the system performance while developing.
2. Safety includes many aspects, here is only elaborated in concurrent control and related issues. For concurrent operation Swinglet does not seem to be considered, and this system-level problem, as our application software development company, there is no need to put too much experience is above, because there are many ready-made things, it has already made the foundation for us. What we have to do is brought to brought or use it, mention concurrent mechanisms, you have to talk about data synchronous updates and data caching mechanisms, in these two points, Swinglet is also doing well, if you want the application Developers are perfect on the basis of the original framework and violate the original intention of the original selection framework. The workload is huge.
six. Flexibility
The Swinglet framework is written on the page is strong intrusion, and must be written in the rules required by the framework. The entire page is almost all written modes based on Swinglet rules. It is very common to join some other things on the page. For example, if you want to join a JavaScript, what you want to do is Complex.
Seven. Counted
In the quality information management system:
First, the data layer, the logic layer, and the performance layer are very large, and the developer is entangled in almost every day in the maze of the performance layer, the logic layer, and the data layer, after compiling the back desk Class, can see the performance layer The page is displayed, and this is also determined by the congenitality of Swinglet;
Furthermore, the connection between the class is also complicated, the coupling is very large, often touches a place, causing a series of chain reactions.
I think the high coupling is the situation that is not wanting to see in any software development, but the actual situation is like this.
Eight. Low development efficiency
Finally, I want to talk about the problem of development efficiency, and put this kind of problem related to programmers and companies in the last talk, because the factors affecting development efficiency are multi-faceted, so I want to Talk about the development efficiency when you talk about other factors.
1. The framework used by the project is unmanned and maintained. In the development, only the old development method is always used, which will inevitably affect the efficiency of development.
2. The framework used by the project is immature. During use, application software developers consciously or unconsciously go to maintain the frame, and this maintenance is unconscious, uncomfortable, this result is increasing framework Unstable, the development efficiency will be lower and lower. 3. Technical data is scarce, I think this is not much more about the impact of development efficiency.
4. The scalability is poor, many very good things can't be introduced, give an example, maybe after another maturity technology, some functions, only a few code can be completed, but the consequences that cannot be introduced are, need to write hundreds of people. Even thousands of lines of code, the code we wrote this, whether it is efficient or reused technology, and also reduces the efficiency of development.
5. System performance and system security, it should be we must consider, but do not need our implementation, because as application software developers, only need a comprehensive evaluation and analysis of the performance and security of the application software, then determine adoption What framework or technology, the problem can be solved, but unfortunately, the current quality of the Swinglet framework has no advantage in performance, which is almost completely considering in security, which makes the application software developers have to stop, To do system-level things, affect software development efficiency.
6. Among the development process, the result of the flexibility difference caused by the Swinglet framework for pages is that developers are developing in order to achieve a small function, while being tired of trivial and complicated rules. The impact of efficiency is also obvious.
7. The coupling between the various classes of the software module is large, causing a chain reaction while developing and modifying the code, and commissioning special time, and serious affecting the development efficiency.
8. Due to the urgency of the lack of information, the developer's control for Swinglet framework is not enough, and the packaged born has many shortcomings. Now we will continue to maintain the rules set when writing these classes during development. On the basis of these classes, more classes are written, but in these rules, or development models, there have been many seriously affected the efficiency of development. When the function of the program is constantly perfect, the amount of code has grown rapidly, and the code complexity has grown in geometric multiple, so that a large code amount and code complexity are huge.
Software, maintenance difficulty will be difficult to estimate.
These are some experiences in the development framework, programming mode, and development status I use in the current quality system.
