Background product manager basic skills: field unification

Background product manager in the design of product structure, the most basic is form design, form is composed of a field. At the beginning of setting up the background page module, if the expansion design of the form is not taken into account, the problems of field disunity and data table storage will occur after background iteration.

What exactly is a form in backend product design? I’ve shared about form design before

Background products must go through a disaster, data structure table design

Before we design a form, we should know that the form follows the object, which I’ll use as a use case diagram

An object is a collection of forms, and I represent objects as people. For your convenience, an object is a concrete thing. This human object has ears, nose, hair, and so on. Such attributes are aggregated into an object.

For example, I have two objects. They are regular users and members. Take regular users and members for example. Background data will set up two sets of databases respectively to store member information and ordinary user information.

But the two must have the same fields, such as account, gender, age.

Because the object is different, there are different fields, membership level, user ownership….

Different objects will have different extended field designs in the future, resulting in the maintenance of the two tables being closely related to the product manager’s design of the table structure. In the background product design, I found that the previous background table structure, member field and user field conflict.

The two fields are the same, but stored in different table structures. Later to the member of the field query, will cause the query to the user table.

In the figure above, it can be seen that membership level and user table are two different tables, while order type, favorite table and brand table are all data forms written by development.

If a field in a member is not the same as a user field, but expresses the same field, data errors will occur.

For example, the two fields are the same data. However, it exists in the member and user forms, leading to the query of only one experience officer or experience engineer.

Therefore, background product manager basic skills, form design should always pay attention to field unity. Even if the object is different, the product manager must always comb through the business fields as the page and requirements overlap.

Well, that’s it for today’s share. I will write two original articles a week

Recommended reading: