Will customer A have new coupon types and rules ws number list that need to be created in the future? What should other customers do if the fields of the coupon are different from A? In the future, there are new major customers who hope that the rule management of the coupon itself and the coupon production are two permissions. What should ws number list I do?
From this example, we can see that large companies ws number list have many and strong personal demands, and have very detailed requirements for the management granularity of function points. At the same time, the needs of customers may also be constantly adjusted with changes in the market . In this case, we need to abstract some ws number list functions into multiple ws number list layers, and only multiple layers can ensure more flexible configuration . For example, coupon templates and instances can be managed separately here, and the coupon template layer supports user-defined fields for configuration.
Of course, this case may not be very suitable for your ws number list own business, but the overall idea is that we need to obtain revenue through more leveraged products, so it is bound to push our products backward through multiple layers of abstraction and ws number list flexibility.