Asset management method, apparatus, computing device and medium executed by computing device

Abstract

This disclosure provides an asset management method executed by a computing device, belonging to the field of big data technology. The asset management method includes: receiving a request to access object data in assets of a business architecture, wherein the request corresponds to a user's identity and permissions as well as the request itself; verifying the attribute information of the user initiating the request; when the user's attribute information meets a first predetermined condition, verifying the operation permissions of the request; and when the operation permissions meet a second predetermined condition for the object data, approving the user to operate on the object data according to the request, thereby achieving asset management of the business architecture. This disclosure also provides an asset management device, a computing device, and a medium.

Description

Technical Field

[0001] The present disclosure relates to the field of big data technology, and in particular to an asset management method executed by a computing device, an asset management apparatus, a computing device, and a computer-readable storage medium. Background Art

[0002] In order to adapt to the development requirements of digital banks, commercial banks need to understand industry development trends and analyze the threats and opportunities of enterprises. The business architecture can globally display the relationship between the various businesses of commercial banks, so as to analyze the threats and opportunities of enterprises. Implementing component-based development based on enterprise-level business architecture is an effective means to bridge the digital divide between business and technology. The business architecture involves assets of various dimensions. Due to the different functions and users of various types of assets, it is necessary to clearly define the relationship between various types of assets, and check the judgment criteria of the relationship between assets through computers and other intelligent devices to ensure that they are stored and called according to the correct asset classification.

[0003] How to effectively manage assets in a business architecture is a technical problem that technical personnel in this field need to solve. Summary of the invention

[0004] In one aspect of an embodiment of the present disclosure, there is provided an asset management method executed by a computing device, the asset management method comprising:

[0005] Receiving a call request for object data in an asset of a business architecture, wherein the call request corresponds to an identity and authority of a user and the call request;

[0006] Verify the attribute information of the user who initiated the call request;

[0007] When the attribute information of the user satisfies a first specified condition, verifying the operation authority of the call request; and

[0008] When the operation authority satisfies a second specified condition for the object data, the user is approved to operate the object data according to the call request to achieve management of the assets of the business architecture.

[0009] According to some embodiments, the assets of the business architecture are stored in the computing device in the form of an aggregate view, and the aggregate view includes N types of assets included in the business architecture and the association relationships between the N types of assets, where N is a positive integer greater than or equal to 2.

[0010] According to some embodiments, the N types of assets include at least two of theory-level assets, method-level assets, mechanism-level assets, technology-level assets, model-level assets, strategy-level assets, business-level assets, patent-level assets, and human-level assets.

[0011] According to some embodiments, the attribute information of the user includes at least one of the identity and authority of the user.

[0012] According to some embodiments, the user's attribute information satisfies the first specified condition including: the user's identity value is greater than or equal to a preset identity standard; and the user's authority value is greater than or equal to a preset authority standard.

[0013] According to some embodiments, the identity of the user includes N identity attribute values, the identity value of the user is equal to the sum of the N identity attribute values, and the N identity attribute values ​​are the values ​​of the user's identity relative to the N assets respectively; and / or, the user's authority includes N authority attribute values, the authority value of the user is equal to the sum of the N authority attribute values, and the N authority attribute values ​​are the values ​​of the user's authority relative to the N assets respectively.

[0014] According to some embodiments, verifying the operation authority of the call request includes:

[0015] Determining a preset standard corresponding to the call request according to the object data targeted by the call request;

[0016] Comparing the identity value of the user initiating the call request with the preset standard; and

[0017] When the identity value of the user initiating the call request is greater than or equal to the preset standard, it is determined that the call request for the object data passes the verification.

[0018] According to some embodiments, verifying the operation authority of the call request further includes:

[0019] Comparing the permission value of the user initiating the call request with the preset standard; and

[0020] When the authority value of the user initiating the call request is greater than or equal to the preset standard, it is determined that the call request for the object data passes the verification.

[0021] According to some embodiments, determining a preset standard corresponding to the call request according to the object data targeted by the call request includes:

[0022] Determining the asset score of the object data according to the assets included in the object data;

[0023] Determining a confidentiality score of the object data according to the confidentiality level of the object data; and

[0024] Based on the asset score and the confidentiality score, a preset standard for the call request is determined.

[0025] According to some embodiments, the asset management method further includes: when the operation authority does not satisfy a second specified condition for the object data, prompting the user to adjust the call request.

