Demand specification generation method and device

Abstract

The invention provides a demand specification generation method and device, and belongs to the technical field of computers. The method comprises the steps of generating an initial template based on a preset clause rule, generating at least one candidate template based on the initial template, determining a target template from the at least one candidate template in response to a template selection instruction, and displaying the target template to a user, and the user edits the target template to generate a demand specification. Therefore, when the user edits the target template, the content from the key chapter of the initial template cannot be tampered, so that the hidden danger of compliance is effectively prevented, and the problems that in the prior art, as the template lacks a unified structured mechanism, the key content of the generated demand specification is easily tampered, and the user experience is poor are solved. And therefore, a compliance hidden danger can be caused.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method and apparatus for generating a requirements specification. Background Technology

[0002] In the entire process of product development, supply chain management, and product manufacturing, the requirements specification document (PSV) is the core document through which companies clarify product functions, performance, quality, and delivery requirements to suppliers. Its quality and efficiency directly impact the development cycle, supply chain collaboration, and product compliance. As companies diversify their product portfolios and product categories become increasingly complex (such as different types of parts like electronic control units and transmission systems), the requirements for PSVs also become more diverse.

[0003] In related technologies, existing methods for generating requirements specifications mainly rely on writers downloading a uniform template from a shared file according to project needs, then writing the requirements specification based on the template. While this method is simple and easy to use, the lack of a unified structured mechanism in the template makes the key content of the generated requirements specification easy to be tampered with, which may lead to compliance risks. Summary of the Invention

[0004] The purpose of this application is to provide a method and apparatus for generating requirements specifications, in order to solve the technical problem that the lack of a unified structured mechanism in existing templates makes the key content of the generated requirements specifications easily tampered with, potentially leading to compliance risks. The specific technical solution is as follows: In a first aspect of this application, a method for generating a requirements specification is provided, the method comprising: Generate an initial template based on preset terms and rules; Based on the initial template, at least one candidate template is generated, wherein the candidate template inherits the locking status of key chapters in the initial template; In response to a template selection instruction, a target template is determined from at least one of the candidate templates; The target template is displayed to the user so that the user can edit the target template to generate a requirements specification.

[0005] In one optional implementation, the preset clause rules include at least one clause text, and the generation of an initial template based on the preset clause rules includes: Obtain the preset structure template; Inject at least one of the aforementioned clause texts into the preset structure template to generate the initial template.

[0006] In an optional implementation, the preset structure template includes at least one chapter template, and the step of injecting at least one clause text into the preset structure template to generate the initial template includes: For any of the chapter templates, determine at least one target clause text from at least one of the clause texts; Inject at least one of the target clause texts into the chapter template to generate the chapter corresponding to the chapter template; The initial template is generated based on at least one chapter corresponding to the chapter template.

[0007] In an optional implementation, generating the initial template based on at least one chapter corresponding to the chapter template includes: Determine at least one key chapter from the chapters corresponding to at least one of the chapter templates, and set the status of at least one key chapter to a locked state; Determine at least one non-key chapter from the chapters corresponding to at least one of the chapter templates, and set the state of at least one non-key chapter to be unlocked. The initial template is generated based on at least one of the key chapters and the non-key chapters.

[0008] In an optional implementation, generating at least one candidate template based on the initial template includes: Obtain a preset category list, wherein the preset category list contains at least one product type; For any of the product types mentioned, obtain the corresponding customization terms for that product type; Based on the initial template and the customized terms corresponding to the product type, a candidate template corresponding to the product type is generated.

[0009] In an optional implementation, generating a candidate template corresponding to the product type based on the initial template and the customization terms corresponding to the product type includes: The customized terms corresponding to the product type are injected into the non-critical sections of the initial template to generate a candidate template corresponding to the product type.

[0010] In an optional implementation, determining the target template from at least one candidate template in response to the template selection instruction includes: In response to the template selection instruction, the template selection instruction is parsed to generate product keywords; Determine the similarity between the product keywords and at least one of the candidate templates; Based on the similarity, the target template is determined from at least one of the candidate templates.

[0011] In an optional implementation, the method further includes: When the user edits the target template, detect whether there is a conflict of concurrent editing by multiple users; In the event of concurrent editing conflicts among multiple users, the operations corresponding to the concurrent editing conflicts will be merged or a manual intervention process will be triggered.

