CN113327002A - Method and device for constructing data asset management model - Google Patents
Method and device for constructing data asset management model Download PDFInfo
- Publication number
- CN113327002A CN113327002A CN202110409871.9A CN202110409871A CN113327002A CN 113327002 A CN113327002 A CN 113327002A CN 202110409871 A CN202110409871 A CN 202110409871A CN 113327002 A CN113327002 A CN 113327002A
- Authority
- CN
- China
- Prior art keywords
- business
- unit
- role
- participant
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000004590 computer program Methods 0.000 claims description 18
- 230000008520 organization Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 7
- 238000010276 construction Methods 0.000 claims description 6
- 238000007726 management method Methods 0.000 abstract description 42
- 230000009286 beneficial effect Effects 0.000 abstract description 3
- 238000013523 data management Methods 0.000 abstract description 2
- 230000000694 effects Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000013499 data model Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000007423 decrease Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/067—Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention is suitable for the technical field of data management and provides a method and a device for constructing a data asset management model, wherein the method comprises the following steps: acquiring a service role and a service entity based on service requirements; inputting the service role and the service entity into a data asset field model to obtain an incidence relation between the service role and the service entity; and constructing a data asset management model based on the service role, the service entity and the incidence relation between the service role and the service entity. The data asset management model obtained by the invention can completely express the association relation between the complex business roles and the business entities, can be used as a tool for helping system analysts and users to know the real business, is beneficial to the business analysts to analyze the core data assets of the company, and improves the core data asset management effect.
Description
Technical Field
The invention belongs to the technical field of data management, and particularly relates to a method and a device for constructing a data asset management model.
Background
Large traditional enterprises (e.g., the energy industry) typically include many subsidiaries, each of which has its own core data assets. When the core data assets are managed, due to the fact that a tool for helping system analysts and users to know real services is lacked, the service analysts do not analyze the core data assets of a company sufficiently, and therefore the core data assets are managed poorly.
Currently, in order to manage data assets, a data model is usually used to describe the relationship between various entities when planning a project so as to show the relationship between real-world things. However, the data model can only express the association relationship between simple business roles and business entities, and cannot express the association relationship between complex business roles and business entities.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for constructing a data asset management model, so as to solve a problem that a model in the prior art cannot express an association relationship between a complex business role and a business entity.
In a first aspect of the embodiments of the present invention, a method for constructing a data asset management model is provided, including:
acquiring a business role and a business entity based on business requirements, wherein the business role comprises an individual participant and an enterprise participant;
inputting the service role and the service entity into a data asset field model to obtain an incidence relation between the service role and the service entity;
and constructing a data asset management model based on the service role, the service entity and the incidence relation between the service role and the service entity.
In a second aspect of the embodiments of the present invention, there is provided a device for constructing a data asset management model, including:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a business role and a business entity based on business requirements, and the business role comprises a personal participant and an enterprise participant;
the association module is used for inputting the business role and the business entity into a data asset field model to obtain an association relation between the business role and the business entity;
and the construction module is used for constructing a data asset management model based on the business role, the business entity and the incidence relation between the business role and the business entity.
In a third aspect of the embodiments of the present invention, a terminal device for constructing a data asset management model is provided, including: the data asset management model building method comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to realize the steps of the data asset management model building method.
In a fourth aspect of embodiments of the present invention, there is provided a computer-readable storage medium, including: the computer readable storage medium stores a computer program which, when executed by a processor, implements the steps of the above-described method of constructing a data asset management model.
Compared with the prior art, the embodiment of the invention has the beneficial effects that at least: the method comprises the steps of inputting a business role and a business entity into a domain model, obtaining an incidence relation between the business role and the business entity, and constructing a data asset management model based on the incidence relation between the business role and the business entity. Therefore, the association relation between the complex business roles and the business entities can be expressed.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a schematic diagram of a process flow of a method for constructing a data asset management model according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a data asset domain model in a method for constructing a data asset management model according to an embodiment of the present invention;
FIG. 3 is another exemplary diagram of a process for building a data asset management model according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an apparatus for constructing a data asset management model according to an embodiment of the present invention;
FIG. 5 is another schematic diagram of an apparatus for constructing a data asset management model provided by an embodiment of the present invention;
fig. 6 is a schematic diagram of a terminal device according to an embodiment of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.
In order to explain the technical means of the present invention, the following description will be given by way of specific examples.
Large traditional enterprises (e.g., the energy industry) typically include many subsidiaries, each of which has its own core data assets. When the core data assets are managed, due to the fact that a tool for helping system analysts and users to know real services is lacked, the service analysts do not analyze the core data assets of a company sufficiently, and therefore the core data assets are managed poorly.
To manage data assets, one way is to employ a data model to describe relationships between various entities to reveal relationships between real-world things. However, the data model can only express the association relationship between simple business roles and business entities, and cannot express the association relationship between complex business roles and business entities.
A Domain Model (also called a Business object Model) is an abstraction of how business roles and business entities should be related and collaborated to perform a business, which determines the static and dynamic relationships business people should have with the objects they handle and use (business classes and objects). Therefore, the domain model can describe the association relationship between the complex business roles and business entities involved in the business, and help the demand analyst of the company to better understand the core data assets, thereby realizing better management.
The domain model focuses on analyzing the problem domain itself, exploring important business domain concepts, and establishing relationships between the business domain concepts. The domain model is composed of the following elements: (1) the service role displays a series of responsibilities assumed by a person; (2) business entities, business entities representing deliverables, resources and events that are used or generated; (3) the business case shows a collaborative business role and how a business entity executes a certain workflow; (4) the diagram shows participating business roles and business entities.
Based on the above, the embodiment of the present invention provides a method for constructing a data asset management model, in which an acquired service role and a service entity are input into a pre-constructed data asset field model to obtain an association relationship between the service role and the service entity, and a data asset management model is constructed based on the association relationship, and the constructed data asset management model can express the association relationship between a complex service role and the service entity.
Fig. 1 is a schematic flow chart of a method for constructing a data asset management model according to an embodiment of the present invention. As shown in fig. 1, the method comprises the steps of:
step S11: and acquiring a business role and a business entity based on business requirements, wherein the business role comprises an individual participant and an enterprise participant.
For example, based on the specific requirements set by the user, it is determined which business roles and business entities are needed, and the determined business roles and business entities are recorded. Where a business participant refers to a business employee and an individual participant refers to a non-business employee.
Step S12: and inputting the service role and the service entity into a data asset field model to obtain the incidence relation between the service role and the service entity.
In this embodiment, the data asset domain model may be a pre-constructed domain model, and since the data asset domain model includes an association relationship between a service role and a service entity, after the service role and the service entity are input, the data asset domain model performs parsing on the service role and the service entity, so as to obtain the association relationship between the service role and the service entity.
In this embodiment, the data asset domain model includes a participant module and a business entity module, where the participant module corresponds to a business role and the business entity module corresponds to a business entity. Fig. 2 is a schematic diagram of a data asset domain model according to an embodiment of the present invention. As shown in fig. 2, the embodiment of the present invention expresses the data asset domain model as a service role-service entity-foreign key, thereby expressing the service role relationship as a service role-relationship-service entity, defining the service role and the service entity as a vertex, and defining the relationship between the two service roles as an edge (i.e., foreign key).
The participant module includes a participant information element (i.e., a participant), an individual participant element (i.e., a physical person), and a business participant element (including businesses and social groups), both of which are associated with the participant information element. In addition, a database, namely a tenant, is associated with the participant information and plays a role in data isolation protection for protecting the participant information module.
The participant information element includes at least one of the following information: participant ID, participant name, participant type, participant code, participant identity. Preferably, the participant information element includes a participant ID, a participant name, a participant type, a participant code, and a participant identity.
The personal participant unit includes at least one of the following information: natural person code, identification card number, name, gender, ethnicity, date of birth, cell phone number and mailbox. The identification card number and the mobile phone number can be used as unique identification of the individual participant. Optionally, when the participant is an individual participant, that is, a natural person, the individual participant information corresponds to the natural person information one to one, the unique identifier of the natural person is an identity card, and the participant can be bound with the natural person after being authenticated. Preferably, the individual participant unit includes a natural person code, an identification number, a name, a gender, a ethnicity, a date of birth, a cell phone number, and a mailbox.
The enterprise participant unit includes at least one of the following information: enterprise code, social Unicode, enterprise name, country, province, city, county, and detailed address. Wherein the social Unicode can serve as a unique identifier for the enterprise participant. Preferably, the enterprise participant units include enterprise code, social Unicode, enterprise name, country, province, city, county, and detailed address.
The business entity module includes at least an employee unit and an organizational structure unit, both of which are associated with the enterprise participant unit, and a participant information unit is associated with the employee unit.
Specifically, an employee unit (i.e., employee) includes at least one of the following information: employee ID, employee code, name, phone number, mailbox, status, enrollment date, departure date, natural person ID, and business participant ID. Employees are people under the organization, and the IDs of employees and natural people can be bound, one employee for each natural person. Preferably, the employee unit includes an employee ID, an employee code, a name, a phone number, a mailbox, a status, an enrollment date, an retirement date, a natural person ID, and a business participant ID.
The organizational structure unit (i.e., organizational structure) includes at least one of the following information: root organization ID, organization code, affiliated participant ID, status, and parent organization ID. Preferably, the organization structure unit includes a root organization ID, an organization code, a participant ID of the organization, a status, and a parent organization ID.
Furthermore, the business entity module also comprises an account unit, a role unit, a permission unit, a resource unit and an application unit.
An account unit (i.e., an account) includes at least one of the following information: account ID, participant ID, account name, password, bound phone number, and bound email. The account numbers may be one-to-one with natural people. Preferably, the account unit comprises an account ID, a participant ID, an account name, a password, a bound mobile phone number and a bound email, so that the account unit information is more complete.
The character unit (i.e., the character) includes at least one of the following information: organization ID, role code, role name, role type, role release status, and description. Preferably, the role unit includes an organization ID, a role code, a role name, a role type, a role issuance state, and a description.
The rights unit (i.e. rights) includes at least one of the following information: authority ID, belonged application system ID, authority name, authority issuing state and authority description. Preferably, the permission unit includes a permission ID, an ID of an application system to which the permission belongs, a permission name, a permission issuing state, and a permission description.
The resource units (i.e. resources) at least comprise page resource subunits (i.e. page resources), API resource subunits (i.e. API resources) and data dictionary resource subunits (i.e. data dictionary resources), and the resource units are associated with the authority units, the authority units are associated with the role units, the role units are associated with the account units, and the authority units and the resource units are associated with the application units. Preferably, the resource units include a page resource sub-unit (i.e., a page resource), an API resource sub-unit (i.e., an API resource), and a data dictionary resource sub-unit (i.e., a data dictionary resource).
Wherein the page resource sub-unit at least comprises one of the following information: resource ID, resource code, resource type, resource name, component type, parent resource ID, and description. Preferably, the page resource sub-unit includes a resource ID, a resource code, a resource type, a resource name, a component type, a parent resource ID, and a description.
The API (Application Programming Interface) resource subunit at least comprises one of the following information: resource ID, Resource code, Resource type, Resource name, description, and url (Uniform Resource Locator). Preferably, the API resource sub-unit includes a resource ID, a resource code, a resource type, a resource name, a description, and a url.
The data dictionary resource sub-unit at least comprises the following information: the application system ID. Of course, in other embodiments, the data dictionary resource sub-unit may also include other information, which is not limited herein.
An application unit (i.e. application system) comprising at least one of the following information: application ID, application code, application name, description, and prime number participant ID. Preferably, the application system includes one of the following information: application ID, application code, application name, description, and prime number participant ID.
Step S13: and constructing a data asset management model based on the service role, the service entity and the incidence relation between the service role and the service entity.
The association relationship between the business role and the business entity acquired by the embodiment of the invention can embody the complex association relationship between the business role and the business entity, so that the data asset management model constructed by combining the business role and the business entity can completely express the complex association relationship between the business role and the business entity, can be used as a tool for helping system analysts and users to know real business, is beneficial to analyzing the core data assets of a company by the business analysts, and improves the core data asset management effect.
In one embodiment, when a data asset management model needs to be constructed according to a plurality of service roles, service entities and association relations, the association relations between all the service roles and the service entities need to be obtained first, and then the data asset management model needs to be constructed according to the obtained association relations and the service roles and the service entities corresponding to the obtained association relations. Referring to fig. 3, after the step S12, the method further includes:
step S20: and judging whether to add the service role or not.
In the process of building a data asset management model, a plurality of business requirements are usually involved, and each business requirement corresponds to different business roles and business entities. Business roles may also vary within an enterprise, requiring corresponding increases or decreases in business roles according to specific business needs. Therefore, after the service role, the service entity and the corresponding association relation are obtained according to the current service requirement, it needs to be determined again whether the service role needs to be added.
If the service role needs to be added, returning to the step S11, so as to continue to acquire the service role, the service entity and the association relationship.
If the service role does not need to be added, step S13 is performed, and a data asset management model is constructed according to the obtained plurality of service roles, service entities and the association relationship corresponding to each service role and service entity. The embodiment of the invention flexibly increases the number of the service roles, the service entities and the incidence relations after judging whether the service roles are needed or not, thereby reflecting the incidence relations between the complex service roles and the service entities in the data asset management model.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Based on the same inventive concept, the embodiment of the invention also provides a device for constructing the data asset management model. Fig. 4 is a schematic diagram of a data asset management model building device according to an embodiment of the present invention. As shown in fig. 4, the construction apparatus of the data asset management model includes an acquisition module 31, an association module 32, and a construction module 33. The obtaining module 31 is configured to obtain a service role and a service entity based on a service requirement, where the service role includes an individual participant and an enterprise participant. The association module 32 is configured to input the service role and the service entity into a data asset domain model, and obtain an association relationship between the service role and the service entity. The construction module 33 is configured to construct a data asset management model based on the service role, the service entity, and the association relationship between the service role and the service entity.
Further, fig. 5 is another schematic diagram of a data asset management model building apparatus according to an embodiment of the present invention. The device for constructing the data asset management model provided by the embodiment of the invention further comprises a judging module 40, wherein the judging module 40 is used for judging whether to add the business role or not.
Fig. 6 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 6, the terminal device 6 of this embodiment includes: a processor 60, a memory 61, and a computer program 62, such as a data asset management model building program, stored in the memory 61 and operable on the processor 60. The processor 50, when executing the computer program 52, implements the various steps in the above-described method embodiment of building a data asset management model, such as steps S11-S13 shown in FIG. 1. Alternatively, the processor 50, when executing the computer program 52, implements the functions of each module/unit in each device embodiment described above, for example, the functions of the modules 31 to 33 shown in fig. 4.
Illustratively, the computer program 62 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 60 to implement the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 62 in the terminal device 6.
The terminal device 6 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The construction terminal 6 may include, but is not limited to, a processor 60, a memory 61. Those skilled in the art will appreciate that fig. 6 is merely an example of a terminal device 6, and does not constitute a limitation of the terminal device 6, and may include more or less components than those shown, or combine some components, or different components, for example, the terminal device 6 may also include an input-output device, a network access device, a bus, etc.
The Processor 60 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6. The memory 61 may also be an external storage device of the terminal device 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the terminal device 6. The memory 61 is used for storing the computer programs and other programs and data required by the terminal device 6. The memory 61 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
1. A method for constructing a data asset management model is characterized by comprising the following steps:
acquiring a business role and a business entity based on business requirements, wherein the business role comprises an individual participant and an enterprise participant;
inputting the service role and the service entity into a data asset field model to obtain an incidence relation between the service role and the service entity;
and constructing a data asset management model based on the service role, the service entity and the incidence relation between the service role and the service entity.
2. The method of claim 1, wherein the data asset domain model comprises a participant module and a business entity module, the participant module corresponding to a business role, the business entity module corresponding to a business entity;
the participant module includes a participant information unit, a personal participant unit, and a business participant unit, the personal participant unit and the business participant unit each associated with the participant information unit;
the business entity module includes at least an employee unit and an organizational structure unit, the employee unit and the organizational structure unit both being associated with the enterprise participant unit, and the participant information unit being associated with the employee unit.
3. The method of claim 2, wherein the business entity module further comprises an account unit, a role unit, a privilege unit, a resource unit, and an application unit;
the resource unit is associated with the authority unit, the authority unit is associated with the role unit, the role unit is associated with the account unit, and the authority unit and the resource unit are associated with the application unit.
4. The method of constructing a data asset management model according to claim 2, wherein said participant information element includes at least one of: participant ID, participant name, participant type, participant code, and participant identity;
the personal participant unit includes at least one of the following information: natural person code, identification card number, name, gender, ethnicity, date of birth, cell phone number and mailbox;
the enterprise participant unit includes at least one of the following information: enterprise code, social unified credit code, enterprise name, country, province, city, county, and detailed address;
the employee unit includes at least one of the following information: employee ID, employee code, name, phone number, mailbox, status, enrollment date, departure date, natural person ID, and business participant ID;
the organizational structure unit includes at least one of the following information: root organization ID, organization code, affiliated participant ID, status, and parent organization ID;
the account unit at least comprises one of the following information: account ID, participant ID, account name, password, bound mobile phone number and bound email;
the role unit at least comprises one of the following information: organization ID, role code, role name, role type, role release state and description;
the privilege unit includes at least one of the following information: authority ID, belonged application system ID, authority name, authority release state and authority description;
the application unit includes at least one of the following information: application ID, application code, application name, description, and affiliated participant ID.
5. The method of constructing a data asset management model according to claim 4, wherein said resource elements comprise at least a page resource sub-element, an API resource sub-element and a data dictionary resource sub-element.
6. The method of constructing a data asset management model according to claim 5, wherein said page resource sub-unit comprises at least one of the following information: resource ID, resource code, resource type, resource name, component type, parent ID, and description;
the API resource sub-unit includes at least one of the following information: resource ID, resource code, resource type, resource name, description, and url;
the data dictionary resource sub-unit at least comprises the following information: the application system ID.
7. The method for constructing a data asset management model according to claim 1, wherein before the step of constructing a data asset management model based on the business roles, the business entities, and the association relationship between the business roles and the business entities, the method further comprises:
judging whether a service role is added or not;
if the service role needs to be added, returning to the step of acquiring the service role and the service entity based on the service requirement;
and if the business role does not need to be added, constructing a data asset management model based on the business role, the business entity and the incidence relation between the business role and the business entity.
8. An apparatus for constructing a data asset management model, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a business role and a business entity based on business requirements, and the business role comprises a personal participant and an enterprise participant;
the association module is used for inputting the business role and the business entity into a data asset field model to obtain an association relation between the business role and the business entity;
and the construction module is used for constructing a data asset management model based on the business role, the business entity and the incidence relation between the business role and the business entity.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor when executing the computer program implements the steps of the method of constructing a data asset management model according to any of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110409871.9A CN113327002A (en) | 2021-04-16 | 2021-04-16 | Method and device for constructing data asset management model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110409871.9A CN113327002A (en) | 2021-04-16 | 2021-04-16 | Method and device for constructing data asset management model |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113327002A true CN113327002A (en) | 2021-08-31 |
Family
ID=77414800
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110409871.9A Pending CN113327002A (en) | 2021-04-16 | 2021-04-16 | Method and device for constructing data asset management model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113327002A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113706060A (en) * | 2021-10-29 | 2021-11-26 | 中国电力科学研究院有限公司 | Power grid regulation and control data asset processing method, system, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101951377A (en) * | 2010-09-21 | 2011-01-19 | 用友软件股份有限公司 | Hierarchical authorization management method and device |
| CN104125219A (en) * | 2014-07-07 | 2014-10-29 | 四川中电启明星信息技术有限公司 | Centralized identity and management method aiming at electric power information system |
| CN104537488A (en) * | 2014-12-29 | 2015-04-22 | 中国南方电网有限责任公司 | Enterprise-level information system function authority unified management method |
| EP3236400A1 (en) * | 2016-04-20 | 2017-10-25 | Bernard Cook | Asset management system |
| CN109840752A (en) * | 2018-12-29 | 2019-06-04 | 航天信息股份有限公司 | Administrative permission operation system based on micro services |
-
2021
- 2021-04-16 CN CN202110409871.9A patent/CN113327002A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101951377A (en) * | 2010-09-21 | 2011-01-19 | 用友软件股份有限公司 | Hierarchical authorization management method and device |
| CN104125219A (en) * | 2014-07-07 | 2014-10-29 | 四川中电启明星信息技术有限公司 | Centralized identity and management method aiming at electric power information system |
| CN104537488A (en) * | 2014-12-29 | 2015-04-22 | 中国南方电网有限责任公司 | Enterprise-level information system function authority unified management method |
| EP3236400A1 (en) * | 2016-04-20 | 2017-10-25 | Bernard Cook | Asset management system |
| CN109840752A (en) * | 2018-12-29 | 2019-06-04 | 航天信息股份有限公司 | Administrative permission operation system based on micro services |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113706060A (en) * | 2021-10-29 | 2021-11-26 | 中国电力科学研究院有限公司 | Power grid regulation and control data asset processing method, system, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Williams | A quick start guide to cloud computing: moving your business into the cloud | |
| US10878514B2 (en) | Expense validator | |
| US9576124B2 (en) | Multi-level password authorization | |
| US10171408B2 (en) | Following/subscribing for productivity applications | |
| Susanto et al. | Toward cloud computing evolution: efficiency vs trendy vs security | |
| CN113779609B (en) | Data management method, device, electronic equipment and storage medium | |
| CN113327002A (en) | Method and device for constructing data asset management model | |
| Saleem | Cloud computing's effect on enterprises | |
| Susanto et al. | A review of cloud computing evolution individual and business perspective | |
| US20100293182A1 (en) | Method and apparatus for viewing documents in a database | |
| Shor | Cloud computing for learning and performance professionals | |
| Skolmen et al. | Protection of personal information in the South African Cloud Computing environment: A framework for Cloud Computing adoption | |
| CN116738482A (en) | Sensitive data processing method, system, computer equipment and storage medium | |
| CN111275542A (en) | Loan request processing method, device and system | |
| Alotaibi | Utilizations of cloud computing in library and information centers: a theoretical study | |
| US20170124573A1 (en) | User profile database system | |
| CN113783828B (en) | Service system monitoring method and device | |
| CN114693035A (en) | Method, system and device for generating time limit task of enterprise intellectual property management system | |
| CN112181817A (en) | Test method and test device for SOA (service oriented architecture) platform | |
| Yu | Data privacy and big data-compliance issues and considerations | |
| Seo et al. | Implementation strategy for a public service based on cloud computing at the government | |
| CN111241528A (en) | Method and system for managing authority facing to business of commercial tenant | |
| US20120198568A1 (en) | Security Classification Applying Social Norming | |
| Thompson | CISOs should work closely with their ITAM colleagues | |
| US20240144242A1 (en) | A system and method of providing a blockchain-based curriculum vitae |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |