Matching system and matching method for software design and research and development and electronic equipment

Abstract

The invention provides a matching system and method for software design and research and development and electronic equipment. The system comprises a software design monitoring module which comprises a software design scheme, the software design scheme is graphically described and displayed, each first graph represents a function demand component in the software design scheme, and the first graphs comprise design related information of the function demand component; the software research and development monitoring module comprises a code set corresponding to a software design scheme, the code set is graphically described and displayed, each second graph represents a code package in the code set, and the second graphs comprise research and development related information of the code package; and the design research and development matching module is used for carrying out matching processing on each function demand component and the code package according to the consistency data between the design related information and the research and development related information to obtain a design research and development matching result. The problem that in the prior art, due to the fact that the software research and development and design matching degree is low, design expectation cannot be met easily is solved.

Description

Technical Field

[0001] The present application relates to the technical field of matching software design and development, and in particular to a matching system, matching method, computer-readable storage medium, and electronic device for software design and development. Background Art

[0002] Software design and development are two of the most important processes in the software implementation lifecycle. Generally speaking, during software development, developers and coders should strictly adhere to the detailed software design before implementing the code. Design must precede development; coding should never precede design, and there should be no mismatch between development and design.

[0003] Generally speaking, most software implementers complete the implementation of a system software according to the above rules. However, some people who are not clear about the software implementation process may not be able to implement it according to the software implementation R&D process. In addition, for complex software implementation requirements or large software systems, due to reasons such as time constraints and the complexity of the software itself, the final software implementation often cannot be achieved according to the standard process. At the same time, due to the complexity of the system itself, it is difficult for management and quality control personnel to check whether the software design and software development implementation match, and whether the software development implementation meets the software design requirements. This ultimately leads to a mismatch between software development units and software functional requirement components, resulting in the software implementation results not meeting the original requirements or design requirements.

[0004] The existing technology mainly includes single software design management or software R&D management and related quality monitoring devices generated based on software design and R&D. Therefore, the existing technology has the problem of low matching degree between software R&D and software design. Summary of the Invention

[0005] The main purpose of this application is to provide a matching system, matching method, computer-readable storage medium and electronic device for software design and development, so as to at least solve the problem in the prior art that the matching degree between software development and software design is low, which makes it difficult for the software to meet the design expectations.

[0006] To achieve the above-mentioned purpose, according to one aspect of the present application, a software design and R&D matching system is provided, including: a software design monitoring module, the software design monitoring module including multiple software design schemes, the software design schemes being graphically described and displayed in the software design monitoring module, each first graphic representing a functional requirement component in the software design scheme, the first graphic including design-related information of the functional requirement component, the design-related information including the meaning, input parameters and output parameters of the functional requirement component; a software R&D monitoring module, the software R&D monitoring module including a code set corresponding to each of the software design schemes, the code set being graphically described and displayed in the software R&D monitoring module, each second graphic representing a code package in the code set, the second graphic including R&D-related information of the code package, the R&D-related information including the type, meaning, input parameters and output parameters of the code package; a design and R&D matching module, the design and R&D matching module being used to match each of the functional requirement components and the code package based on consistency data between the design-related information and the R&D-related information to obtain a design and R&D matching result.

[0007] Optionally, the system also includes: a code processing module, used to package and process the code set through a program packaging service to generate a software executable package; an online module, used to launch the software executable package that meets the design requirements and R&D requirements; a rollback module, used to roll back the functional requirement components that do not meet the design requirements, and roll back the code package that does not meet the R&D requirements.

[0008] Optionally, the system further includes: a view display module, which is used to display the graphical contents of the software design monitoring module, the software R&D monitoring module and the design and R&D matching module.

[0009] Optionally, the system also includes: a status identification module, which is used to perform status identification processing on the design and development matching result based on the consistency data between the functional requirement component and the code package, wherein the status identification includes a design not developed identification, a design developed identification and a development not designed identification.

