Canvas-based demand creation method, device, electronic device and storage medium

Abstract

The present application provides a canvas-based demand creation method, device, electronic device and storage medium, which relates to the field of computer technology. In this method, the creation demand of the first front end is obtained, and the creation demand is distributed on a canvas interface with multiple areas, each creation demand corresponds to one area, and the creation demand is organized through a preset mind map; the demand canvas data corresponding to the creation demand is read from a preset database, and the demand canvas data is loaded into a preset distributed repository, and the demand canvas data is transmitted to the first front end corresponding to the creation demand; in response to the update of the demand canvas data on the canvas interface, the creation update information is obtained; the creation update information of the first front end is obtained, the creation update information is stored in the distributed repository, and the creation update information is sent to the second front end; the creation update information in the distributed repository is obtained and saved in the database, which can ensure the integrity and consistency of the information.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a canvas-based demand creation method, device, electronic device, and storage medium. Background Art

[0002] In the software development process, requirement analysis is a crucial first step. Through requirement analysis, project goals and expected results can be determined, making the project more in line with user needs. Therefore, it is very necessary to improve the quality and efficiency of requirement creation. In related technologies, requirements are expressed by using text descriptions. When expressing, it is necessary to use external tools to express complex information such as business processes and system frameworks. For example, software requirements are generated through large models to obtain requirement texts. However, when requirements change, the update of requirement texts is more complicated, which can easily hinder team collaboration and communication, resulting in inaccurate information transmission, inconsistent documents, and low team collaboration efficiency. Summary of the Invention

[0003] This application provides a canvas-based demand creation method, device, electronic device and storage medium, which can ensure the integrity and consistency of information and improve team collaboration efficiency.

[0004] The technical solutions of the embodiments of this application are as follows:

[0005] In a first aspect, an embodiment of the present application provides a canvas-based demand creation method, the method comprising:

[0006] Acquire the creative requirements of the first front end, distribute the creative requirements on a canvas interface having multiple areas, each creative requirement corresponding to one area, and organize the creative requirements through a preset mind map-like method;

[0007] Reading demand canvas data corresponding to the creation demand from a preset database, loading the demand canvas data into a preset distributed repository, and transmitting the demand canvas data to the first front end corresponding to the creation demand;

[0008] In response to updating the demand canvas data on the canvas interface, creation update information is obtained;

[0009] Acquire creation update information of the first front end, store the creation update information in the distributed repository, and send the creation update information to the second front end, so that when a creation update occurs in the second front end, it is sent to the first front end;

[0010] The creation update information in the distributed repository is obtained and saved in the database.

[0011] In the above technical solution, the creative needs of the first front end are obtained and distributed on a canvas interface with multiple areas, each creative need corresponds to one area, the creative needs are organized through a preset mind map-like method, and multiple areas are formed through the canvas interface. Each area can record different types of demand information, and the needs are organized in the form of a mind map, thereby ensuring the integrity and consistency of the information; the demand canvas data corresponding to the creative needs is read from a preset database, and the demand canvas data is loaded into a preset distributed repository, and the demand canvas data is transmitted to the first front end corresponding to the creative needs to realize diversified forms of editing of the needs; in response to updating the demand canvas data on the canvas interface, creative update information is obtained, and user needs are met by performing demand creation; the creative update information of the first front end is obtained, the creative update information is stored in the distributed repository, and the creative update information is sent to the second front end, so that when a creative update occurs on the second front end, it is sent to the first front end. By transmitting information to multiple parties, the convenience of communication is guaranteed and the efficiency of team collaboration is improved; the creative update information in the distributed repository is obtained and saved in the database, thereby ensuring the integrity and consistency of the updated information, improving the efficiency of team collaboration, and avoiding document inconsistencies.

[0012] In some embodiments of the present application, the canvas interface has multiple components in a cascading relationship;

[0013] The response to updating the demand canvas data on the canvas interface to obtain creation update information includes:

[0014] Verifying the editing permission on the canvas interface, and if the editing permission is granted, constructing a demand structure in response to a dragging operation on the component on the canvas interface, wherein logical relationships of the components are verified during the dragging operation;

[0015] Perform collaborative editing according to the requirement structure to obtain requirement editing information;

[0016] Perform version checking on the required editing information to obtain the creation update information.

[0017] In some embodiments of the present application, performing collaborative editing according to the requirement structure to obtain requirement editing information includes:

[0018] Displaying multiple editing actions on the canvas interface according to the requirement structure, wherein the editing actions include requirement annotations and requirement replies and are generated by multiple users;

[0019] The document is improved using the requirement annotation and the requirement reply to obtain the requirement editing information.

[0020] In some embodiments of the present application, performing version checking on the required editing information to obtain the creation update information includes:

[0021] Backing up the required editing information to obtain backup information;

