Tool integration and tool chain construction method and device based on B / S architecture

Abstract

The invention relates to a tool integration and tool chain construction method and device based on a B / S architecture, and the method comprises the steps: packaging a tool code corresponding to each tool to generate an integrated tool corresponding to each tool, and obtaining the tool code corresponding to each tool through development according to a preset development rule; the integrated tool is stored in an object storage server, and the object storage server has background service and is used for storing static resources; a plurality of integration tools are selected from the static page according to development requirements, a platform service of the object storage server is utilized to construct a tool chain, and the tool chain comprises a plurality of working links and an integration tool in each working link; obtaining a tool chain corresponding to the user access demand from the background service; and executing the workflow according to the tool chain. According to the scheme, development tool ecological co-construction is carried out, and the relation between tools is enhanced; working links of all tools are connected in series to form a complete workflow in combination with tool chain arrangement, and standardization and normalization of the workflow are facilitated.

Description

Technical Field

[0001] This specification relates to the field of software development, and in particular to a method and device for tool integration and tool chain construction based on B / S architecture. Background Art

[0002] As computer system architecture becomes increasingly complex, the size of development teams is gradually expanding. In order to standardize the R&D process and improve the quality and efficiency of R&D, project teams will use a variety of R&D platforms and tools. However, scattered tools will lead to low efficiency of cross-platform collaboration, and due to data barriers, it is difficult to see the full picture of project development on a certain tool or platform. Independent tools divide the R&D process, making it difficult to establish a standardized development process online. Therefore, the concept of platform engineering came into being. There are currently some related solutions on the market, mainly in two categories: 1. A fully open tool platform that supports embedded integration of third-party tools, allowing each project team to classify the tools they need through custom tags; 2. Customization within the platform, customizing the development of all tools within a platform.

[0003] There are two main problems with using a fully open tool platform: First, there is no data interaction between the tools, making it difficult to track matters across multiple tools, which brings difficulties to project management. Second, it only provides tool classification functions, and cannot connect the tools into an overall R&D process, and cannot implement R&D processes and specifications online.

[0004] There is a major problem with adopting customization within the platform. The highly coupled architectural design makes it impossible for the platform to achieve an open co-construction ecosystem, and it is difficult for the platform development team to meet the diverse needs of various projects in the short term. Summary of the invention

[0005] In order to solve the problem in the prior art that there is no data interaction between tools and the tools cannot be connected in series to form a whole, the embodiments of this specification provide a tool integration and tool chain construction method and device based on B / S architecture.

[0006] The embodiment of this specification provides a tool integration and tool chain construction method based on B / S architecture, the method comprising: packaging tool codes corresponding to each tool, generating integrated tools corresponding to each tool, wherein the tool codes corresponding to each tool are developed according to preset development rules; storing the integrated tools in an object storage server, wherein the object storage server is used to store static resources, and the object storage server has a background service; according to development requirements, selecting several integrated tools from the static resources, and using the platform service of the object storage server to build a tool chain, wherein the tool chain includes multiple work links and integrated tools in each work link; obtaining a tool chain corresponding to user access requirements from the background service; and executing a workflow according to the tool chain.

[0007] According to one aspect of an embodiment of the present specification, packaging tool codes corresponding to each tool and generating integrated tools corresponding to each tool includes: generating access links for each tool when packaging the tool codes; publishing the access links to an object storage server to generate integrated tools corresponding to each tool.

[0008] According to one aspect of an embodiment of the present specification, according to development requirements, several integration tools are selected from the static resources, and a tool chain is built using the platform service of the object storage server, including: defining the input and output parameters of the integration tools according to the functions of the integration tools, and the integration tools are working nodes of the working links; configuring the upstream nodes and downstream nodes of the working nodes according to the input and output parameters of each working node; and configuring the tool chain according to all working nodes, the upstream nodes and the downstream nodes.

[0009] According to one aspect of an embodiment of the present specification, before defining the input parameters and output parameters of the integration tool, the method further includes: classifying each integration tool according to its function; and configuring integration tools that belong to the same category as the functions of the work link to the work link for user selection.

[0010] According to one aspect of an embodiment of the present specification, obtaining a tool chain corresponding to a user access requirement from the background service includes: storing the constructed tool chain to an object storage server backend; and, based on a user access request, calling the object storage server backend to obtain the tool chain.

