System management document generation method and device, computer equipment and storage medium

Abstract

The invention relates to the technical field of system management, in particular to a system management document generation method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring a change feature generated in a target system; according to the first association relationship, performing influence traceability processing on the change feature to obtain a demand influence analysis result corresponding to the change feature; according to the demand influence analysis result, updating the first association relationship to obtain a second association relationship between the updated demand feature and the code feature; and generating a management document according to the second association relationship and the demand influence analysis result. According to the method and the device, the influence degree of the change feature received by the demand can be clearly and accurately represented through the demand influence analysis result, a data basis is provided for subsequently unifying the demand feature and the code feature, and operation and maintenance personnel can accurately know the latest state of the demand feature and the code feature through the management document of the target system; and the maintainability and the accuracy of the system are improved.

Description

Technical Field

[0001] The present application relates to the field of system management technology, and in particular to a method, device, computer equipment and storage medium for generating system management documents. Background Art

[0002] In the prior art, the requirement text and the code are managed separately. When one of them is modified, the other needs to be modified accordingly to ensure the synchronization of the two and prevent conflicts between the requirement text and the code.

[0003] However, when requirements or code change, it is difficult to synchronize the requirements and code, which may easily result in the requirement changes not being correctly implemented in the code, or the code changes not meeting the latest requirements. In addition, after the requirements change, the management documents of the code and requirements are often not updated in a timely manner, causing the development team to easily confuse the latest status of the requirements during maintenance and iteration, affecting the maintainability and accuracy of the system. Summary of the invention

[0004] Based on this, it is necessary to provide a method, device, computer equipment and storage medium for generating system management documents that can prevent the development team from easily confusing the latest status of requirements during maintenance and iteration in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for generating a system management document. The method comprises:

[0006] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0007] According to the first association relationship between the requirement feature and the code feature, impact tracing processing is performed on the change feature to obtain a requirement impact analysis result corresponding to the change feature;

[0008] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0009] A management document for the target system is generated according to the second association relationship and the demand impact analysis result.

[0010] In one embodiment, if the change feature is a change code feature; performing impact tracing processing on the change feature according to the first association relationship between the requirement feature and the code feature to obtain a requirement impact analysis result corresponding to the change feature includes:

[0011] Determining at least one historical code feature corresponding to the changed code feature;

[0012] According to the first association relationship between the demand feature and the code feature, the changed code feature and each of the historical code features, a demand impact analysis result corresponding to the changed feature is determined.

[0013] In one embodiment, determining the demand impact analysis result corresponding to the change feature according to the first association relationship between the demand feature and the code feature, the change code feature and each of the historical code features includes:

[0014] Determining a target code block that has been changed according to the changed code feature and each of the historical code features;

[0015] Determining a historical demand feature associated with the target code block according to a first association relationship between the demand feature and the code feature;

[0016] Determine a demand impact analysis result corresponding to the change feature according to the historical demand feature and the target code block.

[0017] In one embodiment, determining the demand impact analysis result corresponding to the change feature according to the historical demand feature and the target code block includes:

[0018] Verifying whether the code logic of the target code block is the same as the requirement logic of the historical requirement feature;

[0019] Determine a demand impact analysis result based on the verification result; wherein the demand impact analysis result includes the demand status and impact level of the historical demand feature.

[0020] In one embodiment, the method further comprises:

[0021] For the historical demand features whose demand status is an affected status in the demand impact analysis result, and the impact level of the historical demand features, verifying the validity of the historical demand features;

[0022] After the validity verification is passed, a new code feature is generated according to the demand information corresponding to the historical demand feature; and the new code feature is updated to the code repository.

[0023] In one of the embodiments, the requirement information includes at least one of a requirement identifier, change content, and a description of affected functions.

[0024] In a second aspect, the present application also provides a system management document generation device. The device includes:

[0025] An acquisition module, used for acquiring change features generated in the target system; wherein the change features include at least one of a change requirement feature and a change code feature;

[0026] A tracing module, configured to perform an impact tracing process on the change feature according to a first association relationship between the demand feature and the code feature, and obtain a demand impact analysis result corresponding to the change feature;

[0027] An updating module, configured to update the first association relationship according to the requirement impact analysis result to obtain an updated second association relationship between the requirement feature and the code feature;

[0028] A generation module is used to generate a management document for the target system according to the second association relationship and the demand impact analysis result.

[0029] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0030] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0031] According to the first association relationship between the requirement feature and the code feature, impact tracing processing is performed on the change feature to obtain a requirement impact analysis result corresponding to the change feature;

[0032] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0033] A management document for the target system is generated according to the second association relationship and the demand impact analysis result.