[0012] In an optional implementation, after generating the requirements specification, the method further includes: Verify that the requirements specification is complete; If the requirements specification is incomplete, a prompt signal will be issued so that the user can edit the requirements specification until it is complete.

[0013] In a second aspect of this application, a requirements specification generation apparatus is also provided, the apparatus comprising: The initial template generation module is used to generate an initial template based on preset clause rules; A candidate template generation module is used to generate at least one candidate template based on the initial template, wherein the candidate template inherits the locking status of key chapters in the initial template; A target template determination module is configured to determine a target template from at least one of the candidate templates in response to a template selection instruction; The requirements specification generation module is used to display the target template to the user so that the user can edit the target template to generate a requirements specification.

[0014] In a third aspect of the embodiments of this application, a vehicle is also provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the method for generating the requirements specification as described in any of the first aspects above.

[0015] In a fourth aspect of the embodiments of this application, a storage medium is also provided, the storage medium storing instructions that, when run on a computer, cause the computer to execute the method for generating the requirements specification as described in any of the first aspects above.

[0016] In a fifth aspect of the embodiments of this application, a computer program product including instructions is also provided, which, when run on a computer, causes the computer to perform the method for generating the requirements specification as described in any of the first aspects above.

[0017] The technical solution provided in this application generates an initial template based on preset clause rules. Based on the initial template, at least one candidate template is generated. The candidate templates inherit the locked state of key sections in the initial template. In response to a template selection instruction, a target template is determined from the at least one candidate template and displayed to the user for editing, generating a requirements specification. This ensures that when the user edits the target template, the content of key sections from the initial template is not tampered with, effectively preventing compliance risks. It solves the technical problem in existing technologies where the lack of a unified structured mechanism in templates leads to the easy tampering of key content in generated requirements specifications, potentially causing compliance risks. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0021] Figure 1 A schematic diagram illustrating the implementation process of a method for generating a requirements specification provided in this application embodiment; Figure 2 A schematic diagram illustrating the implementation process of another method for generating a requirements specification provided in this application embodiment; Figure 3 A schematic diagram illustrating the implementation process of an initial template generation method provided in this application embodiment; Figure 4 A schematic diagram illustrating the implementation process of another method for generating a requirements specification provided in this application embodiment; Figure 5 A schematic diagram of a requirements specification generation apparatus provided in this application embodiment; Figure 6 This is a structural schematic diagram of a vehicle provided in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0024] To address the technical problem in existing technologies where the lack of a unified structured mechanism in templates makes key content in generated requirements specifications susceptible to tampering, potentially leading to compliance risks, this application provides a method and apparatus for generating requirements specifications. Based on preset clause rules, an initial template is generated. Based on the initial template, at least one candidate template is generated, whereby the candidate templates inherit the locked state of key sections from the initial template. In response to a template selection instruction, a target template is determined from the at least one candidate template and displayed to the user for editing, thereby generating the requirements specification. This ensures that when the user edits the target template, the content of key sections from the initial template remains unaltered, effectively preventing compliance risks.

[0025] like Figure 1 The diagram shown illustrates the implementation flow of a method for generating a requirements specification according to an embodiment of this application, which may specifically include the following steps: S101, Generate an initial template based on preset terms and rules.

[0026] In this embodiment, an initial template is generated based on preset clause rules. These preset clause rules can be a set of structured text rules stored in a cloud database for constructing standardized requirements specifications. This ensures that all generated candidate templates comply with internal control standards and external compliance requirements in terms of basic framework and core clauses. Each preset clause rule may contain at least one clause text. The initial template refers to an enterprise-level basic template generated based on the preset clause rules, used to establish a unified starting point and quality baseline. The initial template can be stored in a shared folder or a cloud template library for centralized management and sharing. Within the initial template, key and non-key sections can be divided according to compliance requirements, and key sections can be locked to prevent subsequent modifications by other personnel (such as non-management personnel).

[0027] The aforementioned preset clause rules may include at least one clause text, where the clause text refers to specific technical, quality, or management requirements, which may be enterprise quality standards, general technical specifications, risk statements, etc., such as "the surface roughness of the part shall not exceed Ra0.8" or "all welding points shall be subject to X-ray inspection," etc. The clause text may be derived from enterprise standard libraries, rule libraries, or historical practice data, etc., to be used to fill the corresponding chapters of the preset structure template, and this application embodiment does not limit this.

