Title: Did not end up - Project Development Notes: How to facilitate business-oriented database how to connect
Keywords: distributed development C # project division-based object-oriented database design user interface
November 21: The new day begins again.
Then write yesterday. Now talk about business-oriented user interfaces and object-oriented databases should be connected in the framework.
First, let me define the business-oriented user interface to tell the organizational manner.
l Business-Oriented User Interface: User Operating System, often in a total of several large modules according to the system, and then the module has a specific business to organize. For example, in the system
n procurement module
u Mining purchase
u make a procurement plan
n sales module
u open sales
u settlement
l Object-oriented database design: When you look at it, the design of the database must be based on object-oriented design methods, with the XX paradigm. For example, there is a system
N institution table
N product table
N document table
Ok, if you get it on both sides, then you must link these two pieces (nonsense) in our system. Then how do I think about it on both sides?
First recall how I used to do it. When using the VC or VB writer, we may write directly from the interface to the logic of the database, the implementation of the design is to become from the interface to the database is a write-up mode writer (thinking about the head is also big, but fortunately now Don't write this). Further to Java hierarchical development, there are DataObject, BusinessObject, UI three, structural DataObject, and BusinessObject describe the Dongdong from the content, basically a database, which is an object package. Only when the interface layer is the package. It is not so complicated in Java hierarchy. For example, we will have a lot of different client implementations, these methods may be organized in different business methods; for example, I have written a small part of the framework and code automatic generation tool, the principle of automatic generation tool is The same part of the organizational structure can perform the same code file generation. To make it easy for people to divide (the code generating tool is back and then said to everyone). These all need to consider the interface between the unified relationships at the beginning.
Ok, there is a lot of rollers above. It is that I am talking about the department colleagues. The final conclusion is to make this separation in the Facade layer. Also organizes Business Rules or by object. FACADE organizes in a business manner. Facade's structured business in the interface is one or one, there is a sales business module will have a SalesbillFacade corresponding, and the rules and data tables are corresponding to the code generation, there is a salesbillTable. There is a SalesbillTableRules corresponding to. The corresponding modification principles on both sides is also defined by the partition of the business and objects. If you want to join the operation of the data object, such as queries, modify the data. It must be an additional approach to Business Rules, and then call to the database; if you want to join the business, you have to combine the settlement module in the sales order into a new settlement module, that adjustment should be The Facade layer is, others should not move. This is the principle.
The above is the cause of a principle used in my project, there is nothing necessary to constrain. Everything is a good idea can also be exchanged. The next section will write some things that are cranked after the summary, everyone can also see. (As long as you don't marry the mother! J)
