Demand creation method and device based on canvas, electronic equipment and storage medium

Abstract

The invention provides a demand creation method and device based on canvas, electronic equipment and a storage medium, and relates to the technical field of computers. In the method, creation requirements of a first front end are obtained, the creation requirements are distributed in a canvas interface with a plurality of areas, each creation requirement corresponds to one area, and the creation requirements are organized through a preset mind-like map; reading required canvas data corresponding to the creation requirement from a preset database, loading the required canvas data into a preset distributed storage library, and transmitting the required canvas data to a first front end corresponding to the creation requirement; updating the required canvas data in response to the canvas interface to obtain creation updating information; obtaining creation update information of the first front end, storing the creation update information in a distributed storage library, and sending the creation update information to the second front end; and the creation updating information in the distributed storage library is obtained and stored in the database, so that the integrity and consistency of the information can be ensured.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically to a canvas-based method, apparatus, electronic device, and storage medium for demand creation. Background Technology

[0002] In software development, requirements analysis is a crucial first step. It helps define project goals and expected outcomes, ensuring the project better meets user needs. Therefore, improving the quality and efficiency of requirements creation is essential. In related technologies, requirements are often expressed through text descriptions, requiring external tools to articulate complex information such as business processes and system frameworks. For example, large models can be used to generate software requirements text. However, updating these texts becomes complex when requirements change, hindering team collaboration and communication, leading to inaccurate information delivery, document inconsistencies, and low team efficiency. Summary of the Invention

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

[0004] The technical solution of this application embodiment is as follows: In a first aspect, embodiments of this application provide a canvas-based creative method, the method comprising: The creation requirements of the first front end are obtained and distributed on a canvas interface with multiple areas. Each creation requirement corresponds to one area. The creation requirements are organized through a preset mind map. The system reads the requirement canvas data corresponding to the creation requirement from the preset database, loads the requirement canvas data into the preset distributed repository, and transmits the requirement canvas data to the first front-end corresponding to the creation requirement. In response to updating the required canvas data on the canvas interface, creation update information is obtained; Obtain the creation update information from 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 if a creation update occurs on the second front-end, it will be sent to the first front-end; The creation update information is retrieved from the distributed repository and saved to the database.

[0005] In the above technical solution, the creation requirements of the first front-end are obtained and distributed on a canvas interface with multiple areas. Each creation requirement corresponds to one area. The creation requirements are organized through a preset mind map-like structure. Multiple areas are formed through the canvas interface, and each area can record different types of requirement information. The requirements are organized in the form of a mind map, thereby ensuring the integrity and consistency of the information. The requirement canvas data corresponding to the creation requirements is read from a preset database and loaded into a preset distributed repository. The requirement canvas data is then transmitted to the first front-end corresponding to the creation requirements to realize diverse forms of requirement editing. In response to the canvas interface, the requirement canvas data is updated to obtain creation update information. By creating the requirements, the user's needs are met. The creation update information of the first front-end is obtained, stored in the distributed repository, and sent to the second front-end. This ensures that if a creation update occurs in the second front-end, it is sent back to the first front-end. By transmitting information to multiple parties, the convenience of communication is ensured, and the efficiency of team collaboration is improved. The creation update information in the distributed repository is obtained and saved to the database to ensure the integrity and consistency of the updated information, improve the efficiency of team collaboration, and avoid document inconsistencies.

[0006] In some embodiments of this application, the canvas interface has multiple components in a cascading relationship; The response involves updating the required canvas data on the canvas interface to obtain creation update information, including: The editing permissions on the canvas interface are verified. If the editing permissions are granted, the requirement structure is constructed in response to the drag-and-drop operation of the component on the canvas interface. During the drag-and-drop operation, the logical relationship of the component is verified. Based on the aforementioned requirement structure, collaborative editing is performed to obtain requirement editing information; The version of the requested editing information is checked to obtain the creation update information.

