What is a conceptual scheme?

The conceptual scheme is a design model used for planning or visually representing the structure of the information contained in the database or other entity of the computer system. It affects specific entities in the system, along with their attributes and relationships between different entities. The purpose of the conceptual scheme is to provide the order of a higher level of the computing system. Computer systems in large organizations are so complicated that they require this type of macro-management to maintain them properly and efficiently.

You want to visualize the conceptual scheme, imagine a number of squares. Each square represents an entity table in the structure of the system, such as employees, current employees, projects, payscale, etc. These entities are arranged from top to bottom and connected with lines depending on relations and associations. For example, the table of current employees will be a naturally related subset of the employee table, so that Curtabulka rental of employees will vertically ventilate from the table of employees. On the contrary, tAbulka projects and Payscales will be related to the table of current employees, because each current employee will, as a result, receive a paycheck and work on one or more projects, these tables will be horizontally branching from the table of current employees.

In addition to elaborating the basic relationships between entities, the conceptual scheme can also describe the parameters that must be met in the system. These are rules specific to the organization implemented for enforcement of the order in the system. For example, the specification that each current employee must also exist in the employee table, or specify that each current employee must have at least one but no more than three projects. By implementing these rules at the proposal level, the company ensures that it cannot be violated in the system.

This structure allows the system designers to immediately understand different parts and subsystems afterCounter network. The ultimate result is that the changes in the system are easier to introduce, as it is obvious which entities related will be influenced by the adjustment of specific entities in the system. The continuation of the previous example of a dependent relationship between employees and current employees is clear that any changes in employees' entity will naturally affect the current entity of employees.