A software development platform development method and system

Abstract

The present invention discloses a development method and system for a software development platform, which relates to the field of software development technology. When the system is running, it extracts change records from a code base, analyzes relevant parameters in the code change in detail, and forms a code change set ΔC. The dependency module further constructs and updates a dependency graph G in real time to accurately display the dependencies within the code. The impact analysis module uses the dependency graph G to calculate the impact range of the code change, evaluates the impact of the change on referenced objects and subclasses, and generates a change impact index I. direc t is matched with the preset code impact assessment threshold D, and a code change impact assessment strategy plan is formulated. The feedback response module updates the data and dependency graph G according to the plan content and notifies developers of relevant changes, reducing the risk of human errors and omissions. It can timely evaluate and respond to the potential impact of code changes and ensure the stability and consistency of the code base.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a development method and system for a software development platform. Background Art

[0002] In the field of software engineering, with the development of technology and the increase in demand, software development platforms have become an indispensable and important component. Specifically, software development platforms are designed to provide a series of tools and services to support various stages of the software development life cycle, including requirements analysis, design, coding, testing, deployment and maintenance. In these platforms, automated testing and code quality management are two key quality inspection links. By writing and executing automated test cases, code quality can be improved and system stability can be ensured.

[0003] Currently, many software development platforms suffer from significant shortcomings when managing code changes. First, existing change management systems often rely on developer experience and manual analysis, resulting in inefficiency and error-proneness. Second, while some tools can provide basic dependency analysis, they often fail to update and accurately identify all affected modules in real time. This is particularly true in large, complex projects. Due to the lack of effective impact analysis models, developers may overlook key dependencies, leading to unexpected systemic issues caused by code changes. Furthermore, existing systems rarely consider the impact of code changes on subclasses and referenced objects, further limiting their effectiveness in practical applications. Furthermore, code changes that fail to consider the impact on subclasses and referenced objects can trigger broader systemic issues, impacting the stability and progress of the entire project. This lack of accurate and real-time impact analysis capabilities severely impacts the efficiency and quality of the software development process. Summary of the Invention

[0004] In view of the deficiencies in the prior art, the present invention provides a method and system for developing a software development platform, which solves the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention is implemented through the following technical solutions: a development system for a software development platform, comprising an acquisition module, a dependency module, an impact analysis module, and a feedback response module;

[0006] The acquisition module collects code change records in the code library, including newly added, modified, and deleted codes, and simultaneously extracts parameters related to function, class, method, constant, and object names in the changed codes. It obtains code difference information through statistics and analysis to form a code change set ΔC;

[0007] The dependency module analyzes the dependencies in the code according to the code change set ΔC, constructs a dependency graph G, and updates the dependency graph G in real time according to the code change record;

[0008] The impact analysis module calculates the impact range of the code change based on the dependency graph G, including the impact on the referenced objects and subclasses, and obtains the change impact index I of the code change unit. direct , and at the same time match it with the preset code impact assessment threshold D to obtain the code change impact assessment strategy solution;

[0009] The feedback response module is specifically executed according to the content of the code change impact assessment strategy, including updating data, updating the dependency graph G, and prompting and notifying developers.

[0010] Preferably, the acquisition module includes a trigger unit and an extraction unit;

[0011] The trigger unit triggers the collection operation when the code in the code library is changed, and collects the code change records in the collection code library, including newly added, modified and deleted codes, and uses Git and SVN to manage, record and trigger code changes;

[0012] The extraction unit simultaneously extracts parameters related to functions, classes, methods, constants and object names in the changed code to form a parameter change set P diff , synchronous statistics and analysis to obtain code difference information to obtain the changed version of the code set C new and older versions of Code Set C old , constituting the code change set ΔC.

[0013] Preferably, the code difference information includes newly added codes, modified codes, deleted codes and parameter changes;

[0014] The newly added code includes new classes, new methods, new constants, and new object names;

[0015] The modified code includes modified classes, modified methods, modified constants, and modified object names;

[0016] The deleted code includes deleted classes, deleted methods, deleted constants, and deleted object names;

[0017] Parameter changes include changed function parameters, changed class members, changed constant values, and changed object references.

[0018] Preferably, the dependency module includes a dependency analysis unit and a dependency update unit;

