Application construction method and apparatus, and computing device

Abstract

Provided in the present appreciation are an application construction method and apparatus, and a computing device. The method comprises: acquiring scenario information of a target service; on the basis of the scenario information of the target service, determining a target service item corresponding to the target service; on the basis of the target service item, determining a target service object corresponding to the target service; and on the basis of the target service item and the target service object, constructing a target application corresponding to the target service. In the solution, an application is quickly constructed on the basis of the sorting of services, thereby reducing the costs of application construction and improving the efficiency of application construction.

Description

Methods, apparatus, and computing devices for building applications

[0001] This application claims priority to Chinese Patent Application No. 202410979308.9, filed on July 19, 2024, with the Chinese National Intellectual Property Administration, entitled “Method, Apparatus and Computing Device for Constructing an Application”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of cloud computing, and more specifically, to a method, apparatus, and computing device for building applications. Background Technology

[0003] Digital transformation has become a mainstream trend in China's development, and accelerating this transformation is of paramount importance. However, simply relying on existing architectures and processes and using information technology to improve efficiency and effectiveness is far from sufficient. It requires transformative changes to existing organizational structures, business processes, and service models using information technology.

[0004] Digital transformation primarily involves data governance and application development. Currently, data governance and application development are typically implemented separately. This makes it difficult for data governance and application development to coordinate, hinders data sharing, reduces the effectiveness and efficiency of application development, and increases the cost of application development.

[0005] Therefore, how to reduce the cost of application development and improve the efficiency of application development has become an urgent technical problem to be solved. Summary of the Invention

[0006] This application provides a method, apparatus, and computing device for building applications, which can reduce the cost of application building and improve the efficiency of application building.

[0007] Firstly, a method for constructing an application is provided, comprising: obtaining scenario information of a target business; determining the target business item corresponding to the target business based on the scenario information of the target business; determining the target business object corresponding to the target business based on the target business item; and constructing the target application corresponding to the target business based on the target business item and the target business object.

[0008] In the above technical solution, by analyzing the scenario of the target business, the target business items and target business objects corresponding to the target business are determined, and the target application corresponding to the target business is built based on the target business items and target business objects. In this way, the application can be built quickly from the business analysis, thereby reducing the cost of application building and improving the efficiency of application building.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the scenario information of the target business includes the scenario name, business domain, subject domain, lead department, and scenario description.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the target business matter includes the basic information, forms, processes, and materials of the target business matter.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the target business object includes the target business object's basic information, logical entity, instance information, and data source information.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: determining the organizational responsibility information corresponding to the target business based on the scenario information of the target business, wherein the organizational responsibility information includes the department to which the target business belongs and the responsibilities of that department.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the target application is configured according to the target business matter and the target business object; the page components and layout style required by the target application are configured.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining the page component from a resource management platform, the page component being used to configure the target application.

[0015] The above-mentioned methods of obtaining the page component from the resource management platform include, but are not limited to, the following: dragging and dropping the page component from the resource management platform, or pulling the page component from the resource management platform.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: obtaining target data from a data governance platform, the target data including instance information of the target business object.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: setting management permissions for the target application so that the target department undertaking the target business can use the target application.

[0018] Secondly, an application building apparatus is provided, comprising: an acquisition module, a sorting module, and a building module. The acquisition module acquires scenario information of a target business; the sorting module determines target business items corresponding to the target business based on the scenario information; the sorting module further determines target business objects corresponding to the target business based on the target business items; and the building module builds the target application corresponding to the target business based on the target business items and the target business objects.

[0019] In conjunction with the second aspect, in some implementations of the second aspect, the scenario information of the target business includes the scenario name, business domain, subject domain, lead department, and scenario description.

[0020] In conjunction with the second aspect, in some implementations of the second aspect, the target business matter includes the basic information, forms, processes, and materials of the target business matter.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, the target business object includes the target business object's basic information, logical entity, instance information, and data source information.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the sorting module is also used to determine the organizational responsibility information corresponding to the target business based on the scenario information of the target business. The organizational responsibility information includes the department to which the target business belongs and the responsibilities of that department.

[0023] In conjunction with the second aspect, in some implementations of the second aspect, the building module is specifically used to: configure the target application based on the target business matter and the target business object; and determine the page components and layout style required by the target application.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, the acquisition module is also used to acquire the page component from the resource management platform, which is used to configure the target application.

[0025] In conjunction with the second aspect, in some implementations of the second aspect, the acquisition module is also used to acquire target data from the data governance platform, the target data including instance information of the target business object.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, the building module is used to set the management permissions of the target application, so that the target department undertaking the target business can use the target application.

[0027] Thirdly, a computing device is provided, including a processor and a memory, and optionally, an input / output interface. The processor controls the input / output interface to send and receive information, the memory stores a computer program, and the processor retrieves and runs the computer program from the memory, causing the program to execute the method of the first aspect or any possible implementation thereof.

[0028] Optionally, the processor can be a general-purpose processor, which can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.

[0029] Fourthly, a computing device cluster is provided, including at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, such that the computing device cluster performs the method of the first aspect or any possible implementation thereof.

[0030] Fifthly, a chip is provided that acquires and executes instructions to implement the methods described in the first aspect and any implementation thereof.

[0031] Alternatively, as one implementation, the chip includes a processor and a data interface, through which the processor reads instructions stored in the memory and executes the methods described in the first aspect and any implementation thereof.

[0032] Optionally, as one implementation, the chip may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to perform the method in the first aspect and any implementation thereof.

[0033] In a sixth aspect, a computer program product containing instructions is provided, which, when executed by a computing device, cause the computing device to perform the methods described in the first aspect and any implementation thereof.

[0034] In a seventh aspect, a computer program product containing instructions is provided, which, when run by a cluster of computing devices, causes the cluster of computing devices to perform the methods described in the first aspect and any implementation thereof.

[0035] Eighthly, a computer-readable storage medium is provided, including computer program instructions that, when executed by a computing device, perform the method as described in the first aspect and any implementation thereof.