[0011] According to one aspect of the embodiments of the present specification, storing the constructed tool chain to the object storage server backend further includes: rendering multiple work nodes in the same work link in the tool chain to the same page, and obtaining pages corresponding to each work link in the tool chain, wherein each page displays the corresponding work link; storing the page to a static page of the object storage server; and calling the object storage server backend according to a user access request, and obtaining the tool chain includes: accessing the static page according to the user access requirement to obtain the tool chain.

[0012] According to one aspect of the embodiments of the present specification, according to the tool chain, executing the workflow includes: pre-creating work items and work types according to development requirements; monitoring the execution progress of the workflow; and closing completed work links and opening pending work links according to the execution progress.

[0013] The embodiment of this specification also provides a tool integration and tool chain construction device based on B / S architecture, and the device includes: an integrated tool generation unit, which is used to package the tool code corresponding to each tool and generate an integrated tool corresponding to each tool, and the tool code corresponding to each tool is developed according to preset development rules; a storage unit, which is used to store the integrated tool in an object storage server, wherein the object storage server is used to store static resources, and the object storage server has a background service; a tool chain construction unit, which is used to select a number of integrated tools from the static resources according to development requirements, and use the platform service of the object storage server to build a tool chain, wherein the tool chain includes multiple work links and integrated tools in each work link; a tool chain acquisition unit, which is used to acquire a tool chain corresponding to the user's access requirements from the background service; and an execution unit, which is used to execute the workflow according to the tool chain.

[0014] An embodiment of the present specification also provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the tool integration and tool chain construction method based on the B / S architecture is implemented.

[0015] The embodiments of this specification also provide a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the tool integration and tool chain construction method based on the B / S architecture.

[0016] The embodiments of this specification also provide a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the tool integration and tool chain construction method based on the B / S architecture.

[0017] This solution builds an ecological co-construction of development tools, strengthens the connection between tools through OpenAPI, and breaks down the data barriers between integrated tools; combined with the tool chain orchestration of the work to-do mechanism, the work links originally scattered across tools are connected in series into a complete workflow, which is conducive to the standardization and normalization of the work process. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1The figure is a flow chart of a tool integration and tool chain construction method based on B / S architecture according to an embodiment of the present specification;

[0020] Figure 2 The figure is a flow chart of a method for generating an integrated tool according to an embodiment of the present specification;

[0021] Figure 3 The figure is a flow chart of a method for building a tool chain according to an embodiment of the present specification;

[0022] Figure 4 The figure is a flow chart of a method for configuring a tool chain according to an embodiment of the present specification;

[0023] Figure 5 The figure is a flow chart of a method for obtaining a tool chain according to an embodiment of the present specification;

[0024] Figure 6 The figure shows a flow chart of another method for obtaining a tool chain according to an embodiment of the present specification;

[0025] Figure 7 The figure is a flow chart of a method for executing a workflow according to an embodiment of the present specification;

[0026] Figure 8 The figure shows a schematic diagram of the structure of a tool integration and tool chain building device based on B / S architecture according to an embodiment of the present specification;

[0027] Fig. 9 The figure shows a schematic diagram of the architecture of a co-construction integration tool on a public platform according to an embodiment of the present specification;

[0028] Fig.10 Shown is a schematic diagram of a tool chain arrangement according to an embodiment of this specification;

[0029] Fig.11 The figure shows a tool chain effect display diagram of an embodiment of this specification;

[0030] Fig.12 The figure shows a workflow identification architecture diagram of an embodiment of this specification;

[0031] Fig.13 It is a schematic diagram showing the definition of the input parameter structure of multiple working links in a tool chain according to an embodiment of this specification;

[0032] Fig.14 The figure shows a schematic diagram of the structure of a computer device according to an embodiment of the present specification.

[0033] Description of the accompanying symbols:

[0034] 801, integrated tool generation unit;

[0035] 802, storage unit;

[0036] 803. Tool chain building unit;

[0037] 804, tool chain acquisition unit;

[0038] 805, execution unit;

[0039] 1402. Computer equipment;

[0040] 1404, processor;

[0041] 1406. Memory;

[0042] 1408, driving mechanism;

[0043] 1410, input / output module;

[0044] 1412. Input device;

[0045] 1414. Output device;

[0046] 1416. Presentation equipment;

[0047] 1418. Graphical user interface;

[0048] 1420, network interface;

[0049] 1422, communication link;

