数据采集系统数据库建模_系统数据建模系列：身份管理系统-基本系统

数据采集系统数据库建模

Pretext and Context:借口和上下文：

In this series, I wish to design the data model of systems in question. I will start by defining the scope and boundaries of the system, followed by subsystems involved, then finally the entities in those systems and subsystems. System in question is either made up based on real-life experiences or something that I might have heard before somewhere. Scope and boundaries of the system will have the definition and the different functionalities and roles in that system.

在本系列中，我希望设计相关系统的数据模型。 我将首先定义系统的范围和边界，然后定义所涉及的子系统，最后确定那些系统和子系统中的实体。 所讨论的系统是根据现实生活中的经验构成的，或者是我之前可能在某处听说过的东西。 系统的范围和边界将具有定义以及该系统中的不同功能和角色。

Scope and Boundaries:范围和边界：

Identity Management System (IDM) is a system meant to manage the identity of users in external systems. Scope of managing the identity ranges from usual CRUD (create, update, retrieve and delete) to other activities like:

身份管理系统（IDM）是用于管理外部系统中用户身份的系统。 身份管理的范围从普通的CRUD（创建，更新，检索和删除）到其他活动，例如：

managing the user's role and permissions (basic CRUD)

管理用户的角色和权限（基本CRUD）

verifying user's permissions against an data entity or screen interface attributes

根据数据实体或屏幕界面属性验证用户的权限

Other features of the system are:

该系统的其他功能包括：

management is not based any variable like time, event, etc

管理不基于任何变量，例如时间，事件等

No work flow is involved; request for management, its review and approval is out of the scope.

不涉及任何工作流程； 要求管理，其审核和批准超出了范围。

No credentials required to use the system

不需要凭据即可使用系统

Entities in the System:系统中的实体：

Before I jump on to the entities in this system, let me specify (for the sake of clarity and better understanding) the different elements of the system

在转到该系统中的实体之前，让我指定（为了清楚和更好地理解）系统的不同元素

Equipment Elements: 设备要素：

Since the system in question is an automated one, and is expected to serve the IDM services to the requester, so an example of that could be a desktop application server waiting for the request to come and which will have all the necessary softwares and hardwares for the processing of request and its response.

由于所讨论的系统是自动化系统，并且有望为请求者提供IDM服务，因此，其中的一个示例可能是等待请求到来的台式机应用程序服务器，它将具有所有必需的软件和硬件。处理请求及其响应。

Personnel Elements: 人事要素：

Since the system in question is an automated one, there is no manual operator for this system. Also, the decision making will be done by the system as per the application logic based on the data-captured by the system. So, the decision making while being dynamic in nature (since it depends on requesters' inputs), will still be static in a way, since the logic to process those inputs will still be a static one.

由于所讨论的系统是自动化系统，因此该系统没有手动操作员。 而且，决策将由系统根据应用程序逻辑基于系统捕获的数据来完成。 因此，决策虽然本质上是动态的（因为它取决于请求者的输入），但它在某种程度上仍然是静态的，因为处理这些输入的逻辑仍然是静态的。

Information Storage Elements: 信息存储元素：

Data captured and used by the system will be stored in a database files for persistence and could also be available in the application server's memory based on the criticality of data and depends on when the data was last accessed for processing.

系统捕获和使用的数据将存储在数据库文件中以保持持久性，并且还可以根据数据的关键程度以及最后访问数据的时间进行处理而在应用程序服务器的内存中可用。

Data Elements 数据元素

Data elements are the entities involved in the system, and they will be described ahead in more details in the Data Modeling for the system section.

数据元素是系统中涉及的实体，它们将在前面的“系统数据建模”部分中更详细地描述。

Data Modeling for this system该系统的数据建模

I will derive the entities using a simple process.

我将使用一个简单的过程得出实体。

First, describe the entities and attributes captured by the system

首先，描述系统捕获的实体和属性

Second, describe the relation ship between these entities by describing the relationship entities

其次，通过描述关系实体来描述这些实体之间的关系船

Following are the different entities captured by the system以下是系统捕获的不同实体

1) User

1）用户

User entity has following attributes:

用户实体具有以下属性：

      a) User Id

a）用户编号

      b) User Name

b）用户名

2) Role

2）角色

Role entity has following attributes:

角色实体具有以下属性：

      a) Role Id

a）角色编号

      b) Role Name

b）角色名称

3) Permission_Group

3）Permission_Group

Permission Group entity is basically a logical grouping of the permission, so it has following attributes:

权限组实体基本上是权限的逻辑分组，因此具有以下属性：

      a) Permission Group Id

a）权限组ID

      b) Permission Id

b）权限ID

4) System

4）系统

Systems whose users' identity are going to be managed by IDM system has the following attributes:

其用户身份将由IDM系统管理的系统具有以下属性：

      a) System Name

a）系统名称

      b) System Id

b）系统编号

5) Entity

5）实体

An entity that belongs to a system and access to whome will be managed by the IDM system has the following attributes

属于系统并可以通过IDM系统管理whome的实体具有以下属性

      a) Entity Id

a）实体编号

      b) Entity Name

b）实体名称

6) Attribute

6）属性

An attribute that belongs to a Entity or an interface and access to whome will be managed by the IDM system has the following attributes

属于实体或接口以及对whome的访问权的属性将由IDM系统管理，该属性具有以下属性

      a) Attribute Id

a）属性编号

      b) Attribute Name

b）属性名称

7) Interface

7）界面

An interface (for example a User-Interface) that belongs to a system and access to whome will be managed by the IDM system has the following attributes