[0028] S102, Based on the initial template, generate at least one candidate template, the candidate template inheriting the locking state of the key chapters in the initial template.

[0029] In this embodiment, at least one candidate template is generated based on an initial template. The candidate templates inherit the locking status of key sections from the initial template. These candidate templates are flexibly adapted to different business scenarios (such as different types of components or different project stages) based on the initial template, avoiding redundant template structure building and improving the efficiency of writing requirements specifications. The inheritance of the locking status of key sections from the initial template in the candidate template means that the corresponding key sections in the initial template will automatically inherit their 'locked status,' meaning that the content and attributes of that section (such as prohibiting editing or deletion) are forcibly retained, ensuring that core corporate standards and compliance clauses are transmitted without deviation during template derivation. Candidate templates can be tagged based on their content, or users can manually add tags to them, so that the target template can be determined from at least one candidate template based on the corresponding tags.

[0030] S103, in response to the template selection instruction, determine the target template from at least one candidate template.

[0031] In this embodiment, in response to a template selection instruction, a target template is determined from at least one candidate template. The template selection instruction refers to an input instruction that triggers candidate template matching and selection. The target template refers to the template selected from at least one candidate template that has the highest compatibility with the template selection instruction.

[0032] Specifically, the template selection instruction can be a user-initiated search instruction, such as a user entering keywords (e.g., stamping parts) in the interface to search; or it can be a search instruction automatically triggered based on project attributes (e.g., vehicle platform, part classification code). This application embodiment does not limit this.

[0033] S104. The target template is displayed to the user so that the user can edit the target template and generate a requirements specification.

[0034] In this embodiment, a target template is displayed to the user so that the user can edit the template to generate a requirements specification. This requirements specification is the final, formal technical document used to guide the supplier's production process.

[0035] It should be noted that users can edit the target template in the editing interface, and during the editing process, users can only modify unlocked sections. The rich text content in the above templates (including the initial template and candidate templates) can be stored in a structured format such as HTML to facilitate precise parsing, access control, and data extraction of sections and clauses. Furthermore, each modification to the target template (including content updates and section status changes) will generate a completely new version of the target template, recording the version number, modification time, operator, and modification summary. All historical versions can be persistently stored so that users can view and compare the content of any historical version at any time, or revert to a specific version as needed.

[0036] When a user is detected to be in a state of network instability or abnormality, the system can switch to local caching mode. The user can still perform editing operations such as adding, deleting, and modifying the unlocked chapters of the target template from the editing interface. At this time, all editing operations will be temporarily saved in local storage or client cache, and the operation sequence and timestamp of the editing operations will be recorded. After the network returns to normal, the editing operations in local storage or client cache can be uploaded to the server in sequence to achieve synchronization of editing operations. At the same time, the system can determine whether there are conflicts caused by concurrent editing by multiple users according to preset conflict detection rules. When there are conflicts in concurrent editing by multiple users, the operations corresponding to the conflicts in concurrent editing by multiple users can be merged or a manual intervention process can be triggered. For details, please refer to step S207. The embodiments of this application will not be described in detail here.

[0037] Permissions can be set for both the initial template and any candidate template. When different users operate on the initial template or any candidate template, their actions can be checked in real time to ensure they are within their authorized permission scope. This means that only operations within their authorized scope are allowed, including but not limited to viewing, referencing, editing, sharing, archiving, and deleting. When sensitive operations occur (such as permanently deleting a candidate template or modifying its permission configuration), a secondary approval process will be triggered. This involves transferring the sensitive operation to an administrator with higher privileges or a pre-designated approver for approval, or verifying the identity of the user performing the sensitive operation. Only after the review or identity verification is passed can the sensitive operation be allowed.

[0038] Based on the above description of the technical solution provided in the embodiments of this application, an initial template is generated based on preset clause rules. Based on the initial template, at least one candidate template is generated. The candidate templates inherit the locked state of key sections in the initial template. In response to a template selection instruction, a target template is determined from the at least one candidate template and displayed to the user for editing, generating a requirements specification. This ensures that when the user edits the target template, the content of key sections from the initial template will not be tampered with, effectively preventing compliance risks. It solves the technical problem in existing technologies where the lack of a unified structured mechanism in templates leads to the easy tampering of key content in generated requirements specifications, potentially causing compliance risks.