[0050] 1424. Communication bus. DETAILED DESCRIPTION

[0051] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0052] It should be noted that the terms "first", "second", etc. in the description and claims of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0053] This specification provides method operation steps as described in the embodiments or flow charts, but more or fewer operation steps may be included based on routine or non-creative work. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the system or device product is executed in practice, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel.

[0054] It should be noted that the tool integration and tool chain construction method based on B / S architecture in this specification can be used in the field of software development and in the field of computer technology. This specification does not limit the application field of the tool integration and tool chain construction method based on B / S architecture.

[0055] Figure 1 The flowchart of a tool integration and tool chain construction method based on B / S architecture in an embodiment of this specification is shown, which specifically includes the following steps:

[0056] Step 101 , packaging tool codes corresponding to various tools to generate integrated tools corresponding to various tools, wherein the tool codes corresponding to various tools are developed according to preset development rules.

[0057] In this step, the service creation wizard is provided in this manual. The built-in framework code and component library of the created project can be developed by the development project team according to the specifications defined in the developer manual to obtain the tool code of each tool. Among them, the tool code can be developed by development project teams of multiple different projects, reflecting the diversity of code development.

[0058] Furthermore, the developed code project is hosted in a code repository, and the code is compiled and packaged to form a front-end static resource file or a back-end image. For example, after developing the code for tool 1, tool 2, tool 3, and tool 4, the codes corresponding to these four tools are compiled and packaged to generate integrated tool 1 corresponding to tool 1, integrated tool 2 corresponding to tool 2, integrated tool 3 corresponding to tool 3, and integrated tool 4 corresponding to tool 4.

[0059] Step 102: store the integrated tool in an object storage server, wherein the object storage server is used to store static resources and has a background service.

[0060] In step 101, during the process of packaging the tool code, an access link corresponding to each tool is generated. And through the automated publishing service provided by the platform for providing public services, GitLab CI / CD is triggered to deploy the packaged static resources to the platform's private warehouse (that is, the object storage service in this manual). In this step, during the process of storing the integrated tools on the object storage server, the access link corresponding to each tool is deployed to the object storage server, thereby completing the co-construction of multiple integrated tools on the object storage server.

[0061] Among them, the object storage server can be understood as a service provider, which can provide platform services, including: platform service 1, platform service 2, platform service 3, etc. In addition, the object storage server can provide a development module to support external users to co-build integrated tools. In addition, the object storage server can store static resources and display static resources to users during subsequent processing. At the same time, the object storage server has corresponding background services for providing services such as identity authentication, message push, and output storage / download.

[0062] Step 103, according to development requirements, select several integrated tools from the static resources, and use the platform service of the object storage server to build a tool chain, wherein the tool chain includes multiple work links and integrated tools in each work link.

[0063] In this step, different project teams have different development requirements. Each project team selects the required integration tools from the static page displayed by the object storage server according to its own development requirements, and uses the platform service of the object storage server to create tool chains corresponding to different workflows. Among them, the tool chain includes multiple work links and multiple integration tools. The integration tools here can be regarded as work nodes that constitute the work links. Each work link contains at least one work node.

[0064] In the embodiment of this specification, the tool for development and deployment provided by the above steps is automatically integrated into the platform represented by the machine object storage server. This method is called internal link integration. Since the front-end service is hosted in a private code repository, the platform domain name is used uniformly, and there will be no cross-domain problem.

[0065] In addition to accessing new tools developed by the development team according to standard procedures, the embodiments of this specification can also introduce existing or well-developed external tools and integrate them into the object service storage as external links. Among them, external links only need to configure the access link of the tool and open it inside the platform using the nested Iframe method. Reverse proxy is used to solve cross-domain problems, and a unified authentication API is provided to solve the problem of direct login. Therefore, the platform of this solution can integrate external links and internal links, and is suitable for the rapid integration solution of internal and external tools, so that users can customize tools according to their own needs, quickly integrate them into the platform for use, and are not limited by the platform's own development team. Compared with the existing technology, this solution has more advantages in ecological co-construction and improves the efficiency of tool integration and co-construction.

[0066] Step 104, obtaining a tool chain corresponding to the user's access requirement from the background service. In this step, when the user issues a requirement to access a tool chain on a browser page, the tool chain that the user wants to access can be determined in the background service according to the user.