属于系统的接口（例如，用户界面）将由IDM系统管理对whome的访问，该接口具有以下属性

      a) Interface Id

a）接口ID

      b) Interface Name

b）接口名称

Following are the different relationship entities captured by the system以下是系统捕获的不同关系实体

1) User_Role

1）User_Role

User Role entity is the relationship entity between User and Role. It has the following attributes:

用户角色实体是用户和角色之间的关系实体。 它具有以下属性：

      a) User Id

a）用户编号

      b) Role Id

b）角色编号

2) Role_Permission_Group

2）Role_Permission_Group

Role Permission Group entity is the relationship entity between Role and Permission_Group. It has the following attributes:

角色权限组实体是角色和Permission_Group之间的关系实体。 它具有以下属性：

      a) Role_Id

a）角色编号

      b) Permission_Group_Id

b）Permission_Group_Id

3) Permission_System_Entity_Right

3）Permission_System_Entity_R 权

Permission System Entity Right is the relationship entity between permission group, System, and Entity. It gives a meaning to the permission id. It means that what kind of right does this 'Permission Id' has on the System's entity. It has the following attributes:

权限系统实体权限是权限组，系统和实体之间的关系实体。 它赋予了权限ID含义。 这意味着此“权限ID”对系统实体具有何种权利。 它具有以下属性：

      a) Permission Id

a）权限ID

      b) System Id

b）系统编号

      c) Entity Id

c）实体编号

      d) Right Type: It specifies the type of right on this relation. The 'Right' could be of type 'Write able', "read only', 'hidden', etc

d）权利类型：它指定此关系上的权利类型。 “权限”可以是“可写”，“只读”，“隐藏”等类型。

4) Permission_System_Entity_Attribute_Right

4）Permission_System_Entity_A ttribute_R 权

Permission System Entity Attribute Right is the relationship entity between permission group, System, Entity, and Attribute. It gives a meaning to the permission id. It means that what kind of right does this 'Permission Id' has on the Entity's attribute. It has the following attributes:

权限系统实体属性权限是权限组，系统，实体和属性之间的关系实体。 它赋予了权限ID含义。 这意味着此“权限ID”对实体的属性具有哪种权利。 它具有以下属性：

      a) Permission Id

a）权限ID

      b) System Id

b）系统编号

      c) Entity Id

c）实体编号

      d) Attribute Id

d）属性编号

      e) Right Type: It specifies the type of right on this relation. The 'Right' could be of type 'Write able', "read only', 'hidden', etc

e）权利类型：它指定此关系上的权利类型。 “权限”可以是“可写”，“只读”，“隐藏”等类型。

5) Permission_System_Interface_Right

5）Permission_System_Interfac e_Right

Permission System Interface Right is the relationship entity between permission group, System, and Interface. It gives a meaning to the permission id. It means that what kind of right does this 'Permission Id' has on the System's Interface. It has the following attributes:

权限系统接口权限是权限组，系统和接口之间的关系实体。 它赋予了权限ID含义。 这意味着此“权限ID”在系统界面上具有哪种权利。 它具有以下属性：

      a) Permission Id

a）权限ID

      b) System Id

b）系统编号

      c) Interface Id

c）接口ID

      d) Right Type: It specifies the type of right on this relation. The 'Right' could be of type 'Write able', "read only', 'hidden', etc

d）权利类型：它指定此关系上的权利类型。 “权限”可以是“可写”，“只读”，“隐藏”等类型。

6) Permission_System_Interface_Attribute_Right

6）Permission_System_Interfac e_Attribut e_Right

Permission System Interface Attribute Right is the relationship entity between permission group, System, Interface, and Attribute. It gives a meaning to the permission id. It means that what kind of right does this 'Permission Id' has on the Interface's attribute. It has the following attributes:

权限系统接口属性权限是权限组，系统，接口和属性之间的关系实体。 它赋予了权限ID含义。 这意味着此“权限ID”对接口的属性具有哪种权利。 它具有以下属性：

      a) Permission Id

a）权限ID

      b) System Id

b）系统编号

      c) Interface Id

c）接口ID

      d) Attribute Id

d）属性编号

      e) Right Type: It specifies the type of right on this relation. The 'Right' could be of type 'Write able', "read only', 'hidden', etc

e）权利类型：它指定此关系上的权利类型。 “权限”可以是“可写”，“只读”，“隐藏”等类型。

7) Permission_System_Right

7）Permission_System_Right

Permission System Right is the relationship entity between permission group, and System. It gives a meaning to the permission id. It means that what kind of right does this 'Permission Id' has on the system. It has the following attributes:

权限系统权限是权限组与系统之间的关系实体。 它赋予了权限ID含义。 这意味着此“权限ID”在系统上具有哪种权利。 它具有以下属性：

      a) Permission Id

a）权限ID

      b) System Id

b）系统编号

      c) Right Type: It specifies the type of right on this relation. The 'Right' could be of type 'Write able', "read only', 'hidden', etc

c）权利类型：它指定此关系上的权利类型。 “权限”可以是“可写”，“只读”，“隐藏”等类型。

This concludes the data-modeling design for the IDM. It has covered the master entities on which this system is based on. The 'Right type' attribute could also be foreign key taken from a 'Right' table which can have a name and Id. But, for the simplicity purpose such normalization is left out.

到此结束IDM的数据建模设计。 它涵盖了该系统所基于的主实体。 “权限类型”属性也可以是取自“权限”表的外键，该表可以具有名称和ID。 但是，为简单起见，省略了这种标准化。

翻译自: https://www.experts-exchange.com/articles/4457/System-Data-Modeling-Series-Identity-Management-System-Basic-System.html

数据采集系统数据库建模