[0010] According to another aspect of the present application, a matching method for any one of the software design and development matching systems is provided, comprising: obtaining software design schemes in a software design monitoring module, and determining software to-be-developed schemes that need to be developed based on each of the software design schemes; sending each of the software to-be-developed schemes to a software development monitoring module to obtain a code set corresponding to the software to-be-developed scheme; and matching each of the software design schemes with each of the code sets based on consistency data between the design-related information and the development-related information.

[0011] Optionally, after matching each of the software design schemes with each of the code sets, the method further includes: obtaining quality scores for the software design scheme and the code set respectively; when the quality scores of the software design scheme and the code set are both greater than or equal to a score threshold, obtaining a program packaging service to package the code set and generate a software executable package; when the quality score of the software design scheme is less than the score threshold, rolling back the software design scheme; when the quality score of the code set is less than the score threshold, rolling back the code set.

[0012] Optionally, obtaining a program packaging service to package the code set and generate a software executable package includes: obtaining a program packaging service; building a JAVA container, and preprocessing the program packaging service in the JAVA container to obtain the preprocessed program packaging service, and using the preprocessed program packaging service to package the code set to generate the software executable package, wherein the preprocessing includes service tag processing, service compilation processing and service running processing.

[0013] Optionally, after matching each software design scheme with each code set based on the consistency data between each software design scheme and each code set, the method further includes: obtaining a matching result of the matching process between each software design scheme and each code set, and associating each software design scheme with each code set based on the matching result.

[0014] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the matching methods.

[0015] According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a method for executing any one of the matching methods.

[0016] Applying the technical solution of the present application, a software design monitoring module is provided, wherein the software design monitoring module includes multiple software design schemes, and the software design schemes are graphically described and displayed in the software design monitoring module, wherein each first graphic represents a functional requirement component in the software design scheme, and the first graphic includes design-related information of the functional requirement component, and the design-related information includes the meaning, input parameters and output parameters of the functional requirement component; a software R&D monitoring module is provided, wherein the software R&D monitoring module includes a code set corresponding to each of the software design schemes, and the code set is graphically described and displayed in the software R&D monitoring module, wherein each second graphic represents a code package in the code set, and the second graphic includes R&D-related information of the code package, and the R&D-related information includes the type, meaning, input parameters and output parameters of the code package; a design R&D matching module is provided, wherein the design R&D matching module is used to match each of the functional requirement components and the code package according to the consistency data between the design-related information and the R&D-related information to obtain a design R&D matching result. This significantly improves the efficiency and quality of software development. Through graphical display and consistency matching, developers can more intuitively understand design intent and reduce communication costs. At the same time, automated code packaging, quality scoring, and rollback mechanisms ensure that the entire software product process, from design to R&D to launch, is controllable, effectively avoiding rework caused by inconsistencies between design and R&D and improving team collaboration efficiency. Furthermore, the status identification function makes project progress clear at a glance, facilitating timely adjustments to development strategies and shortening time to market. This solves the problem of existing technologies with a low degree of matching between software R&D and software design, which makes it difficult for software to meet design expectations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings that constitute part of this application are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0018] Figure 1 A structural diagram of a matching system designed and developed according to an embodiment of the present application is shown;

[0019] Figure 2 A flowchart of a software design and development matching method provided in accordance with an embodiment of the present application is shown;

[0020] Figure 3 A flowchart of a matching method for specific software design and development provided in accordance with an embodiment of the present application is shown.

[0021] The above drawings include the following reference numerals:

[0022] 10. Software design monitoring module; 20. Software R&D monitoring module; 30. Design and R&D matching module. DETAILED DESCRIPTION

[0023] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] In order to enable those skilled in the art to better understand the present invention, 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, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] As introduced in the background technology, the existing technology has a low degree of matching between software development and software design, which makes it difficult for the software to meet the design expectations. In order to solve the problem that the existing technology has a low degree of matching between software development and software design, which makes it difficult for the software to meet the design expectations, the embodiments of the present application provide a matching system, matching method, computer-readable storage medium and electronic device for software design and development.

[0027] The technical solutions in the embodiments of the present invention will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present invention.