[0026] According to some embodiments, the asset management method further includes: when the attribute information of the user does not satisfy a first specified condition, directly rejecting the call request.

[0027] According to some embodiments, the asset management method further includes: when the attribute information of the user does not satisfy the first specified condition, accumulating the number of times the user does not comply with the call request; and when the accumulated number reaches a warning threshold, adding the user to a blacklist.

[0028] According to some embodiments, the operation on the object data includes at least one of query, addition, editing and deletion.

[0029] According to some embodiments, the asset management method further comprises:

[0030] Determine whether the call request requires manual approval;

[0031] When the call request requires manual approval, analyzing the approval level to determine the approver corresponding to the call request; and

[0032] The call request is sent to the corresponding approval personnel.

[0033] According to another aspect of an embodiment of the present disclosure, there is provided an asset management device, the asset management device comprising:

[0034] A receiving module, used to receive a call request for object data in an asset of a business architecture, wherein the call request corresponds to the identity and authority of the user and the call request;

[0035] User verification module, used to verify the attribute information of the user who initiates the call request;

[0036] A call request verification module, used to: when the attribute information of the user meets the first specified condition, verify the operation authority of the call request; and

[0037] The approval module is used to: when the operation authority meets the second specified condition for the object data, approve the user to operate the object data according to the call request to achieve management of the assets of the business architecture.

[0038] According to another aspect of an embodiment of the present disclosure, a computing device is provided, comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the method as described above.

[0039] According to another aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which executable instructions are stored. When the instructions are executed by a processor, the processor executes the method as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0041] Figure 1 Schematically illustrates an aggregated view of assets of a business architecture according to some exemplary embodiments of the present disclosure;

[0042] Figure 2 A schematic diagram showing the operation of the asset using the intelligent verification module according to an embodiment of the present disclosure;

[0043] Figure 3 A flowchart of an asset management method executed by a computing device according to an embodiment of the present disclosure is schematically shown;

[0044] Figure 4 Schematically illustrates a flow chart of an asset management method executed by a computing device according to some other exemplary embodiments of the present disclosure;

[0045] Figure 5 to Figure 7 Flowcharts of the asset management method according to the embodiments of the present disclosure are respectively shown, wherein: Figures 5 to 7 The schematic diagram shows the operations of stakeholders, intelligent verification modules and approvers in different situations;

[0046] Figure 8 A structural block diagram of an asset management device according to an embodiment of the present disclosure is schematically shown; and

[0047] Fig. 9 A block diagram suitable for implementing the above-mentioned asset management method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0048] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0049] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0050] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0051] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0052] In this article, the expression "stakeholder" refers to individuals or organizations that are actively involved in project management or whose interests may be positively or negatively affected after the project is completed (such as customers, users, sponsors, senior management, the performing organization, the public, or those who oppose the project).

[0053] In this article, the expression "aggregate view" refers to a combination of architectural asset types that embody different dimensions and are used to inherit the core iterative genes of the business architecture. For example, the aggregate view may include, but is not limited to, the documentation of theoretical-level assets, method-level assets, mechanism-level assets, technology-level assets, model-level assets, strategic-level assets, business-level assets, patent-level assets, and human-level assets, as well as the relationships between the above assets.

[0054] The embodiment of the present disclosure provides an asset management method executed by a computing device, the asset management method comprising: receiving a call request for object data in an asset of a business architecture, wherein the call request corresponds to the identity and authority of the user and the call request; verifying the attribute information of the user who initiated the call request; when the attribute information of the user meets a first specified condition, verifying the operation authority of the call request; and when the operation authority meets a second specified condition for the object data, approving the user to operate the object data according to the call request to achieve management of the assets of the business architecture. In this way, effective and intelligent management of the assets of the business architecture can be achieved.

[0055] Figure 1 Schematically illustrates an aggregated view of assets of a business architecture according to some exemplary embodiments of the present disclosure. Figure 1 In an embodiment of the present disclosure, an aggregate view may represent a combination of architecture asset types that embody different dimensions for inheriting the core iterative genes of a business architecture. For example, an aggregate view may include, but is not limited to, document materials of theoretical-level assets, method-level assets, mechanism-level assets, technical-level assets, model-level assets, strategic-level assets, business-level assets, patent-level assets, and human-level assets, as well as the relationships between the above-mentioned assets.