[0007] In some embodiments of this application, the step of collaboratively editing according to the requirement structure to obtain requirement editing information includes: Based on the aforementioned requirement structure, multiple editing actions are displayed on the canvas interface. These editing actions include requirement annotations and requirement responses, and are generated by multiple users. The document is improved using the aforementioned requirement annotations and requirement responses, resulting in the requirement editing information.

[0008] In some embodiments of this application, the step of performing version verification on the required editing information to obtain the creation update information includes: The required editing information is backed up to obtain backup information; The current editing information is compared with the backup information. If the documents are inconsistent, the current editing information is used as the creation update information.

[0009] In some embodiments of this application, the response to update the required canvas data on the canvas interface to obtain creation update information includes: Based on the required canvas data, the requirements are edited to obtain edited data. Then, the problems are extracted from the edited data to obtain the extracted problems. The intent information is obtained by performing intent recognition on the extraction question using preset guidance rules, and vector matching is performed in a preset vector library based on the intent information to obtain vector-related information. Using the guidance rules, a query statement is generated from the vector-related information and the intent information; The query statement is used to query a preset database, and the query content and intent information are processed using a preset large language model to obtain the answer information corresponding to the extraction question. The edit data is improved using the answer information to obtain the creation update information.

[0010] In some embodiments of this application, after obtaining the author update information from the distributed repository and saving it to the database, the method further includes: The creation update information is encapsulated into web page data; The webpage data is parsed to obtain parsed data, and the parsed data is then converted into an editable document.

[0011] In some embodiments of this application, parsing the webpage data to obtain parsed data and converting the parsed data into an editable document includes: The webpage data is parsed using the pre-defined BeautifulSoup library to obtain parsed data, and then the parsed data is converted into a Word document using the python-docx library.

[0012] Secondly, embodiments of this application provide a canvas-based creative device, the device comprising: The data acquisition module is used to acquire the creation requirements of the first front end and distribute the creation requirements on a canvas interface with multiple areas. Each creation requirement corresponds to one area, and the creation requirements are organized through a preset mind map. The canvas acquisition module is used to read the required canvas data corresponding to the creation requirement from a preset database, load the required canvas data into a preset distributed repository, and transmit the required canvas data to the first front end corresponding to the creation requirement. The response update module is used to update the required canvas data in response to the canvas interface, and obtain creation update information; The information interaction module is used 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. An information storage module is used to retrieve the creation update information from the distributed repository and save it to the database.

[0013] Thirdly, embodiments of this application provide an electronic device including a processor, a memory, a user interface, a communication bus, and a network interface. 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. The processor is used to execute the instructions stored in the memory to cause the electronic device to perform the method described in any one of the first aspects.

[0014] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed, perform the method described in any one of the methods provided in the first aspect above.

[0015] In summary, one or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages: 1. The system employs a method of first acquiring the creation requirements from the first front-end and distributing these requirements across a multi-area canvas interface. Each creation requirement corresponds to one area, and these requirements are organized using a pre-defined mind map-like structure. The canvas interface forms multiple areas, each capable of recording different types of requirement information. This mind map-based organization ensures information integrity and consistency. The system then reads the corresponding canvas data from a pre-defined database and loads it into a pre-defined distributed repository. This canvas data is then transmitted to the first front-end corresponding to the creation requirement, enabling diverse editing of the requirements. In response to updates to the canvas data on the canvas interface, updated creation information is obtained, allowing users to create and fulfill their needs. The system also acquires updated creation information from the first front-end, stores it in the distributed repository, and sends it to the second front-end. This ensures that updates occurring on the second front-end are also sent to the first front-end. This multi-party information transmission facilitates communication and improves team collaboration efficiency. Finally, the system acquires updated creation information from the distributed repository and saves it to the database, ensuring the integrity and consistency of the updated information, further improving team collaboration efficiency, and preventing document inconsistencies. Therefore, it effectively solves the problems of inaccurate information transmission, inconsistent documents, and low team collaboration efficiency in related technologies.

[0016] 2. The use of diverse and interconnected components in requirement building ensures richness in the requirement creation process.