[0028] Figure 1This is a structural diagram of the matching system designed and developed according to the software embodiment of this application. Figure 1 As shown, the system includes:

[0029] A software design monitoring module, wherein the software design monitoring module includes multiple software design solutions, wherein the software design solutions are graphically described and displayed in the software design monitoring module, wherein each first graphic represents a functional requirement component in the software design solution, and the first graphic includes design-related information of the functional requirement component, wherein the design-related information includes the meaning, input parameters, and output parameters of the functional requirement component;

[0030] Specifically, software design solutions are described and displayed graphically. Each graphic represents a functional requirement component (design output), and design-related information, such as its meaning, entry and exit points, can be obtained from the graphic. Software design solutions are connected by one or more connecting lines, with a containment or hierarchical relationship from left to right.

[0031] a software development monitoring module, the software development monitoring module including a code set corresponding to each of the software design solutions, the code set being graphically depicted and displayed in the software development monitoring module, each second graphic representing a code package in the code set, the second graphic including development-related information for the code package, including the type, meaning, input parameters, and output parameters of the code package;

[0032] Specifically, code collections are described and displayed graphically. Each graphic represents a code package (R&D output). The graphic provides information about the R&D module, such as its type, meaning, input and output parameters. Code collections are connected by one or more connecting lines, with a containment or hierarchical relationship from left to right.

[0033] R&D personnel can carry out corresponding software development according to the software design plan. When associating software design plans, R&D personnel have the following optional association methods: "select first and then develop", "develop first and then select", and a mixed mode with both modes.

[0034] Graphically identifying each unit of the software design plan and code collection, and graphically linking, data-based display, and process-based processing of these units not only solves the drawbacks of previous design and development processes where documents were difficult to understand and communicate, but also solves the problem of difficulty in describing the relationship between each unit in documents.

[0035] The design and R&D matching module is used to match each of the above functional requirement components and the above code packages based on the consistency data between the above design related information and the above R&D related information to obtain a design and R&D matching result.

[0036] The consistency data between the above-mentioned design-related information and the above-mentioned R&D-related information includes a meaning consistency part, an input parameter consistency part and an output parameter consistency part between the design-related information and the R&D-related information.

[0037] Through this embodiment, a seamless connection between software design and R&D is achieved through graphical display and consistency matching. Specifically, the software design monitoring module and the software R&D monitoring module respectively present the design and R&D information in an intuitive graphical manner, which not only makes it easier for developers to understand complex design requirements, but also simplifies the communication process and reduces the possibility of information misunderstanding. The design and R&D matching module automatically identifies and matches functional requirement components and code packages by comparing the consistency data of the design and R&D information. This avoids the inefficiency and errors of manual matching and ensures the precise correspondence between design and implementation. For example, in an e-commerce software project, there may be a graphic representing a "shopping cart" in the design module, which describes its functional requirements in detail, such as adding products, modifying quantities, deleting products, etc.; there is also a "shopping cart" component implemented in code in the R&D module. Through the automatic identification and matching of the matching module, it can be ensured that the code accurately implements the design intent, thereby improving the efficiency and quality of software development. It solves the problem that the existing technology has a low degree of matching between software R&D and software design, which makes it difficult for the software to meet design expectations.

[0038] Optionally, the above system also includes: a code processing module, which is used to package and process the above code collection through a program packaging service to generate a software executable package; an online module, which is used to launch the above software executable package that meets the design requirements and R&D requirements; a rollback module, which is used to roll back the above functional requirement components that do not meet the above design requirements, and roll back the above code packages that do not meet the above R&D requirements.

[0039] This technical solution further optimizes the software development process and realizes full-cycle management from design to R&D and then to online launch. The code processing module uses the program packaging service to automatically build a JAVA container for preprocessing, including service tagging, compilation and service operation, and finally packages the code collection to generate a software executable package. This not only simplifies the deployment process, but also ensures the integrity of the code and the consistency of the operating environment. The online module and the rollback module are responsible for the release of the software and the rollback of the problem code respectively, ensuring the stability and reliability of the software product. For example, when a code package of a "user login" function fails to pass the verification of the matching module, the rollback module will roll it back to the R&D stage until the code package is completely consistent with the design requirements before it can be released through the online module, thereby avoiding software failures and reduced user experience caused by inconsistencies between design and R&D.