[0019] The dependency analysis unit analyzes the dependencies in the code according to the code change set ΔC, including the dependencies between classes, methods, and object references, represents the extracted dependencies in the form of a dependency graph and a dependency tree, and constructs a dependency graph G, including code unit nodes and dependency edge sets between code units, wherein the code unit nodes include class, method, constant, and object names;

[0020] Among them, code analysis includes using JavaParser code parser and Clang code parser to parse the code and extract dependencies, including class dependencies, method calls, inheritance relationships, interface implementations, member variables, constant references, instantiations, and parameter passing.

[0021] Preferably, the dependency updating unit detects changes in the dependency graph, obtains a dependency change record set ΔE, marks a set of code units with code changes, and updates the dependency graph G in real time according to the code change records.

[0022] Preferably, the impact analysis module includes an impact calculation unit and an evaluation strategy unit;

[0023] The impact calculation unit calculates the impact range of the code change according to the dependency graph G, including the impact on the referenced objects and subclasses, and obtains the change impact index I of the code change unit. direct .

[0024] Preferably, the assessment strategy unit matches preset relevant information with the required comparison value, including matching with a preset code impact assessment threshold D, to obtain a code change impact assessment strategy solution.

[0025] Preferably, the code change impact assessment strategy is obtained by the following matching method:

[0026] When the change impact index I direct <Code impact assessment threshold D: Get the risk-free impact assessment result of the code change, and do not prompt or notify the code change developer;

[0027] When the change impact index I direct ≥Code impact assessment threshold D, obtain the code change impact risk assessment results, and prompt and notify the code change developer;

[0028] When the change impact index I direct When the code impact assessment threshold D is ≥ twice, the code change impact warning assessment results are obtained, and warning prompts and warning notifications are issued to the code change developer, and the developer is marked at the same time.

[0029] Preferably, the feedback response module is specifically executed according to the content of the code change impact assessment strategy, including updating data, updating the dependency graph G and prompting and notifying the developer;

[0030] Wherein, updating the dependency graph G includes modifying, adding and deleting dependency relationships. The dependency relationship specifically includes class A increasing its dependency on class C, and updating the dependency graph G to add a dependency edge (A, C);

[0031] Prompt notification to developers includes notifying relevant developers of the code change impact assessment strategy plan content in real time, prompting the impact of the change that needs to be handled, and recording the developer's handling results and change processing status.

[0032] A method for developing a software development platform comprises the following steps:

[0033] Step 1: The acquisition module collects code change records in the code base, including newly added, modified, and deleted code, and simultaneously extracts parameters related to function, class, method, constant, and object names in the changed code. Through statistics and analysis, it obtains code difference information and forms a code change set ΔC;

[0034] Step 2: The dependency module analyzes the dependencies in the code based on the code change set ΔC, constructs a dependency graph G, and updates the dependency graph G in real time based on the code change records;

[0035] Step 3: The impact analysis module calculates the impact scope of the code change based on the dependency graph G, including the impact on referenced objects and subclasses, and obtains the change impact index I of the code change unit. direct , and at the same time match it with the preset code impact assessment threshold D to obtain the code change impact assessment strategy solution;

[0036] Step 4: The feedback response module performs specific actions based on the code change impact assessment strategy, including updating data, updating the dependency graph G, and notifying developers.

[0037] The present invention provides a method and system for developing a software development platform, which has the following beneficial effects:

[0038] (1) When the system is running, the acquisition module can automatically extract the change records in the code base, analyze the relevant parameters such as function, class, method, constant and object name in the code change in detail, and form the code change set ΔC. The dependency module further constructs and updates the dependency graph G in real time to accurately display the dependency relationship within the code. The impact analysis module uses the dependency graph G to calculate the impact range of the code change, evaluate the impact of the change on the referenced objects and subclasses, and generate the change impact index I direct and matches it with the preset code impact assessment threshold D to formulate a code change impact assessment strategy. The feedback response module promptly updates data and the dependency graph G based on the assessment strategy and notifies developers of relevant changes. This significantly improves the accuracy and efficiency of code changes, reduces the risk of human error and missed changes, and promptly assesses and responds to the potential impact of code changes, ensuring the stability and consistency of the codebase. Compared to traditional manual management and assessment methods, this better meets the efficiency and reliability requirements of modern software development, significantly resolving the problems of dependency disorder and uncontrollable change impacts caused by code changes in traditional development processes.

