What is the role hierarchy?
role hierarchy is the organizational term most commonly used in databases and computer security systems. Users have escalating roles that branch up as branches of the tree. Because system users are promoted through these roles. They will inherit other attributes, duties and related variable roles they accept without losing any of their attributes from their earlier role. The advantage is that it allows a simple organizational standard for designing databases and security permissions. The disadvantages come from the fact that often, individual roles, do not form into each other, forcing each other in the design of the system.
They imagine a snowball. As it proceeds, an increasing size accumulates without losing any original content. Before reaching the bottom of the hill or higher database level, it has expanded far beyond its original size. This is the basic concept of the role hierarchy.
For example, consider the hierarchy of roles of employees database. The most basic level of the database will be a table of employees that naturally contain every record of every person working in the company because they are all employees. Employees above can be a table of managers that could add other attributes, such as lists of employees that each manager oversees. However, the manager table will naturally be more exclusive; Because every manager is an employee, but not every employee is a manager. The role hierarchy table will continue to “run” in the shape of a pyramid, maybe add a table for branch managers, business managers, vice -chairmen, etc.
In terms of safety, the peak of the hierarchy would be an unlimited system manager that can make any adjustment or change the computer system. While the lowest would be a simple user who could only access a handful of programs without allowing any significant changes to make. INBoth cases - either a database or a security situation - the role hierarchy scheme allows efficient "upward bleeding", allowing the system to migrate from one position to another in a relatively linear format.
The disadvantage comes from complex organizations in which the attributes of one entity do not necessarily bleed to another. Consider the case where employees are promoted to the position of management after adheres to the role of programmers or human resources. Suppose the company prohibits the rules of the company to work as a programmer and human resource workers. Now, according to the role hierarchy structure, everyone in the managers table must inherit both the attributes of the programmer and the attributes of someone who works in human resources. This results in unnecessary space and zero attributes under the database, because no single manager will have both the attributes of the programmer and someone in human resources.