The first test of the iron community medical insurance project

In just over a month, a simple version has been developed to complete the main Medical Insurance process, including the holiday on October 1 and Saturday, in fact, the Project Creation Time is one month. This system is a big integrated system. What we do is a small subsystem, so far, this system can run. Some of the supplementary content about statistical analysis, data graphs, and so on has not been added last night. These functions may be implemented in the second edition.

Although the system has been submitted for testing and can run, there are still a lot of insights in the project. This project is involved in the preliminary database design and code implementation, consider where problems may occur and how to design them. Some problems are simple, but they deserve our attention in development.

1. Selection of implementation methods

Many times we can implement a function in several ways. Which method do you choose to implement, developers always want to use their own high-point implementations. This is just as understandable, in fact, from the perspective of users, they do not care about the technologies you use, what they really care about is the user experience, what they care about is the interface, and the interface is a channel for directly dealing with users. Therefore, it is not how advanced technology you are using that will make the product very good. Here is a simple example:

One interface in our system is to add data in batches. Each piece of data is an entity, that is, to add data in too many batches from the front-end. In our memory, we can look at the similar content in colleges and universities, the dwz framework encapsulates this function for us. You only need to follow the example given by dwz, if the front-end does not use the framework, we need to write a general method to solve this problem. This problem is actually a good solution. We can use arrays, each object has many fields and we use several arrays. This seems troublesome, but the idea is clear and simple, and there is also self-Writing Method injection. It is recalled that DRP has a similar implementation method, you have attempted to pass the value.

I think that if there are multiple implementation methods, if the project is not tight, you can try to use difficult methods. If the project is tight, you need to consider the time.

2. Insufficient execution

The initial stage of project creation is often slow and the execution is weak. When a task is assigned or another task is assigned, the project is not very anxious and there is no sense of urgency, leaders always say that they should look at the system and how the functions in the system are done before they are anxious to do so. These days are usually a few days of high efficiency. If the project has been properly allocated time, it should not lead to loose and tightness.

When working on projects, there will be serious overtime in the later stages, and the system will have to work overtime in a hurry, in the end, we have to work for a few days for a project, so we have to have a good rest over the past few days.

If you plan some details for the project in the early stage, there will be fewer bugs during the test, so you don't have to wait a few days.

3. Select database Field Type

General dictionary fields such as men and women, section chiefs, employees, etc. It is best to use strings. For example, if you want to use double type for money types, you also need to rounding to retain two decimal places, in our system, we often encounter type conversion errors when using database types. We cannot see which types are integer, long, complex, and double, when we design our own databases, we 'd better make some provisions or unify them so that later development and usage are convenient. After the first time, we have used hibernate ing to design database entities and table structures, the front-end can be implemented only after the background is designed. Otherwise, it is difficult to operate multiple data tables and the front-end is not flexible.

4. Foreground Style

We recommend that you unify the system foreground style when creating a small module in the early stage, saving the trouble of later modification. Now we need to unify the style of the debugging interface after the function is complete, we need to debug each interface and the style of each interface. It is better to unify it in the early stage. A good system design is far from a poor one.

5. Unified Front and back-end code

During development, sometimes the front-end and the back-end will be separated for writing. The advantage of separate writing is that the Code style in the system will be very uniform, and only the back-end will be written to the front-end and only the front-end, it is easy to maintain and read code. In a complicated and large business system, this write method is often used separately. This gives different people different advantages, if you are unfamiliar with database operations and SQL statements, you do not have to worry about development failures.

6. There are too many redundant fields in the database design.

In this system, there are a total of more than a dozen tables, and almost every table has many redundant fields. Some two tables have almost the same table structure and can be obtained by associating fields.

7. Employees

Formal employees here do not work very much, nor do they do it. They may develop such a habit in state-owned enterprises, no one is worried about the project if the team is not busy or the leaders are not busy with the project. Most people here are the personnel who maintain other systems, which is much easier than doing development, there are also a group of people who maintain 12306 of them here. Think about the development of 12306 servers we use nationwide, and 12306 is around us.

Most of the work is done by outsourcing personnel. Why do you say that outsourcing is more practical, so you have to do more work and solve problems, in this way, you have more opportunities to exercise and practice than others, and you have accumulated more things than others. Outsourcing has also been beneficial in the past few years. It is growing fast but tired, it depends on your choice.

8. Communication and communication

Communication and communication during project creation are often very important. When a project is created, you may encounter various problems and need to consult with a certain person. Therefore, the content of each person is different, even if you have different responsibilities, there will be business exchanges. It is impossible to do not communicate with each other in a project, when I was doing this, I also had some problems. If I had to discuss it with others, I was looking for someone to discuss it. Our group had a 211-Year-Old China Overseas Petroleum University, which is also a cool and very fond of learning, students who can be admitted to a good university have certain learning qualities and have a strong desire to take the initiative to learn. Otherwise, they will not be admitted to a good university.

In a project cycle, you need to deal with all types of personnel. In the early stage, you need to deal with project managers, directors, architects, and Technical Directors, after the project starts development, it mainly deals with managers and developers. Sometimes communication pushes forward the project, and gradually deepens understanding of some problems during communication with others, so as to understand the business.

Summary

This is another Java project. The first SSM framework is used. This is an SSH framework, which is easy to use and has gained a lot during the project, more is the perception at work. You need to try it at to learn about projects, communicate with others, and cooperate with everyone, in fact, what I learned most in my work is not technology, but how to cooperate with others at work. When I am working on a project, I better participate in it and communicate with others, I think this is the most learned thing. As for some technical knowledge, I have also deepened my understanding. The communication and communication technologies will be self-recognized, and the two will promote each other.

The first test of the iron community medical insurance project