[0039] (2) The trigger unit automatically starts the collection operation when the code base changes, is compatible with version control tools such as Git and SVN, and records the code changes that are added, modified, and deleted. The extraction unit further extracts the relevant parameters such as function, class, method, constant, and object names in the changed code to form a parameter change set P diff , and statistically analyze the new version code set C new and older versions of Code Set C old , forming a complete code change set, through detailed code difference information, including accurate records of additions, modifications, deletions and parameter changes, it is possible to capture and analyze the impact of code changes in a timely manner.

[0040] (3) By obtaining the code change impact assessment strategy, accurate dependency analysis and risk assessment of code changes are achieved. The dependency module uses JavaParser and Clang code parsers to build and update the dependency graph G in real time, and through the dependency analysis unit and dependency update unit, it comprehensively captures the dependency changes between code units. The impact analysis module calculates the change impact index I of the code change unit. direct , and matches it with the preset code impact assessment threshold D to generate a corresponding change impact assessment strategy plan. The multi-level risk assessment and notification mechanism not only solves the unforeseen risk problems caused by complex dependencies in traditional code change management, but also greatly reduces the possibility of errors and system failures caused by changes, and improves the security and reliability of the software development process. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of a development system block diagram of a software development platform of the present invention;

[0042] Figure 2 The present invention is a schematic diagram of the steps of a development method of a software development platform. DETAILED DESCRIPTION

[0043] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0044] Example 1

[0045] The present invention provides a software development platform development system, please refer to Figure 1 , including acquisition module, dependency module, impact analysis module and feedback response module;

[0046] The acquisition module collects code change records in the code library, including newly added, modified, and deleted codes, and simultaneously extracts parameters related to function, class, method, constant, and object names in the changed codes. It obtains code difference information through statistics and analysis to form a code change set ΔC;

[0047] The dependency module analyzes the dependencies in the code according to the code change set ΔC, constructs a dependency graph G, and updates the dependency graph G in real time according to the code change record;

[0048] The impact analysis module calculates the impact range of the code change based on the dependency graph G, including the impact on the referenced objects and subclasses, and obtains the change impact index I of the code change unit. direct , and at the same time match it with the preset code impact assessment threshold D to obtain the code change impact assessment strategy solution;

[0049] The feedback response module is specifically executed according to the content of the code change impact assessment strategy, including updating data, updating the dependency graph G, and prompting and notifying developers.

[0050] In this embodiment, the acquisition module can automatically extract the change records in the code base, analyze the relevant parameters such as function, class, method, constant and object names in the code changes in detail, and form a code change set ΔC. The dependency module further constructs and updates the dependency graph G in real time to accurately display the dependencies within the code. The impact analysis module uses the dependency graph G to calculate the impact range of the code change, evaluate the impact of the change on the referenced objects and subclasses, and generate the change impact index I direct and matches it with the preset code impact assessment threshold D to formulate a code change impact assessment strategy. The feedback response module promptly updates data and the dependency graph G based on the assessment strategy and notifies developers of relevant changes. This significantly improves the accuracy and efficiency of code changes, reduces the risk of human error and missed changes, and promptly assesses and responds to the potential impact of code changes, ensuring the stability and consistency of the codebase. Compared to traditional manual management and assessment methods, this better meets the efficiency and reliability requirements of modern software development, significantly resolving the problems of dependency disorder and uncontrollable change impacts caused by code changes in traditional development processes.

[0051] Example 2

[0052] This embodiment is explained in Example 1, please refer to Figure 1 ,Specifically: the acquisition module includes a trigger unit and an extraction unit;

[0053] The trigger unit triggers the collection operation when the code in the code library is changed, and collects the code change records in the collection code library, including newly added, modified and deleted codes, and uses Git and SVN to manage, record and trigger code changes;

[0054] The extraction unit simultaneously extracts parameters related to functions, classes, methods, constants and object names in the changed code to form a parameter change set P diff , synchronous statistics and analysis to obtain code difference information to obtain the changed version of the code set C new and older versions of Code Set C old , constituting the code change set ΔC.

[0055] The code difference information includes newly added codes, modified codes, deleted codes and parameter changes;

[0056] The newly added code includes new classes, new methods, new constants, and new object names;

[0057] The modified code includes modified classes, modified methods, modified constants, and modified object names;