[0067] Specifically, based on step 103, after the toolchain is built, it is stored in the background service of the object storage server. The background service of the object storage server summarizes all the built toolchains. The user's triggering behavior in the static service page: click on one or several toolchains. According to the user's click behavior, the browser obtains static resources from the object storage server and renders it into a page. The page calls the corresponding toolchain from the background server, loads the specific structure of the toolchain into the Nginx cache, and then returns it to the browser to render it into a page for display to the user.

[0068] Step 105, executing the workflow according to the tool chain. When the user obtains the tool chain, the development process can be executed according to the work links in the tool chain.

[0069] In this step, when the user accesses the browser, the static resource scheduling service loads the static resources stored in the object storage into the Nginx cache and then returns them to the browser to be rendered into a page for display to the user.

[0070] Figure 2 The flowchart of a method for generating an integrated tool according to an embodiment of the present specification is shown, which specifically includes the following steps:

[0071] Step 201, when packaging the tool code, generate access links for each tool. In the embodiment of this specification, the tool code developed according to the preset development rules cannot be executed directly, and it needs to be compiled before it can be executed. Specifically, the tool code needs to be packaged as a static resource file on the front end, and the tool code needs to be packaged as a mirror in the background. The packaged code can actually run.

[0072] Step 202: publish the access link to the object storage server and generate an integration tool corresponding to each tool.

[0073] Figure 3 The flowchart of a method for building a tool chain in an embodiment of this specification is shown, which specifically includes the following steps:

[0074] Step 301, according to the functions of each integration tool, define the input parameters and output parameters of the integration tool, and the integration tool is a working node of the working link.

[0075] In the embodiments of this specification, each integrated tool can realize its own function, and different integrated tools have different functions. According to the functions of different integrated tools, the output parameters and input parameters of each integrated tool can be determined.

[0076] In the embodiments of this specification, each node may include data interaction input parameter definition, data interaction output parameter definition and tool corresponding user manual or specification document in addition to the tool information. Specifically, the output parameter and input parameter of each integrated tool are determined according to the function of each integrated tool.

[0077] Step 302, configure the upstream node and downstream node of the working node according to the input and output parameters of each working node. The data interaction input and output parameters of the integrated tool can enable the node to receive the output data of the upstream node in the tool chain, and use the output data of the upstream node as the data input parameter of the current tool. After the current tool processes the data through the function, the output is formed in the format defined by the output parameter and delivered to the next node, thereby completing the entire data flow of the tool chain, thereby determining the output and input parameters of each integrated tool.

[0078] Step 303: Configure a tool chain according to all working nodes, the upstream nodes and the downstream nodes. In tool chain arrangement, each tool is packaged as a node, and the nodes can be freely combined by dragging and dropping on the page to arrange into a full-process tool chain.

[0079] In the embodiments of this specification, for example, in the tool chain involving the requirements and design process, there are three consecutive links, namely: requirements assessment, requirements specification writing, and requirements specification review. Among them, the requirement number, name, implementer and other information generated by the requirements assessment work node will be used as the basic information for the requirements specification writing to create the requirements specification corresponding to this requirement. After the requirements specification writing work node is completed, the generated requirements specification document will be used as the basic information for the requirements specification review to create an audit. The specific input and output parameter structure can be as follows Fig.13 shown.

[0080] Fig.13 Shown is a schematic diagram of the input parameter structure definition of multiple work links in a tool chain of an embodiment of this specification. In the figure, there are three work nodes, "Requirements Assessment", "Requirements Writing", and "Requirements Review". Define input parameters and output parameters for each work node. The output of the "Requirements Assessment" work node is consistent with the input parameters of the "Requirements Writing" work node, and the output of the "Requirements Writing" work node is consistent with the input parameters of the "Requirements Review" work node. According to the input parameters and output parameters of each work node, the upstream and downstream work nodes of each work node are determined, thereby determining the tool chain.

[0081] Figure 4 The flowchart of a method for configuring a tool chain in an embodiment of this specification is shown, which specifically includes the following steps:

[0082] Step 401, classify each integrated tool according to its function. In the embodiments of this specification, each integrated tool can realize different functions, and some integrated tools among multiple integrated tools will have the same or similar functions. Therefore, each integrated tool is classified according to its function to obtain a classification result. First, multiple integrated tools are preliminarily classified so that different types of integrated tools can be matched with work links quickly and efficiently in the later stage, and the arrangement or construction of the tool chain can be further completed quickly and efficiently.