[0022] The current required editing information is compared with the backup information. If the documents are inconsistent, the current required editing information is used as the creation update information.

[0023] In some embodiments of the present application, in response to updating the demand canvas data on the canvas interface to obtain the creation update information, includes:

[0024] Editing the requirements according to the requirements canvas data to obtain edited data, and extracting questions from the edited data to obtain extracted questions;

[0025] Using preset guiding rules to perform intent recognition on the extraction question to obtain intent information, and performing vector matching in a preset vector library based on the intent information to obtain vector related information;

[0026] Generate a statement based on the vector-related information and the intent information using the guidance rule to obtain a query statement;

[0027] Utilizing the query statement to query a preset database, utilizing a preset large language model to process the query content and the intent information, and obtaining answer information corresponding to the extracted question;

[0028] The editing data is improved using the answer information to obtain the creation update information.

[0029] In some embodiments of the present application, after obtaining the creation update information in the distributed repository and saving it in the database, the method further includes:

[0030] Encapsulating the creation and update information into web page data;

[0031] The web page data is parsed to obtain parsed data, and the parsed data is converted into an editable document.

[0032] In some embodiments of the present application, parsing the webpage data to obtain parsed data, and converting the parsed data into an editable document includes:

[0033] The web page data is parsed using the preset BeautifulSoup library to obtain parsed data, and the parsed data is converted into a word document using the python-docx library.

[0034] In a second aspect, an embodiment of the present application provides a canvas-based demand creation device, the device comprising:

[0035] A data acquisition module, configured to acquire the creative requirements of the first front end, distribute the creative requirements on a canvas interface having multiple areas, each creative requirement corresponding to one area, and organize the creative requirements through a preset mind map-like structure;

[0036] A canvas acquisition module is used to read the demand canvas data corresponding to the creation demand from a preset database, load the demand canvas data into a preset distributed repository, and transmit the demand canvas data to the first front end corresponding to the creation demand;

[0037] A response update module, configured to update the required canvas data in response to the canvas interface to obtain creation update information;

[0038] An information interaction module, configured to obtain creation update information of the first front end, store the creation update information in the distributed repository, and send the creation update information to the second front end, so that when a creation update occurs in the second front end, it is sent to the first front end;

[0039] The information storage module is used to obtain the creation update information in the distributed repository and save it in the database.

[0040] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor, a memory, a user interface, a communication bus, and a network interface, wherein the processor, the memory, the user interface, and the network interface are respectively connected to the communication bus, the memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device executes any one of the methods provided in the first aspect.

[0041] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed, any one of the methods provided in the first aspect is executed.

[0042] In summary, one or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

[0043] 1. The method adopts the method of first obtaining the creative requirements of the first front end and distributing the creative requirements on a canvas interface with multiple areas, each creative requirement corresponds to an area, organizing the creative requirements through a preset mind map, forming multiple areas through the canvas interface, each area can record different types of demand information, and organizing the requirements in the form of a mind map, thereby ensuring the integrity and consistency of the information; reading the demand canvas data corresponding to the creative requirements from the preset database, loading the demand canvas data into the preset distributed repository, and transmitting the demand canvas data to the first front end corresponding to the creative requirements to realize diversified editing of the requirements; in response to the update of the demand canvas data on the canvas interface, obtaining the creative update information, and satisfying the user's needs by performing demand creation; obtaining the creative update information of the first front end, storing the creative update information in the distributed repository, and sending the creative update information to the second front end, so that when the creative update occurs on the second front end, it is sent to the first front end. By transmitting information to multiple parties, the convenience of communication is guaranteed and the efficiency of team collaboration is improved; obtaining the creative update information in the distributed repository and saving it in the database, ensuring the integrity and consistency of the updated information, improving the efficiency of team collaboration, and avoiding document inconsistencies. Therefore, it effectively solves the problems of inaccurate information transmission, inconsistent documents, and low team collaboration efficiency in related technologies.

[0044] 2. Demand is constructed through diverse and related components, ensuring the richness of the demand creation process.

[0045] 3. The canvas interface introduces functions such as collaborative editing and annotation, allowing users to perform collaborative editing and further improve team collaboration efficiency.

[0046] 4. Introduce guiding rules in the large model to assist in writing demand content, achieve efficient retrieval and document writing, and provide solution references. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 This is a flowchart of a canvas-based demand creation method provided by an embodiment of the present application;

[0048] Figure 2 yes Figure 1 A schematic flow chart of a sub-step of step S300;

[0049] Figure 3 yes Figure 2 A schematic flow chart of a sub-step of step S320;

[0050] Figure 4 yes Figure 1 Another sub-step flow diagram of step S300;

[0051] Figure 5 This is a schematic diagram of canvas design interaction of a canvas-based demand creation method provided by an embodiment of the present application;