[0017] 3. The canvas interface introduces collaborative editing and annotation functions, allowing users to collaborate and further improve team collaboration efficiency.

[0018] 4. Introduce guiding rules from the large model to assist in writing requirements, achieve efficient retrieval and document writing, and provide solution references. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating a canvas-based demand creation method provided in one embodiment of this application; Figure 2 yes Figure 1 A flowchart illustrating a sub-step of step S300; Figure 3 yes Figure 2 A flowchart illustrating a sub-step of step S320; Figure 4 yes Figure 1 A flowchart illustrating another sub-step of step S300; Figure 5This is a schematic diagram of canvas design interaction for a canvas-based demand creation method provided in one embodiment of this application; Figure 6 This is a schematic diagram of collaborative editing of a canvas-based demand creation method provided in one embodiment of this application; Figure 7 This is a data parsing diagram of a canvas-based demand creation method provided in one embodiment of this application; Figure 8 This is a schematic diagram of the structure of a canvas-based demand creation device provided in one embodiment of this application; Figure 9 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0020] 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 with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

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

[0022] In the description of the embodiments of this application, the term "multiple" means two or more. For example, multiple systems means two or more systems, and multiple screen terminals means two or more screen terminals. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0023] This application provides a canvas-based requirement creation method, apparatus, electronic device, and readable storage medium. The canvas-based requirement creation method first acquires the creation requirements from a first front-end and distributes these requirements across a canvas interface with multiple regions, each corresponding to one region. The creation requirements are organized using a preset mind map-like structure, forming multiple regions on the canvas interface. Each region can record different types of requirement information. The requirement organization via mind map ensures the integrity and consistency of the information. The method then reads the requirement canvas data corresponding to the creation requirements from a preset database, loads the requirement canvas data into a preset distributed repository, and transmits the requirement canvas data to the creation requirement database. The system is structured as follows: First, it enables diverse editing of requirements. Second, it updates the canvas data on the canvas interface to obtain creation update information, allowing users to create content that meets their needs. Third, it retrieves creation update information from the first frontend, stores it in a distributed repository, and sends it to a second frontend. This ensures that updates occurring on the second frontend are also sent to the first frontend, facilitating communication and improving team collaboration efficiency through multi-party information transfer. Fourth, it retrieves creation update information from the distributed repository and saves it to a database, ensuring the integrity and consistency of updated information, further improving team collaboration efficiency, and preventing document inconsistencies.

[0024] It should be noted that this canvas-based requirements creation method is mainly used for requirements analysis in the software development process. In addition, it can also be applied to service requirements analysis in the service industry, requirements creation for market understanding, and other scenarios that require requirements analysis. Its application is quite wide.

[0025] The technical solutions provided in the embodiments of this application will be further described below with reference to the accompanying drawings.

[0026] Reference Figure 1 , Figure 1 This is a flowchart illustrating the canvas-based requirements creation method provided in this application embodiment. The canvas-based requirements creation method is applied to a WebSock server. The canvas-based requirements creation device in the WebSock server executes the canvas-based requirements creation method through a processor in an electronic device or a readable storage medium. The canvas-based requirements creation method includes steps S100, S200, S300, S400, and S500.

[0027] Step S100: Obtain the creation requirements from the first front end and distribute the creation requirements on a canvas interface with multiple areas. Each creation requirement corresponds to one area. Organize the creation requirements using a preset mind map-like structure.

[0028] In one embodiment, the creation requirements of the first front-end are obtained. These requirements are requests from the creator to create a requirement document after understanding the requirements, including business background, business objectives, and various functional modules. The first front-end can obtain the creation requirements by having the creator input them. Besides input, it can also obtain the requirements through voice, images, etc., converting voice and images into text to obtain the creation requirements of the first front-end. The creation requirements are then obtained through a preset interface, specifically through protocol transmission. The creation requirements are distributed across a canvas interface with multiple areas, each corresponding to a specific area, allowing for the recording of different types of requirement information. The creation requirements are organized using a preset mind map-like structure. This mind map structure can group the creation requirements from different areas together, forming a relational requirement structure. This mind map approach ensures the completeness and consistency of the requirement information.