[0036] As examples, these computer-readable storage devices include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard drive.

[0037] Alternatively, as one implementation method, the aforementioned storage medium can specifically be a non-volatile storage medium.

[0038] A ninth aspect provides a computer-readable storage medium including computer program instructions that, when executed by a cluster of computing devices, perform the method as described in the first aspect and any implementation thereof.

[0039] As examples, these computer-readable storage devices include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard drive.

[0040] Alternatively, as one implementation method, the aforementioned storage medium can specifically be a non-volatile storage medium. Attached Figure Description

[0041] Figure 1 is a schematic block diagram of a cloud scenario applicable to an embodiment of this application.

[0042] Figure 2 is a schematic block diagram of a system architecture applied to an embodiment of this application.

[0043] Figure 3 is a schematic diagram of an application construction provided by an embodiment of this application.

[0044] Figure 4 is a schematic diagram of another application building method provided in an embodiment of this application.

[0045] Figure 5 is a schematic flowchart of a method for building an application provided in an embodiment of this application.

[0046] Figure 6 is a schematic block diagram of a scene sorting interface provided in an embodiment of this application.

[0047] Figure 7 is a schematic block diagram of a business responsibility sorting interface provided in an embodiment of this application.

[0048] Figure 8 is a schematic block diagram of a business item sorting interface provided in an embodiment of this application.

[0049] Figure 9 is a schematic block diagram of a business item overview interface provided in an embodiment of this application.

[0050] Figure 10 is a schematic block diagram of a business object sorting interface provided in an embodiment of this application.

[0051] Figure 11 is a schematic block diagram of an application configuration interface provided in an embodiment of this application.

[0052] Figure 12 is a schematic block diagram of a business scenario analysis provided in an embodiment of this application.

[0053] Figure 13 is a schematic block diagram of another business scenario analysis provided in the embodiments of this application.

[0054] Figure 14 is a schematic diagram of an analysis business object provided in an embodiment of this application.

[0055] Figure 15 is a schematic block diagram of an application building apparatus 900 provided in an embodiment of this application.

[0056] Figure 16 is a schematic diagram of the architecture of a computing device 1500 provided in an embodiment of this application.

[0057] Figure 17 is a schematic diagram of the architecture of a computing device cluster provided in an embodiment of this application.

[0058] Figure 18 is a schematic diagram of the connection between computing devices 1500A and 1500B via a network provided in an embodiment of this application. Detailed Implementation

[0059] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0060] This application will present various aspects, embodiments, or features relating to systems comprising multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0061] Furthermore, in the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0062] In the embodiments of this application, "corresponding" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, their intended meanings are consistent.

[0063] The business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0064] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0065] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0066] Digital transformation has become a mainstream trend in China's development, and accelerating this transformation is of paramount importance. However, simply relying on existing architectures and processes and using information technology to improve efficiency and effectiveness is far from sufficient. It requires transformative changes to existing organizational structures, business processes, and service models using information technology.

[0067] Digital transformation primarily involves data governance and application development. Currently, data governance and application development are typically implemented separately. This makes it difficult for data governance and application development to coordinate and cooperate, hindering data sharing and reducing the effectiveness and efficiency of application development.

[0068] Taking the current data governance as an example, it starts from the database and table model of the business system. Each commission and bureau system carries out separate governance according to the functions involved, or the data is aggregated to the big data platform and uniformly governed by the big data platform. After the big data platform completes the data governance, it provides the governed data to each business department through data services.

[0069] The aforementioned data governance and aggregation through big data platforms, employing different governance methods, typically face challenges related to systems, mechanisms, platform capabilities, and methodologies. For example, a big data platform primarily focuses on data aggregation, failing to truly govern data from departmental and bureau business systems, resulting in data that cannot be analyzed, shared, or its value realized. Conversely, a big data platform may implement unified governance, aggregating data from departmental and bureau business systems for unified governance. However, if the platform lacks an understanding of the business processes, the data governance quality is low, and the value for sharing and use is minimal. Finally, a big data platform may employ decentralized governance, developing independent governance plans based on departmental and bureau data and business needs. This lack of a reasonable and unified data governance approach leads to inconsistent data quality and difficulty in ensuring the quality of data sharing.

[0070] Taking current application building as an example, the traditional siloed building method is usually used, where each business department builds an application separately for its specific business, or the business application of the department is quickly built based on a low-code platform through a simple drag-and-drop method.

[0071] The above-mentioned traditional siloed construction method involves each business department building its own application for specific business needs. These applications are completely independent of each other, and common capabilities between different applications cannot be reused or accumulated. All applications need to be built and developed from scratch, resulting in high construction costs and low efficiency.

[0072] In view of this, embodiments of this application provide a method for building applications. This method starts with business analysis and quickly builds applications, thereby reducing the cost of application building and improving the efficiency of application building.

[0073] In one possible implementation, the method provided in this application embodiment can be applied to a cloud service scenario, where the method is executed by a cloud management platform within the cloud service scenario. For ease of description, the cloud service scenario will be described in detail below with reference to Figure 1.

[0074] Figure 1 is a schematic block diagram of a cloud scenario applicable to an embodiment of this application. As shown in Figure 1, the cloud scenario may include: a cloud management platform 110, the Internet 120, and a client 130.

[0075] As shown in Figure 1, the cloud management platform 110 is used to manage the infrastructure that provides multiple cloud services. The infrastructure includes multiple cloud data centers, each cloud data center includes multiple servers, and each server includes cloud service resources to provide corresponding cloud services to tenants.

[0076] The cloud management platform 110 can be located in a cloud data center and provides access interfaces (such as user interfaces or application program interfaces, APIs). Tenants can use client 130 to remotely access the cloud management platform 110, register a cloud account and password, and log in. After successful authentication of the cloud account and password, the tenant can further select and purchase virtual machines of specific specifications (processor, memory, disk) on the cloud management platform 110. After successful purchase, the cloud management platform 110 provides the remote login account and password for the purchased virtual machine, allowing client 130 to remotely log in and install and run the tenant's applications. Therefore, tenants can create, manage, log in to, and operate virtual machines in the cloud data center through the cloud management platform 110. Virtual machines can also be referred to as Elastic Compute Service (ECS) or Elastic Instances (different cloud service providers may use different names).