[0034] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0035] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0036] According to the first association relationship between the requirement feature and the code feature, impact tracing processing is performed on the change feature to obtain a requirement impact analysis result corresponding to the change feature;

[0037] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0038] A management document for the target system is generated according to the second association relationship and the demand impact analysis result.

[0039] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0040] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0041] According to the first association relationship between the requirement feature and the code feature, impact tracing processing is performed on the change feature to obtain a requirement impact analysis result corresponding to the change feature;

[0042] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0043] A management document for the target system is generated according to the second association relationship and the demand impact analysis result.

[0044] The above-mentioned system management document generation method, device, computer equipment and storage medium obtain the change characteristics generated in the target system to realize the impact tracing processing of the change characteristics according to the first association relationship between the demand characteristics and the code characteristics, obtain the demand impact analysis result corresponding to the change characteristics, and update the first association relationship according to the demand impact analysis result, and then generate the management document for the target system according to the second association relationship and the demand impact analysis result. According to the above content, it can be seen that in the process of generating system management files, the present application performs the impact tracing processing on the change characteristics according to the first association relationship between the demand characteristics and the code characteristics to realize the operation of generating the demand impact analysis result, and then, through the demand impact analysis result, the degree of influence of the demand on the change characteristics can be clearly and accurately characterized, and then the data basis is provided for the subsequent unification of the demand characteristics and the code characteristics, ensuring the smooth progress of the subsequent process, preventing the situation where the demand changes are not correctly implemented in the code, or the code changes do not meet the latest requirements, and ensuring that the development team and operation and maintenance personnel can accurately know the latest status of the demand characteristics and code characteristics through the management documents of the target system, improving the maintainability and accuracy of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 An application environment diagram of a method for generating a system management document provided in an embodiment of the present application;

[0046] Figure 2A flowchart of a method for generating a first system management document provided in an embodiment of the present application;

[0047] Figure 3 A flowchart of a second method for generating a system management document provided in an embodiment of the present application;

[0048] Figure 4 A flowchart of a third method for generating a system management document provided in an embodiment of the present application;

[0049] Figure 5 A flowchart of a fourth method for generating a system management document provided in an embodiment of the present application;

[0050] Figure 6 A structural block diagram of a device for generating system management documents provided in an embodiment of the present application;

[0051] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0053] The method for generating a system management document provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. By obtaining the change features generated in the target system, the change features can be traced according to the first association relationship between the demand features and the code features, and the demand impact analysis results corresponding to the change features are obtained. According to the demand impact analysis results, the first association relationship is updated, and then, according to the second association relationship and the demand impact analysis results, the management document for the target system is generated. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0054] In one embodiment, Figure 2As shown, a method for generating a system management document is provided, and the method is applied to Figure 1 Taking the server 104 in the example as an example, the following steps are included:

[0055] S201, obtaining change features generated in the target system.

[0056] The change feature includes at least one of a change requirement feature and a change code feature.

[0057] It should be noted that when it is necessary to obtain the change characteristics generated in the target system, the change monitoring function can be pre-set to record and analyze each code submission and requirement change submission in the target system, so as to achieve the purpose of obtaining the change characteristics generated in the target system.

[0058] As an example, the hook mechanism can be used to monitor each code submission, that is, for each submission, the system will automatically trigger the following operations: extract the changed code lines, functions, modules, and file paths. And extract the submission log and comment information to help analyze the purpose and impact of the change.

[0059] To further illustrate, a change monitoring module may be preset, and then, an operation of acquiring characteristics of changes generated in the target system may be implemented according to the change monitoring module.

[0060] In one embodiment of the present application, the change monitoring module can be responsible for real-time monitoring of code changes, and trace back to related requirements based on the content of the changes to evaluate whether the requirements are affected. Specifically, the change monitoring module can monitor code submissions through a hook mechanism through an integrated control system, and record changed code blocks, files, and submission comments. In addition, when the code changes, the code structure before and after the change is compared, the difference is extracted, and its functional changes are analyzed to see whether they affect the realization of the requirements. Furthermore, the change monitoring module can also query the requirement-code association database based on the changed code blocks, and trace back to the requirement items related to the changed code.

[0061] Among them, the input parameters for the change monitoring module can be code submission information (from Git or other version control systems); the output parameters of the change monitoring module can be the requirement traceability report of the changed code block and the affected requirement list; the technical tools used by the change monitoring module to obtain the change characteristics generated in the target system may include but are not limited to: version control systems (such as Git), semantic difference detection tools, etc.

[0062] S202: Perform impact tracing on the changed feature according to the first association relationship between the demand feature and the code feature to obtain a demand impact analysis result corresponding to the changed feature.