[0029] In another embodiment, there can be multiple creation requirements for the first front-end, 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 creation, another creator can create on a second front-end, and there can even be a third, fourth, etc., enabling collaborative editing within the team. During this process, the multiple areas of the canvas interface and the mind map-like structure ensure the completeness and consistency of the requirement information, improving team collaboration efficiency.

[0030] Step S200: Read the requirement canvas data corresponding to the creation requirement from the preset database, load the requirement canvas data into the preset distributed repository, and transmit the requirement canvas data to the first front-end corresponding to the creation requirement.

[0031] In one embodiment, based on the acquired creative requirements, corresponding requirement canvas data is read from a preset database. The preset database can be a MySQL database, or a DB database, etc., capable of data storage; details are omitted here. The requirement canvas data is the requirement data corresponding to the creation of the requirement. The requirement canvas data is read from the database using the creation requirement number. The requirement canvas data can be represented in the form of components and loaded into a preset distributed repository to prepare for subsequent editing and creation. The preset distributed repository is a Redis database, but other caching databases can also be used. The requirement canvas data is then transmitted to the first front-end corresponding to the creation requirement, so that the requirement creator can perform requirement creation on the first front-end.

[0032] In step S300, in response to updating the required canvas data on the canvas interface, creation update information is obtained.

[0033] In one embodiment, the canvas interface has multiple cascading components, each of which is a pre-made template, enabling diverse writing styles. For example... Figure 2 As shown, in response to updating the required canvas data on the canvas interface, the creation update information is obtained, including but not limited to the following steps: Step S310: Verify the editing permissions on the canvas interface. If the editing permissions are granted, respond to the drag-and-drop operation of the component on the canvas interface and construct the requirement structure. During the drag-and-drop operation, the logical relationship of the components is verified.

[0034] In some possible embodiments of this application, editing permissions on the canvas interface are first verified. User roles can be used to determine editing permissions. For example, the team leader, as the editor, has higher permissions, including annotation, modification, and flowchart generation, while ordinary team members only have writing permissions. Verifying permissions through user roles ensures data security. With editing permissions, the requirement canvas data can be edited and updated. Components on the canvas interface can be dragged and dropped. Responding to dragging and dropping components on the canvas interface, the requirement canvas data is updated and modified. The requirement content can be organized like building blocks to construct the requirement structure, which is then used to generate creation update information and create a requirement document. It should be noted that because components have cascading relationships, logical relationships between components need to be verified during dragging. Based on the mind map arranged within the components, the logical relationships between the components can be determined, thereby constructing the correct requirement structure.

[0035] Among the various components, each has a different interaction method with the editor due to its different definition. The basic components include: rich text boxes, dynamic tables in JavaScript, file upload and download components, flowchart drawing components, etc., which can support users' relatively rich expression needs. Changes in requirements are detected periodically and saved for later backup.

[0036] Step S320: Collaboratively edit according to the requirement structure to obtain requirement editing information.

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

[0038] like Figure 3As shown, collaborative editing is performed based on the requirement structure to obtain requirement editing information, including but not limited to the following steps: Step S321: Based on the requirement structure, display multiple editing actions on the canvas interface. The editing actions include requirement annotations and requirement replies, and are generated by multiple users.

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

[0040] Step S322: Improve the document using requirement annotations and requirement replies to obtain requirement editing information.

[0041] In some possible embodiments of this application, the document content is filled in using requirement annotations and requirement replies based on the content of the writing and editing, so that the document can be specific and rich, clearly expressing the purpose of the requirement, and obtaining requirement editing information.

[0042] In other possible embodiments of this application, collaborative editing can also be performed by integrating drawing tools, etc., to realize the drawing of various forms of graphics such as organizational charts, business process diagrams, and swimlane diagrams, thereby increasing the richness of collaborative editing.