[0058] The deleted code includes deleted classes, deleted methods, deleted constants, and deleted object names;

[0059] Parameter changes include changed function parameters, changed class members, changed constant values, and changed object references;

[0060] Among them, the parameter change set P diff Extracted by the following formula:

[0061] P diff={p i p i ∈P new \P old};

[0062] Where, P diff Represents a parameter change set, P i Parameters that represent parameter changes, including function, class, method, constant, and object names, P new Represents the parameter set in the updated version, P old Represents a parameter set from an older version.

[0063] In this embodiment, the trigger unit automatically starts the collection operation when the code base changes, is compatible with version control tools such as Git and SVN, and records the code changes that are added, modified, and deleted. The extraction unit further extracts relevant parameters such as function, class, method, constant, and object names in the changed code to form a parameter change set P diff , and statistically analyze the new version code set C new and older versions of Code Set C old , forming a complete code change set, through detailed code difference information, including accurate records of additions, modifications, deletions and parameter changes, it is possible to capture and analyze the impact of code changes in a timely manner.

[0064] Example 3

[0065] This embodiment is explained in Example 2, please refer to Figure 1 ,Specifically: the dependency module includes a dependency analysis unit and a dependency update unit;

[0066] The dependency analysis unit analyzes the dependencies in the code based on the code change set ΔC, including dependencies between classes, methods, and object references, and expresses the extracted dependencies in the form of a dependency graph and a dependency tree, thereby constructing a dependency graph G:

[0067] G=(V,E);

[0068] Where G represents the dependency graph, V represents the code unit set, specifically indicating that the code unit nodes include class, method, constant and object names, and E represents the dependency set, specifically indicating the dependency relationship between the code units in the dependency edge set.

[0069] Among them, code analysis includes using JavaParser code parser and Clang code parser to parse the code and extract dependencies, including class dependencies, method calls, inheritance relationships, interface implementations, member variables, constant references, instantiations, and parameter passing.

[0070] The dependency update unit detects changes in the dependency graph, obtains a dependency change record set ΔE, marks a set of code units with code changes, and updates the dependency graph G in real time according to the code change records;

[0071] Among them, the changes in the detection dependency graph are detected by the following formula:

[0072] ΔE=E new \E old ;

[0073] Where ΔE represents the dependency change record set, E new Represents the set of dependencies in the changed version, E old Represents a collection of dependencies from an older version.

[0074] The impact analysis module includes an impact calculation unit and an evaluation strategy unit;

[0075] The impact calculation unit calculates the impact range of the code change according to the dependency graph G, including the impact on the referenced objects and subclasses, and obtains the change impact index I of the code change unit. direct ;

[0076] The evaluation strategy unit matches the preset relevant information with the required comparison value, including matching with the preset code impact evaluation threshold D, to obtain a code change impact evaluation strategy solution.

[0077] Among them, the change impact index I of the code change unit direct Obtained through the following calculation formula:

[0078]

[0079] Where, I direct (u i ) represents the code unit u i Direct change impact index I direct , N ( ui ) indicates the code unit u i The set of code units that have direct dependencies, included in the dependency graph G, with the code unit u i Directly related code unit node, w(ui,uj) represents code unit u i and u j The dependency weight value between them, uj represents the code unit node that has a direct dependency relationship with the code unit ui, R(u j ) represents the code unit u i risk level.

[0080] The code change impact assessment strategy is obtained through the following matching methods:

[0081] When the change impact index I direct <Code impact assessment threshold D: Get the risk-free impact assessment result of the code change, and do not prompt or notify the code change developer;

[0082] When the change impact index I direct ≥ Code impact assessment threshold D: Obtain code change impact risk assessment results and provide prompts and notifications to code change developers. The notifications include the change type, change content, impact scope, and recommended measures. Recommended measures include: code review, unit testing, and dependency checking.

[0083] When the change impact index I direct When the code impact assessment threshold D is ≥ twice, the code change impact warning assessment results are obtained, and warning prompts and warning notifications are issued to the code change developers. At the same time, the developers are marked, fully tested, and management is notified, and tracking and recording are carried out;

