(02) Permission System Database General Plan

The followingMicrosoft SQL Server 2005For example,
The general permission section of the system starts with base _. When developing a project, you can directly import the data and modify the permission configuration as appropriate,
Otherwise, setting up demo data from scratch during each software development is also a very troublesome thing. There are many things that do not have much knowledge.
They are not intended, and they are not willing to take the test seriously.
The value of software products lies in the ability to reuse. Of course, the system architecture, permission module, test data, and demonstration data can also be continuously improved and optimized.
Something cool. Especially when developing a slightly larger software project, the organization and staff information is also very heavy.

The following part of the image is the applicationProgramFor example, a device management system starts with equipment.

Our company has thousands of employees and may have dozens of management systems. I don't know exactly how many sets of management systems we have. In fact, Maintenance Management
Such a multi-system is also a headache. If the data of every employee is input into so many management systems, the head will be big,
If a core data center can be created, other management systems will read the organizational structure and determine permissions from the system,
It is really ideal. Let's take a step back. The background management of these systems is the same, and the users are also very convenient to use.
A system can manage the back-end management of dozens of software. It is easy to train these maintenance personnel, and the system solves problems.
It's easy.
If the data needs to be imported to another system, it is simpler. Only one system is input, and other systems use data synchronization.
Function, You can import it to other systems.

If n multiple management systems developed by N companies are N * n, and the background database structure is roughly the same, these software systems are integrated,
It is feasible to reduce unnecessary troubles and concentrate on integrating the business module. If there are 1000 Software
Companies do not need to develop these modules, so they can develop their own business functions with peace of mind, which reduces unnecessary duplication.
Testing, maintenance, and optimization costs.

Developers who have just learned how to write software, as long as they carefully study this partCodeHow the data is written, how the software is structured
How should I configure and use the library design principles, permissions, and so on? How should the page program be combined with permissions and workflows?
This saves software companies a lot of trouble in training and getting started.

If several companies have partnerships or outsourcing relationships, this part of design and communication is also saved, and the compatibility theory will be good.
Yes.

Despite all these attacks, I feel that few people are interested in them, or these are not serious problems,
There are more problems to be solved than this. When your company has fewer employees and fewer management systems, it's better to have more people,
There are too many management systems on it, which can also be a headache for leaders, administrators, and operators. Although theoreticallyWindowsAD and other solutions
But how many developers are familiar with AD, can have a deep understanding of the AD permission system, and then
The permission system has been well developed on the ad. Companies are using less than a lot of AD, and there may be some problems. Don't lose bricks.

I have been developing software for 8 years. During the day, I develop software at night, during work, and at rest, I am also confused with cool people.
Communication and learning. This year, I feel that I have thoroughly understood the permissions. I am not confused, and I am completely clear. Even if you are very smart, I
I think it will take at least 8 months for you to understand. If I can provide a sound idea, it may take one month for you to fully understand the right.
Limits all management details.

I hope cainiao with similar capabilities can look at how to design applications with permissions.
Of course, you are welcome to give us more advice if you have profound accomplishments in this regard.

With permission management and workflow management, one person can do only a few things well.