[0043] Step S330: Verify the version of the required editing information to obtain the creation update information.

[0044] In some possible embodiments of this application, since multiple editors are involved in the editing, it is necessary to verify the version of the required editing information and use the verified version as the creation update information. By performing version verification, the correctness of the final version can be ensured, and the integrity and consistency of the information can be guaranteed.

[0045] Specifically, the version verification of the editing requirements is performed to obtain the creation update information, which includes, but is not limited to, the following steps: Step S331: Back up the required editing information to obtain the backup information.

[0046] In some possible embodiments of this application, during version verification, the requirement editing information can 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, ensuring the integrity of the information. The requirement editing information can be backed up in the form of data storage, storing the data in another database.

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

[0048] In some possible embodiments of this application, after backing up the requirement editing information, it can be edited again to obtain the current requirement editing information; alternatively, the current requirement editing information can be directly used as the current requirement editing information to determine whether the information has been edited and updated. The current requirement editing information is then compared with the backup information, using a preset comparison algorithm, such as a character similarity algorithm. If the documents are inconsistent, it indicates that the editing information has been updated, and the current requirement editing information is used as the creation update information to ensure the accuracy of the creation update information.

[0049] like Figure 4 As shown, in response to updating the required canvas data on the canvas interface, the creation update information is obtained, including but not limited to the following steps: Step S340: Edit the requirements based on the requirements canvas data to obtain edit data, and extract the problems from the edit data to obtain the extracted problems.

[0050] In one embodiment, editing permissions on the canvas interface are first verified. This can be done using user roles to determine editing permissions, ensuring data security. Similar to step S310, this will not be elaborated further. With editing permissions granted, the canvas data is updated and edited according to requirements. Components on the canvas interface can be dragged and dropped. Responding to these drag-and-drop operations, the required content can be organized like building blocks to obtain edit data, which can then be used for subsequent text expansion and refinement. It should be noted that because components have cascading relationships, logical relationships between them need to be verified during dragging. Based on the mind map arranged within the components, the logical relationships between them can be determined, thereby constructing the correct requirement structure.

[0051] In another embodiment, the edited data obtained above is used to extract questions. Specifically, manually defined rules can be used to summarize questions from the edited data to obtain extracted questions, which can then be used for intent recognition. The manually defined rules can be implemented by manually summarizing questions from the edited data and then transmitting the extracted questions to a WebSock server for processing. Alternatively, questions can be manually entered and then transmitted to a WebSock server for processing.

[0052] Step S350: Use preset guidance rules to perform intent recognition on the extraction question to obtain intent information, and perform vector matching in a preset vector library based on the intent information to obtain vector-related information.

[0053] In one embodiment, the preset guidance rules are represented as prompt statements, which are pre-defined by experts. The preset guidance rules are used to perform intent recognition on the extracted question, primarily identifying business rules, functions, business processes, functional paths, documents, etc., to obtain intent information for subsequent vector queries. The preset vector library includes multiple metadata vectors. Specifically, the query involves matching the intent information with each vector in the preset vector library, calculating the similarity between the intent information and the metadata vectors using a cosine similarity algorithm, and obtaining vector-related information for subsequent query statement generation.

[0054] Step S360: Use the guidance rules to generate a statement from the vector-related information and intent information to obtain the query statement.

[0055] In one embodiment, the guidance rule is similar to the guidance rule in step S350, and is based on rules preset by experts. The guidance rule is used to generate statements from vector-related information and intent information, producing a cypher query statement for subsequent data retrieval.

[0056] Step S370: Use a query statement to query the preset database, and use a preset large language model to process the content and intent information of the query to obtain the answer information corresponding to the extracted question.

[0057] In one embodiment, using the Cypher query obtained in step S360, data is queried from a preset database using a preset Application Programming Interface (API). The preset database is the Neo4j database, which stores the business data corresponding to the Cypher query. A preset large language model is used to process the business data and intent information. Specifically, feature extraction and feature fusion are performed on the business data and intent information to obtain the answer information corresponding to the extracted question. This answer information can be a direct answer to the question or an enrichment and expansion of the extracted question, including rich search content that can provide a solution reference for subsequent refinement of the requirements.

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