[0084] In this embodiment, accurate dependency analysis and risk assessment of code changes are achieved by obtaining a code change impact assessment strategy. The dependency module uses JavaParser and Clang code parsers to build and update the dependency graph G in real time, and comprehensively captures the dependency changes between code units through the dependency analysis unit and the dependency update unit. The impact analysis module calculates the change impact index I of the code change unit. direct , and matches it with the preset code impact assessment threshold D to generate a corresponding change impact assessment strategy plan. The multi-level risk assessment and notification mechanism not only solves the unforeseen risk problems caused by complex dependencies in traditional code change management, but also greatly reduces the possibility of errors and system failures caused by changes, and improves the security and reliability of the software development process.

[0085] Example 4

[0086] This embodiment is explained in Example 3, please refer to Figure 1 ,Specifically: the feedback response module is specifically executed according to the content of the code change impact assessment ,strategy scheme, including updating data, updating the dependency graph G, and ,notifying the developer;

[0087] Wherein, updating the dependency graph G includes modifying, adding and deleting dependency relationships. The dependency relationship specifically includes class A increasing its dependency on class C, and updating the dependency graph G to add a dependency edge (A, C);

[0088] Add dependency: For example, if class A increases its dependency on class C, a new dependency edge (A, C) is added to the dependency graph G;

[0089] Modify dependencies: Modify existing dependencies, such as when method calls change, and update the properties of the dependency edge:

[0090] G = (V, E∪{A, C});

[0091] Delete dependencies: Remove dependencies that no longer exist. For example, if a class or method is deleted, remove the corresponding dependency edge:

[0092] G = (V,,-{(B,,)});

[0093] Notifying developers includes: notifying relevant developers in real time via email and internal application software communication tools;

[0094] The notification content includes the change type, specific content of the change, the content of the code change impact assessment strategy, and the specific content and recommended measures that need to be handled;

[0095] Synchronously record processing results: After the developer processes the change, the feedback response module will record the developer's processing results and change processing status for subsequent tracking and review;

[0096] Prompt notification to developers includes notifying relevant developers of the code change impact assessment strategy plan content in real time, prompting the impact of the change that needs to be handled, and recording the developer's handling results and change processing status.

[0097] This embodiment enables comprehensive management of code change impacts and real-time feedback. When updating the dependency graph G, the feedback response module can precisely modify, add, and delete dependencies, such as adding a dependency edge from class A to class C, ensuring that the dependency graph G always reflects the latest code dependency status. Simultaneously, the code change impact assessment strategy is notified to relevant developers in real time, indicating the impact of the changes that require resolution, and recording the developer's handling results and change processing status.

[0098] Example 5

[0099] A method for developing a software development platform, please refer to Figure 2 , specifically: including the following steps:

[0100] Step 1: The acquisition module collects code change records in the code base, including newly added, modified, and deleted code, and simultaneously extracts parameters related to function, class, method, constant, and object names in the changed code. Through statistics and analysis, it obtains code difference information and forms a code change set ΔC;

[0101] Step 2: The dependency module analyzes the dependencies in the code based on the code change set ΔC, constructs a dependency graph G, and updates the dependency graph G in real time based on the code change records;

[0102] Step 3: The impact analysis module calculates the impact scope of the code change based on the dependency graph G, including the impact on referenced objects and subclasses, and obtains the change impact index I of the code change unit. direct , and at the same time match it with the preset code impact assessment threshold D to obtain the code change impact assessment strategy solution;

[0103] Step 4: The feedback response module performs specific actions based on the code change impact assessment strategy, including updating data, updating the dependency graph G, and notifying developers.

[0104] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A development system for a software development platform, characterized by: It includes acquisition module, dependency module, impact analysis module and feedback response module; The acquisition module collects code change records in the code library, including newly added, modified, and deleted codes, and simultaneously extracts parameters related to function, class, method, constant, and object names in the changed codes. It obtains code difference information through statistics and analysis to form a code change set ΔC; The dependency module analyzes the dependencies in the code according to the code change set ΔC, constructs a dependency graph G, and updates the dependency graph G in real time according to the code change record; The impact analysis module calculates the impact scope of the code change based on the dependency graph G, including the impact on referenced objects and subclasses, obtains the change impact index Idirect of the code change unit, and matches it with the preset code impact assessment threshold D to obtain the code change impact assessment strategy solution; The impact analysis module includes an impact calculation unit and an evaluation strategy unit; the impact calculation unit calculates the impact range of the code change based on the dependency graph G, including the impact on referenced objects and subclasses, and obtains the change impact index Idirect of the code change unit; the evaluation strategy unit matches the required comparison value with the preset relevant information, including matching with the preset code impact evaluation threshold D, to obtain the code change impact evaluation strategy solution; The code change impact assessment strategy is obtained through the following matching methods: When the change impact index Idirect is less than the code impact assessment threshold D, the code change impact no-risk assessment result is obtained, and no prompt or notification is given to the code change developer; When the change impact index Idirect ≥ the code impact assessment threshold D, the code change impact risk assessment results are obtained and the code change developer is prompted and notified; When the change impact index Idirect ≥ twice the code impact assessment threshold D, obtain the code change impact warning assessment results, issue warning prompts and warning notifications to the code change developer, and mark the developer at the same time; The feedback response module is specifically executed according to the content of the code change impact assessment strategy, including updating data, updating the dependency graph G, and prompting and notifying developers.