[0040] Optionally, the system further includes: a view display module, which is used to display the graphical contents of the software design monitoring module, the software R&D monitoring module and the design and R&D matching module.

[0041] The addition of the visual display module to this solution greatly improves the readability and comprehension of information, making the design and R&D status of the software development process clear at a glance. Through dynamic graphical display, team members can view the matching status of the software design plan and code collection in real time, promptly identifying and resolving inconsistencies. For example, in one project, the design and R&D teams can use the visual display module to monitor the design and implementation of the "payment function" in real time. If a mismatch between the design and code is discovered, such as inconsistent payment interface parameter types, adjustments can be made immediately, avoiding extensive rework later and improving development efficiency.

[0042] Optionally, the above system also includes: a status identification module, which is used to perform status identification processing on the above design and development matching results based on the consistency data between the above functional requirement component and the above code package, wherein the above status identification includes the design not developed identification, the design developed identification and the development not designed identification.

[0043] This solution's status identification module provides strong support for project management through clear status classification. The "design but not R&D" status indicates that the design is complete but has no corresponding code implementation yet. The "design but R&D" status indicates that the design and code are fully matched, and the "R&D but not design" status indicates that the code has been written but lacks design guidance. This status identification mechanism enables project managers to quickly identify development bottlenecks, rationally allocate resources, and ensure project progress. For example, in the development of an "order management" function, the status identification module can show which design requirements have been converted into code, which are still under development, and which codes lack design guidance, thereby helping the team adjust development strategies and accelerate product iteration.

[0044] Figure 2 Flowchart of the software design and development matching method according to the embodiment of the present application. Figure 2 As shown, the method includes the following steps:

[0045] Step S201: obtaining software design plans in the software design monitoring module, and determining software development plans that need to be developed based on the software design plans;

[0046] Step S202: Send each of the software to-be-developed solutions to a software development monitoring module to obtain a code set corresponding to the software to-be-developed solution;

[0047] Step S203 , matching each of the software design solutions with each of the code sets based on consistency data between the design-related information and the R&D-related information.

[0048] The matching method flow of this embodiment significantly improves the efficiency of software development through automated processing and intelligent matching. First, the software design monitoring module obtains and analyzes the software design plan to determine the specific functional requirements to be developed; then, these requirements are passed to the software development monitoring module in a graphical form, and the development team writes the code accordingly; finally, the design and development matching module automatically compares the design and code information, performs matching processing, and ensures that the design intent is accurately implemented. For example, when developing a "data analysis" function, the design team may need a data visualization chart. The matching method flow can ensure that the code written by the development team can generate a chart that is completely consistent with the design, thereby avoiding rework caused by deviations in the understanding of requirements and improving development efficiency. It solves the problem that the existing technology has a low degree of matching between software development and software design, which makes it difficult for the software to meet design expectations.

[0049] During the specific implementation process, after matching each of the above-mentioned software design schemes with each of the above-mentioned code sets, the above-mentioned method also includes: respectively obtaining quality scores for the above-mentioned software design schemes and the above-mentioned code sets; when the above-mentioned quality scores of the above-mentioned software design schemes and the above-mentioned code sets are both greater than or equal to the score threshold, obtaining a program packaging service to package the above-mentioned code sets and generate a software executable package; when the quality score of the above-mentioned software design scheme is less than the above-mentioned score threshold, rolling back the above-mentioned software design scheme; when the quality score of the above-mentioned code set is less than the above-mentioned score threshold, rolling back the above-mentioned code set.