[0077] It should be understood that cloud service tenants can be individuals, businesses, schools, hospitals, government agencies, etc.

[0078] The cloud management platform 110 includes, but is not limited to, a user console, compute management services, network management services, storage management services, authentication services, and image management services. The user console provides an interface or API for interaction with tenants. The compute management services manage servers running virtual machines and containers, as well as bare metal servers. The network management services manage network services (such as gateways and firewalls). The storage management services manage storage services (such as data bucket services). The authentication services manage tenant account passwords. The image management services manage virtual machine images. Tenants can log in to the cloud management platform 110 via client 130 and the internet 120 to manage their rented cloud services.

[0079] For ease of description, the system architecture applied to the embodiments of this application will be described in detail below with reference to Figure 2.

[0080] Figure 2 is a schematic block diagram of a system architecture applied to an embodiment of this application. As shown in Figure 2, the system architecture may include an application building platform 210, a data governance platform 220, a resource management platform 230, and a project management platform 240. The application building platform 210, based on a metadata-driven technical framework, executes the application building method provided in this embodiment of the application, and, with the support of large-scale model intelligence capabilities, quickly configures and builds scenario applications. The data governance platform 220 integrates different business systems, carries the capability of data aggregation and organization, and provides the governed data to different applications built in the application building platform 210 through data services. The resource management platform 230 uniformly collects and classifies different types of resources, and uniformly manages common components to facilitate on-demand use and reuse, improving resource utilization efficiency and avoiding redundant resource construction. The project management platform 240, taking architecture organization as a starting point and project lifecycle management as its core, ensures the standardization and intensification of application construction from scenario requirement analysis to application implementation, and simultaneously completes data governance and business streamlining while performing application governance.

[0081] The functions of each platform included in the above system architecture are illustrated in detail below.

[0082] 1. Application building platform 210

[0083] The application building platform 210 mainly includes a business analysis module 211, a data analysis module 212, an application building module 213, an intelligent application module 214, and a metadata engine module 215. The business analysis module 211 analyzes business scenarios, breaks down business solutions, instantiates business processes into business items, and completes the closed loop of business functions through these business items. The data analysis module 212 analyzes the business attributes of business items, analyzes and abstracts specific business objects, and integrates and governs data around these business objects. The application building module 213 orchestrates and combines business items and business objects, and combines them with page components to configure different scenario applications. The intelligent application module 214, aided by industry experience and large-scale models, performs data governance and application building to maximize efficiency. The metadata engine module 215 supports code-free configuration, enabling configuration and execution through drag-and-drop methods.

[0084] 2. Data Governance Platform 220

[0085] The data governance platform 220 mainly includes a data integration module 221, a data development module 222, a data security module 223, and a data service module 224. The data integration module 221 is primarily used to integrate data from different sources into a unified data warehouse, including functions such as data extraction, transformation, and loading to ensure data consistency and accuracy. The data development module 222 is mainly used for data processing and analysis, including functions such as data cleaning, data transformation, and data modeling. The data security module 223 is primarily used to protect the confidentiality, integrity, and availability of data, including functions such as identity authentication, access control, and data encryption to ensure data security. The data service module 224 is mainly used to provide data services, including functions such as data querying, data distribution, and data sharing, to support business departments and data consumers in obtaining the data they need.

[0086] 3. Resource Management Platform 230

[0087] The resource management platform 230 mainly includes a resource aggregation module 231, a resource service module 232, and a resource scheduling module 233. The resource aggregation module 231 is primarily responsible for integrating with various business systems, collecting and managing different types of resources, such as data resources, component resources, and model resources. The resource service module 232 is mainly responsible for providing various resource access services, offering the managed business objects and data to business systems for access through data services. The resource scheduling module 233 is responsible for resource scheduling and allocation to meet the needs of different applications.

[0088] 4. Project Management Platform 240

[0089] The project management platform 240 mainly includes the following modules: project application module 241, project approval module 242, project construction module 243, project acceptance module 244, and supervision and evaluation module 245. Among them, the project approval module 242 receives and approves submitted projects, and then inputs requirements into the application construction platform 210. The construction platform 210 builds the corresponding application and returns it to the project management platform 240. The project acceptance module 244 in the project management platform 240 is responsible for receiving the application built by the construction platform 210 and for accepting the application.

[0090] The application construction method provided in this application embodiment creates a new model for scenario application construction by internalizing a systematic approach to the integrated governance of business, data, and applications. It standardizes and normalizes the solution decomposition and configuration development process for scenario applications. Driven by business needs, it accurately identifies data requirements, performs data modeling and builds common service components around business objects, and achieves real-time data aggregation and natural sharing. Business analysis and data governance are completed simultaneously with application governance.

[0091] As an example, the method for building an application provided in this application embodiment is mainly divided into three stages, as shown in Figure 3. These three stages are the business analysis stage, the data governance stage, and the application building stage.

[0092] 1. Business Review Phase

[0093] The business process streamlining phase primarily includes scenario streamlining, responsibility streamlining, and task streamlining. Scenario streamlining involves identifying the scenarios within a specific business context. Responsibility streamlining involves identifying the relevant departments and their responsibilities based on the scope of the business scenario, including responsibility categories and relevant business units. Task streamlining involves identifying specific business tasks according to responsibility categories, including basic task information, business processes, and rule-based scenarios. Based on the governance concept that all business is a task, business processes are abstracted into concrete, actionable tasks, thus achieving business concretization and instantiation.

[0094] 2. Data Governance Phase