2. A software development platform development system according to claim 1, characterized in that: The acquisition module includes a trigger unit and an extraction unit; The trigger unit triggers the collection operation when the code in the code library is changed, and collects the code change records in the collection code library, including newly added, modified and deleted codes, and uses Git and SVN to manage, record and trigger code changes; The extraction unit synchronously extracts parameters related to functions, classes, methods, constants and object names in the changed code to form a parameter change set Pdiff, and synchronously collects statistics and analyzes the code difference information to obtain the changed version code set Cnew and the old version code set Cold to form a code change set ΔC.

3. A software development platform development system according to claim 2, characterized in that: in, Code difference information includes newly added codes, modified codes, deleted codes, and parameter changes; The newly added code includes new classes, new methods, new constants, and new object names; The modified code includes modified classes, modified methods, modified constants, and modified object names; The deleted code includes deleted classes, deleted methods, deleted constants, and deleted object names; Parameter changes include changed function parameters, changed class members, changed constant values, and changed object references.

4. The software development platform development system according to claim 1, wherein: The dependency module includes a dependency analysis unit and a dependency update unit; The dependency analysis unit analyzes the dependencies in the code according to the code change set ΔC, including the dependencies between classes, methods, and object references, represents the extracted dependencies in the form of a dependency graph and a dependency tree, and constructs a dependency graph G, including code unit nodes and dependency edge sets between code units, wherein the code unit nodes include class, method, constant, and object names; Among them, code analysis includes using JavaParser code parser and Clang code parser to parse the code and extract dependencies, including class dependencies, method calls, inheritance relationships, interface implementations, member variables, constant references, instantiations, and parameter passing.

5. A software development platform development system according to claim 4, characterized in that: The dependency update unit detects changes in the dependency graph, obtains a dependency change record set ΔE, marks a set of code units with code changes, and updates the dependency graph G in real time according to the code change records.

6. A software development platform development system according to claim 1, characterized in that: The feedback response module is used to perform specific execution according to the content of the code change impact assessment strategy, including updating data, updating the dependency graph G, and prompting and notifying developers; Wherein, updating the dependency graph G includes modifying, adding and deleting dependency relationships. The dependency relationship specifically includes class A increasing its dependency on class C, and updating the dependency graph G to add a dependency edge (A, C); Prompt notification to developers includes notifying relevant developers of the code change impact assessment strategy plan content in real time, prompting the impact of the change that needs to be handled, and recording the developer's handling results and change processing status.

7. A method for developing a software development platform, applied to a development system for a software development platform according to any one of claims 1 to 6, characterized in that: The following steps are involved: Step 1: The acquisition module collects code change records in the code base, including newly added, modified, and deleted code, and simultaneously extracts parameters related to function, class, method, constant, and object names in the changed code. Through statistics and analysis, it obtains code difference information and forms a code change set ΔC; Step 2: The dependency module analyzes the dependencies in the code based on the code change set ΔC, constructs a dependency graph G, and updates the dependency graph G in real time based on the code change records; Step 3: The impact analysis module calculates the impact scope of the code change based on the dependency graph G, including the impact on referenced objects and subclasses, obtains the change impact index Idirect of the code change unit, and matches it with the preset code impact assessment threshold D to obtain the code change impact assessment strategy solution; Step 4: The feedback response module performs specific actions based on the code change impact assessment strategy, including updating data, updating the dependency graph G, and notifying developers.

Images