to be used independently or in conjunction with each

[rifattryo.ut11]

What tool is suitable to use? It depends on your personal habits. The tool is not important. It is mainly this design idea. I usually use x to draw directly and do not completely follow the rules of -chart. How to confirm which are entities and which are not entities? I generally follow two principles. Principles: Entities are generally nouns rather than verbs and adjectives, and most of them are concepts that already exist in real business/life. For example, department staff, classroom teachers, order record videos, etc. are all entities, but sales department outstanding staff, classrooms, pending orders, short videos/long videos, etc.



are not entities. Principle: Entities must iran phone code be able value for users. For example, overtime scenarios can extend overtime rules, which can be used independently or in association with other entities to ultimately help users complete the productization of overtime rules, and overtime records, which can be used independently to help users record overtime behaviors. So are the more entities the better? Obviously not. If there are too many entities, maintenance costs will increase, usage efficiency will decrease, and user cognitive costs will increase.



It is consistent with the scope logic of managers. If the management radius is too large, the effect will definitely not be good. So how can we confirm whether to add a new entity or just treat it as an attribute of an entity? Principle: When its own independent attribute value contains attributes that will be expanded in the foreseeable future>=, it can be considered as an entity, otherwise try to treat it as an attribute of an entity. For example, the third solution does not treat the field card supplement as an independent entity but as an attribute of the attendance group because the number of independent attribute values ​​of the two is not enough to make it independent.