Forum Posts

nafiche 123
Jun 19, 2022
In General Discussions
From the requirements specification, we can get: There are three types of user roles: super administrator, business administrator, and HR. The operation objects executive email list are: departments, positions, personnel, and permission packages. Executable operations include traditional ones: adding, deleting, modifying, and checking, as well as the "association" executive email list related to this business, that is, the granting of permissions. What is the relationship between the various objects? We combine all the objects in pairs, and then delete the unrelated ones. That is: A post can be established under a department, but the post must be executive email list subordinate to the department Person must belong to a department Personnel must belong to a certain position Permission packages can be assigned to departments Permission packages can be assigned to positions There is no direct relationship between personnel and permission packages, executive email list which is also the core of this permission assignment This specific business logic is not important, and you don’t need to bother to understand it. What is important is that such a structured thinking method executive email list can be applied to various subsequent designs. The association between objects, combined with the characters and operations we just sorted out, can be reduced to a series of demand descriptions: [role] can be under [A object] [operation] [B object], for example: a super administrator can executive email list Add jobs under the department. So far, we have been able to establish [Requirement → Function Correspondence
What Is Important Executive Email List content media
0
0
3

nafiche 123

More actions