[0050] This method ensures the high quality of software products through a quality scoring mechanism and rollback operations. After the matching process is completed, the system automatically evaluates the quality of the design and code. Only when both meet the preset standards will the program be packaged and released online. This avoids the release of low-quality code and improves software stability and user experience. For example, for a "user interface" design, if the scoring system finds that the user interaction logic in the design is unclear, or there is a performance bottleneck in the code implementation, the system will automatically perform a rollback operation and send the design or code back to the corresponding team for optimization until it meets the quality requirements. Only then can the subsequent process continue, thus ensuring the ultimate quality of the software product.

[0051] Specifically, obtaining a program packaging service to package the above-mentioned code set and generate a software executable package includes: obtaining a program packaging service; building a JAVA container, and preprocessing the above-mentioned program packaging service in the above-mentioned JAVA container to obtain the above-mentioned program packaging service that has passed the preprocessing, and using the above-mentioned program packaging service that has passed the preprocessing to package the above-mentioned code set to generate the above-mentioned software executable package, wherein the above-mentioned preprocessing includes service marking processing, service compilation processing and service running processing.

[0052] This method utilizes a program packaging service to achieve efficient code packaging and deployment. Specifically, by building a JAVA container, the system can automatically tag the service to ensure the correct identification of the code; then, code compilation is performed to convert the source code into an executable binary file; finally, the service runs pre-processing to test the code's running status, and after ensuring that it is correct, it is packaged to generate a software executable package. For example, in a JAVA-based "online education platform" project, the program packaging service can automatically identify and package all necessary code packages, including user management, course management, payment systems, etc., to form a complete software executable package, simplifying the deployment process and increasing the speed of software launch.

[0053] More specifically, after matching each of the above-mentioned software design schemes with each of the above-mentioned code sets based on the consistency data between each of the above-mentioned software design schemes and each of the above-mentioned code sets, the above-mentioned method also includes: obtaining the matching results of the matching processing of each of the above-mentioned software design schemes with each of the above-mentioned code sets, and associating each of the above-mentioned software design schemes with each of the above-mentioned code sets based on the above-mentioned matching results.

[0054] The application of this method's matching results builds a complete product development chain from design to R&D and launch, ensuring the coherence and consistency of software development. Through the matching results, the system automatically links design and code to form a clear development flow chart, which not only makes it easier for project managers to track development progress but also facilitates subsequent maintenance and upgrades.

[0055] In addition, this embodiment also includes an intelligent suggestion and optimization module, which further integrates artificial intelligence algorithms. Based on the matching between design and R&D, it can automatically identify inefficient or redundant code that may exist in the R&D unit and provide optimization suggestions to R&D personnel. For example, if the device identifies multiple slightly different methods for implementing the same function in the R&D unit, it can recommend the most efficient or simplest implementation through algorithm comparison, helping R&D personnel improve code, reduce duplication of work, and improve R&D efficiency.

[0056] In practice, the system parses the executable packages of each R&D unit, extracting the parameters, execution path, and performance metrics (such as execution time and memory usage) of each service, interface, or function. Combined with the functional description and expected performance in the design unit (software design plan), it uses a machine learning model to analyze the efficiency and necessity of each R&D unit (code collection). For R&D units with duplicated functionality or low efficiency, the device generates a detailed report listing possible code optimization suggestions and providing corresponding code snippets or links to relevant resources to help developers quickly understand and improve the code.

[0057] Through intelligent identification and optimization suggestions, this embodiment enables software development units to be more efficient and refined, helping to improve overall software performance and reduce resource consumption. It also avoids unnecessary coding and repetitive work, reducing software development costs and shortening the development cycle.

[0058] This embodiment also includes a multi-dimensional quality assessment and prediction module, which not only assesses the consistency and quality of current software design and development units but also predicts the impact of future software changes on overall quality based on historical data. This prediction module builds a predictive model by analyzing historical software change records, bug fix frequency, user feedback, and usage data to provide decision makers with quality risk predictions during the software design and development phase.

[0059] In practice, when design units are matched with R&D units, the evaluation and prediction module checks whether each R&D unit meets the design requirements and scores them based on pre-set quality rules (such as coding standards, performance indicators, and security requirements). Furthermore, by inputting the current software architecture, inter-module dependencies, and expected user behavior into the prediction model, the module can predict quality issues that may be encountered in future software updates, providing forward-looking guidance to the R&D team.