[0039] like Figure 2 The diagram shown illustrates the implementation flow of another method for generating a requirements specification provided in this application, which may specifically include the following: S201, Obtain a preset structure template, wherein the preset structure template contains at least one chapter template.

[0040] In this embodiment, a preset structure template is obtained. The preset structure template refers to a predefined document framework skeleton that specifies the standard chapter divisions and order of the requirements specification, used to ensure that all generated requirements specifications have a unified structural paradigm. For example, the preset structure template includes chapter templates such as "1. Scope", "2. Referenced Standards", "3. Technical Requirements", "4. Acceptance Methods", and "5. Appendix". This embodiment does not limit this aspect.

[0041] S202, inject at least one clause text into a preset structure template to generate an initial template.

[0042] In this embodiment, at least one clause text is injected into a preset structure template to generate an initial template. Specifically, a clause injection operation can be performed to fill the corresponding chapter template of the preset structure template with at least one clause text from the preset clause rules through semantic matching or rule mapping, thereby generating a content-rich initial template.

[0043] The question is how to inject at least one clause text into a pre-defined structure template to generate an initial template. For example... Figure 3 The diagram shown illustrates the implementation flow of an initial template generation method provided in this application, which may specifically include the following steps: S301, for any chapter template, determine at least one target clause text from at least one clause text.

[0044] In this application embodiment, for any chapter template, at least one target clause text is determined from at least one clause text.

[0045] In an alternative implementation, the text can be matched with at least one clause text based on the semantic tags or classification codes of the chapter template, and the clause text with the same or similar tags can be used as the target clause text.

[0046] For example, a template labeled "3.1 Material Requirements" will automatically match all clause text labeled "Materials".

[0047] In an alternative implementation, content semantic matching can be performed, i.e., extracting keywords, entities, or semantic vectors of chapter templates and clause texts using natural language processing technology, calculating their similarity, and thus determining at least one target clause text from at least one clause text based on the similarity.

[0048] Specifically, the names and descriptions of the chapter templates, as well as the content of each clause text, can be semantically encoded using pre-trained language models (such as BERT or Word2Vec) or keyword extraction algorithms to generate high-dimensional semantic vectors. The similarity between the semantic vector of the chapter template and the semantic vector of each clause text is calculated (e.g., using cosine similarity). Clause texts with similarity scores higher than a preset threshold are identified as candidate target clauses. The matched candidate target clauses can be further ranked based on similarity scores, historical usage frequency of the clauses, or relevance to the company's current project type to form a recommendation list. At least one target clause text is then selected from the recommendation list.

[0049] S302, inject at least one target clause text into the chapter template to generate the chapter corresponding to the chapter template.

[0050] In this embodiment, at least one target clause text is injected into a chapter template to generate a chapter corresponding to the chapter template. Specifically, at least one determined target clause text can be inserted or filled into the chapter template in a logical order.

[0051] For example, multiple clauses about "material strength", "surface treatment" and "dimensional tolerance" can be sequentially filled into the "3. Technical Requirements" section template to generate a complete and formatted section (i.e., the specific content of the "3. Technical Requirements" section).

[0052] S303, Generate an initial template based on at least one chapter template corresponding to a chapter.

[0053] In this embodiment of the application, an initial template is generated based on the chapter corresponding to at least one chapter template.

[0054] Generating an initial template based on at least one chapter template may include the following steps.

[0055] Step 31: Identify at least one key chapter from the chapters corresponding to at least one chapter template, and set the status of at least one key chapter to locked state.

[0056] In this embodiment, at least one key chapter is identified from the chapters corresponding to at least one chapter template, and the status of at least one key chapter is set to locked. A key chapter refers to a chapter containing mandatory regulations, core performance indicators, disclaimers of liability, or other content that cannot be arbitrarily changed (such as security requirements, core performance parameters, etc.). The locked status refers to a protective attribute applied to the chapter, used to prohibit downstream users (non-administrators) from performing any editing, deletion, or other operations on the chapter, thereby ensuring the consistency and compliance of the core clauses.