[0063] It should be noted that the first association relationship records the association relationship between at least one requirement feature and at least one code feature in the target system. Therefore, when constructing the first association relationship, it is necessary to parse the requirements and codes of the target system in advance to realize the construction of the first association relationship based on the code features and requirement features obtained by parsing.

[0064] In one embodiment of the present application, when it is necessary to build a first association relationship, the following contents may be included: For demand features: connect to the demand management system, obtain detailed demand documents according to version information, and the formats include pdf, word, etc.; the system uses natural language processing (NLP) technology to parse the detailed demand documents and extract key terms, functional descriptions and business logic. The demand features recorded in the detailed demand document are parsed, which include at least one demand and at least one sub-requirement corresponding to each demand, and a unique identifier is generated for each demand and sub-requirement to form a tree structure label for subsequent tracking and matching. For code features: according to the relevant service system that can be obtained for each version of the target system, the code library branch address is obtained according to the system name to obtain the source code; the code structure is parsed through the abstract syntax tree AST to obtain code features, including semantic features such as code class name, function name, variables, comments and business features. The demand features and code features are matched with semantic features to build the first association relationship between the demand features and the code features.

[0065] As an example, the demand features extracted by natural language processing technology can include specific examples in the following aspects: (1) For functional description: describe the functions that the system or module needs to implement. The demand feature can be "user login verification", the system should have the function of verifying the user name and password. And "order processing", the system should support users to submit orders, calculate order amounts, confirm payments and other functions. (2) For insurance policy review: the process and rules for reviewing insurance policies after customers submit insurance applications. The demand feature can be "preliminary review of the customer's health status and insurance history", the system needs to conduct preliminary screening of insurance eligibility based on the customer's health information, age, occupation, etc. and "review is required before the insurance policy takes effect". If the initial review is passed, a review is required to ensure that there are no errors before it takes effect. (3) For claim review: the business logic for reviewing claim applications when customers apply for claims. The demand feature can be "check claim eligibility based on insurance type", the system checks whether the customer's claim conditions are met based on the insurance type (such as critical illness insurance, accident insurance, etc.). and "large claims require manual review". When the claim amount exceeds a certain threshold (such as 500,000 yuan), the system automatically triggers the manual review process to reduce risks. (4) Regarding policy payment: the process and rules for customers to pay premiums regularly. The demand characteristics can be "overdue premiums enter the grace period". When the customer fails to pay the premium on time, the system automatically sets a grace period (such as 30 days), during which the customer can continue to pay the premium without invalidation. And "automatically invalidate after exceeding the grace period". If the customer still fails to pay the premium within the grace period, the system automatically sets the policy status to invalid and notifies the customer. (5) Regarding policy reinstatement: the process for customers to apply for reinstatement of the policy after the policy expires. The demand characteristics can be "repayment of premiums is required for reinstatement after expiration". When the customer applies for reinstatement after the grace period, he / she needs to pay the unpaid premium. And "re-health review is required for reinstatement application". If the policy has been invalid for more than a certain period of time (such as half a year), a health review is required before reinstatement. (6) Regarding the renewal process: After the insurance expires, the system automatically handles the business logic of renewal. The demand characteristics can be "send a renewal notice 30 days before expiration". The system automatically sends a renewal reminder 30 days before the policy expires to notify the customer that the policy is about to expire. And "automatic renewal requires customer confirmation and payment". If the customer agrees to renew, the system requires the customer to confirm and pay the renewal premium before it can continue to take effect. (7) Regarding customer change applications: the process of processing policy information change requests submitted by customers. The demand characteristics can be "policy beneficiary changes require customer signature confirmation". If the customer wishes to change the beneficiary, the system generates a change application form and requires the customer to sign and confirm. And "adding insurance coverage requires recalculation of premiums". If the customer applies to add insurance coverage items, the system recalculates the premium based on the new coverage and generates a premium payment notice. (8) Regarding cancellation processing: the process after the customer submits a cancellation application.The requirement characteristics may be "deduct handling fees for policy cancellation". The system calculates the handling fees to be deducted and the refund amount according to the policy terms and generates a policy cancellation settlement statement. And "preferential refunds are available for policy cancellation within a specified time". If the customer cancels the policy within a specified time (such as 30 days) after the contract is signed, the system automatically calculates the preferential refund according to the terms. Interface requirements: interface requirements for the system to interact with other systems or modules. (9) Performance requirements: requirements for system performance. The requirement characteristics may be "page loading time is less than 2 seconds". The system should ensure that the page loading time is within 2 seconds. And "support 500 concurrent requests per second". The system needs to support stability under high concurrency and ensure that 500 requests can be processed per second. (10) Security requirements: requirements for system security. The requirement characteristics may be "sensitive data encrypted storage". Sensitive information such as user passwords should be encrypted and stored. And "need to support two-factor authentication". The system requires users to perform two-factor authentication when logging in to improve security. (11) User experience requirements: requirements for user interface or interaction design. The required features can be "provide a clear error prompt when user registration fails". If the registration fails, the system should display a clear error message to the user. And "pop up a payment success prompt after the order is confirmed". When the order payment is successful, the system should display a success prompt message.