[0095] The data governance phase mainly includes object identification and data governance. Object identification refers to extracting business-related parameters based on event and process information, analyzing these parameters to abstract business objects, or expanding and refining instance information of business objects, and identifying the object's business domain, subject domain, responsible department, and data source information. Data governance refers to aggregating the identification results onto a data platform based on the identified object attribution and data source information, and then collecting and integrating data based on business domain, subject domain, and responsible department. Finally, it involves configuring data sources according to the data sources to complete the governance of the object data.

[0096] 3. Application Building Phase

[0097] The application development phase mainly includes scenario configuration, application component orchestration, and scenario application deployment. Scenario configuration refers to configuring applications based on required capabilities and governable objects through business items and objects. Application component orchestration involves analyzing business functions within the scenario, determining the required page components and layout styles, and making specific layout and style adjustments to enable interaction between components. Scenario application deployment involves releasing the application to specific business departments, enabling them to manage and use the application.

[0098] For example, as shown in Figure 4, the above-mentioned application construction based on business mainly consists of two processes: one is to decompose business based on policies, and the other is to configure applications based on platforms. The policy-based business decomposition mainly includes business scenarioization, scenario itemization, item processization, process objectification, and object datafication. Through sorting and analysis, business is abstracted into specific items and objects. The platform-based application configuration mainly includes object serviceification, item serviceification, and service scenarioization. The abstracted objects and items are orchestrated, and scenarios are configured into specific applications.

[0099] In this embodiment of the application, through the two processes shown in Figure 4, data governance at the source, scenario construction agile, and integrated governance intelligently are achieved in the process of sorting out business and building applications.

[0100] For example, source-oriented data governance refers to achieving data quality "back to the source." This involves building an integrated business governance methodology system closely aligned with business needs. Through input from policy documents, business planning, and demand surveys, scenarios and responsibilities are clarified, resulting in scenario lists, scenario directories, and responsibility directories. This supports the establishment of a data asset catalog during the data governance process. By analyzing the input and output information in the process of each task, a task list, task process, task rules, and data requirements are generated, providing crucial support for data governance and scenario construction. Based on the supply and demand of data resources obtained through business governance, business objects, logical models, and data standards are output through object sorting, providing data modeling and data standards for data governance. Data sorting also confirms the data's ownership department and system data source. This forms a "back to the source" data governance methodology system, achieving the high-quality data governance goal of "one data source, one standard."

[0101] For example, agile scenario building refers to constructing a "highway" for business innovation. By practicing a metadata-driven modern software construction model, it leverages the inherent advantage of encompassing the ever-changing business manifestations through abstract models. Meta-model design is performed on business items and objects, forming atomic capabilities and enabling agile assembly of business models. Following the governance philosophy that "all business is an item," scenario items are continuously reviewed and sorted out by supporting business construction across departments. On the one hand, managed business items and object assets are accumulated, and managed business scenarios are visualized. On the other hand, existing item and object assets are quickly reused in new business scenarios, supporting rapid business innovation. Scenario applications are built through low-code configuration, using business items and objects as the core. Applications are quickly built using process-oriented configuration templates, associating business items and objects to support business flow, thus forming a "highway" for application construction and facilitating agile business innovation.

[0102] For example, intelligent integrated governance refers to the formation of large-scale models to support intelligent assistance. Government affairs are conducted based on policies, regulations, and laws. The scenarios and matters involved in these affairs can be accumulated into general industry assets. Using this data, a large-scale model is trained to form an intelligent integrated governance assistance model. This model assists in business governance, data governance, and application governance, forming a capability to build diverse and integrated intelligent scenarios. During the construction of the integrated governance model, training data is continuously generated based on the intelligent construction usage and business scenario governance status, continuously improving accuracy. This data flywheel approach makes scenario construction more intelligent.

[0103] As an example, the application building method provided in this application embodiment can be executed by the application building platform 210 described above. The application building method provided in this application embodiment will be described in detail below with reference to FIG5. It should be understood that the examples in FIG5 are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments to the specific values ​​or scenarios exemplified in FIG5. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given below in FIG5, and such modifications and changes also fall within the scope of the embodiments of this application.

[0104] Figure 5 is a schematic flowchart of a method for building an application according to an embodiment of this application. As shown in Figure 5, the method may include steps 510-530, which will be described in detail below.

[0105] Step 510: Analyze the business information entered by the user.

[0106] As an example, the users mentioned above could be various commissions, offices, and bureaus.

[0107] In this embodiment of the application, the user-inputted services can be obtained and sorted out.

[0108] As an example, the process of sorting out the business input from users can include sorting out business scenarios, sorting out business responsibilities, and sorting out business matters.

[0109] Optionally, in some embodiments, intelligent assistance capabilities can also be used to intelligently analyze the business information input by the user.

[0110] The following is a detailed description of each step in the business process.

[0111] 1. Business Scenario Analysis

[0112] As an example, business scenario analysis refers to the process of identifying and categorizing the scenarios to which the business matters requiring governance belong, and designing and generating a list of business scenarios. For instance, as shown in Figure 6, the scenario analysis interface requires confirmation of important information including, but not limited to: scenario name, business domain, subject domain, lead department, and scenario description.

[0113] It should be understood that, as an example and not a limitation, the scenario sorting interface in Figure 6 only lists a few possible pieces of information that need to be sorted out. Other information related to business scenarios can also be sorted out and determined. This application embodiment does not make specific limitations in this regard.

[0114] Optionally, in some embodiments, the capabilities of an intelligent assistant can be used to assist in the scene analysis, and the results can be used directly or modified. The modified data will be used as new training data.

[0115] For example, a user can enter "Please help me summarize the business scenario description of the 'Market Supervision Office'" into the smart assistant's interface, and the smart assistant can generate information for the business scenario of the "Market Supervision Office".

[0116] For example, the information generated by the intelligent assistant for the business scenario of the "Market Supervision Bureau" is shown below.

[0117] Scene Name: Market Supervision Office

[0118] Business domain: Digital government

[0119] Subject area: Administrative supervision

[0120] Lead department: Market Supervision Bureau

[0121] Scenario Description: The market supervision bureau is responsible for supervising and managing the market, including supervising the quality, price, and advertising of goods and services, as well as protecting consumer rights.

