Software design includes system design and database design, a professional software engineering project data sheet is more than 100, some hundred. As a professional programmer, if you do not form a concept of data sheets, it will inevitably cause difficulties when programming. The key to solving the problem is to familiarize them, and they are familiar with them. With the progress of the project, business, logic, data gradually clear.
Information available for reference is generally a database design document, including ER diagrams. All associations in the data table are reflected in the ER diagram, and the programmer needs to understand the relationship between the tables, and the SQL code is required according to the service needs. These work look very simple, when the relationship between the table is increasing, it is not easy to understand and completely realize it.
In order to better understand the data sheet, it can be analyzed from the viewpoints of object-oriented and relational databases. Regarding the design of object-oriented analysis methods and relational databases, we can find considerable papers from the Internet. Designing a database while still speaking a map between the reality class and the stored table, the design of the database requires theory, experience and judgment. When programming, you should see the framework of the business system from the relationship between the data sheet, or combine the two to form a clear concept. "If you don't know how to ask for Friends, talk about how easy!
A typical business stream is a document forward. There is a survival cycle and state migration, which corresponds to a status field in its feature table. Different status decide to its own business position. At this time, the problem is coming, in addition to processing normal user operations, you have to make a correct response to all possible exception operations. Forcalable, sometimes it is more like a psychological war. When completing the code, it is like surgical surgery, and a pen is clear, the line is not useless.
The program enters the test period, and the test of business processes is cumbersome, complicated. If the bug measured at this time is that it is not easy to locate and correct it through multiple special steps. Of course, this is just relatively, any bug is gently wiped like a spider, as long as there is sufficient preparation in advance, such as is familiar with the data table, which is really important.