[0066] Among them, the first association relationship between the requirement characteristics and the code characteristics can be stored in the requirement-code association database to provide a basis for subsequent change monitoring and traceability.

[0067] To further explain, the impact of the change feature can be traced to analyze and determine whether the change has affected the realization of historical requirements. The analysis content can specifically include all affected requirement items and their specific impacts, and then generate the requirement impact analysis results corresponding to the change feature.

[0068] To further explain, the requirement identifier is a 12-bit data, of which bits 1 and 2 are system identifiers, bits 3-6 are subsystem identifiers, bits 7 and 8 are requirement version number identifiers, bits 9, 10, and 11 are sub-requirement identifiers, and bit 12 is the requirement status identifier.

[0069] S203: Update the first association relationship according to the demand impact analysis result to obtain an updated second association relationship between the demand feature and the code feature.

[0070] It should be noted that after determining the results of the demand impact analysis, the content of the change requirement can be determined based on the results of the demand impact analysis; then, through auxiliary programming tools, the code is modified in combination with the change requirement content to obtain the modified code; the first association relationship is updated through the modified code to obtain the second association relationship between the updated demand characteristics and the code characteristics.

[0071] Further explanation: The modified code can be submitted to the code repository.

[0072] In one embodiment of the present application, after determining the results of the demand impact analysis, the change content of the demand impact analysis results can be extracted to obtain the change demand content; and the change demand content is submitted to a manual review process so that the operation and maintenance personnel can judge the validity of the change demand content. When it is determined that the change demand content is valid, the step of modifying the code through auxiliary programming tools in combination with the change demand content is executed.

[0073] S204: Generate a management document for the target system according to the second association relationship and the demand impact analysis result.

[0074] It should be noted that the management documents for the target system may cover the implementation of requirements, code descriptions, interface information, etc.; to ensure the validity of the management documents, it is necessary to ensure that the status of the content in the management documents is consistent with the latest status of the requirement characteristics and code characteristics. If changes to the requirement characteristics and code characteristics continue to occur in the future, the management documents of the target system must also be updated synchronously.

[0075] Among them, the change action of the requirement characteristics and code characteristics can be verified after manual verification to verify whether the change action of the requirement characteristics and code characteristics is valid. After the change action is valid, the operation of synchronously updating the management document of the target system is executed.

[0076] To further explain, operation and maintenance personnel who are to receive management documents may be specified in advance. After the management document is generated or the management document is updated, the management document with the latest status may be synchronously sent to the operation and maintenance personnel who are to receive management documents in advance, so that the relevant operation and maintenance personnel can be informed of the latest status and actual situation of the target system in a timely manner.

[0077] The above-mentioned method for generating system management documents obtains the change features generated in the target system to realize the impact tracing processing of the change features according to the first association relationship between the demand features and the code features, obtains the demand impact analysis results corresponding to the change features, and updates the first association relationship according to the demand impact analysis results, and then generates management documents for the target system according to the second association relationship and the demand impact analysis results. According to the above content, it can be seen that in the process of generating system management files, the present application performs the impact tracing processing on the change features according to the first association relationship between the demand features and the code features to realize the operation of generating the demand impact analysis results, and then, through the demand impact analysis results, the degree of influence of the demand on the change features can be clearly and accurately characterized, and then a data basis is provided for the subsequent unification of demand features and code features, ensuring the smooth progress of subsequent processes, preventing the situation where the demand changes are not correctly implemented in the code, or the code changes do not meet the latest requirements, and ensuring that the development team and operation and maintenance personnel can accurately know the latest status of the demand features and code features through the management documents of the target system, improving the maintainability and accuracy of the system.

[0078] In one embodiment, if Figure 3 As shown, if the changed feature is a changed code feature, when it is necessary to perform impact tracing processing on the changed feature according to the first association relationship between the requirement feature and the code feature to obtain the requirement impact analysis result corresponding to the changed feature, the following contents may be specifically included:

[0079] S301, determining at least one historical code feature corresponding to the changed code feature.