[0122] 2. Business Responsibilities Review

[0123] Business responsibility streamlining refers to identifying the responsibilities of relevant commissions and bureaus for specific business scenarios and configuring them on the platform. Alternatively, existing responsibilities on the platform can be reused.

[0124] For example, as shown in Figure 7, the business responsibility sorting interface mainly sorts out the following information, including but not limited to: responsibility category, responsibility name, and responsible department.

[0125] It should be understood that, as an example and not a limitation, the business responsibility sorting interface in Figure 7 only lists a few possible responsibility information that needs to be sorted out. Other information related to business responsibilities can also be sorted out, and this application embodiment does not make specific limitations in this regard.

[0126] Optionally, in some embodiments, when sorting out business responsibilities, intelligent automatic sorting can also be carried out based on the assistance capabilities of intelligent assistants, and the modified data can also be used as training data for further training.

[0127] 3. Business Items Review

[0128] As an example, corresponding business scenarios and organizational responsibilities require implementation through business task execution. Business task sorting refers to sorting out tasks based on the selected scenario tasks and clarifying the list of tasks involved.

[0129] For example, the process of streamlining business matters mainly includes sorting out the following information: basic information of the matter, forms for the matter, materials for the matter, and processes for the matter. This application embodiment can configure the streamlined business matters onto the platform, or reuse existing business matters on the platform.

[0130] For example, as shown in Figure 8, the business item sorting interface uses the basic information of the sorted items as an example for explanation. The basic information of the items includes, but is not limited to: item name, item code, item description, responsible department, and related inspection objects.

[0131] It should be understood that, as an example and not a limitation, the business item sorting interface in Figure 8 only lists the basic information of several possible items that need to be sorted out. Other basic information related to business items can also be sorted out, and this application embodiment does not make specific limitations in this regard.

[0132] Optionally, in some embodiments, when sorting out business matters, intelligent automatic sorting can also be carried out based on the assistance capabilities of the intelligent assistant, and the modified data can also be used as training data for further training.

[0133] For example, the platform also provides corresponding templates based on the category of the matter. Commonly used categories include, but are not limited to, approval, inspection, and supervision. Templates for acceptance conditions, forms, materials, and processes are designed separately for each category.

[0134] This application embodiment allows users (e.g., various commissions and bureaus) to view and manage the business matters that have been sorted out.

[0135] For example, as shown in Figure 9, the business item overview interface presents an overview of business items, various thematic areas, and various commissions and bureaus.

[0136] It should be understood that the content listed in Figure 9 is for illustrative purposes only and not as a limitation. The embodiments of this application do not specifically limit the types and quantities of the sorted business items, nor do they specifically limit the subject areas or commissions / bureaus.

[0137] Step 520: Govern business data.

[0138] As an example, the process of governing user-input data can include business object governance and big data platform governance.

[0139] 1. Business Object Governance

[0140] As an example, business object governance refers to the process of abstracting and designing business objects based on the information extracted from each item during the item sorting process, in accordance with the modeling principles of business objects.

[0141] In this application embodiment, existing object data on the platform can be used or new object data can be added to the platform. This application does not make specific limitations in this regard.

[0142] For example, the business object governance process mainly includes sorting out and configuring important information such as basic information sorting, logical entity design, instance information design, and data source confirmation.

[0143] For example, as shown in Figure 10, the business object sorting interface uses the basic information of a business object as an example for explanation. The basic information of the business object includes, but is not limited to: resource type name, resource type code, whether it comes from a third party, the type of the parent resource, the category to which it belongs, and description.

[0144] It should be understood that, as an example and not a limitation, the business object sorting interface in Figure 10 only lists the basic information of several possible business objects that need to be sorted. Other basic information related to business objects can also be sorted. This application embodiment does not make specific limitations in this regard.

[0145] In this embodiment, the accumulated resources can be sorted out based on the platform's business objects, and the sorted resources can be reused. Similarly, intelligent capabilities can be used to assist in governance, and the final results can be used as training data for further training.

[0146] 2. Big Data Platform Governance

[0147] Big data platform governance refers to sending information such as object models and data standards generated by business object governance to the data governance platform 220 through an integration interface, thereby completing the data governance of standard library, object library, theme library, etc., and completing the "source-correction" data governance of business guidance data.

[0148] Step 530: Complete the application construction based on business matters and business objects.

[0149] In this embodiment, the application configuration can be built on a low-code page using business items and business objects generated by business analysis and data governance based on the meta-model application construction method, according to the application template.

[0150] As an example, application configuration includes, but is not limited to, configurations for: application information, application account, application permissions, application roles, application functions, and application menus. For instance, in the management configuration interface, business items and business objects are associated; in the page configuration, login and navigation pages are set; and in the permission configuration, accounts and organizations are set. Once configured, the application is ready to use.

[0151] For example, as shown in Figure 11, the application configuration interface uses the basic information of the application as an example. The basic information of the application includes, but is not limited to: application code, application name, application abbreviation, application definition, application category, application description, application configuration, etc.

[0152] It should be understood that, as an example and not a limitation, the application configuration interface in Figure 11 only lists a few possible applications that need to be sorted out. Other basic information related to the application can also be sorted out. This application embodiment does not make specific limitations in this regard.

[0153] Optionally, in some embodiments, a smart assistant can also be used to assist in application building.

[0154] In this embodiment of the application, applications already built by various commissions and bureaus can also be viewed and managed in the intelligent scene construction workshop.

[0155] The following describes in detail a specific implementation process of the application construction method provided in this application embodiment, taking the information technology scenario innovation of a market supervision bureau as an example. It should be understood that the following examples are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments to the specific values ​​or scenarios exemplified below. Those skilled in the art can obviously make various equivalent modifications or changes based on the following examples, and such modifications and changes also fall within the scope of the embodiments of this application.