[0052] Figure 6 This is a collaborative editing diagram of a canvas-based demand creation method provided by an embodiment of the present application;

[0053] Figure 7 This is a data parsing diagram of a canvas-based demand creation method provided by an embodiment of the present application;

[0054] Figure 8 This is a schematic diagram of the structure of a canvas-based demand creation device provided by an embodiment of the present application;

[0055] Figure 9 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0056] 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 application, not all of the embodiments.

[0057] In the description of the embodiments of this application, words such as "for example" or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "for example" or "for instance" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "for example" or "for instance" is intended to present the relevant concepts in a concrete manner.

[0058] In the description of the embodiments of the present application, the term "multiple" means two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals. In addition, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0059] The embodiment of the present application provides a canvas-based demand creation method, device, electronic device and readable storage medium. The canvas-based demand creation method first obtains the creation demand of the first front end, and distributes the creation demand on a canvas interface with multiple areas. Each creation demand corresponds to an area. The creation demand is organized through a preset mind map. Multiple areas are formed through the canvas interface. Each area can record different types of demand information. The demand is organized in the form of a mind map to ensure the integrity and consistency of the information; the demand canvas data corresponding to the creation demand is read from a preset database, and the demand canvas data is loaded into a preset distributed repository, and the demand canvas data is transmitted to the creation demand. The first front end responds to the needs and realizes the editing of diversified forms of needs; in response to the needs canvas data on the canvas interface, the creation update information is obtained, and the user needs are met by creating needs; the creation update information of the first front end is obtained, the creation update information is stored in the distributed repository, and the creation update information is sent to the second front end, so that when the creation update occurs in the second front end, it is sent to the first front end. By transmitting information to multiple parties, the convenience of communication is guaranteed and the efficiency of team collaboration is improved; the creation update information in the distributed repository is obtained and saved in the database to ensure the integrity and consistency of the updated information, improve the efficiency of team collaboration, and avoid document inconsistencies.

[0060] It should be noted that this canvas-based demand creation method is mainly used for demand analysis in the software development process. In addition, it can also be applied to demand analysis of services in the service industry, demand analysis creation in understanding the market, and other scenarios that require demand analysis. It is widely used.

[0061] The technical solutions provided in the embodiments of the present application are further described below in conjunction with the accompanying drawings.

[0062] Reference Figure 1 , Figure 1 1 is a flowchart of a canvas-based demand creation method provided in an embodiment of the present application. The canvas-based demand creation method is applied to a websock server. A canvas-based demand creation device in the websock server executes the canvas-based demand creation method through a processor in an electronic device or a readable storage medium. The canvas-based demand creation method includes steps S100, S200, S300, S400, and S500.

[0063] Step S100: Acquire the creative requirements of the first front end, and distribute the creative requirements on a canvas interface having multiple areas, where each creative requirement corresponds to one area, and organize the creative requirements through a preset mind map-like method.

[0064] In one embodiment, the creative requirements of the first front end are obtained. The creative requirements are requests from the creator of the requirements to create a requirement document after understanding the requirements, including business background, business goals, various functional modules, etc. The first front end can use the creator of the requirements to input the creative requirements. In addition to obtaining the creative requirements by input, voice, pictures, etc. can also be used to convert voice and pictures into text, thereby obtaining the creative requirements of the first front end. The creative requirements of the first front end are then obtained through a preset interface. Specifically, protocol transmission can be used to obtain the creative requirements. The creative requirements are distributed on a canvas interface with multiple areas. Each creative requirement corresponds to an area, and different types of demand information can be recorded. The creative requirements are organized through a preset mind map. The mind map can organize the creative requirements of each area together to form a demand structure with correlation relationships. The integrity and consistency of the demand information can be ensured by the mind map method.

[0065] In another embodiment, the first front-end can have multiple creative requirements, and these requirements can be distributed across multiple areas of the canvas interface, with each requirement corresponding to one area. There can also be multiple front-ends, meaning multiple creators can collaborate on requirement creation, while another creator can create requirements on a second front-end. There can also be a third front-end, a fourth front-end, and so on, enabling collaborative editing and creation within the team. In this process, the multiple areas of the canvas interface and the mind map-like interface can ensure the integrity and consistency of requirement information, improving team collaboration efficiency.

[0066] Step S200: read the demand canvas data corresponding to the creation demand from a preset database, load the demand canvas data into a preset distributed storage repository, and transmit the demand canvas data to a first front end corresponding to the creation demand.

[0067] In one embodiment, according to the obtained creation requirements, the corresponding requirement canvas data is read from a preset database. The preset database is a MySQL database, or a DB database, etc., which can store data and will not be elaborated here. The requirement canvas data is the requirement data corresponding to the requirement creation. The requirement canvas data is read from the database through the number of the requirement creation. The requirement canvas data can be represented in the form of a component, and the requirement canvas data is loaded into a preset distributed repository to prepare for subsequent editing and creation. The preset distributed repository is a redis library, or it can be other cache libraries. The requirement canvas data is transmitted to the first front end corresponding to the creation requirement, so that the requirement creator can create the requirement on the first front end.

