Chapter 1 Preface
Compared with front-end design, I prefer to design background management system. If the front-end design tests the ability of empathy, then the design of the back-end management system tests the logical ability. The former needs to be considered from the user’s point of view, while the latter is considered from the manager’s point of view.
Fortunately, I participated in the design of many business systems of the company from "0-1", such as customer information middle platform system, small e-commerce applet, fixed asset management system, etc. These systems are undoubtedly designed independently from the front end to the back end. Although I am very satisfied with the sense of accomplishment, I am a little discouraged. After seeing the front-end functional modules, my friends and colleagues will all have an expression of "this is it?". After all, the products that serve the company's business can only be designed according to the company's development strategy. , In this way, under the premise that the front-end UI is mediocre, the function points are also mediocre, as if only the product and R&D know that the essence lies in the background design.
It is also mentioned in the previous articles that I have changed careers from technology, so I have my own methods and opinions on the design of the background management system. This is just a record. If there are any fallacies, please give me advice.
Chapter II Project Overview
2.1 Project Background
The company's business includes sales of software, sales of hardware, sales of services, etc. Different business departments are responsible for selling different products , one of which is the sales business of training courses ( free and paid) launched by business department A , which is now vigorously promoted by major companies. Informatization and paperless office, the company is no exception. It wants to have a small program to help various business departments sell the company's products, including training courses.
2.2 Project Requirements
- Need a small program to sell company products;
- Business departments can list paid/free courses through the background;
[The author has something to say: the actual business is more complicated than this, such as managing orders, distributing coupons, managing students’ class status, etc., and there are more than these types of roles. Here we take one of the product management processes as an example]
Chapter Three Scheme Design
"Object-oriented" is a very interesting subject, so after I get the requirements, I start from the objects and conduct a brief analysis, what roles are there in the requirements, and what each role does, so as to determine the subject and the relationship between the subjects , the subject can help us analyze the table fields, and the relationship between the subjects can help us establish the relationship between the tables, thereby determining the functional module, and output the prototype diagram according to the functional module.
3.1 Demand Analysis
Combined with the project background and needs, the following conclusions can be drawn:
- The company has many business units;
- Each business department puts products belonging to its own department on the shelves;
- Products include courses, hardware, software, services, etc.;
- There are paid and free courses;
3.2 Analysis subject
When analyzing the subject, it is recommended to use the ER diagram , that is, the entity relationship diagram. The ER diagram can clearly see the fields of the subject and the one-to-one or one-to-many relationship between subjects. As mentioned earlier, the relationship between subjects can help us determine functional modules .
From the demand analysis, it can be seen that the subjects include companies, business departments, products, courses...
- A company with multiple business units
- Business Units Contain Multiple Commodities
- For business department A, the product is the course
Therefore, the company and the business department have a 1:n relationship, the business department and the product have a 1:n relationship, and the product and the course have a 1:1 relationship
3.3 Product structure
The background management system is inseparable from the management of the main body. With the ER diagram, you can use the mind map to sort out the product structure
There is a term among programmers called " decoupling ", that is, to reduce the relationship between modules, so each subject is used as an independent management module, which is convenient for business development, operation and maintenance in the future
According to the association relationship of the ER diagram, in the field of the included subject management module, there must be the subject id containing it
For example: if the product contains courses, then in the course management table, there needs to be a product id to establish a perfect relationship
Some friends may be confused, since there is a 1:1 relationship between products and courses, why not manage courses directly in the product management office
As mentioned earlier, there are free and paid courses, and the price is an attribute of the product. Course-related products need to be paid, and unrelated products are free. In addition, products are not only courses, but also hardware and software. Independent management Commodities and courses can be decoupled to the greatest extent.
3.4 Prototyping
3.4.1 Company management
3.4.2 Business department management
3.4.3 Commodity Management
3.4.4 Course Management
Chapter 4 Summary
Although this process is only a small business, it also uses object-oriented thinking and ER diagrams to solve problems. It's over, and I don't have much to say, so I wish you all peace and joy.