[0083] Step 402: configure an integrated tool that has the same function as the work link to the work link for the user to select. In this step, the tool chain has at least one work link, and the work link has corresponding development and testing functions. Fig.10As shown, a complete tool chain includes the following work links: start, demand assessment, demand design, demand implementation, demand change, and end. Among them, the middle work links respectively include assessing development needs, carrying out specific design planning for development needs, and changing development needs. Therefore, according to the functions of each work link and the classification result of the integrated tool determined in step 401, the category of the integrated tool is matched with the function of the work link. If the category of the integrated tool is consistent, consistent or similar to the function of the work link, the integrated tool of this category is configured for each work link as a preliminary configuration tool for the work link, which is used to be selected by the system or user during the tool chain configuration process. This step preliminarily classifies the integrated tools and configures them to the corresponding work links, effectively improving the efficiency of the orchestration and construction tool chain, reducing the errors caused by selecting or randomly selecting the integration work adaptation work links from a large number of integrated tools, and improving the accuracy of the orchestration and construction tool chain.

[0084] Figure 5 The flowchart of a method for obtaining a tool chain in an embodiment of this specification is shown, which specifically includes the following steps:

[0085] Step 501, storing the constructed tool chain in the backend of the object storage server. In this step, the constructed tool chain is stored in the backend service group of the object storage server.

[0086] Step 502: according to the user access request, call the object storage server backend to obtain the tool chain.

[0087] The user sends an access request through the browser, which is intended to obtain the tool chain required by the user. Specifically, the user selects various different built tool chains presented in the static page provided by the static service browser. The user's selection behavior triggers the generation of the user access request. Based on the user's selection, the tool chain corresponding to the user access request is called from the object storage server backend to obtain the tool chain.

[0088] In the embodiment of this specification, the background service group of the object storage server provides background services with specific service functions. According to the user's access request to obtain the tool chain required by the user, the background service of the object server provides the tool chain that has been orchestrated.

[0089] Figure 6 The flowchart of another method for obtaining a tool chain in an embodiment of this specification is shown, which specifically includes the following steps:

[0090] Step 601, render multiple work nodes in the same work link in the tool chain to the same page, and obtain pages corresponding to each work link in the tool chain, wherein each page displays the corresponding work link. Fig.11 shown.

[0091] After the orchestration and construction tool chain is completed, the platform front end will render multiple work nodes of the same work link into one page for display, and share login information at the same time. Specifically, configure the access link of the tool and use the Iframe nesting method to open the tool page inside the platform, and get the following Fig.11 The integrated tool page in the black solid line area can be accessed through static resource scheduling or external links to obtain the integrated tool page.

[0092] Fig.11 The entire page is a work link. The left interface is the framework provided by the platform, which displays modules such as work name, work stage, and specification guidance. Among them, the work stage module specifically displays the user opening a specific work link in the work chain after obtaining the work chain, and the work nodes included in the work link. The left interface can switch work nodes according to the current progress of the development task, and simultaneously display the corresponding integrated tool page in the black solid line area. For example, Fig.11 In the development process, the user's current development task is executed to the "requirements design" work link, which includes two integrated tools: "requirements writing tool" and "requirements review tool".

[0093] Use reverse proxy to solve cross-domain problems and provide a unified authentication API to share user login credentials to achieve direct login.

[0094] According to the user access request, the object storage server backend is called to obtain the tool chain including:

[0095] Step 602: based on the user's access requirements, the page is stored and rendered into a static page of the object storage server, and the user obtains the tool chain.

[0096] In this step, after obtaining the user's access request, the page in step 601 is stored or rendered to the static page of the object storage server through the static resource scheduling service. The static resources stored in the static page of the object storage server are further loaded into the Nginx cache, and then returned to the browser to be rendered into a page for display to the user, so that the user can obtain the tool chain that he accesses.

[0097] Figure 7 The flowchart of a method for executing a workflow in an embodiment of the present specification is shown, which specifically includes the following steps:

[0098] Step 701, pre-create work items and work types according to development requirements.