[0056] For example, theoretical assets may refer to all academic theories and academic theory research reports that constitute the business architecture. For example, some examples of theoretical assets may include: "Research on 5G message applications based on business architecture", "New technology innovation based on business architecture - method research", "New technology innovation based on business architecture - application practice", "Research on quality assurance methods based on business architecture" and other documents.

[0057] For example, method-level assets can refer to all methods and guidelines in the process of business architecture research, implementation, and innovation. For example, some examples of method-level assets may include: "Integration and Construction of Enterprise-level Business Architecture Work Guidelines - Process Modeling", "Integration and Construction of Enterprise-level Business Architecture Work Guidelines - Product Modeling", "Integration and Construction of Enterprise-level Business Architecture Work Guidelines - Entity Modeling" and other documents.

[0058] For example, mechanism-level assets can refer to the work mechanisms, planning schemes and other document materials formed during the full life cycle management of the business architecture. For example, some examples of mechanism-level assets can include: "Enterprise-level Business Architecture Integration Construction Work Manual", "Business Architecture Quality Assurance Work Manual", "Cross-domain Reuse Task Construction Operation Manual", "Business Architecture Post-evaluation Operation Manual" and other documents.

[0059] For example, technical-level assets can refer to all systems, platforms, technologies, requirements, meeting minutes and other documents that complete the construction, storage, operation and extension of the business architecture. For example, some examples of technical-level assets may include: "Change Letter of New Capability Modeling Function Requirements for Architecture Asset Management and Control Platform", "Summary of Business Architecture Asset Change Details", "List of Main Functions of Architecture Asset Management and Control Platform" and other documents.

[0060] For example, model-level assets may refer to various management methods, management ideas, management measures, etc. adopted in business architecture management. For example, some examples of model-level assets may include: "Business Architecture Engineering Management Measures", "Business Architect Management Measures", "Business Architecture Resource Management Rules", "Business Architecture Asset Assessment Management Measures" and other documents.

[0061] For example, strategic assets may refer to high-level iterative strategic planning and capability requirements documents for business architecture assets. For example, some examples of strategic assets may include: "Top-level planning for personal payment and settlement business", "Top-level planning for international trade financing business", "Strategic implementation planning map", "Strategic capability implementation field hotspot map" and other documents.

[0062] For example, business-level assets may refer to business asset elements and project-related assets formed during the construction and application of business architecture assets. For example, some examples of business-level assets may include: "Supply Chain Financing Business Requirements", "E-Phase Project Architecture Analysis Table", "Use Case Division Work Guide", "Project Docking Architecture Asset Docking Guide" and other documents.

[0063] For example, patent-level assets may refer to all technical patent documents mined during the implementation of the business architecture, etc. For example, some examples of patent-level assets may include: "Guidelines for Writing Patent Technology Briefing Documents", "Patent Application Writing Specifications", "Technical Briefing Documents - Data Cutting Technology Based on Metamodel", "Technical Briefing Documents - Intelligent Data Algorithm Tools for Basic Business Architecture", and other documents.

[0064] For example, human-level assets may refer to comprehensive talents with strategic dimensions, business dimensions, architectural dimensions, project dimensions, and management and control dimensions. For example, some examples of human-level assets may include: product managers, product line leaders, enterprise architects, business architects, data architects, application architects, technical architects, etc.

[0065] In some embodiments of the present disclosure, it is necessary to manage the above-mentioned theoretical-level assets, method-level assets, mechanism-level assets, technical-level assets, model-level assets, strategic-level assets, business-level assets, patent-level assets, human-level assets and other assets. For example, it is necessary to query, add, edit, delete and other operations on various assets and the relationship between various assets. To this end, in the embodiments of the present disclosure, combined technologies such as data storage, data mining, and data collision are used to complete the verification and judgment of data objects on a computing device (such as a computer), thereby forming an intelligent verification module, with the intelligent verification module as the core, to complete the optimal set control of aggregate view calls.

[0066] Figure 2 A schematic diagram of operating the asset using the intelligent verification module according to an embodiment of the present disclosure is shown. Figure 2 , the intelligent verification module 20 may include a data storage module 201, a data mining module 202 and a data collision module 203. In case one, stakeholder one can use the intelligent verification module 20 to operate the data objects A, B and C in the above-mentioned assets (such as query, add, edit, delete, etc.). In case two, stakeholder two can use the intelligent verification module 20 to operate the data objects D, E and F in the above-mentioned assets (such as query, add, edit, delete, etc.). In case three, stakeholder three can use the intelligent verification module 20 to operate the data objects G, H and I in the above-mentioned assets (such as query, add, edit, delete, etc.).