[0068] Step S300, in response to updating the required canvas data on the canvas interface, obtains creation update information.

[0069] In one embodiment, the canvas interface has multiple components in a cascade relationship, and each component is a prefabricated template, which can realize a variety of writing forms. Figure 2 As shown, in response to updating the demand canvas data on the canvas interface, obtaining the creation update information includes but is not limited to the following steps:

[0070] Step S310 , verifying the editing authority on the canvas interface. If the editing authority is granted, a demand structure is constructed in response to a dragging operation on a component on the canvas interface, wherein the logical relationship of the component is verified during the dragging operation.

[0071] In some possible embodiments of the present application, the editing permissions on the canvas interface are first verified, and the user role can be used to determine the editing permissions. For example, the editor is the team leader with higher permissions, including annotation, modification, and generation of flowcharts, while ordinary team members only have writing operations, etc. The security of the data can be guaranteed by verifying permissions through user roles. In the case of having editing permissions, the demand canvas data can be edited and updated, the components on the canvas interface can be dragged and dropped, and in response to the dragging operation of the components on the canvas interface, the demand canvas data is updated and modified. The demand content can be organized in a stacking block manner to construct a demand structure so that the creation update information can be generated according to the demand structure to generate the demand document. It should be noted that due to the cascading relationship between the components, the logical relationship of the components needs to be verified during the dragging process. According to the mind map arranged in the components, the logical relationship of the components can be determined, thereby constructing the correct demand structure.

[0072] Each component interacts with the editor in a different way, depending on its definition. Basic components include rich text boxes, JavaScript dynamic tables, file upload and download components, and flowchart drawing components, supporting a wide range of user expression needs. Changes in requirements are regularly detected and saved for subsequent backup.

[0073] Step S320: perform collaborative editing according to the requirement structure to obtain requirement editing information.

[0074] In one embodiment, based on the requirement structure obtained in step S310, the canvas interface also supports multiple editors to perform collaborative editing, obtaining requirement edit information so that subsequent creation update information can be generated based on the requirement edit information. Collaborative editing includes requirement annotations, replies to requirement annotations, chat box discussions, and comments. This ensures that each editor can see the editing actions of other editors, not only ensuring information consistency but also improving team communication efficiency.

[0075] like Figure 3 As shown, collaborative editing is performed according to the requirement structure to obtain requirement editing information, including but not limited to the following steps:

[0076] Step S321: Display multiple editing actions on the canvas interface according to the demand structure. The editing actions include demand annotations and demand replies, and are generated by multiple users.

[0077] In some possible embodiments of this application, editing is performed based on the requirement structure, with multiple editors (i.e., users) performing editing. Multiple editing actions are displayed on the canvas interface, including requirement annotations, requirement replies, chat box discussions, and comments, thereby improving team communication efficiency. The canvas interface can also display the editor's relevant identity information, allowing users to distinguish the content edited by each user.

[0078] Step S322: Use the requirement annotations and requirement replies to improve the document and obtain requirement editing information.

[0079] In some possible embodiments of the present application, based on the content of the writing and editing, the document content is filled with demand annotations and demand replies, so that the document can be specific and rich, clearly express the purpose of the demand, and obtain demand editing information.

[0080] In other possible embodiments of the present application, collaborative editing can also be performed through integrated drawing tools, etc., to achieve various forms of graphic drawing such as organizational charts, business process diagrams, swim lane diagrams, etc., thereby increasing the richness of collaborative editing.

[0081] Step S330: perform version check on the required editing information to obtain creation update information.

[0082] In some possible embodiments of the present application, since multiple editors are editing, it is necessary to perform version checking on the required editing information, and use the checked version as the creation update information. By performing version checking, the correctness of the final version can be ensured, and the integrity and consistency of the information can be guaranteed.

[0083] Specifically, performing version checking on the required editing information to obtain the creation update information includes but is not limited to the following steps:

[0084] Step S331: Back up the required editing information to obtain backup information.

[0085] In some possible embodiments of the present application, during version verification, the requirement editing information may be backed up first to obtain backup information. This backup information can prevent information loss during verification and can also be used to compare and confirm uncertain content to ensure information integrity. The requirement editing information may be backed up in the form of data preservation, and the data may be stored in another database.

[0086] Step S332: compare the current required editing information with the backup information. If the documents are inconsistent, use the current required editing information as the creation update information.