[0080] In one embodiment of the present application, when it is necessary to determine at least one historical code feature corresponding to a changed code feature, the following may specifically be included: comparing the code before and after the change, performing semantic analysis, and determining whether the function of the code has changed (for example, adding new function calls, modifying core business logic, etc.); performing comparison based on the first association relationship between the requirement feature and the code feature, identifying which requirement the affected code module belongs to, and tracing back to a specific requirement document entry, which contains at least one historical code feature.

[0081] S302: Determine a demand impact analysis result corresponding to the change feature according to the first association relationship between the demand feature and the code feature, the change code feature and each historical code feature.

[0082] It should be noted that when it is necessary to determine the demand impact analysis results corresponding to the changed features, the following contents may be included: determining the target code block that has changed based on the changed code features and the historical code features; determining the historical demand features associated with the target code block based on the first association relationship between the demand features and the code features; determining the demand impact analysis results corresponding to the changed features based on the historical demand features and the target code block.

[0083] Specifically, retrieve the version information before the changed code feature is changed, use a difference detection tool (such as a Diff algorithm) to compare and analyze the changed code features of each version information, extract the changed target code block, match the historical requirement entries in the first association relationship between the requirement feature and the code feature of the target code block, determine the historical requirement feature associated with the target code block, and then perform semantic analysis on the code change to determine whether the change has destroyed the core function of the historical requirement feature, and generate a requirement impact analysis result.

[0084] Furthermore, when it is necessary to determine the demand impact analysis results corresponding to the change characteristics based on the historical demand characteristics and the target code block, it may include the following contents: verifying whether the code logic of the target code block is the same as the demand logic of the historical demand characteristics; determining the demand impact analysis results based on the verification results; wherein the demand impact analysis results include the demand status and impact level of the historical demand characteristics.

[0085] Specifically, semantic analysis tools (such as Word2Vec and BERT) can be used to verify whether the code logic of the target code block is the same as the requirement logic of the historical requirement features, so as to identify whether the change affects the implementation of the requirement; the changed code is matched with the semantic features of the requirement, and if it is found that the change affects the requirement logic of the requirement, the requirement is marked as "affected". Based on the degree of impact, the impact level of the requirements is classified (such as high, medium, and low), and the development team determines the change requirements to be handled according to priority.

[0086] In one embodiment of the present application, validity verification processing can also be performed to recommend to the development team which requirements need to be retested or verified based on the results of the requirements impact analysis to ensure that the logic of the requirements is not destroyed. Specifically, according to the impact level of the requirements, high-impact requirements are assigned to the priority verification task list. Generate or call existing test cases for the affected requirements so that the development team can efficiently verify the integrity of the requirements implementation. Push the validity verification requirement task to the task management system to clarify the responsible person, task content and deadline.

[0087] In another embodiment of the present application, automated regression can also be triggered to record and push the regression results to relevant personnel to ensure the stability of the system after the code is changed. Specifically, the automated test script of the existing test platform is called to verify whether the changed code passes the established test case. After the regression task is triggered, the system monitors the test progress in real time to ensure that all tests are completed successfully. The test results are synchronized with the test platform (such as success, failure, and exception, etc.) and fed back to the development and testing team. Relevant personnel are notified through the notification system.

[0088] In another embodiment of the present application, additional manual checkpoints can be set for key requirements and high-impact changes to allow relevant personnel (such as demand analysts or product managers) to manually review and confirm the key parts of the demand impact report. Among them, the review content may include but is not limited to reviewing the accuracy of the impact of the change, confirming whether the demand logic is affected, and whether additional manual verification is required. After determining the feedback results, the feedback results are recorded and fed back to ensure the smooth progress of subsequent processes.

[0089] In another embodiment of the present application, a process management module for task flow can be added to automatically generate tasks after detecting requirements or code changes. The system automatically generates a task list, including requirements to be verified, affected code modules, and test requirements. The system automatically assigns tasks to processing personnel, such as developers, test engineers, product managers, etc., based on requirements and changes. The task status is updated in real time to ensure that each task has a clear progress status (such as pending, in progress, completed, etc.), and is archived after completion.

[0090] The above-mentioned system management document generation method determines at least one historical code feature corresponding to the changed code feature to achieve the demand impact analysis result corresponding to the changed feature based on the first association relationship between the demand feature and the code feature, the changed code feature and each historical code feature, thereby providing a data basis for the subsequent unification of demand features and code features, ensuring the smooth progress of subsequent processes, and preventing the situation where the demand change is not correctly implemented in the code or the code change does not meet the latest requirements.

[0091] In one embodiment, if Figure 4 As shown, when a new code feature needs to be generated, the following contents may be included:

[0092] S401, verifying the validity of the historical demand characteristics for which the demand status is an affected status in the demand impact analysis result and the impact level of the historical demand characteristics.

[0093] Specifically, for historical requirement features affected by the change, the system will generate a requirement verification suggestion, listing all potentially affected historical requirement features and their associated code modules, and recommending that developers retest or verify the implementation of these requirements.

[0094] S402, after the validity verification is passed, a new code feature is generated according to the demand information corresponding to the historical demand feature; and the new code feature is updated to the code repository.

[0095] The requirement information includes at least one of the requirement identification, change content, and impact function description.

[0096] In one embodiment of the present application, when it is necessary to generate new code features based on the demand information corresponding to the historical demand features, the following may be specifically included: a detailed analysis of the changed historical demand features is performed to extract the demand features related to the code, such as functional descriptions, business logic, and interface requirements, etc. New code features are generated based on the demand description through existing auxiliary programming tools, and the developer confirms the validity of the intelligently generated new code features and submits them to the code repository.

[0097] The above-mentioned method for generating system management documents ensures the consistency of the correspondence between requirement features and code features by generating new code features, prevents the situation where requirement changes are not correctly implemented in the code, or code changes do not meet the latest requirements, and ensures that the development team and operation and maintenance personnel can accurately obtain the latest status of requirement features and code features through the management documents of the target system, thereby improving the maintainability and accuracy of the system.

[0098] In one embodiment, if Figure 5 As shown in the figure, when you need to generate management documents for the target system, you can include the following:

[0099] S501, obtaining change characteristics generated in the target system.

[0100] S502: Determine at least one historical code feature corresponding to the changed code feature.

[0101] S503, determining the target code block where the change occurs according to the changed code feature and each historical code feature.

[0102] S504: Determine the historical demand feature associated with the target code block according to the first association relationship between the demand feature and the code feature.

[0103] S505 , verify whether the code logic of the target code block is the same as the requirement logic of the historical requirement feature.

[0104] S506: Determine the demand impact analysis result based on the verification result.

[0105] S507, updating the first association relationship according to the demand impact analysis result to obtain an updated second association relationship between the demand feature and the code feature.

[0106] S508: Generate a management document for the target system according to the second association relationship and the demand impact analysis result.

[0107] The above-mentioned method for generating system management documents obtains the change features generated in the target system to realize the impact tracing processing of the change features according to the first association relationship between the demand features and the code features, obtains the demand impact analysis results corresponding to the change features, and updates the first association relationship according to the demand impact analysis results, and then generates management documents for the target system according to the second association relationship and the demand impact analysis results. According to the above content, it can be seen that in the process of generating system management files, the present application performs the impact tracing processing on the change features according to the first association relationship between the demand features and the code features to realize the operation of generating the demand impact analysis results, and then, through the demand impact analysis results, the degree of influence of the demand on the change features can be clearly and accurately characterized, and then a data basis is provided for the subsequent unification of demand features and code features, ensuring the smooth progress of subsequent processes, preventing the situation where the demand changes are not correctly implemented in the code, or the code changes do not meet the latest requirements, and ensuring that the development team and operation and maintenance personnel can accurately know the latest status of the demand features and code features through the management documents of the target system, improving the maintainability and accuracy of the system.

[0108] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0109] In accordance with the above-mentioned concept, the embodiment of the present application also provides a system management document generation device for implementing the system management document generation method involved in the above-mentioned. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above-mentioned method, so the specific limitations of one or more system management document generation device embodiments provided below can refer to the limitations of the system management document generation method above, and will not be repeated here.

[0110] In one embodiment, Figure 6 As shown, a system management document generation device is provided, comprising: an acquisition module 10, a source tracing module 20, an update module 30 and a generation module 40, wherein:

[0111] The acquisition module 10 is used to acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of the change requirement characteristics and the change code characteristics.

[0112] The tracing module 20 is used to perform impact tracing processing on the changed feature according to the first association relationship between the demand feature and the code feature, and obtain the demand impact analysis result corresponding to the changed feature.

[0113] The updating module 30 is used to update the first association relationship according to the requirement impact analysis result to obtain an updated second association relationship between the requirement feature and the code feature.

[0114] The generating module 40 is used to generate a management document for the target system according to the second association relationship and the demand impact analysis result.

[0115] In one embodiment, determining at least one historical code feature corresponding to the changed code feature;

[0116] According to the first association relationship between the demand feature and the code feature, the changed code feature and each historical code feature, a demand impact analysis result corresponding to the changed feature is determined.

[0117] In one embodiment, a target code block that has been changed is determined based on the changed code feature and each historical code feature;