[0067] In an embodiment of the present disclosure, the intelligent verification module 20 may be disposed in a computing device such as a server.

[0068] Figure 3 The flowchart of the asset management method executed by the computing device according to the embodiment of the present disclosure is schematically shown. Figure 3 , the asset management method 100 may include operations S310 to S340.

[0069] In operation S310, a call request for object data in an asset of a business architecture is received, wherein the call request corresponds to the identity and authority of a user and the call request.

[0070] According to the embodiment of the present disclosure, the object data in the asset is, for example, any one or more of the multiple asset data stored in the storage device. The computing device used to execute the method of the embodiment of the present disclosure can be a device in the business architecture, for example, the computing device can be a server, a server cluster, and other devices.

[0071] In operation S320, attribute information of the user who initiated the call request is verified.

[0072] For example, the attribute information of the user includes at least one of the identity and authority of the user.

[0073] In operation S330, when the attribute information of the user satisfies the first prescribed condition, the operation authority of the calling request is verified.

[0074] For example, the user's attribute information satisfies the first specified condition including: the user's identity value is greater than or equal to a preset identity standard; and the user's authority value is greater than or equal to a preset authority standard.

[0075] For example, the user's identity includes N identity attribute values, the user's identity value is equal to the sum of the N identity attribute values, and the N identity attribute values ​​are the values ​​of the user's identity relative to the N assets respectively.

[0076] For example, the user's authority includes N authority attribute values, the user's authority value is equal to the sum of the N authority attribute values, and the N authority attribute values ​​are the values ​​of the user's authority relative to the N assets respectively.

[0077] In some exemplary embodiments, verifying the operational authority of the call request includes: determining a preset standard corresponding to the call request based on the object data targeted by the call request; comparing the identity value of the user initiating the call request with the preset standard; and when the identity value of the user initiating the call request is greater than or equal to the preset standard, determining that the call request for the object data has passed the verification.

[0078] Optionally, verifying the operational authority of the call request also includes: comparing the authority value of the user initiating the call request with the preset standard; and when the authority value of the user initiating the call request is greater than or equal to the preset standard, determining that the call request for the object data passes the verification.

[0079] For example, based on the object data targeted by the call request, determining the preset standard corresponding to the call request includes: determining the asset score of the object data based on the assets included in the object data; determining the confidentiality score of the object data based on the confidentiality level of the object data; and determining the preset standard of the call request based on the asset score and the confidentiality score.

[0080] In operation S340, when the operation authority satisfies the second specified condition for the object data, the user is approved to operate the object data according to the call request to implement the management of the assets of the business architecture.

[0081] Through the technical solution of the embodiment of the present disclosure, the effect of automatic asset management is achieved, the efficiency of asset management is improved, the burden on asset maintenance personnel is reduced, and the cost of asset maintenance is reduced.

[0082] For example, the assets of the business architecture are stored in the computing device in the form of an aggregate view, and the aggregate view includes N types of assets included in the business architecture and the association relationship between the N types of assets, wherein N is a positive integer greater than or equal to 2. As described above, the N types of assets may include at least two of the above-mentioned theoretical-level assets, method-level assets, mechanism-level assets, technical-level assets, model-level assets, strategic-level assets, business-level assets, patent-level assets, and human-level assets.

[0083] Figure 4 Schematically shows a flowchart of an asset management method executed by a computing device according to some other exemplary embodiments of the present disclosure. Figure 4 As shown, the method may include operations S310 to S340 and operations S410 to S450. Figure 3 The operations described in are the same or similar and will not be repeated here.

[0084] In operation S410, when the attribute information of the user does not satisfy the first prescribed condition, the calling request may be directly rejected.

[0085] In operation S420, when the attribute information of the user does not satisfy the first prescribed condition, the number of times that the user does not meet the call request may be accumulated.

[0086] In operation S430, when the accumulated number of times reaches the warning threshold, the user is added to a blacklist.

[0087] In operation S440, it may also be determined whether manual approval is required. For example, in this operation, it may be determined whether the call request requires manual approval; when the call request requires manual approval, the approval level is analyzed to determine the approval personnel corresponding to the call request; and the call request is sent to the corresponding approval personnel.