[0057] Specifically, identifying at least one key chapter from at least one chapter template can include one or more of the following methods: Based on preset tags and rules, at least one key chapter can be identified from at least one chapter template. Specifically, automatic identification can be performed based on preset tags or classification codes of chapters. For example, all chapters with tags containing "regulations," "safety," "responsibility," or "core performance" will be identified as key chapters. Furthermore, more complex business rules can be configured, such as identifying a chapter as a key chapter when it references a specific external standard number (e.g., "ISO 26262") or internal control document.

[0058] Based on the semantics of the content and the type of clauses, at least one key chapter can be identified from the chapters corresponding to at least one chapter template. Specifically, natural language processing analysis can be used to analyze the clause content injected into the chapter to identify whether it contains preset mandatory wording patterns (such as "must", "prohibited", "must not"), specific risk terms (such as "high pressure", "flammable", "toxic"), or quantitative indicators (such as "≥99.9%" or "≤0.1mm"). When the proportion of such content exceeds a set threshold, the chapter can be identified as a key chapter and submitted to the administrator for confirmation.

[0059] It is also possible to determine at least one key chapter from the chapters corresponding to at least one chapter template based on the association of knowledge base or permission mapping. Specifically, a key requirement knowledge base can be defined, which contains the mapping relationship between key clauses and chapters. Based on the key requirement knowledge base, the chapters containing key clauses in the chapters corresponding to at least one chapter template can be determined as key chapters.

[0060] Users with administrator privileges can also directly select or batch specify any chapters as key chapters through a graphical interface.

[0061] Step 32: Determine at least one non-key chapter from the chapters corresponding to at least one chapter template, and set the status of at least one non-key chapter to unlocked.

[0062] In this embodiment, at least one non-critical chapter is determined from the chapters corresponding to at least one chapter template, and the status of at least one non-critical chapter is determined to be unlocked. An unlocked chapter refers to a chapter containing overview descriptions, references, project-specific information, etc., which can be adjusted according to actual circumstances (such as "1. Scope", "5. Appendix"). The unlocked state refers to the openness attribute applied to the chapter, allowing downstream users (non-administrators) to edit, supplement, or delete the content of the chapter in subsequent processes according to specific business needs, thereby achieving template flexibility and scenario adaptation. This embodiment does not limit this aspect.

[0063] Step 33: Generate an initial template based on at least one key chapter and non-key chapters.

[0064] In this embodiment, an initial template is generated based on at least one key chapter and one non-key chapter. Specifically, chapters with locked or unlocked states can be encapsulated to generate an initial template with embedded access control logic.

[0065] It should be noted that when generating the initial template based on at least one key chapter and non-key chapters, the content corresponding to the key chapters and non-key chapters can be analyzed to generate a template summary. This template summary may include: the number of key chapters, the main target clause texts involved, and the level of customization complexity.

[0066] In addition, quality checks can be performed on the generated initial template, such as checking for required but unfilled key sections; verifying the validity of all cross-references; and ensuring that the format of locked sections conforms to non-editable technical specifications.

[0067] S203, Based on the initial template, generate at least one candidate template, the candidate template inheriting the locking state of the key chapters in the initial template.

[0068] In this embodiment of the application, this step is similar to step S102 above, and will not be described in detail here.

[0069] S204, in response to the template selection instruction, determine the target template from at least one candidate template.

[0070] In this embodiment of the application, this step is similar to step S103 above, and will not be described in detail here.

[0071] S205. The target template is displayed to the user so that the user can edit the target template and generate a requirements specification.

[0072] In this embodiment of the application, this step is similar to step S104 above, and will not be described in detail here.

[0073] S206, when a user is editing the target template, detect whether there is a conflict between concurrent editing by multiple users.

[0074] In this embodiment, when a user edits a target template, the system detects whether there is a multi-user concurrent editing conflict. A multi-user concurrent editing conflict refers to two or more users simultaneously performing inconsistent modifications on the same content, paragraph, or value in a non-critical section of the same target template (e.g., user A deletes clause 1, while user B simultaneously modifies the value of that clause), making it impossible to determine the final content of that section. This can include content overlay conflicts (i.e., multiple users making completely different modifications to the same text segment), format conflicts (e.g., user A modifies the paragraph style, while user B simultaneously modifies the font of the same paragraph), structural conflicts (e.g., user A deletes list item 1, while user B simultaneously adds a sub-item under that list item), and attachment association conflicts (i.e., multiple users performing different upload or deletion operations on attachments associated with the same section). The detection mechanism for multi-user concurrent editing conflicts can be based on operation conversion or differential synchronization algorithms, achieved by comparing the timestamps, target positions, and content differences of operation sequences from different user terminals. This embodiment does not limit this approach.