[0060] This embodiment predicts potential future quality issues, enabling R&D teams to optimize in advance and reduce errors and maintenance costs after the software is launched. Furthermore, based on the predictions from data and models, management and quality control personnel can make more scientific and reasonable decisions, improving the overall management of software projects.

[0061] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the software design and development matching method of the present application will be described in detail below with reference to specific embodiments.

[0062] This embodiment involves a specific matching method for software design and development. This embodiment implements the backend program through JAVA language, uses VUE as the front-end implementation language, and uses graphics as a display method. The program includes a design unit, a research and development unit, a dynamic matching unit, processing logic, etc. The design unit module contains two submodules, namely a large software design unit based on modeling and a small software design unit based on business customization; the research and development unit module is mainly for the generation and analysis of research and development; the dynamic matching unit mainly includes service matching, internal interface matching and function matching, etc.; the processing logic completes the closed-loop processing flow in design and development. Figure 3 Specifically, it includes the following contents:

[0063] Step S1: Designers conduct software design. The design types are divided into modeling and customization, and there are also two corresponding units.

[0064] Step S2: R&D personnel use this device to carry out corresponding software development according to the design unit. The R&D includes code development, asset costs, etc.

[0065] Step S3: R&D personnel complete the final functional development, including service, interface, function and other type units.

[0066] Step S4: The R&D personnel use the device to generate an executable package. If the executable package does not need to be improved, it is an online package and cannot be tampered with at will.

[0067] Step S5: The device parses the executable package, matches it according to the identifier, name, etc. in the development process, and associates the design unit with the development unit.

[0068] Step S6: The device matches the design and R&D units and generates comparison marks with consistency and inconsistency to facilitate subsequent management.

[0069] Step S7: The device uses front-end rendering technology to realize a complete design-R&D view structure according to the consistency comparison mark and the like.

[0070] Step S8: Technical personnel, management personnel, and quality personnel can directly view the consistency of the design unit and the R&D unit through the view, and can perform corresponding process management such as improvement.

[0071] The core of this embodiment is to perform graphic virtual processing on the design outputs / units in the system (marked with gray modules of various shapes). The sources of design outputs are modeling and customization, that is, they are generated by external modeling or manually added directly in the device by the designer. After the design outputs are marked with gray graphics of various shapes in the device, the designer completes his work. The R&D personnel conduct actual R&D based on the design outputs (marked with graphics) as described above, and uniquely match the design outputs with the R&D outputs. The R&D outputs are then directly generated into an executable package in the device and run directly. If they meet the original design goals, they are completed. If they do not meet the goals, the R&D personnel will continue to improve them.

[0072] The following describes the technical implementation method based on the software implementation process:

[0073] The technical implementation method includes eight technical and operational points:

[0074] 1. Description, relationship and display of design units.

[0075] 2. R&D personnel conduct research and development according to the design unit identification.

[0076] 3. Description, relationship and presentation of R&D units.

[0077] 4. The device generates executable package processing.

[0078] 5. Device parsing and executable package processing.

[0079] 6. Device matching design and R&D unit.

[0080] 7. Rendering design-R&D view.

[0081] 8. Handling of inconsistencies between design and R&D units.

[0082] The following is a detailed description of the above eight technical and operational points:

[0083] 1. Description, relationship and display of design units:

[0084] 1) Design units are described and displayed graphically. Each graphic represents a design output. Design-related information, such as its meaning, entry and exit, can be obtained from the graphic.

[0085] 2) Design units are connected by one or more connecting lines, which are inclusion or superior-subordinate relationships from left to right.

[0086] 2. R&D personnel conduct research and development according to the design unit logo:

[0087] 1) R&D personnel carry out corresponding software development according to the design unit.

[0088] 2) When R&D personnel associate design units, the optional association methods include "select first, then develop", "develop first, then select", and a mixed mode that includes both modes.

[0089] 3. Description, relationship and display of R&D units:

