In the business process, it is best to determine the role, after all, there will be few and the most clear. Just in roles, don't ignore sysadmins. Only when the administrator grants job function email list each user permission can the entire process be smoothly completed. At the same job function email list time, parts that may have different schemes for each user can also be placed here, and different details can be distinguished through configuration. Existing configuration items, remember not to forget the default values.
The objects in the business process may be the job function email list most difficult to determine, there are inconsistent understandings, inconsistent naming, and inconsistent division of details and functions... The business process is to assist both parties in communication to reach a consensus understanding, and can make key information remarks on the object, as well job function email list as extended functional details. For example, placing an order itself contains information, and it needs to include
The order of who placed what product and how job function email list many quantities; the functions involved in placing an order include order generation, automatic job function email list cancellation, and payment reminder. In this way, although the other party does not understand the object of "ordering", it is very clear what to do in this area. (Hahaha, I was accidentally discovered by you, the name of this "ordering" is indeed a bit less rigorous. Hey, it's not like that, for the stability of the overall framework, a little error in the details does not affect ~~~