[0075] S207: In the event of concurrent editing conflicts among multiple users, merge the operations corresponding to the concurrent editing conflicts or trigger a manual intervention process.

[0076] In this embodiment, when multiple users are concurrently editing in conflict, the operations corresponding to the conflicting operations are merged or a manual intervention process is triggered. Merging the operations corresponding to the conflicting operations can be based on preset conflict resolution rules (such as "last saver takes precedence" or "determined by user role weight"), or by using an operation conversion algorithm to attempt to automatically merge the modifications of non-conflicting parts and select a version for the conflicting parts.

[0077] For example, if user A modifies the first five characters of a chapter title and user B modifies the last five characters of a chapter title, the modifications in these two different locations can be automatically merged.

[0078] For manual intervention processes, when conflicts cannot be automatically merged according to preset conflict resolution rules (such as a complete rewrite of the same sentence), automatic merging will be stopped, the conflict area will be locked, and a conflict resolution notification will be pushed to the users involved or the predefined template administrators. Administrators or collaborating users can manually review the conflicted content and select the final version to resolve the conflict. This application embodiment does not limit this.

[0079] Furthermore, after generating the requirements specification, its completeness can be verified. This can include checking whether the requirements specification is complete; if it is incomplete, a prompt signal is issued to allow the user to edit the requirements specification until it is complete. The prompt signal can be a visual or text message reminder to the user or administrator through interface pop-ups, message notifications, task list highlighting, etc.

[0080] Specifically, verifying the completeness of the requirements specification can involve checking whether all sections or fields marked as "required" in the target template have been filled in, and whether all required attachments (such as drawings and standard documents) have been uploaded and linked. It also involves verifying whether the attachments meet the preset format.

[0081] Based on the above description of the technical solution provided in the embodiments of this application, an initial template is generated based on preset clause rules. Based on the initial template, at least one candidate template is generated. The candidate templates inherit the locked state of key sections in the initial template. In response to a template selection instruction, a target template is determined from the at least one candidate template and displayed to the user for editing, generating a requirements specification. This ensures that when the user edits the target template, the content of key sections from the initial template will not be tampered with, effectively preventing compliance risks. It solves the technical problem in existing technologies where the lack of a unified structured mechanism in templates leads to the easy tampering of key content in generated requirements specifications, potentially causing compliance risks.

[0082] like Figure 4 The diagram shown illustrates the implementation flow of another method for generating a requirements specification provided in this application, which may specifically include the following: S401, Generate an initial template based on preset terms and rules.

[0083] In this embodiment of the application, this step is similar to step S101 above, and will not be described in detail here.

[0084] S402, Obtain a preset category list, which contains at least one product type.

[0085] In this embodiment, a preset category list is obtained, which contains at least one product type. The preset category list refers to a pre-defined structured directory used to categorize a company's product lines or component families. Examples include drivetrain systems, chassis systems, interior trim, electronic and electrical architecture, and intelligent driving systems. Product types refer to specific category items under this structured directory, used to associate with specific business scenarios, technical specifications, and customization requirements, such as "electronic control unit (ECU)," "driveshaft," and "vehicle display screen."

[0086] S403: For any product type, obtain the corresponding customization terms.

[0087] In this application embodiment, for any product type, the corresponding customized terms are obtained. Customized terms refer to the specific technical or management provisions preset for the characteristics, application scenarios, or special compliance requirements of that product type.

[0088] For example, customized terms for the "power battery" product type may include "cell cycle life requirements" and "thermal management system interface definition".

[0089] To obtain customized terms corresponding to a product type, it can be read from a predefined exclusive terms library associated with the product type, or it can be obtained from a global terms library through rule matching or semantic retrieval based on preset rules (such as product classification codes). This application embodiment does not limit this.