[0090] 1) The R&D unit is described and displayed graphically. Each graphic represents an R&D output. Relevant information about the R&D module, such as its type, meaning, input parameters, and output parameters, can be obtained from the graphic.

[0091] 2) R&D units are connected by one or more connecting lines, which are inclusive or superior-subordinate relationships from left to right.

[0092] 4. The device generates an executable package for processing:

[0093] 1) After completing the corresponding software development, R&D personnel can select one or more services for direct packaging.

[0094] 2) The device builds a JAVA container, and marks, compiles, and runs the selected services correctly, completing the packaging to generate an executable package.

[0095] 5. Device parsing and executable package processing:

[0096] 1) The device obtains all top-level services and service-related information in the executable package based on the information of the service tag.

[0097] 2) The device obtains information such as sub-services, interfaces and functions contained in the service in the executable package by traversing.

[0098] 6. Device matching design and R&D unit:

[0099] 1) The device obtains all design unit information.

[0100] 2) The device obtains information of all R&D units.

[0101] 3) The device is trained in rotation according to the aforementioned identification to obtain consistent data from all design and R&D units.

[0102] 4) The device specially marks the consistency data, including three states: "not implemented in design", "implemented in design" and "implemented but not designed".

[0103] 7. Rendering Design-R&D View:

[0104] 1) The front end renders based on design data, R&D data, and matching information.

[0105] 2) The front end uses the design unit as a benchmark to synchronously render the basic information, inclusion, and superior-subordinate relationship information of the design module.

[0106] 8. Handling of inconsistencies between the design and R&D units:

[0107] Design and R&D units can be directly viewed through views.

[0108] Operations personnel can identify inconsistencies.

[0109] Management and quality personnel can return inconsistent modules to design or R&D personnel for confirmation or further design and development.

[0110] After confirmation or processing by the design or R&D personnel, the process will be returned to the management and quality personnel.

[0111] The operation package can be exported and put online only after confirmation by management and quality personnel.

[0112] This embodiment graphically identifies each design unit and R&D unit, and graphically associates, digitally displays, and processes these units in a process-based manner. This not only solves the drawbacks of previous design and R&D processes where documents were difficult to understand and communicate, but also solves the problem of difficulty in describing the relationship between each unit in documents.

[0113] This embodiment strongly associates the design unit and the R&D unit by identification and serial connection, so that the R&D output and the design output are matched, solving the problem of frequent inconsistencies between software design and actual software implementation in previous software implementation processes, thereby greatly improving the quality of software development. In addition, this method is simple, has no threshold, and does not require code verification or other methods.

[0114] The device of this embodiment uses the idea and specific implementation of strong association between the executable package and the design and development unit, which can not only enable management and quality personnel to perform quality control and enhance the quality inspection capability when the software is put online, but also prevent R&D personnel from illegally tampering with the executable package, and reduce various hidden dangers caused by long-term inconsistencies in software design and development.

[0115] The device of this embodiment uses a graphically marked "inconsistency" closed-loop processing flow method to dynamically match and monitor executable packages in real time, so that management personnel and quality personnel can monitor in real time the inconsistency between R&D output and target design during the software design and development process, and conduct pre-emptive control of software implementation quality.

[0116] Compared with the prior art, this embodiment has the following advantages:

[0117] 1. Compared with the previous manual design and development matching monitoring method, this device can solve the problem of mismatch between software design and software development by dynamically matching software design units and software development units.

[0118] 2. Solve the problem of inconsistency between software development results and design goals by supporting the improvement of software development units. Currently, there is no systematic and visual solution to solve this problem.

[0119] 3. Through graphical and intuitive display methods, R&D personnel can have a clearer understanding of R&D goals, and managers and quality personnel can directly obtain the differences between design and R&D units.

[0120] 4. The device displays software design and R&D outputs in three corresponding modes: "design implemented", "design not implemented" and "implemented but not designed", solving the problem of inconsistencies between design and R&D that was difficult to detect in the past. These three states are normal in the software development process, and problems often exist, but there is currently no effective visualization solution or specific digital comparison method.