[0099] In the embodiments of this specification, in order to apply the configured tool chain to actual work, it is also necessary to establish the corresponding relationship between work items, work types, processors and tool chains. That is, how to identify who is responsible for a work and what workflow to follow. Fig.12 The workflow recognition architecture diagram is shown in the figure. In the figure, a multi-dimensional work recognition engine is created. When processing work, work to-do is created in the order of tool chain arrangement based on work links. According to the dimensions such as work type, project to which the work belongs, designated person to handle the work, and work urgency, the current work is determined to which work scenario it belongs, and then the corresponding tool chain is executed.

[0100] In this step, according to the development requirements, Fig.12 Create work items and work types in .

[0101] Step 702: monitor the execution progress of the workflow. Fig.12 Automatically identify work types, work items, and the current execution progress of the workflow.

[0102] Step 703, according to the execution progress, close the completed work link and open the to-be-done work link.

[0103] When users process to-do tasks, Fig.12 Display the node tool page corresponding to the current work link, and use the tool to complete the current work link. When the previous work link is completed, the next work link is automatically created to achieve the purpose of workflow.

[0104] like Figure 8 The figure shows a schematic diagram of a tool integration and tool chain construction device based on a B / S architecture according to an embodiment of the present specification. The figure describes the basic structure of the tool integration and tool chain construction device based on a B / S architecture, wherein the functional units and modules can be implemented in software, or a general chip or a specific chip can be used to implement the tool integration and tool chain construction based on the B / S architecture. The device specifically includes:

[0105] An integrated tool generating unit 801 is used to package tool codes corresponding to various tools and generate integrated tools corresponding to various tools, wherein the tool codes corresponding to various tools are developed according to preset development rules;

[0106] A storage unit 802, used to store the integrated tool in an object storage server, wherein the object storage server is used to store static resources, and the object storage server has a background service;

[0107] A tool chain construction unit 803 is used to select several integrated tools from the static resources according to development requirements, and use the platform service of the object storage server to build a tool chain, wherein the tool chain includes multiple work links and integrated tools in each work link;

[0108] The tool chain acquisition unit 804 is used to acquire the tool chain corresponding to the user access requirement from the background service;

[0109] The execution unit 805 is used to execute the workflow according to the tool chain.

[0110] Fig. 9 The following is a schematic diagram of the architecture of an integrated tool co-built on a public platform in accordance with an embodiment of this specification. In the figure, the development team packages the developed tool code and integrates it into the public service platform. The backend service of the tool party uses OpenAPI to call the interfaces provided by the backend service of the platform, such as identity authentication, message push, and output storage / download.

[0111] Fig.10 The figure shows a schematic diagram of a tool chain arrangement of an embodiment of this specification. In the figure, the tool chain includes the following work links: start, demand assessment, demand design, demand implementation, demand change, and end. Among them, the intermediate work links include evaluating development requirements, making specific design plans for development requirements, and changing development requirements. Each work link corresponds to multiple work nodes. The work nodes are represented by integrated tools. For example, the demand assessment work link includes the integrated tool of the demand assessment tool; the demand design work link includes the requirement specification writing tool and the requirement specification review tool.

[0112] Fig.11 The figure shows a tool chain effect display diagram of an embodiment of this specification. Fig.11 The tool chain page shown shows the working process. The black solid line area is the integrated tool page, which can be accessed through static resource scheduling or external links. Fig.11 On the left is the framework provided by the platform. You can switch working nodes and simultaneously display the corresponding tool page in the black solid line area.

[0113] Fig.12 The figure shows a workflow identification architecture diagram of an embodiment of this specification. In order to apply the configured tool chain to actual work, a correspondence between work items, work types, handlers and tool chains is established. That is, how to identify who is handling a work and what workflow to follow. According to the four dimensions of work type, project to which the work belongs, designated handler of the work, and work urgency, determine what kind of work scenario the current work belongs to, and then execute the corresponding tool chain.

[0114] like Fig.14The diagram shows a schematic diagram of a computer device provided by an embodiment of the specification. The tool integration and tool chain construction method based on the B / S architecture described in the present application can be applied to the computer device. The computer device 1402 may include one or more processors 1404, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 1402 may also include any memory 1406, which is used to store any kind of information such as code, settings, data, etc. Non-limitingly, for example, the memory 1406 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 1402. In one case, when the processor 1404 executes an associated instruction stored in any memory or combination of memories, the computer device 1402 may perform any operation of the associated instruction. The computer device 1402 also includes one or more drive mechanisms 1408 for interacting with any storage, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0115] The computer device 1402 may also include an input / output module 1410 (I / O) for receiving various inputs (via input devices 1412) and for providing various outputs (via output devices 1414). A specific output mechanism may include a presentation device 1416 and an associated graphical user interface (GUI) 1418. In other embodiments, the input / output module 1410 (I / O), input device 1412, and output device 1414 may not be included, and the computer device 1402 may be used as a computer device in a network. The computer device 1402 may also include one or more network interfaces 1420 for exchanging data with other devices via one or more communication links 1422. One or more communication buses 1424 couple the components described above together.