[0088] Next, combine Figure 5 to Figure 7 Further describing the flow chart of the asset management method according to the embodiment of the present disclosure, each of which is attached Figures 5 to 7 The diagram schematically shows the operations of stakeholders, the intelligent verification module and the approver in different situations.

[0089] Reference Figure 5 , in operation S510 , the stakeholder initiates a call request.

[0090] In operation S520 , the intelligent verification module 20 determines and verifies the identity of the stakeholder.

[0091] For example, the judgment and verification of the identity of the stakeholders by the intelligent verification module 20 can be called primary verification. In the primary verification process, the intelligent verification module 20 verifies the identity and authority of each stakeholder one by one according to the uploaded attribute information of the stakeholder.

[0092] For example, when the identity value x≥identity preset standard y and the authority value x′≥authority preset standard y′, the intelligent verification module 20 gives a pass.

[0093] For example, the identity value x can be calculated as follows. Assume that the identity of the stakeholder is allowed to have n attributes, where n is a positive integer greater than or equal to 2. For example, the n attributes may include, but are not limited to, position, title, age, years of work experience, etc. In each case, an identity value is generated. For example, the following identity values ​​A, B, C... or Z can be generated. Each identity value can be equal to the sum of the values ​​of 1 to n attributes in each case corresponding to each call requirement.

[0094] For example, in the case corresponding to the first call requirement, the identity value A = attribute 1 value + attribute 2 value + attribute 3 value .... attribute n value; in the case corresponding to the second call requirement, the identity value B = attribute 1 value + attribute 2 value + attribute 3 value .... attribute n value; in the case corresponding to the third call requirement, the identity value C = attribute 1 value + attribute 2 value + attribute 3 value .... attribute n value; ... In the case corresponding to the Zth call requirement, the identity value Z = attribute 1 value + attribute 2 value + attribute 3 value .... attribute n value.

[0095] It should be noted that, in the case of corresponding various calling requirements, at least one of the values ​​of 1 to n attributes may be different.

[0096] For example, the identity preset standard y can be calculated as follows.

[0097] In the case of the first call demand, the identity preset standard A = asset 1 * identity type coefficient A + asset 2 * identity type coefficient A + asset 3 * identity type coefficient A + asset 4 * identity type system number A + asset 5 * identity type coefficient A + asset 6 * identity type coefficient A +..... asset N * identity type coefficient A. In the case of the second call demand, the identity preset standard B = asset 1 * identity type coefficient B + asset 2 * identity type coefficient B + asset 3 * identity type coefficient B + asset 4 * identity type system number B + asset 5 * identity type coefficient B + asset 6 * identity type coefficient B +..... asset N * identity type coefficient B. In the case of the third call demand, the identity preset standard C = asset 1 * identity type coefficient C + asset 2 * identity type coefficient C + asset 3 * identity type coefficient C + asset 4 * identity type system number C + asset 5 * identity type coefficient C + asset 6 * identity type coefficient C +..... asset N * identity type coefficient C. .......In the case corresponding to the Zth call demand, the identity preset standard Z = asset 1*identity type coefficient Z+asset 2*identity type coefficient Z+asset 3*identity type coefficient Z+asset 4*identity type system number Z+asset 5*identity type coefficient Z+asset 6*identity type coefficient Z+.....asset N*identity type coefficient Z.

[0098] It should be noted that the identity type coefficients A, B, ....Z are the weights of various types of assets in response to various call requirements.

[0099] It should also be noted that the calculation principles of the authority value x' and the authority preset standard y' are the same as those of the above-mentioned identity value x and the identity preset standard y, which will not be repeated here.

[0100] In operation S530, if the verification determines that "identity matches", proceed to the next step.

[0101] In operation S540 , the intelligent verification module 20 verifies whether the call request of the stakeholder is legitimate and reasonable.

[0102] In the embodiment of the present disclosure, the intelligent verification module 20 verifies the call request options one by one according to the attribute information of the uploaded call request, which can be called advanced verification. In the advanced verification process, the size between the demand options and the call permission preset standard can be compared respectively. For example, when the demand option p1≥call permission preset standard q1, the demand option p2≥call permission preset standard q2, ... and the demand option pi≥call permission preset standard qi, the intelligent verification module 20 gives a pass.

[0103] It should be noted that requirement option p1, requirement option p2, ... requirement option pi respectively represent the requirements for each asset involved in the call request.