[0156] For example, taking the innovation of information technology scenarios in market supervision offices as an example, newly established market supervision offices are required to carry out supervision, inspection, law enforcement and daily work under the guidance of higher-level departments, and need corresponding information technology platforms to support their business.

[0157] In this embodiment, user and business requirements can be analyzed according to project management requirements. For example, as shown in Figure 12, the users identified for this scenario include: management committee users, the Commerce and Finance Bureau (including management personnel), and the Market Supervision and Management Office (e.g., management personnel and inspection and enforcement personnel). The main business requirements identified include: public service business, market management business, and internal management business. Among them, public service business includes services to enterprises, complaints and reports, and petitions; market management business includes public service management, risk monitoring management, and inspection and enforcement management; and internal management business includes organizational resource management and internal work management.

[0158] As an example, based on the above analysis of the main business requirements, the application constructed in this application embodiment needs to support three types of businesses: internal management, market management, and public services. It serves market supervision personnel and inspection and enforcement personnel, while also providing management services to management committee users and the Commerce and Finance Bureau.

[0159] The following example, using the market management business of the market supervision bureau as an example of regulating small food and beverage businesses, illustrates the specific implementation process of each part, such as business sorting, data governance, and application construction, as shown in Figure 5.

[0160] 1. Business review of "supervision of small food and beverage businesses"

[0161] One example is to categorize and summarize the scenarios to which the businesses requiring governance belong, and design and generate a list of business scenarios. For instance, for the business of "supervision of small grocery stores and small catering establishments," the following information needs to be confirmed: name, business domain, subject domain, lead department, and scenario description.

[0162] Another example is the business scenario of "supervision of small food and beverage businesses," which outlines the corresponding business responsibilities. For instance, as shown in Figure 13, the business responsibilities for this scenario include: supervision of small food and beverage businesses, inspection of registered items, administrative penalties for simple cases, food safety risk levels of food operators, and other daily operations.

[0163] Another example involves outlining the corresponding business items for the "supervision of small food and beverage businesses." For instance, as shown in Figure 13, the business items for this role include: supervisory work and internal affairs. Supervisory work includes: post-licensing supervision, enforcement and penalties, risk rating, daily tasks, special tasks, annual report follow-up, enterprise communication, and others. Internal affairs include: human resources management and other internal matters.

[0164] As an example, other internal affairs mentioned above include: management of inspection matters, management of task cases, management of complaint tasks, etc.

[0165] 2. Data governance for the supervision of small food and beverage businesses

[0166] For example, in the scenario of "supervision of small food and beverage businesses," business objects are derived based on information extracted from various business items during the business item sorting process. For instance, business objects include: enterprises, leads, and tasks. Business objects are designed according to data supply, such as inspection tasks, inspection items, and risk level scoring sheets, and data governance is performed according to the object model.

[0167] For example, Figure 14 illustrates a schematic diagram of business object analysis. As shown in Figure 14, based on the business data analysis of "small food and beverage supervision," business demand objects such as enterprises, leads, and tasks are derived. Business objects are designed according to data supply, such as inspection tasks, inspection items, and risk level rating sheets, and data governance is carried out according to the object model.

[0168] 3. Create a regulatory application for "small food and beverage businesses".

[0169] In this embodiment of the application, based on the business items and business objects sorted out above, a regulatory application for "small food and beverage" is quickly constructed through scenario application to carry out the corresponding market supervision business.

[0170] The aforementioned application scenarios provide capabilities such as unified integration, task coordination and management, closed-loop process, and automatic data synchronization, providing market supervision offices with efficient business operation tools.

[0171] For example, as shown in Figure 13, the constructed "small food and beverage" regulatory application mainly includes: regulatory work and internal affairs. Regulatory work includes: post-licensing supervision, enforcement and penalties, food safety risk rating, daily tasks, special tasks, annual report supervision, publicity and education, and others. Internal affairs include personnel management, matter management, task management, plan management, and market entity management. Personnel management refers to the management of law enforcement personnel; matter management includes the management of inspection matters, enforcement matters, risk rating, publicity and education matters, and annual report supervision; task management includes the management of inspection tasks, rating tasks, enforcement cases, complaint tasks, and publicity and education tasks; plan management includes the management of task plans and plan batches; and market entity management refers to the management of market entities.

[0172] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 14. The embodiments of the apparatus of this application will be described in detail below with reference to Figures 15 to 18. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0173] Figure 15 is a schematic block diagram of an application building device 900 provided in an embodiment of this application. The device 900 can be implemented by software, hardware, or a combination of both. The device 900 provided in this embodiment can implement the method flow shown in Figure 15 of this embodiment. The device 900 includes: an acquisition module 910, a sorting module 920, and a building module 930. The acquisition module 910 is used to acquire scenario information of a target business; the sorting module 920 is used to determine the target business item corresponding to the target business based on the scenario information of the target business; the sorting module 920 is also used to determine the target business object corresponding to the target business based on the target business item; the building module 930 is used to build the target application corresponding to the target business based on the target business item and the target business object.

[0174] Optionally, the scenario information for the target business includes the scenario name, business domain, subject domain, lead department, and scenario description.

[0175] Optionally, the target business matter includes the basic information, forms, processes, and materials of the target business matter.

[0176] Optionally, the target business object includes its basic information, logical entity, instance information, and data source information.

[0177] Optionally, the sorting module 920 is also used to determine the organizational responsibility information corresponding to the target business based on the scenario information of the target business. The organizational responsibility information includes the department to which the target business belongs and the responsibilities of that department.

[0178] Optionally, the building module 930 is specifically used to: configure the target application according to the target business matter and the target business object; and configure the page components and layout style required by the target application.

[0179] Optionally, the acquisition module 910 is also used to acquire the page component from the resource management platform, which is used to configure the target application.

[0180] Optionally, the acquisition module 910 is also used to acquire target data from the data governance platform, the target data including instance information of the target business object.

[0181] Optionally, the building module 930 is used to set the management permissions of the target application, so that the target department undertaking the target business can use the target application.

[0182] The device 900 here can be embodied in the form of a functional module. The term "module" here can be implemented in software and / or hardware, without specific limitations.

