[Business Knowledge] access control state

In the process of doing the project, all the basic business software modules, it is the turn around a core -

What kind of organization , through which flow (what kind of process information data ), what made things

 Organization : that is, different personnel. Here different people will have different roles, and the reason is that the distinction between roles: different rights, different operating functions (to do something different in reality).

Process: is literally a process, a series of operations . However, the process at the software level, there will always be a  message data as a carrier. Like the reality of leave, if you want to leave, you need to fill out the leave form (this document is an information carrier), then your supervisor to apply again until the TA approved (or denied permission to operate and so on). During this process, initiated [leave] and fill in the leave form, marking the competent [], [] in charge of this operation is a process.

Thing: going on here is simply more of the target achievement. Leave like the example above, you are in charge of you, leave through the process, it is to determine "whether you can leave."

In information technology products, we want to show a business, that is a different role , through different functional operation , the output of certain information results .

Usually a use case diagram, a software information to two points: 1, software who (roles). 2, software functionality (functional operation).

Permissions: functional scope of rights, a matter of scope and extent of decision-making. It is often used "has approved ...... rights matters" to express. For example, it has permission gift expenses within the approved budget of 5,000 yuan. 

Function: has a specific function , it can bring any effect. For example, the list display function is by implementing this feature, it allows users to see a list of information.

The roles and powers are sometimes intertwined, mainly because the authority is divided into

1. Functional-level permissions ( you can not do something )

2. Data-level permissions ( you can operate a range of things limit )

For example, the daily performance of the general staff with a view performance function, but may only limit the range of view of the TA itself.

 Function-level permissions mean you can not do something. Data-level authority is a range of things you can limit the operation.

For the function right, you can draw a cross similar to the following table, or in the development of this test, we are clear logic.


Control state, preferably using buttons, particularly with the kind of finite state. Each business object, the state of the basic current is unique, it will not be the case both A and B mode state.

 

Guess you like

Origin blog.csdn.net/ZYD45/article/details/93457673