[0090] S404, based on the initial template and the customized terms corresponding to the product type, generates a candidate template corresponding to the product type, wherein the candidate template inherits the locking status of the key chapters in the initial template.

[0091] In this embodiment of the application, a candidate template corresponding to the product type is generated based on the initial template and the customized terms corresponding to the product type. The candidate template inherits the locking status of the key chapters in the initial template.

[0092] Specifically, generating a candidate template corresponding to a product type based on the initial template and the customized terms corresponding to the product type may include: injecting (such as filling, replacing or appending) the customized terms corresponding to the product type into the non-critical chapters (i.e., editable chapters) in the initial template to generate a candidate template corresponding to the product type.

[0093] S405 responds to the template selection instruction, parses the template selection instruction, and generates product keywords.

[0094] In this embodiment of the application, in response to a template selection instruction, the template selection instruction is parsed to generate product keywords. Product keywords refer to words or phrases used to characterize the core features of the user's current project or needs, such as component names ("suspension springs"), functional modules ("vehicle communication"), or project codes.

[0095] Specifically, parsing the template selection instruction to generate product keywords may include receiving text input by the user on the front-end interface, selected category tags, or uploaded documents, and using natural language processing technology for word segmentation, entity recognition, and keyword extraction to obtain structured product keywords. This application embodiment does not limit this process.

[0096] S406, determine the similarity between the product keywords and at least one candidate template.

[0097] In this embodiment of the application, the similarity between product keywords and at least one candidate template is determined.

[0098] Specifically, the text similarity between product keywords and the metadata (such as template name, product type, and description text) of each candidate template can be calculated (e.g., based on TF-IDF and cosine similarity), or a comprehensive evaluation can be conducted by combining the historical usage data of candidate templates (such as the frequency of use by the same or similar keyword items) to obtain a similarity score that represents the degree of matching.

[0099] S407, Based on similarity, determine the target template from at least one candidate template.

[0100] In this embodiment of the application, the target template is determined from at least one candidate template based on similarity.

[0101] Specifically, candidate templates can be sorted in descending order of similarity score, with the top-ranked candidate template automatically identified as the target template. Alternatively, the top N (where N is a positive integer, such as 2 or 3) candidate templates can be displayed to the user as a recommendation list, allowing the user to ultimately select and confirm the target template. This application does not limit this approach.

[0102] S408 presents the target template to the user so that the user can edit the target template and generate a requirements specification.

[0103] In this embodiment of the application, this step is similar to step S104 above, and will not be described in detail here.

[0104] In addition, the system can statistically analyze the frequency of use of target templates and user ratings for their use. Specifically, each time a user identifies and uses a target template through search, recommendation, or manual selection, the usage behavior can be recorded, and the template's "frequency of use" statistics can be updated. The frequency of use can be calculated on a rolling basis based on time windows (such as the last 30 days or the last year) to reflect the current popularity and applicability of the target template.

[0105] Once users have completed the writing, approval, or release process of their requirements specification based on the target template, they can be invited to rate the target template for satisfaction (e.g., using a five-star rating system) or submit text feedback. The ratings and feedback information will be linked to the target template's metadata and used to calculate the target template's usage score (e.g., using the average of users' satisfaction ratings for the target template as the usage score).

[0106] Based on the above statistics on usage frequency and usage rating, when a user enters keywords to search for a target template, the target template can be determined by combining usage frequency, usage rating, and keyword semantic similarity.

[0107] Corresponding to the above method embodiments, this application also provides a requirement specification generation apparatus, such as... Figure 5 As shown, the device may include an initial template generation module 501, a candidate template generation module 502, a target template determination module 503, and a requirements specification generation module 504.

[0108] The initial template generation module 501 is used to generate an initial template based on preset clause rules; The candidate template generation module 502 is used to generate at least one candidate template based on the initial template. The candidate template inherits the locking status of the key chapters in the initial template. The target template determination module 503 is used to determine a target template from at least one candidate template in response to a template selection instruction; The requirements specification generation module 504 is used to display the target template to the user so that the user can edit the target template and generate the requirements specification.

[0109] This application also provides a vehicle, such as... Figure 6 As shown, it includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, wherein the processor 601, the communication interface 602, and the memory 603 communicate with each other through the communication bus 604. Memory 603 is used to store computer programs; In one embodiment of this application, when the processor 601 executes a program stored in the memory 603, it performs the following steps: Based on preset terms and rules, an initial template is generated; based on the initial template, at least one candidate template is generated, which inherits the locked status of key chapters in the initial template; in response to a template selection instruction, a target template is determined from at least one candidate template; the target template is displayed to the user so that the user can edit the target template and generate a requirements specification.

[0110] The communication bus mentioned in the above vehicles can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0111] The communication interface is used for communication between the aforementioned vehicle and other devices.