[0087] In some possible embodiments of the present application, after backing up the required editing information, the required editing information can be edited again to obtain the current required editing information. Alternatively, the required editing information can be directly used as the current required editing information to determine whether the information has been edited and updated. The current required editing information is then compared with the backup information using a preset comparison algorithm, which can be a character similarity algorithm. If the documents are inconsistent, indicating that the editing information has been updated, the current required editing information is used as the creation update information to ensure the accuracy of the creation update information.

[0088] like Figure 4 As shown, in response to updating the demand canvas data on the canvas interface, obtaining the creation update information includes but is not limited to the following steps:

[0089] Step S340 , performing demand editing according to the demand canvas data to obtain edited data, and extracting problems from the edited data to obtain extracted problems.

[0090] In one embodiment, the editing authority on the canvas interface is first verified, and the user role can be used to determine the editing authority. The authority verification through the user role can ensure the security of the data, which is similar to step S310 and will not be repeated here. In the case of having editing authority, the canvas data is updated and edited according to the requirements, and the components on the canvas interface can be dragged and dropped. In response to the dragging operation of the components on the canvas interface, the requirements content can be organized in the form of stacking blocks to obtain editing data, so that the text can be expanded and improved according to the editing data later. It should be noted that due to the cascading relationship between the components, the logical relationship of the components needs to be verified during the dragging process. According to the mind map arranged in the components, the logical relationship of the components can be determined, thereby constructing the correct requirement structure.

[0091] In another embodiment, question extraction is performed on the edited data obtained above. Specifically, manually formulated rules can be used to summarize the questions in the edited data to obtain extracted questions, so that intent recognition can be performed based on the extracted questions. The manually formulated rules can be manually summarized from the edited data and then the extracted questions are transmitted to the websock server for processing. Alternatively, the questions can be manually input and then transmitted to the websock server for processing.

[0092] In step S350 , the intent of the extraction question is identified using the preset guiding rules to obtain intent information, and vector matching is performed in a preset vector library based on the intent information to obtain vector related information.

[0093] In one embodiment, the preset guidance rules are expressed as prompt statements, which are rules preset by experts. The preset guidance rules are used to identify the intent of the extraction problem, mainly identifying business rules, functions, business processes, function paths, documents, etc., to obtain intent information so that vector queries can be performed based on the intent information. The preset vector library includes multiple matadata vectors. The specific query is to use the intent information to match vectors one by one in the preset vector library, and use the cosine similarity algorithm to calculate the similarity between the intent information and the matadata vector to obtain vector related information, so that the vector related information can be used to generate query statements later.

[0094] Step S360: Generate a statement based on the vector-related information and the intent information using the guidance rules to obtain a query statement.

[0095] In one embodiment, the guidance rules are similar to the guidance rules in step S350 and are preset by experts. The guidance rules are used to generate statements based on the vector-related information and intent information to generate cypher query statements, so that data can be subsequently queried based on the cypher query statements.

[0096] Step S370: Use the query statement to query in the preset database, use the preset large language model to process the query content and intention information, and obtain the answer information corresponding to the extracted question.

[0097] In one embodiment, the cypher query statement obtained in step S360 is used to query data from a preset database, a neo4j database, using a preset application programming interface (API). The preset database is stored in the business data corresponding to the cypher query statement. The business data and intent information are processed using a preset large language model. Specifically, feature extraction and feature fusion operations can be performed on the business data and intent information to obtain answer information corresponding to the extracted question. This answer information can be an answer to the question or an enrichment and expansion of the extracted question, including rich search content, which can provide a reference solution for subsequent use in demand editing.

[0098] Step S380: Use the answer information to improve the editing data and obtain the creation update information.

[0099] In one embodiment, the answer information can be used to replace the edited data, or the content in the answer information can be used to supplement the edited data, wherein the supplementation operation is performed through manual screening to obtain the creation update information. The creation update information includes rich search content, and the editing of the required content is more comprehensive.

[0100] Figure 5 The canvas design interaction diagram is shown. For a certain requirement, the canvas interface displays the details of the requirement order, requirement overview, business scenario, system flow chart, system relationship diagram, requirement scope, function description, requirement plan, attachments, etc., which have a cascading relationship. Figure 5 The function description, process, rules, etc. all have their own corresponding pages, which are not shown in the figure.

[0101] Step S400, obtain the creation update information of the first front end, store the creation update information in the distributed repository, and send the creation update information to the second front end, so that when the creation update occurs in the second front end, it is sent to the first front end.

[0102] In one embodiment, the creation update information of the first front-end can be obtained through a transmission protocol and stored in a distributed repository, which can be a Redis library or other cache database. The creation update information is saved and the modified content can be saved at any time to facilitate the subsequent tracing of the required version. In response to the first front-end editing the required creation, the creation update information is sent to the second front-end so that other creators can synchronize with the required creation, ensuring the integrity and consistency of information in multiple front-ends.