[0104] For example, requirement option p1 may involve theoretical-level assets. For example, theoretical-level assets are divided into level one, level two, and level three from high to low according to different confidentiality levels.

[0105] Requirement option p2 may involve method-level assets. For example, method-level assets are classified into level one, level two, and level three according to the different confidentiality levels.

[0106] Requirement option p3 may involve mechanism-level assets. For example, mechanism-level assets are classified into level one, level two, and level three from high to low according to the different levels of confidentiality.

[0107] Requirement option p4 may involve technical-level assets. For example, technical-level assets are classified into level one, level two, and level three according to the different levels of confidentiality.

[0108] Requirement option p5 may involve model-level assets. For example, model-level assets are divided into level one, level two, and level three from high to low according to different confidentiality levels.

[0109] Requirement option p6 may involve strategic-level assets. For example, strategic-level assets are classified into level one, level two, and level three according to different levels of confidentiality.

[0110] Requirement option p7 may involve business-level assets. For example, business-level assets are classified into level one, level two, and level three according to different confidentiality levels.

[0111] Requirement option p8 may involve patent-level assets. For example, business-level assets are divided into levels one, two, and three from high to low according to the degree of confidentiality.

[0112] Requirement option p9 may involve human-level assets. For example, human-level assets are classified into level one, level two, and level three from high to low according to different confidentiality levels.

[0113] For example, the above-mentioned call permission preset standard can be obtained by adding each asset score and the confidentiality score of the asset.

[0114] In an exemplary embodiment, in a certain call request, it is necessary to call the business architecture construction method guide. The asset belongs to the method-level asset, the confidentiality level is level 1, and its call permission preset standard q1 = method-level asset score + level 1 confidentiality score. For example, when the identity value A≥call permission preset standard q1, the intelligent verification module 20 can give a pass; when the identity value A<call permission preset standard, the intelligent verification module 20 can give a rejection.

[0115] In an exemplary embodiment, the business demand of online payroll project is called. The asset belongs to business-level assets, and the confidentiality level is level 3. Its call permission preset standard q7 = business-level asset score + level 3 confidentiality score. For example, when the identity value B≥call permission preset standard q7, the intelligent verification module 20 can give a pass; when the identity value B<call permission preset standard q7, the intelligent verification module 20 can give a rejection.

[0116] For example, a patent document of a business architecture is called. The asset belongs to a patent-level asset with a confidentiality level of level 2. Its call permission preset standard q8 = patent-level asset score + level 2 confidentiality score. For example, when the identity value C≥call permission preset standard q8, the intelligent verification module 20 can give a pass; when the identity value C<call permission preset standard q8, the intelligent verification module 20 can give a rejection.

[0117] In operation S550, if the check determines that "the demand is reasonable", proceed to the next step.

[0118] In operation S560 , the intelligent verification module 20 performs value judgment and technical analysis on the data object initiated by the stakeholder.

[0119] In operation S570, the intelligent verification module 20 determines whether the call request requires manual approval and performs a logical analysis on the approval level.

[0120] In operation S580 , the intelligent verification module 20 pushes the aggregate view call request that needs to be approved to the relevant approver for processing.

[0121] In operation S590 , the approver receives the pending approval request and approves it according to the analysis result of the intelligent verification module 20 .

[0122] Reference Figure 6 , in operation S610 , the stakeholder initiates a call request.

[0123] In operation S620 , the intelligent verification module 20 determines and verifies the identity of the stakeholder.

[0124] In operation S630, if the verification determines that "identity matches", the next step is performed.

[0125] In operation S640 , the intelligent verification module 20 verifies whether the call request of the stakeholder is legitimate and reasonable.

[0126] In operation S650, if the check determines that "the demand is unreasonable", the next step is performed.

[0127] In operation S660 , the intelligent verification module 20 prompts the stakeholder to adjust the call request (eg, query, add, edit, delete).

[0128] In operation S670 , the stakeholder adjusts the relevant data objects according to the analysis prompt of the intelligent inspection module 20 , and then submits the application again.

[0129] In operation S680, the intelligent verification module again verifies whether the stakeholder's call request is legitimate and reasonable.

[0130] In operation S690, if the verification determines that "the demand is reasonable", the following operations are performed. It should be noted that the following operations are basically the same as the above operations S560 to S590, and will not be repeated here.

[0131] Reference Figure 7 , in operation S710 , the stakeholder initiates a call request.