[0112] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0113] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0114] In another embodiment provided in this application, a storage medium is also provided, which stores instructions that, when run on a computer, cause the computer to execute the requirement specification generation method described in any of the above embodiments.

[0115] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute the requirement specification generation method described in any of the above embodiments.

[0116] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0117] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0118] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0119] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the protection scope of this application.

Claims

1. A method for generating a requirements specification, characterized in that, The method includes: Generate an initial template based on preset terms and rules; Based on the initial template, at least one candidate template is generated, wherein the candidate template inherits the locking status of key chapters in the initial template; In response to a template selection instruction, a target template is determined from at least one of the candidate templates; The target template is displayed to the user so that the user can edit the target template to generate a requirements specification.

2. The method according to claim 1, characterized in that, The preset terms and conditions rule contains at least one terms and conditions text, and the generation of an initial template based on the preset terms and conditions rule includes: Obtain the preset structure template; Inject at least one of the aforementioned clause texts into the preset structure template to generate the initial template.

3. The method according to claim 2, characterized in that, The preset structure template includes at least one chapter template. Injecting at least one clause text into the preset structure template to generate the initial template includes: For any of the chapter templates, determine at least one target clause text from at least one of the clause texts; Inject at least one of the target clause texts into the chapter template to generate the chapter corresponding to the chapter template; The initial template is generated based on at least one chapter corresponding to the chapter template.

4. The method according to claim 3, characterized in that, The step of generating the initial template based on at least one chapter corresponding to the chapter template includes: Determine at least one key chapter from the chapters corresponding to at least one of the chapter templates, and set the status of at least one key chapter to a locked state; Determine at least one non-key chapter from the chapters corresponding to at least one of the chapter templates, and set the state of at least one non-key chapter to be unlocked. The initial template is generated based on at least one of the key chapters and the non-key chapters.

5. The method according to claim 1, characterized in that, The step of generating at least one candidate template based on the initial template includes: Obtain a preset category list, wherein the preset category list contains at least one product type; For any of the product types mentioned, obtain the corresponding customization terms for that product type; Based on the initial template and the customized terms corresponding to the product type, a candidate template corresponding to the product type is generated.

6. The method according to claim 5, characterized in that, The step of generating a candidate template corresponding to the product type based on the initial template and the customization terms corresponding to the product type includes: The customized terms corresponding to the product type are injected into the non-critical sections of the initial template to generate a candidate template corresponding to the product type.

7. The method according to claim 1, characterized in that, The step of determining a target template from at least one candidate template in response to a template selection instruction includes: In response to the template selection instruction, the template selection instruction is parsed to generate product keywords; Determine the similarity between the product keywords and at least one of the candidate templates; Based on the similarity, the target template is determined from at least one of the candidate templates.

8. The method according to claim 1, characterized in that, The method further includes: When the user edits the target template, detect whether there is a conflict of concurrent editing by multiple users; In the event of concurrent editing conflicts among multiple users, the operations corresponding to the concurrent editing conflicts will be merged or a manual intervention process will be triggered.

9. The method according to claim 1, characterized in that, After generating the requirements specification, the following is also included: Verify that the requirements specification is complete; If the requirements specification is incomplete, a prompt signal will be issued so that the user can edit the requirements specification until it is complete.

10. A device for generating a requirements specification, characterized in that, The device includes: The initial template generation module is used to generate an initial template based on preset clause rules; A candidate template generation module is used to generate at least one candidate template based on the initial template, wherein the candidate template inherits the locking status of key chapters in the initial template; A target template determination module is configured to determine a target template from at least one of the candidate templates in response to a template selection instruction; The requirements specification generation module is used to display the target template to the user so that the user can edit the target template to generate a requirements specification.

Images