[0103] Specifically, when an update occurs in the first front end, it is sent to the second front end. When a creative update occurs in the second front end, the creative update information will also be sent to the first front end. The second front end is regarded as the first front end, and the first front end is regarded as the second front end. The second front end executes steps S100 to S400 to ensure that the update information of each front end can be synchronized to other front ends. It should be noted that when the second front end is creating, the creative requirements of the second front end are obtained, and it is determined whether the creative requirements are loaded into redis. If loaded, the data in redis can be directly returned; if not loaded, the demand canvas data corresponding to the creative requirements is read from the preset database, and the demand canvas data is loaded into the preset distributed repository, and similar subsequent operations are performed as mentioned above. Having multiple front ends can perform creative editing according to the above process, which can ensure the integrity and consistency of information and improve team collaboration efficiency.

[0104] like Figure 6As shown, the instructions for editing the first front end and the second front end are performed. The first front end is front end 1, the second front end is front end 2, and the processing process is a websock service. Get the creative needs of front end 1, and distribute the creative needs on a canvas interface with multiple areas. Each creative need corresponds to an area, and the creative needs are organized through a preset mind map; read the demand canvas data corresponding to the creative needs from the MySQL database, and load the demand canvas data into the preset redis library, and transmit the demand canvas data to the front end 1 corresponding to the creative needs. Get the creative needs of front end 2, and distribute the creative needs on a canvas interface with multiple areas. Each creative need corresponds to an area, and the creative needs are organized through a preset mind map; determine whether the creative needs are loaded into the redis library. If loaded, the data in the redis library can be directly returned; if not loaded, read the demand canvas data corresponding to the creative needs from the preset database, and load the demand canvas data into the preset redis library. Front-end 1 modifies the demand canvas data and, in response to the canvas interface, updates the demand canvas data to obtain creation update information. It then obtains the creation update information of the first front-end, stores it in the distributed repository, and sends it to front-end 2. Front-end 2 updates the demand canvas data, sends the updated data, and disconnects the session. The modified information is sent to front-end 1. The creation update information in the distributed repository is obtained and saved in the database to ensure the integrity and consistency of the updated information, improve team collaboration efficiency, and avoid document inconsistencies. Front-end 1 modifies the canvas, submits and saves it, and generates a document.

[0105] Step S500: Obtain creation update information in the distributed repository and save it in the database.

[0106] In one embodiment, the creation update information in the distributed repository redis is read out using a data reading function, and then saved to the database using a saving function for subsequent use.

[0107] In one embodiment, after obtaining the creation update information in the distributed repository and saving it in the database, the canvas-based demand creation method also includes but is not limited to: encapsulating the creation update information into web page data; parsing the web page data to obtain parsed data, and converting the parsed data into an editable document.

[0108] Specifically, creation and update information is stored in the database in JSON format, while web page data is displayed using HTML data. The JSON data contains the canvas structure and user-entered data, and can be easily converted into HTML data. JavaScript can be used to parse the JSON data and encapsulate it into HTML data for subsequent processing. The web page data is then parsed and converted into an editable document for viewing and editing.

[0109] In one embodiment, web page data is parsed to obtain parsed data, and the parsed data is converted into an editable document, including but not limited to: using a preset BeautifulSoup library to parse the web page data to obtain parsed data, and using the python-docx library to convert the parsed data into a word document.

[0110] like Figure 7 As shown, the web page data is HTML data, and the editable document is a Word document. The BeautifulSoup library integrated in the Python library is used to parse the HTML data, and then the python-docx library integrated in the Python library is used to convert the parsed data into a Word document for easy viewing and editing.

[0111] like Figure 8As shown, the embodiment of the present application provides a canvas-based demand creation device 100, which obtains the creation demand of the first front end through the data acquisition module 110, and distributes the creation demand on a canvas interface with multiple areas, each creation demand corresponds to an area, and organizes the creation demand through a preset mind map-like method, and forms multiple areas through the canvas interface. Each area can record different types of demand information, and organizes the demand in the form of a mind map to ensure the integrity and consistency of the information; then, the canvas acquisition module 120 reads the demand canvas data corresponding to the creation demand from the preset database, and loads the demand canvas data into the preset distributed repository, and transmits the demand canvas data to the first front end corresponding to the creation demand, so as to realize The system can edit the content in various forms according to the current needs; use the response update module 130 to respond to the update of the demand canvas data on the canvas interface, obtain the creation update information, and meet the user needs by creating the needs; then use the information interaction module 140 to obtain the creation update information of the first front end, store the creation update information in the distributed repository, and send the creation update information to the second front end, so that when the creation update occurs in the second front end, it is sent to the first front end. By transmitting the information to multiple parties, the convenience of communication is guaranteed and the efficiency of team collaboration is improved; use the information storage module 150 to obtain the creation update information in the distributed repository and save it to the database to ensure the integrity and consistency of the updated information, improve the efficiency of team collaboration, and avoid document inconsistencies.