[0121] An embodiment of the present invention provides a computer-readable storage medium, which includes a stored program, wherein when the program is run, the device where the computer-readable storage medium is located is controlled to execute the matching method of software design and development.

[0122] An embodiment of the present invention provides a processor, which is used to run a program, wherein the matching method of software design and development is executed when the program is running.

[0123] An embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, at least the steps of the above-mentioned software design and development matching method are implemented.

[0124] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0125] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes at least the steps of the matching method of the above-mentioned software design and development.

[0126] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, can be centralized on a single computing device, or can be distributed across a network of multiple computing devices. They can be implemented using program code executable by the computing device, and thus, can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described herein can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0127] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0128] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0129] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0130] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0131] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0132] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0133] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0134] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0135] The above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A matching system for software design and development, characterized in that: include: a software design monitoring module, the software design monitoring module including a plurality of software design solutions, wherein the software design solutions are graphically described and displayed in the software design monitoring module, wherein each first graphic represents a functional requirement component in the software design solution, and the first graphic includes design-related information of the functional requirement component, wherein the design-related information includes the meaning, input parameters, and output parameters of the functional requirement component; a software development monitoring module, the software development monitoring module including a code set corresponding to each of the software design solutions, the code set being graphically depicted and displayed in the software development monitoring module, each second graphic representing a code package in the code set, the second graphic including development-related information for the code package, the development-related information including the type, meaning, input parameters, and output parameters of the code package; A design and development matching module is used to match each functional requirement component and the code package according to the consistency data between the design related information and the development related information to obtain a design and development matching result.

2. The software design and development matching system according to claim 1, characterized in that: The system further comprises: A code processing module, configured to package the code set through a program packaging service to generate a software executable package; An online module, used to launch the software executable package that meets the design requirements and R&D requirements; The rollback module is used to roll back the functional requirement components that do not meet the design requirements, and to roll back the code packages that do not meet the R&D requirements.

3. The software design and development matching system according to claim 1, characterized in that: The system further comprises: A view display module is used to display the graphical contents of the software design monitoring module, the software R&D monitoring module and the design R&D matching module.

4. The software design and development matching system according to claim 1, characterized in that: The system further comprises: A status identification module is used to perform status identification processing on the design and development matching result according to the consistency data between the functional requirement component and the code package, wherein the status identification includes a design not developed identification, a design developed identification and a development not designed identification.

5. A matching method for a matching system for software design and development according to any one of claims 1 to 4, characterized in that: include: Obtain the software design plans in the software design monitoring module, and determine the software to be developed plans that need to be developed based on each of the software design plans; Sending each of the software to-be-developed solutions to a software development monitoring module to obtain a code set corresponding to the software to-be-developed solution; According to the consistency data between the design-related information and the R&D-related information, each software design solution is matched with each code set.

6. The method according to claim 5, characterized in that After matching each of the software design solutions with each of the code sets, the method further includes: Obtaining quality scores for the software design solution and the code set respectively; If the quality scores of the software design solution and the code set are both greater than or equal to a score threshold, obtaining a program packaging service to package the code set to generate a software executable package; If the quality score of the software design solution is less than the score threshold, rolling back the software design solution; When the quality score of the code set is less than the score threshold, the code set is rolled back.

7. The method according to claim 6, characterized in that Obtaining a program packaging service to package the code set to generate a software executable package includes: Get program packaging services; Construct a JAVA container, and preprocess the program packaging service in the JAVA container to obtain the preprocessed program packaging service, and use the preprocessed program packaging service to package the code set to generate the software executable package, wherein the preprocessing includes service marking processing, service compilation processing and service running processing.

8. The method according to claim 5, characterized in that After matching each software design solution with each code set based on the consistency data between each software design solution and each code set, the method further includes: A matching result of each software design solution and each code set is obtained, and each software design solution is associated with each code set according to the matching result.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the matching method according to any one of claims 5 to 8.

10. An electronic device, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include instructions for executing the matching method described in any one of claims 5 to 8.

Images