[0183] For example, a "module" can be a software program, a hardware circuit, or a combination of both that implements the above functions. For instance, the implementation of module 910 will be described below using module 910 as an example. Similarly, the implementation of other modules, such as module 920 and module 930, can refer to the implementation of module 910.

[0184] As an example of a software functional unit, the acquisition module 910 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, or a container. Further, the aforementioned computing instance may be one or more. For example, the acquisition module 910 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0185] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0186] As an example of a hardware functional unit, the acquisition module 910 may include at least one computing device, such as a server. Alternatively, the acquisition module 910 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0187] The multiple computing devices included in the acquisition module 910 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the acquisition module 910 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in the acquisition module 910 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0188] Therefore, the modules of the various examples described in the embodiments of this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0189] It should be noted that the above embodiments of the device, when executing the above methods, are only illustrative examples of the division of functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. For example, the acquisition module 910 can be used to execute any step in the above methods, the sorting module 920 can be used to execute any step in the above methods, and the construction module 930 can be used to execute any step in the above methods. The steps implemented by the acquisition module 910, the sorting module 920, and the construction module 930 can be specified as needed. By implementing different steps in the above methods through the acquisition module 910, the sorting module 920, and the construction module 930, all the functions of the above device can be realized.

[0190] Furthermore, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments above, which will not be repeated here.

[0191] The method provided in this application can be executed by a computing device, which can also be referred to as a computer system. It includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as processing units, memory, and memory control units; the functions and structure of this hardware will be described in detail later. The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Optionally, the computer system can be a handheld device such as a smartphone, or a terminal device such as a personal computer; this application does not particularly limit this, as long as the method provided in this application can be used. The executing entity of the method provided in this application can be a computing device, or a functional module within the computing device capable of calling and executing programs.

[0192] The following describes in detail, with reference to Figure 16, a computing device provided in an embodiment of this application.

[0193] Figure 16 is a schematic diagram of the architecture of a computing device 1500 provided in an embodiment of this application. The computing device 1500 may be a server, a computer, or other device with computing capabilities. The computing device 1500 shown in Figure 16 includes at least one processor 1510 and a memory 1520.

[0194] It should be understood that this application does not limit the number of processors and memories in the computing device 1500.

[0195] The processor 1510 executes instructions in the memory 1520, causing the computing device 1500 to implement the method provided in this application. Alternatively, the processor 1510 executes instructions in the memory 1520, causing the computing device 1500 to implement the various functional modules provided in this application, thereby implementing the method provided in this application.

[0196] Optionally, the computing device 1500 also includes a communication interface 1530. The communication interface 1530 uses a transceiver module, such as, but not limited to, a network interface card or a transceiver, to enable communication between the computing device 1500 and other devices or communication networks.

[0197] Optionally, the computing device 1500 also includes a system bus 1540, wherein the processor 1510, memory 1520, and communication interface 1530 are respectively connected to the system bus 1540. The processor 1510 can access the memory 1520 through the system bus 1540; for example, the processor 1510 can perform data read / write or code execution in the memory 1520 through the system bus 1540. The system bus 1540 is a peripheral component interconnect express (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus 1540 is divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in Figure 16, but this does not mean that there is only one bus or one type of bus.

[0198] In one possible implementation, the processor 1510 primarily functions to interpret the instructions (or code) of a computer program and process data within the computer software. The instructions of the computer program and the data within the computer software can be stored in memory 1520 or cache 1516.

[0199] Optionally, processor 1510 may be an integrated circuit chip with signal processing capabilities. By way of example and not limitation, processor 1510 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. Among these, a general-purpose processor is a microprocessor, etc. For example, processor 1510 may be a central processing unit (CPU).

[0200] Optionally, each processor 1510 includes at least one processing unit 1512 and a memory control unit 1514.

[0201] Optionally, the processing unit 1512, also known as the core, is the most important component of the processor. The processing unit 1512 is manufactured from single-crystal silicon using a specific production process. All calculations, command reception, command storage, and data processing are performed by the core. Each processing unit independently executes program instructions, utilizing parallel computing capabilities to accelerate program execution. Various processing units have fixed logical structures; for example, a processing unit includes logical units such as a Level 1 cache, a Level 2 cache, an execution unit, an instruction-level unit, and a bus interface.

[0202] In one implementation example, the memory control unit 1514 controls the data interaction between the memory 1520 and the processing unit 1512. Specifically, the memory control unit 1514 receives memory access requests from the processing unit 1512 and controls access to memory based on the memory access requests. By way of example and not limitation, the memory control unit is a device such as a memory management unit (MMU).

[0203] In one implementation example, each memory control unit 1514 addresses the memory 1520 via the system bus. An arbitrator (not shown in Figure 16) is configured on the system bus to handle and coordinate contention for access by the multiple processing units 1512.

[0204] In one implementation example, the processing unit 1512 and the memory control unit 1514 are connected via internal chip connection lines, such as address lines, thereby enabling communication between the processing unit 1512 and the memory control unit 1514.

[0205] Optionally, each processor 1510 also includes a cache 1516, which is a buffer for data exchange (called a cache). When the processing unit 1512 needs to read data, it first looks for the required data in the cache. If the data is found, it is executed directly; otherwise, it looks for the data in memory. Since the cache operates much faster than memory, its purpose is to help the processing unit 1512 run faster.

[0206] The memory 1520 provides runtime space for processes in the computing device 1500. For example, the memory 1520 stores the computer program (specifically, the program code) used to generate the process. After the computer program is run by the processor to generate a process, the processor allocates corresponding storage space for the process in the memory 1520. Furthermore, the aforementioned storage space further includes text segments, initialized data segments, bit initialized data segments, stack segments, heap segments, etc. The memory 1520 stores data generated during the process's execution, such as intermediate data or process data, in the aforementioned process-specific storage space.

[0207] Optionally, the memory, also known as RAM, is used to temporarily store the data processed by the processor 1510, as well as data exchanged with external storage devices such as hard disks. As long as the computer is running, the processor 1510 will load the data that needs to be processed into RAM for processing, and after the processing is completed, the processing unit 1512 will send the result out.

[0208] By way of example and not limitation, memory 1520 is volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory is read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory is random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory 1520 of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0209] The structure of the computing device 1500 listed above is merely illustrative and is not limited thereto. The computing device 1500 in this application includes various hardware components in existing computer systems. For example, the computing device 1500 also includes other memories besides memory 1520, such as disk storage. Those skilled in the art should understand that the computing device 1500 may also include other devices necessary for normal operation. Furthermore, depending on specific needs, those skilled in the art should understand that the computing device 1500 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the computing device 1500 may only include the devices necessary for implementing the embodiments of this application, and not necessarily all the devices shown in FIG16.