[0132] In operation S720 , the intelligent verification module 20 determines and verifies the identity of the stakeholder.

[0133] In operation S730, if the verification determines that "identity does not match", proceed to the next step.

[0134] In operation S740, the intelligent verification module 20 directly rejects the call request. At this time, the intelligent verification module 20 no longer verifies whether the demand is legitimate.

[0135] In operation S750, the intelligent verification module 20 records the "identity does not match" intelligent ledger and accumulates the number of times. When the number reaches the warning threshold, blacklist management is performed.

[0136] Some exemplary embodiments of the present disclosure also provide an asset management device. Figure 8 The asset management device is described in detail. Figure 8 The structure block diagram of the asset management device according to the embodiment of the present disclosure is schematically shown. Figure 8 As shown, the asset management device 800 may include a receiving module 810 , a user verification module 820 , a call request verification module 830 and an approval module 840 .

[0137] The receiving module 810 is used to receive a call request for object data in an asset of a business architecture, wherein the call request corresponds to the identity and authority of the user and the call request.

[0138] The user verification module 820 is used to verify the attribute information of the user who initiates the call request.

[0139] The call request verification module 830 is used to verify the operation authority of the call request when the attribute information of the user meets the first specified condition.

[0140] The approval module 840 is used to: when the operation authority meets the second specified condition for the object data, approve the user to operate the object data according to the call request to achieve management of the assets of the business architecture.

[0141] According to an embodiment of the present disclosure, any multiple modules and units in the above-mentioned asset management device can be combined into one module, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the modules and units in the above-mentioned asset management device can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the modules and units in the above-mentioned asset management device can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0142] Fig. 9 A block diagram suitable for implementing the above-mentioned asset management method according to an embodiment of the present disclosure is schematically shown.

[0143] like Fig. 9 As shown, the electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include an onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0144] In RAM 903, various programs and data required for the operation of electronic device 900 are stored. Processor 901, ROM 902 and RAM 903 are connected to each other via bus 904. Processor 901 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 902 and / or RAM 903. It should be noted that the program can also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0145] According to an embodiment of the present disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to the bus 904. The electronic device 900 may further include one or more of the following components connected to the I / O interface 905: an input portion 906 including a keyboard, a mouse, etc.; an output portion 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 908 including a hard disk, etc.; and a communication portion 909 including a network interface card such as a LAN card, a modem, etc. The communication portion 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage portion 908 as needed.

[0146] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0147] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 902 and / or RAM 903 described above and / or one or more memories other than ROM 902 and RAM 903.

[0148] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the item recommendation method provided by the embodiment of the present disclosure.

[0149] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 901. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0150] In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium, and downloaded and installed through the communication part 909, and / or installed from a removable medium 911. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0151] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0152] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0153] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0154] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0155] Although the present disclosure has been shown and described with reference to specific exemplary embodiments of the present disclosure, it should be understood by those skilled in the art that various changes in form and details may be made to the present disclosure without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Therefore, the scope of the present disclosure should not be limited to the above-mentioned embodiments, but should be determined not only by the appended claims, but also by the equivalents of the appended claims.

Claims

1. An asset management method performed by a computing device, characterized in that: The asset management method comprises: Receiving a call request for object data in an asset of a business architecture, wherein the call request corresponds to an identity and authority of a user and the call request; Verifying the attribute information of the user who initiated the call request, wherein the attribute information of the user includes at least one of the identity and authority of the user; When the attribute information of the user satisfies the first specified condition, verifying the operation authority of the call request, wherein the attribute information of the user satisfies the first specified condition includes: The user's identity value is greater than or equal to a preset identity standard, wherein the preset identity standard is determined based on the assets and identity type coefficient of the business architecture; and The user's authority value is greater than or equal to the authority preset standard, wherein the authority preset standard is determined based on the assets and authority type coefficients of the business architecture, The identity type coefficient and the permission type coefficient are the weights of the assets of the business architecture in response to various call requirements. The user's identity includes N identity attribute values, the user's identity value is equal to the sum of the N identity attribute values, the N identity attribute values ​​are the values ​​of the user's identity relative to N assets, respectively, wherein N is a positive integer greater than or equal to 2; and / or, The user's authority includes N authority attribute values, the user's authority value is equal to the sum of the N authority attribute values, and the N authority attribute values ​​are the values ​​of the user's authority relative to the N assets respectively. The checking of the operation authority of the call request includes: Determining a preset standard corresponding to the call request according to the object data targeted by the call request; Comparing the identity value of the user initiating the call request with the preset standard; and When the identity value of the user initiating the call request is greater than or equal to the preset standard, it is determined that the call request for the object data passes the verification, Wherein, according to the object data targeted by the call request, determining the preset standard corresponding to the call request includes: Determining the asset score of the object data according to the assets included in the object data; Determining a confidentiality score of the object data according to the confidentiality level of the object data; and Determining a preset standard for the call request based on the asset score and the confidentiality score; and When the operation authority passes the verification, the user is approved to operate the object data according to the call request to achieve the management of the assets of the business architecture.