[0059] In one embodiment, the edited data can be replaced using the answer information, or the edited data can be supplemented using the content in the answer information. The supplementation operation involves manual screening to obtain updated creation information. This updated creation information includes rich search content, making the editing of the required content more comprehensive.

[0060] Figure 5 The diagram illustrates the canvas design interaction. For a specific requirement, the canvas interface displays the following: requirement details, requirement overview, business scenario, system flowchart, system relationship diagram, requirement scope, functional description, requirement plan, attachments, etc., which have a cascading relationship. Details are as follows: Figure 5 As shown, details will not be elaborated here. The function descriptions, processes, rules, etc., each have their own corresponding pages, which are not shown in the diagram.

[0061] Step S400: Obtain the creation update information from 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 if a creation update occurs on the second front-end, it will be sent to the first front-end.

[0062] In one embodiment, the creation update information of the first frontend can be obtained through a transmission protocol and stored in a distributed repository, which can be a Redis database or other caching database. Saving the creation update information allows for the preservation of modified content at any time, facilitating subsequent tracking of required versions. For editing of the required creation by the first frontend, the creation update information is sent to the second frontend so that other creators can synchronize with the creation of that requirement, ensuring the integrity and consistency of information across multiple frontends.

[0063] Specifically, when an update occurs on the first frontend, it is sent to the second frontend. Similarly, when a creation update occurs on the second frontend, the creation update information is also sent to the first frontend. Treating the second frontend as the first frontend and the first frontend as the second frontend, the second frontend executes steps S100 to S400 to ensure that update information from each frontend can be synchronized to other frontends. It should be noted that when creation occurs on the second frontend, the creation requirement from the second frontend is obtained, and it is determined whether the creation requirement is loaded into Redis. If it is loaded, the data in Redis can be directly returned; if not, the requirement canvas data corresponding to the creation requirement is read from a preset database, and the requirement canvas data is loaded into a preset distributed repository, and similar subsequent operations are performed. Having multiple frontends that can perform creation and editing according to the above process ensures the integrity and consistency of information and improves team collaboration efficiency.

[0064] like Figure 6The diagram illustrates the editing process using the first and second front-ends. The first front-end is Front-end 1, and the second front-end is Front-end 2. The processing utilizes WebSocket services. Front-end 1 retrieves the creation requirements and distributes them across a canvas interface with multiple regions, each requirement corresponding to one region. These requirements are organized using a pre-defined mind map. The process reads the corresponding canvas data from the MySQL database, loads it into a pre-defined Redis database, and then transfers the canvas data to Front-end 1. Similarly, Front-end 2 retrieves the creation requirements and distributes them across a canvas interface with multiple regions, each requirement corresponding to one region. This is organized using a pre-defined mind map. The process checks if the creation requirement is loaded into the Redis database. If it is, the data is directly returned; otherwise, the corresponding canvas data is read from the pre-defined database and loaded into the Redis database. Frontend 1 modifies the required canvas data, responding by updating the canvas data on the canvas interface and obtaining creation update information. It then retrieves the creation update information from the first frontend, stores it in a distributed repository, and sends it to Frontend 2. Frontend 2 updates the required canvas data, sends the updated data, and disconnects the session. The modified information is then sent back to Frontend 1. The creation update information in the distributed repository is retrieved and saved to the database, ensuring the integrity and consistency of the updated information, improving team collaboration efficiency, and avoiding document inconsistencies. Frontend 1 modifies the canvas, submits and saves the changes, and generates the documentation.

[0065] Step S500: Obtain the creation update information from the distributed repository and save it to the database.

[0066] In one embodiment, the author update information is read from the distributed repository Redis using a data read function, and then saved to the database using a save function for later use.