[0112] It should be noted that the data acquisition module 110 is connected to the canvas acquisition module 120, the canvas acquisition module 120 is connected to the response update module 130, the response update module 130 is connected to the information interaction module 140, and the information interaction module 140 is connected to the information storage module 150. The above-mentioned canvas-based demand creation method is applied to a canvas-based demand creation device 100. The canvas-based demand creation device 100 obtains the creative demand of the first front end and distributes the creative demand on a canvas interface with multiple areas. Each creative demand corresponds to an area, and the creative demand is organized through a preset mind map. Multiple areas are formed through the canvas interface. Each area can record different types of demand information, and the demand is organized in the form of a mind map, thereby ensuring the integrity and consistency of the information; the demand canvas data corresponding to the creative demand is read from the preset database, and the demand canvas data is loaded into the preset distributed repository, and the demand canvas data is transmitted to the corresponding The first front end is used to realize diversified forms of editing of requirements; in response to the update of the requirement canvas data on the canvas interface, the creation update information is obtained, and the user requirements are met by creating the requirements; the creation update information of the first front end is obtained, the creation update information is stored in the distributed repository, and the creation update information is sent to the second front end, so that when the creation update occurs in the second front end, it is sent to the first front end. By transmitting information to multiple parties, the convenience of communication is guaranteed and the efficiency of team collaboration is improved; the creation update information in the distributed repository is obtained and saved in the database to ensure the integrity and consistency of the updated information, improve the efficiency of team collaboration, and avoid document inconsistencies.

[0113] It should also be noted that the above embodiments provide devices that implement their functions using only the division of the above functional modules as examples. In actual 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. In addition, the device and method embodiments provided in the above embodiments are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0114] This application also discloses an electronic device. Figure 9 , Figure 9 Schematic diagram of the structure of an electronic device according to an embodiment of the present application. The electronic device 500 may include: at least one processor 501 , at least one network interface 504 , a user interface 503 , a memory 505 , and at least one communication bus 502 .

[0115] The communication bus 502 is used to implement the connection and communication between these components.

[0116] The user interface 503 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 503 may also include a standard wired interface and a wireless interface.

[0117] The network interface 504 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0118] The processor 501 may include one or more processing cores. Using various interfaces and circuits, the processor 501 connects to various components within the server. It executes instructions, programs, code sets, or instruction sets stored in the memory 505, as well as accesses data stored in the memory 505, to perform various server functions and process data. Optionally, the processor 501 may be implemented using at least one of the following hardware forms: a digital signal processing (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 501 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing content displayed on the display screen; and the modem handles wireless communications. It is understood that the modem may also be implemented as a separate chip, rather than integrated into the processor 501.

[0119] Among them, the memory 505 may include a random access memory (RAM) or a read-only memory (Read-Only Memory). Optionally, the memory 505 includes a non-transitory computer-readable storage medium. The memory 505 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 505 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 505 may also be optionally at least one storage device located away from the aforementioned processor 501. Reference Figure 9, the memory 505 as a computer storage medium may include an operating system, a network communication module, a user interface module and an application program of a canvas-based demand creation method.

[0120] exist Figure 9 In the electronic device 500 shown, the user interface 503 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 501 can be used to call an application program stored in the memory 505 for a canvas-based demand creation method. When executed by one or more processors 501, the electronic device 500 executes one or more methods in the above-mentioned embodiments. It should be noted that for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should know that this application is not limited to the described order of actions, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required for this application.

[0121] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0122] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely schematic, such as the division of units, which is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interface, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0123] Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0124] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0125] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of this application, or the portion that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the method of this application. The aforementioned memory includes various media that can store program code, such as USB flash drives, mobile hard drives, magnetic disks, or optical disks.

[0126] The above are merely exemplary embodiments of the present disclosure and are not intended to limit the scope of the present disclosure. In other words, any equivalent variations and modifications made in accordance with the teachings of the present disclosure are still within the scope of the present disclosure. Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the disclosure and the practical implications thereof.

[0127] This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not described herein. The description and examples are to be considered as exemplary only, and the scope and spirit of the present disclosure are to be defined by the claims.

Claims