2. The asset management method according to claim 1, characterized in that: The assets of the business architecture are stored in the computing device in the form of an aggregate view, where the aggregate view includes the N types of assets included in the business architecture and association relationships between the N types of assets.

3. The asset management method according to claim 2, characterized in that: The N types of assets include at least two of theory-level assets, method-level assets, mechanism-level assets, technology-level assets, model-level assets, strategy-level assets, business-level assets, patent-level assets and human-level assets.

4. The asset management method according to claim 1, characterized in that: The verifying the operation authority of the call request further includes: Comparing the permission value of the user initiating the call request with the preset standard; and When the authority value of the user initiating the call request is greater than or equal to the preset standard, it is determined that the call request for the object data passes the verification.

5. The asset management method according to any one of claims 1 to 3, characterized in that: The asset management method further comprises: When the operation authority fails to pass the verification, the user is prompted to adjust the call request.

6. The asset management method according to any one of claims 1 to 3, characterized in that: The asset management method further comprises: When the attribute information of the user does not satisfy the first specified condition, the calling request is directly rejected.

7. The asset management method according to claim 6, characterized in that: The asset management method further comprises: When the attribute information of the user does not meet the first specified condition, accumulating the number of times that the user does not meet the call request; and When the accumulated number of times reaches the warning threshold, the user is added to the blacklist.

8. The asset management method according to any one of claims 1 to 3, characterized in that: The operation on the object data includes at least one of query, add, edit and delete.

9. The asset management method according to any one of claims 1 to 3, characterized in that: The asset management method further comprises: Determine whether the call request requires manual approval; When the call request requires manual approval, analyzing the approval level to determine the approver corresponding to the call request; and The call request is sent to the corresponding approval personnel.

10. An asset management device, characterized in that: The asset management device comprises: A receiving module, used to receive a call request for object data in an asset of a business architecture, wherein the call request corresponds to the identity and authority of the user and the call request; A user verification module, used to verify the attribute information of the user who initiates the call request, wherein the attribute information of the user includes at least one of the identity and authority of the user; The call request verification module is used to verify the operation authority of the call request when the attribute information of the user meets the first specified condition, wherein the attribute information of the user meets the first specified condition includes: The user's identity value is greater than or equal to a preset identity standard, wherein the preset identity standard is determined based on the assets and identity type coefficient of the business architecture; and The user's authority value is greater than or equal to the authority preset standard, wherein the authority preset standard is determined based on the assets and authority type coefficients of the business architecture, The identity type coefficient and the permission type coefficient are the weights of the assets of the business architecture in response to various call requirements. The user's identity includes N identity attribute values, the user's identity value is equal to the sum of the N identity attribute values, the N identity attribute values ​​are the values ​​of the user's identity relative to N assets, respectively, wherein N is a positive integer greater than or equal to 2; and / or, The user's authority includes N authority attribute values, the user's authority value is equal to the sum of the N authority attribute values, and the N authority attribute values ​​are the values ​​of the user's authority relative to the N assets respectively. The checking of the operation authority of the call request includes: Determining a preset standard corresponding to the call request according to the object data targeted by the call request; Comparing the identity value of the user initiating the call request with the preset standard; and When the identity value of the user initiating the call request is greater than or equal to the preset standard, it is determined that the call request for the object data passes the verification, Wherein, according to the object data targeted by the call request, determining the preset standard corresponding to the call request includes: Determining the asset score of the object data according to the assets included in the object data; Determining a confidentiality score of the object data according to the confidentiality level of the object data; and Determining a preset standard for the call request based on the asset score and the confidentiality score; and The approval module is used to: when the operation authority passes the verification, approve the user to operate the object data according to the call request to achieve the management of the assets of the business architecture.

11. A computing device comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 9.

Images