[0118] Determining a historical demand feature associated with the target code block according to a first association relationship between the demand feature and the code feature;

[0119] Based on the historical demand characteristics and the target code block, determine the demand impact analysis results corresponding to the changed characteristics.

[0120] In one embodiment, verifying whether the code logic of the target code block is the same as the requirement logic of the historical requirement feature;

[0121] Determine the demand impact analysis result based on the verification result; wherein the demand impact analysis result includes the demand status and impact level of the historical demand characteristics.

[0122] In one embodiment, for the historical demand features whose demand status is an affected status in the demand impact analysis result and the impact level of the historical demand features, the validity of the historical demand features is verified;

[0123] After the validity verification is passed, new code features are generated based on the demand information corresponding to the historical demand features; and the new code features are updated to the code repository.

[0124] In one embodiment, the requirement information includes at least one of a requirement identifier, change content, and an impact function description.

[0125] The above-mentioned system management document generation device obtains the change features generated in the target system to realize the impact tracing processing of the change features according to the first association relationship between the demand features and the code features, obtains the demand impact analysis results corresponding to the change features, and updates the first association relationship according to the demand impact analysis results, and then generates the management document for the target system according to the second association relationship and the demand impact analysis results. According to the above content, it can be seen that in the process of generating system management files, the present application performs the impact tracing processing on the change features according to the first association relationship between the demand features and the code features to realize the operation of generating the demand impact analysis results, and then, through the demand impact analysis results, the degree of influence of the demand on the change features can be clearly and accurately characterized, and then the data basis is provided for the subsequent unification of the demand features and the code features, ensuring the smooth progress of the subsequent process, preventing the demand changes from being correctly implemented in the code, or the code changes from not meeting the latest requirements, and ensuring that the development team and operation and maintenance personnel can accurately know the latest status of the demand features and code features through the management documents of the target system, improving the maintainability and accuracy of the system.

[0126] Each module in the above-mentioned system management document generation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0127] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface, the display unit and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a method for generating a system management document is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0128] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0129] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0130] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0131] According to the first association relationship between the requirement feature and the code feature, the change feature is subjected to impact tracing processing to obtain the requirement impact analysis result corresponding to the change feature;

[0132] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0133] Based on the second association relationship and the demand impact analysis results, a management document for the target system is generated.

[0134] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0135] Determining at least one historical code feature corresponding to the changed code feature;

[0136] According to the first association relationship between the demand feature and the code feature, the changed code feature and each historical code feature, a demand impact analysis result corresponding to the changed feature is determined.

[0137] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0138] Determine the target code block that has been changed based on the changed code features and the features of each historical code;

[0139] Determining a historical demand feature associated with the target code block according to a first association relationship between the demand feature and the code feature;

[0140] Based on the historical demand characteristics and the target code block, determine the demand impact analysis results corresponding to the changed characteristics.

[0141] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0142] Verify whether the code logic of the target code block is the same as the requirement logic of the historical requirement features;

[0143] Determine the demand impact analysis result based on the verification result; wherein the demand impact analysis result includes the demand status and impact level of the historical demand characteristics.

[0144] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0145] For the historical demand features whose demand status is affected in the demand impact analysis results, and the impact levels of the historical demand features, the validity of the historical demand features is verified;

[0146] After the validity verification is passed, new code features are generated based on the demand information corresponding to the historical demand features; and the new code features are updated to the code repository.

[0147] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0148] The requirement information includes at least one of the requirement identification, change content, and impact function description.

[0149] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0150] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0151] According to the first association relationship between the requirement feature and the code feature, the change feature is subjected to impact tracing processing to obtain the requirement impact analysis result corresponding to the change feature;

[0152] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0153] Based on the second association relationship and the demand impact analysis results, a management document for the target system is generated.

[0154] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0155] Determining at least one historical code feature corresponding to the changed code feature;

[0156] According to the first association relationship between the demand feature and the code feature, the changed code feature and each historical code feature, a demand impact analysis result corresponding to the changed feature is determined.

[0157] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0158] Determine the target code block that has been changed based on the changed code features and the features of each historical code;

[0159] Determining a historical demand feature associated with the target code block according to a first association relationship between the demand feature and the code feature;

[0160] Based on the historical demand characteristics and the target code block, determine the demand impact analysis results corresponding to the changed characteristics.

[0161] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0162] Verify whether the code logic of the target code block is the same as the requirement logic of the historical requirement features;

[0163] Determine the demand impact analysis result based on the verification result; wherein the demand impact analysis result includes the demand status and impact level of the historical demand characteristics.