1. A canvas-based demand creation method, characterized in that: Applied to the requirements analysis phase of the software development process, the method includes: Acquire the creative requirements of the first front end, distribute the creative requirements on a canvas interface having multiple areas, each creative requirement corresponding to one area, and organize the creative requirements through a preset mind map-like method; Reading demand canvas data corresponding to the creation demand from a preset database, loading the demand canvas data into a preset distributed repository, and transmitting the demand canvas data to the first front end corresponding to the creation demand; There are multiple components in a cascade relationship on the canvas interface, and the editing permission on the canvas interface is verified. If the editing permission is granted, a demand structure is constructed in response to a dragging operation on the components on the canvas interface, wherein the logical relationship of the components is verified during the dragging operation; Displaying multiple editing actions on the canvas interface according to the requirement structure, wherein the editing actions include requirement annotation, requirement reply, chat box discussion, and comment, and are generated by multiple users; Using the requirement annotations and the requirement replies to improve the document, and obtain requirement editing information, the requirement editing information including an organizational chart, a business process diagram, and a swim lane diagram; Performing version checking on the required editing information to obtain creation update information; Acquire creation update information of the first front end, store the creation update information in the distributed repository, and send the creation update information to the second front end, so that when a creation update occurs in the second front end, it is sent to the first front end; Obtaining the creation update information in the distributed repository and saving it to the database; The response to updating the demand canvas data on the canvas interface to obtain creation update information includes: Performing requirement editing according to the requirement canvas data to obtain edited data, and extracting questions from the edited data to obtain extracted questions, wherein the edited data includes annotation data; Using preset guiding rules to perform intent recognition on the extraction question to obtain intent information, and performing vector matching in a preset vector library based on the intent information to obtain vector related information; Generate a statement based on the vector-related information and the intent information using the guidance rule to obtain a query statement; Utilizing the query statement to query a preset database, utilizing a preset large language model to process the query content and the intent information, and obtaining answer information corresponding to the extracted question, wherein the answer information includes an expansion of the extracted question and an answer to the extracted question; The editing data is improved using the answer information to obtain the creation update information.

2. The method according to claim 1, characterized in that The version checking of the required editing information to obtain the creation update information includes: Backing up the required editing information to obtain backup information; The current required editing information is compared with the backup information. If the documents are inconsistent, the current required editing information is used as the creation update information.

3. The method according to claim 1, characterized in that After obtaining the creation update information from the distributed repository and saving it in the database, the method further includes: Encapsulating the creation and update information into web page data; The web page data is parsed to obtain parsed data, and the parsed data is converted into an editable document.

4. The method according to claim 3, characterized in that The parsing of the webpage data to obtain parsed data and converting the parsed data into an editable document includes: The web page data is parsed using the preset BeautifulSoup library to obtain parsed data, and the parsed data is converted into a word document using the python-docx library.

5. A canvas-based demand creation device, characterized in that: Applied to the demand analysis stage of software development, the device includes: A data acquisition module (110) is used to acquire the creative requirements of the first front end, and distribute the creative requirements on a canvas interface having multiple areas, each creative requirement corresponding to one area, and organize the creative requirements through a preset mind map-like method; A canvas acquisition module (120) is used to read the demand canvas data corresponding to the creation demand from a preset database, load the demand canvas data into a preset distributed storage repository, and transmit the demand canvas data to the first front end corresponding to the creation demand; A response update module (130) is used for verifying the editing authority of multiple components on the canvas interface with a cascade relationship. If the editing authority is granted, the module constructs a requirement structure in response to a drag operation on the component on the canvas interface, wherein the logical relationship of the component is verified during the drag operation; displays multiple editing actions on the canvas interface according to the requirement structure, wherein the editing actions include requirement annotations, requirement replies, chat box discussions, and comments, and are generated by multiple users; uses the requirement annotations and the requirement replies to improve the document and obtain requirement editing information, wherein the requirement editing information includes an organizational chart, a business process diagram, and a swim lane diagram; performs version verification on the requirement editing information to obtain creation update information; An information interaction module (140) is used to obtain creation update information of the first front end, store the creation update information in the distributed repository, and send the creation update information to the second front end, so that when a creation update occurs in the second front end, it is sent to the first front end; An information storage module (150) is used to obtain the creation and update information in the distributed repository and save it in the database; The response update module (130) is further used to perform demand editing based on the demand canvas data to obtain edited data, perform question extraction on the edited data to obtain extracted questions; perform intent recognition on the extracted questions using preset guidance rules to obtain intent information, and perform vector matching in a preset vector library based on the intent information to obtain vector related information; perform sentence generation on the vector related information and the intent information using the guidance rules to obtain a query sentence; perform a query in a preset database using the query sentence, and process the query content and the intent information using a preset large language model to obtain answer information corresponding to the extracted questions, wherein the answer information includes an expansion of the extracted questions and an answer to the extracted questions; and use the answer information to improve the edited data to obtain the creation update information.

6. An electronic device, characterized in that: The electronic device (500) comprises a processor (501), a memory (505), a user interface (503), a communication bus (502) and a network interface (504), wherein the processor (501), the memory (505), the user interface (503) and the network interface (504) are respectively connected to the communication bus (502), the memory (505) is used to store instructions, the user interface (503) and the network interface (504) are used to communicate with other devices, and the processor (501) is used to execute the instructions stored in the memory (505) so that the electronic device (500) executes the method according to any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed, the method according to any one of claims 1 to 4 is executed.

Images