[0067] In one embodiment, after obtaining the creation update information from the distributed repository and saving it to the database, the canvas-based creation method further 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.

[0068] Specifically, creation update information is stored in JSON data format, while webpage data is displayed using HTML data. The JSON data contains canvas structure information and user-entered data, which can be easily converted into HTML data. JavaScript or similar tools can be used to parse the JSON data and encapsulate it into HTML data for subsequent processing. Then, the webpage data is parsed, and the parsed data is converted into an editable document for viewing and editing.

[0069] 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.

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

[0071] like Figure 8As shown, this application embodiment provides a canvas-based requirement creation device 100. This device 100 acquires creation requirements from a first front-end via a data acquisition module 110 and distributes these requirements across a canvas interface with multiple regions. Each creation requirement corresponds to one region. The creation requirements are organized using a preset mind map-like structure, forming multiple regions on the canvas interface. Each region can record different types of requirement information. The requirement organization via the mind map ensures the integrity and consistency of the information. Then, the canvas acquisition module 120 reads the requirement canvas data corresponding to the creation requirements from a preset database, loads the requirement canvas data into a preset distributed repository, and transmits the requirement canvas data to the first front-end corresponding to the creation requirements. The system supports diverse editing formats to meet current needs. The response update module 130 updates the canvas data on the canvas interface to obtain creation update information. This allows users to create content that meets their requirements. The information interaction module 140 then retrieves the creation update information from the first front-end, stores it in a distributed repository, and sends it to the second front-end. This ensures that if a creation update occurs on the second front-end, it is sent back to the first front-end. This multi-party information transmission ensures convenient communication and improves team collaboration efficiency. Finally, the information storage module 150 retrieves the creation update information from the distributed repository and saves it to the database, ensuring the integrity and consistency of the updated information, further improving team collaboration efficiency, and preventing document inconsistencies.

[0072] 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 aforementioned canvas-based demand creation method is applied to the canvas-based demand creation device 100. The canvas-based demand creation device 100 acquires the creation demands from the first front end and distributes these demands across a canvas interface with multiple areas. Each creation demand corresponds to one area. The creation demands are organized using a preset mind map-like structure, forming multiple areas on the canvas interface. Each area can record different types of demand information. The demand organization is achieved through mind mapping, ensuring the integrity and consistency of the information. The device also reads the demand canvas data corresponding to the creation demands from a preset database, loads the demand canvas data into a preset distributed repository, and transmits the demand canvas data to the corresponding creation demand. The first front-end enables diverse editing of requirements; it updates the requirement canvas data on the canvas interface to obtain creation update information, and satisfies user needs through requirement creation; it retrieves creation update information from the first front-end, stores it in a distributed repository, and sends it to the second front-end, so that if creation updates occur in the second front-end, they are sent back to the first front-end. By transmitting information through multiple parties, it ensures convenient communication and improves team collaboration efficiency; it retrieves creation update information from the distributed repository and saves it to the database to ensure the integrity and consistency of updated information, improves team collaboration efficiency, and avoids document inconsistencies.

[0073] It should also be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. 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 apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0074] This application also discloses an electronic device. (See reference...) Figure 9 , Figure 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of this 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.

[0075] The communication bus 502 is used to enable communication between these components.

[0076] The user interface 503 may include a display screen and a camera. Optionally, the user interface 503 may also include a standard wired interface and a wireless interface.

[0077] The network interface 504 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

[0078] The processor 501 may include one or more processing cores. The processor 501 connects to various parts of the server using various interfaces and lines, and performs various server functions and processes data by running or executing instructions, programs, code sets, or instruction sets stored in memory 505, and by calling data stored in memory 505. Optionally, the processor 501 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 501 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content to be displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 501 and may be implemented as a separate chip.

[0079] The memory 505 may include random access memory (RAM) or read-only memory. Optionally, the memory 505 may include a non-transitory computer-readable storage medium. The memory 505 may be used to store instructions, programs, code, 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 touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 505 may also be at least one storage device located remotely from the aforementioned processor 501. (Refer to...) Figure 9The memory 505, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an application for a canvas-based demand creation method.