[0164] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0165] For the historical demand features whose demand status is affected in the demand impact analysis results, and the impact levels of the historical demand features, the validity of the historical demand features is verified;

[0166] After the validity verification is passed, new code features are generated based on the demand information corresponding to the historical demand features; and the new code features are updated to the code repository.

[0167] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0168] The requirement information includes at least one of the requirement identification, change content, and impact function description.

[0169] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0170] Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic;

[0171] According to the first association relationship between the requirement feature and the code feature, the change feature is subjected to impact tracing processing to obtain the requirement impact analysis result corresponding to the change feature;

[0172] According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature;

[0173] Based on the second association relationship and the demand impact analysis results, a management document for the target system is generated.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0175] Determining at least one historical code feature corresponding to the changed code feature;

[0176] According to the first association relationship between the demand feature and the code feature, the changed code feature and each historical code feature, a demand impact analysis result corresponding to the changed feature is determined.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0178] Determine the target code block that has been changed based on the changed code features and the features of each historical code;

[0179] Determining a historical demand feature associated with the target code block according to a first association relationship between the demand feature and the code feature;

[0180] Based on the historical demand characteristics and the target code block, determine the demand impact analysis results corresponding to the changed characteristics.

[0181] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0182] Verify whether the code logic of the target code block is the same as the requirement logic of the historical requirement features;

[0183] Determine the demand impact analysis result based on the verification result; wherein the demand impact analysis result includes the demand status and impact level of the historical demand characteristics.

[0184] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0185] For the historical demand features whose demand status is affected in the demand impact analysis results, and the impact levels of the historical demand features, the validity of the historical demand features is verified;

[0186] After the validity verification is passed, new code features are generated based on the demand information corresponding to the historical demand features; and the new code features are updated to the code repository.

[0187] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0188] The requirement information includes at least one of the requirement identification, change content, and impact function description.

[0189] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0190] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0191] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0192] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for generating a system management document, characterized in that: The method comprises: Acquire the change characteristics generated in the target system; wherein the change characteristics include at least one of a change requirement characteristic and a change code characteristic; According to the first association relationship between the requirement feature and the code feature, impact tracing processing is performed on the change feature to obtain a requirement impact analysis result corresponding to the change feature; According to the requirement impact analysis result, the first association relationship is updated to obtain an updated second association relationship between the requirement feature and the code feature; A management document for the target system is generated according to the second association relationship and the demand impact analysis result.

2. The method according to claim 1, characterized in that If the change feature is a change code feature; the impact tracing process is performed on the change feature according to the first association relationship between the requirement feature and the code feature to obtain the requirement impact analysis result corresponding to the change feature, including: Determining at least one historical code feature corresponding to the changed code feature; According to the first association relationship between the demand feature and the code feature, the changed code feature and each of the historical code features, a demand impact analysis result corresponding to the changed feature is determined.

3. The method according to claim 2, characterized in that The determining, according to the first association relationship between the demand feature and the code feature, the changed code feature and each of the historical code features, a demand impact analysis result corresponding to the changed feature includes: Determining a target code block that has been changed according to the changed code feature and each of the historical code features; Determining a historical demand feature associated with the target code block according to a first association relationship between the demand feature and the code feature; Determine a demand impact analysis result corresponding to the change feature according to the historical demand feature and the target code block.

4. The method according to claim 3, characterized in that: The determining, according to the historical demand feature and the target code block, a demand impact analysis result corresponding to the change feature includes: Verifying whether the code logic of the target code block is the same as the requirement logic of the historical requirement feature; Determine a demand impact analysis result based on the verification result; wherein the demand impact analysis result includes the demand status and impact level of the historical demand feature.

5. The method according to claim 1, characterized in that The method further comprises: For the historical demand features whose demand status is an affected status in the demand impact analysis result, and the impact level of the historical demand features, verifying the validity of the historical demand features; After the validity verification is passed, a new code feature is generated according to the demand information corresponding to the historical demand feature; and the new code feature is updated to the code repository.

6. The method according to claim 5, characterized in that The requirement information includes at least one of a requirement identifier, change content, and an impact function description.

7. A system management document generation device, characterized in that: The device comprises: An acquisition module, used for acquiring change features generated in the target system; wherein the change features include at least one of a change requirement feature and a change code feature; A tracing module, configured to perform an impact tracing process on the change feature according to a first association relationship between the demand feature and the code feature, and obtain a demand impact analysis result corresponding to the change feature; An updating module, configured to update the first association relationship according to the requirement impact analysis result to obtain an updated second association relationship between the requirement feature and the code feature; A generation module is used to generate a management document for the target system according to the second association relationship and the demand impact analysis result.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images