[0210] This application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device may be a server. In some embodiments, the computing device may also be a desktop computer, a laptop computer, or a smartphone, or other terminal device.

[0211] As shown in Figure 17, the computing device cluster includes at least one computing device 1500. The memory 1520 of one or more computing devices 1500 in the computing device cluster may store the same instructions for performing the methods described above.

[0212] In some possible implementations, the memory 1520 of one or more computing devices 1500 in the computing device cluster may also each store a portion of the instructions for executing the above-described methods. In other words, a combination of one or more computing devices 1500 can jointly execute the instructions of the above-described methods.

[0213] It should be noted that the memory 1520 in different computing devices 1500 within the computing device cluster can store different instructions, each used to execute a portion of the functions of the aforementioned device. That is, the instructions stored in the memory 1520 of different computing devices 1500 can implement the functions of one or more modules within the aforementioned device.

[0214] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 18 illustrates one possible implementation. As shown in Figure 18, two computing devices, 1500A and 1500B, are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device.

[0215] It should be understood that the functions of computing device 1500A shown in Figure 18 can also be performed by multiple computing devices 1500. Similarly, the functions of computing device 1500B can also be performed by multiple computing devices 1500.

[0216] In this embodiment, a computer program product containing instructions is also provided. The computer program product may be a software or program product containing instructions capable of running on a computing device or stored on any usable medium. When run on a computing device, it causes the computing device to perform the methods provided above, or causes the computing device to perform the functions of the apparatus provided above.

[0217] In this embodiment, a computer-readable storage medium is also provided. This computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that, when executed on a computing device, cause the computing device to perform the method described above.

[0218] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0219] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0220] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0221] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0222] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0223] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0224] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0225] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of constructing an application, characterized by, The method comprises: obtaining scene information of a target service; determining a target service matter corresponding to the target service according to the scene information of the target service; determining a target service object corresponding to the target service according to the target service matter; constructing a target application corresponding to the target service according to the target service matter and the target service object.

2. The method of claim 1, wherein, The method further comprises: determining institution responsibility information corresponding to the target service according to the scene information of the target service, the institution responsibility information comprising a department to which the target service belongs and a responsibility of the department.

3. The method according to claim 1 or 2, characterized in that, The constructing of the target application corresponding to the target service according to the target service matter and the target service object comprises: configuring the target application according to the target service matter and the target service object; determining a page component and a layout style required by the target application.

4. The method of claim 3, wherein, The method further comprises: obtaining the page component from a resource management platform, the page component being used for configuring the target application.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: obtaining target data from a data governance platform, the target data comprising instance information of the target service object.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: setting a management permission of the target application, so that a target department undertaking the target service can use the target application.

7. The method according to any one of claims 1 to 6, characterized in that, The scene information of the target service comprises a scene name, a business domain, a theme domain, a leading department and a scene description.

8. The method according to any one of claims 1 to 7, characterized in that, The target service matter comprises basic information, a form, a process and materials of the target service matter.

9. The method according to any one of claims 1 to 8, characterized in that, The target service object comprises basic information, a logical entity, instance information and data source information of the target service object.

10. An apparatus for constructing an application, the apparatus comprising: The device comprises: an obtaining module, configured to obtain scene information of a target service; a sorting module, configured to determine a target service matter corresponding to the target service according to the scene information of the target service; the sorting module is further configured to determine a target service object corresponding to the target service according to the target service matter; a constructing module, configured to construct a target application corresponding to the target service according to the target service matter and the target service object.

11. The device of claim 10, wherein: the sorting module is further configured to determine institution responsibility information corresponding to the target service according to the scene information of the target service, the institution responsibility information comprising a department to which the target service belongs and a responsibility of the department.

12. The apparatus of claim 10 or 11, wherein, The constructing module is specifically configured to: configure the target application according to the target service matter and the target service object; determine a page component and a layout style required by the target application.

13. The device of claim 12, wherein: the obtaining module is further configured to obtain the page component from a resource management platform, the page component being used for configuring the target application.

14. The device of any one of claims 10 to 13, wherein: the obtaining module is further configured to obtain target data from a data governance platform, the target data comprising instance information of the target service object.

15. The device of any one of claims 10 to 14, wherein: The construction module is further configured to set a management permission of the target application, so that a target department undertaking the target business can use the target application.

16. The apparatus of any one of claims 10 to 15, wherein, The scenario information of the target business includes a scenario name, a business domain, a theme domain, a leading department, and scenario description.

17. The apparatus of any one of claims 10-16, wherein, The target business matter includes basic information, a form, a process, and materials of the target business matter.

18. The apparatus of any one of claims 10-17, wherein, The target business object includes basic information, a logical entity, instance information, and data source information of the target business object.

19. A cluster of computing devices, characterized in that, including at least one computing device, each computing device including a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method of any one of claims 1-9.

20. A computer program product comprising instructions, characterized in that, When the instructions are executed by the cluster of computing devices, the cluster of computing devices performs the method of any one of claims 1-9.

21. A computer-readable storage medium, characterized in that, including computer program instructions, when the computer program instructions are executed by the cluster of computing devices, the cluster of computing devices performs the method of any one of claims 1-9.

Images