[0116] The communication link 1422 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 1422 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0117] Corresponds to Figures 1 to 7 The method in the embodiment of the present specification also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0118] The embodiment of the present specification also provides a computer-readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 1 to 7 The method shown.

[0119] It should be understood that in the various embodiments of this specification, the size of the serial numbers of the above-mentioned processes does not mean 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 specification.

[0120] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0121] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this specification.

[0122] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0123] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0124] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this specification.

[0125] In addition, each functional unit in each embodiment of this specification may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0126] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this specification is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0127] Specific embodiments are used in this specification to illustrate the principles and implementation methods of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of this specification. At the same time, for those skilled in the art, according to the ideas of this specification, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on this specification.

Claims

1. A tool integration and tool chain construction method based on B / S architecture, characterized in that: The method comprises: Packing tool codes corresponding to each tool to generate integrated tools corresponding to each tool, wherein the tool codes corresponding to each tool are developed according to preset development rules; Storing the integrated tool in an object storage server, wherein the object storage server is used to store static resources and has a background service; According to development requirements, select several integrated tools from the static resources, and use the platform service of the object storage server to build a tool chain, wherein the tool chain includes multiple work links and integrated tools in each work link; Obtaining a tool chain corresponding to the user's access requirements from the backend service; According to the tool chain, a workflow is executed.

2. The method according to claim 1, characterized in that Packaging the tool codes corresponding to each tool and generating the integrated tools corresponding to each tool include: When packaging tool codes, generate access links for each tool; The access link is published to the object storage server, and an integrated tool corresponding to each tool is generated.

3. The method according to claim 2, characterized in that According to development requirements, several integrated tools are selected from the static resources, and the tool chain is constructed by using the platform service of the object storage server, including: According to the functions of each integrated tool, define the input and output parameters of the integrated tool, and the integrated tool is the working node of the working link; Configure the upstream and downstream nodes of the working node according to the input and output parameters of each working node; A tool chain is configured according to all working nodes, the upstream nodes and the downstream nodes.

4. The method according to claim 3, characterized in that Before defining the input parameters and output parameters of the integration tool, the method further includes: Classify each integrated tool according to its function; An integrated tool that belongs to the same category as the function of the work link is configured to the work link for user selection.

5. The method according to claim 1, characterized in that Obtaining a tool chain corresponding to the user's access requirements from the background service includes: Store the built toolchain to the object storage server backend; According to the user access request, the object storage server backend is called to obtain the tool chain.

6. The method according to claim 5, characterized in that Storing the built toolchain to the object storage server backend further includes: Render multiple work nodes in the same work link in the tool chain to the same page, and obtain pages corresponding to each work link in the tool chain, wherein each page displays the corresponding work link; According to the user access request, the object storage server backend is called to obtain the tool chain including: According to the user's access requirements, the page is stored and rendered as a static page in the object storage server, and the user obtains the tool chain.

7. The method according to claim 1, characterized in that According to the toolchain, the execution workflow includes: Pre-create work items and work types based on development requirements; Monitor the progress of workflow execution; According to the execution progress, the completed work link is closed and the to-be-done work link is opened.

8. A tool integration and tool chain construction device based on B / S architecture, characterized in that: The device comprises: An integrated tool generation unit, used to package tool codes corresponding to each tool and generate integrated tools corresponding to each tool, wherein the tool codes corresponding to each tool are developed according to preset development rules; A storage unit, used to store the integrated tool in an object storage server, wherein the object storage server is used to store static resources and the object storage server has a background service; A tool chain construction unit, configured to select a number of integrated tools from the static resources according to development requirements, and use the platform service of the object storage server to construct a tool chain, wherein the tool chain includes a plurality of work links and integrated tools in each work link; A tool chain acquisition unit, used to acquire a tool chain corresponding to the user's access requirements from the background service; The execution unit is used to execute the workflow according to the tool chain.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images