After analyzing the product requirements, is it UML (including class diagram) for line design or database design first?
I designed the database first. UML usually draws a component diagram to show it. Usually, no class diagram is drawn, and the person in charge of the component draws it himself. Because the database model diagram can not only grasp the general picture of the project, but also grasp the general logical relationship through the setting of the relationship between fields and foreign keys, which is almost the same. As for the class diagram, it is too trivial, and the first Plans always fall behind changes, the second developer and your different thinking may be self-defeating, third, thinking too much and getting old too fast.