[0080] exist Figure 9 In the illustrated electronic device 500, the user interface 503 is mainly used to provide an input interface for the user and to acquire user input data; while the processor 501 can be used to call an application program stored in the memory 505 that represents a canvas-based creation method. When executed by one or more processors 501, the electronic device 500 performs one or more methods as described in the above embodiments. It should be noted that, for the foregoing method embodiments, for the sake of simplicity, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0081] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

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

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

[0084] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0085] 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 storage device (CMD). Based on this understanding, the technical solution of this application, in essence, 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. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0086] The above are merely exemplary embodiments of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Other embodiments of this disclosure will readily conceive of those skilled in the art upon consideration of the specification and the disclosure of practical truths.

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

Claims

1. A canvas-based demand creation method, characterized in that: The method comprises: Acquire the creation requirements of the first front end, and distribute the creation requirements on a canvas interface having multiple areas, each of the creation requirements corresponds to one of the areas, and organize the creation 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 storage repository, and transmitting the demand canvas data to the first front end corresponding to the creation demand; In response to updating the required canvas data on the canvas interface, obtaining creation update information; Acquire 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; The creation update information in the distributed repository is obtained and saved in the database.

2. The method according to claim 1, characterized in that The canvas interface has multiple components in a cascading relationship; The response to updating the required canvas data on the canvas interface to obtain creation update information includes: Verifying the editing authority on the canvas interface, and if the editing authority is granted, building a demand structure in response to a dragging operation on the component on the canvas interface, wherein a logical relationship check is performed on the component during the dragging operation; Perform collaborative editing according to the demand structure to obtain demand editing information; A version check is performed on the required editing information to obtain the creation update information.

3. The method according to claim 2, characterized in that The collaborative editing according to the requirement structure to obtain requirement editing information includes: According to the requirement structure, multiple editing actions are displayed on the canvas interface, wherein the editing actions include requirement annotations and requirement replies and are generated by multiple users; The document is improved using the requirement annotation and the requirement reply to obtain the requirement editing information.

4. The method according to claim 2, characterized in that: The performing version checking on the required editing information to obtain the creation update information includes: Backing up the required editing information to obtain backup information; The currently required editing information is compared with the backup information, and in the case of document inconsistency, the currently required editing information is used as the creation update information.

5. The method according to claim 1, characterized in that The response to updating the required canvas data on the canvas interface to obtain creation update information includes: Edit the requirements according to the requirements canvas data to obtain edited data, and extract problems from the edited data to obtain extracted problems; Using a preset guiding rule to perform intent recognition on the extraction question to obtain intent information, and performing vector matching in a preset vector library according to the intent information to obtain vector related information; Using the guidance rule to generate a statement for the vector related information and the intention information to obtain a query statement; Using the query statement to query in a preset database, using a preset large language model to process the query content and the intention information, to obtain answer information corresponding to the extracted question; The editing data is improved using the answer information to obtain the creation update information.

6. The method according to claim 1, characterized in that After obtaining the creation update information in the distributed repository and saving it in the database, the method further includes: Encapsulating the creation 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.

7. The method according to claim 6, 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.

8. A canvas-based demand creation device, characterized in that: The device comprises: A data acquisition module (110) is used to acquire the creation requirements of the first front end, and distribute the creation requirements on a canvas interface having multiple areas, each of the creation requirements corresponds to one of the areas, and organize the creation requirements through a preset mind map-like structure; A canvas acquisition module (120), used for reading demand canvas data corresponding to the creation demand from a preset database, loading the demand canvas data into a preset distributed storage repository, and transmitting the demand canvas data to the first front end corresponding to the creation demand; A response update module (130), used for updating the required canvas data in response to the canvas interface to obtain creation update information; An information interaction module (140) is used 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; The information storage module (150) is used to obtain the creation update information in the distributed storage repository and save it in the database.

9. 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 7.

10. 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 7 is executed.

Images