Full-life-cycle management method, device and system for engineering machinery industry product software

Abstract

The invention discloses a full-life-cycle management method, device and system for engineering machinery industry product software, and the method comprises the steps: generating a software research and development demand list based on a received original software demand; performing software design, software development and software testing in sequence based on the software research and development demand list to generate a first software product, and a first testing scheme and a first software material number corresponding to the first software product; generating a change demand list based on the received software change demand; and based on the change demand list, the first software product and the first test scheme, performing software design, software development and software test in sequence to generate a second software product, and a second test scheme and a second software material number corresponding to the second software product. The whole process systematic management of product software from demand receiving to software quit can be realized.

Description

Technical Field

[0001] This invention belongs to the field of product software management technology, specifically relating to a method, device, and system for full lifecycle management of product software in the engineering machinery industry. Background Technology

[0002] With the deep integration of the "Industrial Internet" and construction machinery manufacturing, the industry is ushering in a wave of industrial upgrading centered on intelligent and unmanned operations. In this process, product software has become a key factor determining overall machine performance, differentiated competitiveness, and user experience. "Software-defined construction machinery" is profoundly influencing the industry's technological development path and business model innovation. Faced with the new situation of continuously increasing software functional complexity, accelerating iteration speed, and increasingly sophisticated requirements for collaboration with hardware systems, the traditional project management-centric software development model is proving inadequate, and there is an urgent need to establish a systematic, standardized, and full-process software lifecycle management method.

[0003] The construction machinery industry currently faces numerous challenges in software management. The software development process lacks unified standards, with incomplete documentation and missing quality gates at each stage, from requirements analysis to testing and verification. This results in poor visibility, weak control, and difficulty in traceability. Insufficient collaboration mechanisms between hardware and software development lead to delays in information transmission between hardware design changes and software requirement updates, extending development cycles and increasing the difficulty of system integration. Simultaneously, low software asset reuse rates and insufficient knowledge accumulation are prominent issues. Code, documentation, and solutions from various projects are managed in a fragmented manner, making it difficult to establish an effective technology accumulation and reuse system at the enterprise level. During software maintenance, inadequate management mechanisms often result in difficulties in problem localization and chaotic version management, leading to high maintenance costs that directly impact customer satisfaction and product market competitiveness.

[0004] These problems severely restrict the improvement of software development efficiency and product quality, hindering the full realization of software's potential as a product value center and profit growth point. Therefore, building a comprehensive management system covering the entire process from requirements gathering, design, development, testing, installation, market maintenance, to software decommissioning is particularly important. This system aims to achieve process standardization, process quantification, asset collaboration, and management security, ensuring effective connection and full controllability of each stage of software development through the establishment of unified management standards and collaboration mechanisms.

[0005] Establishing a comprehensive lifecycle management system is of significant strategic importance for promoting the "high-end, intelligent, and green" development of the construction machinery industry. It not only significantly improves software delivery efficiency and product reliability but also strengthens enterprises' core competitiveness and continuous innovation capabilities in the field of intelligent equipment. With the deepening of the industry's digital transformation, this management system will also provide a solid foundation for enterprises' technological evolution, knowledge accumulation, and value creation, ultimately injecting continuous momentum into the transformation and upgrading of the entire construction machinery industry.

[0006] In the field of product software development, construction machinery companies typically follow a waterfall development process with clearly defined phases. This process is strictly divided into three main phases: requirements analysis, design and development, and testing and verification. The requirements analysis phase is responsible for collecting and analyzing requirements; the design and development phase sequentially involves software architecture design, detailed design, coding implementation, and unit testing; and the testing and verification phase includes integration testing, system testing, and user acceptance testing. Each phase is executed sequentially, emphasizing the entry and exit criteria for each phase.

[0007] In the construction machinery industry, product development is primarily led and driven by personnel from the product development domain. Other functional domains, such as software, hardware, testing, quality, and service, intervene at pre-defined project milestones to provide phased support or cooperation. Software delivery is marked by successful testing and verification, after which the software is handed over to the product department or customer, and the R&D team's primary responsibilities conclude.

[0008] In the traditional product development model of the construction machinery industry, the software function usually plays a subordinate and supporting role in the entire process. This model is product development domain-led, and the software team often passively undertakes the requirements and functional specifications defined by the product domain, and needs to carry out corresponding work in accordance with the rhythm and milestones of hardware development.

[0009] Within an enterprise, software development processes are primarily defined and formalized in the form of documents for project teams to reference and implement. The management focus of the R&D process is concentrated on core deliverables of the development phase, such as code and test cases, with the product's delivery serving as the endpoint of project completion.

[0010] Project management primarily relies on offline, manual communication. Throughout the development process, project status tracking, risk coordination, and decision-making are mainly conducted through regular meetings, progress reports, and other offline communication methods. The software development process is not integrated and visualized within a unified digital platform; the breakdown and execution of specific tasks heavily depend on the individual experience and capabilities of the project manager or technical lead.

[0011] Under the existing technological system, the following problems may arise:

[0012] (1) The feedback loop is slow, and software requirements often lag behind hardware development. Moreover, the requirements are not communicated in a timely manner and are not clearly described, resulting in a mismatch between software and hardware. Because continuous feedback cannot be obtained during the development process, problems can only be exposed in the later stages, and the cost of correction is high, making it difficult to respond quickly to market changes.

[0013] (2) Fragmented lifecycle management, lacking proactive planning and value operation. Existing management basically ends after version release, turning into a reactive firefighting mode that only receives faults. Online operation and maintenance, user behavior analysis, new requirement discovery and other activities are scattered and disordered, making it difficult to make accurate decisions on product iteration or termination of maintenance, thus hindering the continuous value-added of software.

[0014] (3) Lack of asset management leads to waste and rising costs. When hardware products or old software are withdrawn from the market, their associated software assets (such as code libraries, testing environments, and data) are not systematically archived and cleaned up, resulting in a large number of outdated resources being idle for a long time, ineffectively occupying storage resources, and generating unnecessary maintenance costs.

[0015] (4) The R&D process relies heavily on offline documents and lacks a dedicated system to solidify, visualize and drive the lifecycle process. Team collaboration is highly dependent on manual communication and personal experience, resulting in coarse-grained R&D activities, inconsistent task decomposition, and opaque execution process, making it difficult to achieve standardized, reusable and efficient engineering management.

[0016] (5) Lack of artifact management and security traceability capabilities, and absence of a unified software asset management mechanism. Software deliverables are mainly stored in the form of source code and build artifacts, lacking full-chain, standardized management and security control of artifacts. The version, dependency relationship and transfer process of artifacts are difficult to trace accurately, which not only poses security and compliance risks, but also hinders the reuse of software assets. Summary of the Invention

[0017] To address the aforementioned issues, this invention proposes a method, device, and system for full lifecycle management of product software in the engineering machinery industry, which enables systematic management of the entire process of product software management, from demand reception to software delisting.

[0018] To achieve the above-mentioned technical objectives and effects, the present invention is implemented through the following technical solution:

[0019] In a first aspect, this invention provides a method for full lifecycle management of product software in the engineering machinery industry, applied to an ALM platform, comprising:

[0020] Based on the received original software requirements, a software development requirements list is generated;

[0021] Based on the software development requirements list, software design, software development and software testing are carried out in sequence to generate a first software artifact, as well as a first test plan and a first software material number corresponding to the first software artifact;

[0022] Based on the received software change requests, generate a list of software change requests;

[0023] Based on the software change requirement list, the first software artifact, and the first test plan, software design, software development, and software testing are carried out in sequence to generate the second software artifact, as well as the second test plan and the second software material number corresponding to the second software artifact.

[0024] In conjunction with the first aspect, optionally, the method for generating the software development requirements list includes:

[0025] Receive the original software requirements from the requester and automatically generate a unique and traceable original requirement ID for the original software requirements;

[0026] Receive the initial software development requirement list obtained by the software system engineer from analyzing the original software requirements, and automatically generate a unique and traceable development requirement ID for each software development requirement in the initial software development requirement list.

[0027] The system receives the review results from the initial software development requirements list entered by software system engineers, performs baseline processing on the initial software development requirements list that has passed the review, and obtains the final software development requirements list.

[0028] In conjunction with the first aspect, optionally, the method for generating the software change requirement list includes:

[0029] Receive software change requests from software system engineers at different stages of the software lifecycle, and automatically generate a unique and traceable software change request ID for each request.

[0030] The software system engineer receives and analyzes the software change requirements to obtain an initial list of software change requirements, and automatically generates a unique and traceable development requirement ID for each software development requirement in the initial list of software change requirements.

[0031] The system receives the review results from the initial software change requirement list entered by the software system engineer, performs baseline processing on the initial software change requirement list that has passed the review, and obtains the final software change requirement list.

[0032] In conjunction with the first aspect, optionally, the software design, software development, and software testing include:

[0033] The system receives the approved software design specifications entered by the software system engineer, as well as the review comments and modification records generated during the review process of the software design specifications. The software design specifications are obtained by conducting software design based on the final software development requirements list or the final software change requirements list.

[0034] When applying for a software material number, if the software design specification is obtained based on the final software development requirements list, then the software material number is the first software material number; if the software design specification is obtained based on the final software change requirements list, then the software material number is the second software material number.

[0035] Receive software code written by software development engineers based on the approved software design specification, store it in the code library, and forcibly associate the software code with the corresponding R&D requirement ID;

[0036] The software code in the code library is processed by the built-in pipeline to generate software artifacts, realizing the correlation and traceability between software code, software development requirements and software artifacts;

[0037] The system receives test plans designed by software test engineers based on the approved software design specifications. These test plans include test planning and test cases, and the test cases are forcibly associated with corresponding development requirement IDs.

[0038] Receive the test results obtained by software test engineers based on the test plan and software artifacts, and generate a software defect list based on the test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and development requirement IDs.

[0039] Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID;

[0040] The software code in the codebase is processed through a built-in pipeline to generate new software artifacts;

[0041] In response to the signal that the new software artifact has passed regression testing and review in sequence, the new software artifact is designated as either the first software artifact or the second software artifact.

[0042] In conjunction with the first aspect, the full lifecycle management method may optionally further include:

[0043] The first or second software artifact is filled into the prototype for use by software test engineers to conduct software prototype testing.

[0044] Receive the software prototype test results obtained by the software test engineer, and generate a defect list based on the software prototype test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and R&D requirement IDs.

[0045] Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID;

[0046] The software code in the codebase is processed through a built-in pipeline to generate new software artifacts;

[0047] In response to the signal that the new software artifact has passed regression testing and review in sequence, if there is no small-batch production stage, the software artifact is released and bound to a software part number; if there is a small-batch production stage, the software artifact is output for small-batch production testing.

[0048] In conjunction with the first aspect, the full lifecycle management method may optionally further include:

[0049] Receive the small-batch production test results obtained by the software test engineer, and generate a defect list based on the software prototype test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and R&D requirement IDs.

[0050] Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID;

[0051] The software code in the codebase is processed through a built-in pipeline to generate new software artifacts;

[0052] In response to the signal that the new software artifact has passed regression testing and review in sequence, the new software artifact is delivered.

[0053] In conjunction with the first aspect, optionally, the delivery of the new software artifact includes:

[0054] Package the new software artifacts, along with their corresponding software design specifications and test plans, to generate delivery materials.

[0055] Receive data from software system engineers to generate a delivery review report for the packaged delivery materials;

[0056] Archive the delivered materials and delivery review report.

[0057] Secondly, this invention provides a lifecycle management device for product software in the engineering machinery industry, applied to an ALM platform, comprising:

[0058] The software development requirements list generation module is used to generate a software development requirements list based on the received original software requirements.

[0059] The software development requirements management module is used to sequentially perform software design, software development and software testing based on the software development requirements list, and generate a first software artifact, as well as a first test plan and a first software material number corresponding to the first software artifact;

[0060] The software change request list generation module is used to generate a software change request list based on the received software change requests.

[0061] The software change requirement management module is used to sequentially perform software design, software development, and software testing based on the software change requirement list, the first software artifact, and the first test plan, to generate a second software artifact, as well as a second test plan and a second software material number corresponding to the second artifact.

[0062] Thirdly, the present invention provides a full lifecycle management system for product software in the construction machinery industry, including an ALM platform, a quality management platform, a manufacturing execution platform, and a product data management platform;

[0063] The ALM platform is configured to perform the method according to any one of claims 1-7;

[0064] The quality management platform, manufacturing execution platform, and product data management platform are respectively connected to the ALM platform and receive software artifacts issued by the ALM platform.

[0065] Fourthly, this invention provides a full lifecycle management system for product software in the engineering machinery industry, including a storage medium and a processor;

[0066] The storage medium is used to store instructions;

[0067] The processor is configured to operate according to the instructions to perform the method according to any one of the first aspects.

[0068] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0069] This invention establishes a unified full lifecycle management method, device, and system, which standardizes and visualizes product software R&D activities, effectively improves the overall capabilities of enterprises in software development, production management, and quality control, and provides systematic support for the digitalization and intelligentization of complex equipment manufacturing fields such as engineering machinery.

[0070] Specifically, this invention addresses the problems of fragmented lifecycle management, insufficient hardware and software collaboration, untraceable R&D processes, and non-standardized product management in existing technologies. It constructs a unified management system that integrates demand, design, development, testing, filling, and market withdrawal, offering the following significant advantages:

[0071] This invention effectively connects the various stages of software requirements management, design, development, testing, mass production, delivery, and delisting through the ALM platform, avoiding the problems of information fragmentation and repetitive data entry in the traditional model. It ensures the efficient flow of core R&D assets such as requirements, design, and code within a unified platform, and significantly improves R&D collaboration efficiency and project transparency.

[0072] This invention enables information integration between the ALM system and other systems such as QMS (Quality Management System), MES (Manufacturing Execution System), and PDM (Product Data Management), achieving synchronous linkage between software and hardware design data. When hardware design changes, software requirement updates and verifications can be triggered in real time, avoiding rework and mismatches caused by information lag, thereby significantly shortening the development cycle and improving the efficiency of integrated software and hardware R&D.

[0073] This invention establishes quality gates at each stage, linking test results, defect closure, code inspection reports, etc., to project progress to ensure that phased outputs meet quality standards. The system can automatically generate quality assessment and trend analysis reports, improving the measurability and quality controllability of the R&D process.

[0074] This invention establishes a full-chain management mechanism for software artifacts within the ALM system. The entire process of artifact generation, testing, release, packaging, and decommissioning is recorded, enabling bidirectional traceability from the source of requirements to the software artifact. By introducing verification mechanisms and version dependency tracking, it ensures that the artifact's origin is traceable, the process is controllable, and responsibility is accountable, effectively meeting compliance audit requirements in areas such as functional safety and information security.

[0075] This invention introduces artificial intelligence technology into the software delivery and archiving phase, intelligently mining data generated during the development process, such as design documents, code, test cases, and defect analyses, to extract reusable components and general solutions, forming a structured knowledge base. Through cross-project reuse and experience accumulation, it reduces redundant development and enhances the value of enterprise R&D assets.

[0076] This invention not only focuses on the R&D and production stages, but also integrates operational data, user feedback, and maintenance records to achieve continuous improvement of product software and support for product delisting decisions. The system can provide enterprises with decision-making support based on lifecycle data, promoting the transformation of software products from one-time delivery to continuous value operation and enhancing product competitiveness. Attached Figure Description

[0077] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein:

[0078] Figure 1 This is a flowchart illustrating a method for full lifecycle management of product software in the machinery industry according to an embodiment of the present invention.

[0079] Figure 2 This is a schematic diagram of a full lifecycle management system according to an embodiment of the invention. Detailed Implementation

[0080] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0081] Furthermore, if the embodiments of this invention involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed by this invention.

[0082] Example 1

[0083] This invention provides a method for full lifecycle management of product software in the construction machinery industry, applied to an ALM platform, comprising the following steps:

[0084] (1) Generate a software development requirements list based on the received original software requirements;

[0085] (2) Based on the software development requirements list, software design, software development and software testing are carried out in sequence to generate a first software artifact, as well as a first test plan and a first software material number corresponding to the first software artifact;

[0086] (3) Generate a list of change requirements based on the received software change requests;

[0087] (4) Based on the change requirement list, the first software artifact, and the first test plan, software design, software development, and software testing are carried out in sequence to generate the second software artifact, as well as the second test plan and the second software material number corresponding to the second artifact.

[0088] In one specific embodiment of the present invention, the method for generating the software development requirements list includes:

[0089] Receive the original software requirements from the requester and automatically generate a corresponding traceable original requirement ID for the original software requirements;

[0090] Receive the initial software development requirement list obtained by the software system engineer from analyzing the original software requirements, and automatically generate a unique and traceable development requirement ID for each software development requirement in the initial software development requirement list.

[0091] The system receives the review results from the initial software development requirements list entered by software system engineers, performs baseline processing on the initial software development requirements list that has passed the review, and obtains the final software development requirements list.

[0092] In one specific embodiment of the present invention, the method for generating the software change requirement list includes:

[0093] Receive software change requests from software system engineers at different stages of the software lifecycle, and automatically generate corresponding traceable software change request IDs for the software change requests.

[0094] The software system engineer receives and analyzes the software change requirements to obtain an initial list of software change requirements, and automatically generates a unique and traceable development requirement ID for each software development requirement in the initial list of software change requirements.

[0095] The system receives the review results from the initial software change requirement list entered by the software system engineer, performs baseline processing on the initial software change requirement list that has passed the review, and obtains the final software change requirement list.

[0096] In one specific embodiment of the present invention, the step of performing software design, software development, and software testing includes:

[0097] The system receives the approved software design specifications entered by the software system engineer, as well as the review comments and modification records generated during the review process of the software design specifications. The software design specifications are obtained by conducting software design based on the final software development requirements list or the final software change requirements list.

[0098] When applying for a software material number, if the software design specification is obtained based on the final software development requirements list, then the software material number is the first software material number; if the software design specification is obtained based on the final software change requirements list, then the software material number is the second software material number.

[0099] Receive software code written by software development engineers based on the approved software design specification, store it in the code library, and forcibly associate the software code with the corresponding R&D requirement ID;

[0100] The software code in the code library is processed by the built-in pipeline to generate software artifacts, enabling the traceability of the association between software code, software requirements, and software artifacts.

[0101] The system receives test plans designed by software test engineers based on the approved software design specifications. These test plans include test planning and test cases, and the test cases are forcibly associated with corresponding development requirement IDs.

[0102] Receive the test results obtained by software test engineers based on the test plan and software artifacts, and generate a software defect list based on the test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and development requirement IDs.

[0103] Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID;

[0104] The software code in the codebase is processed through a built-in pipeline to generate new software artifacts;

[0105] In response to the signal that the new software artifact has passed regression testing and review in sequence, the new software artifact is designated as either the first software artifact or the second software artifact.

[0106] In one specific embodiment of the present invention, the full lifecycle management method further includes:

[0107] The first or second software artifact is filled into the prototype for use by software test engineers to conduct software prototype testing.

[0108] Receive the software prototype test results obtained by the software test engineer, and generate a defect list based on the software prototype test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and R&D requirement IDs.

[0109] Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID;

[0110] The software code in the codebase is processed through a built-in pipeline to generate new software artifacts;

[0111] In response to the signal that the new software artifact has passed regression testing and review in sequence, if there is no small-batch production stage, the software artifact is released and bound to a software part number; if there is a small-batch production stage, the software artifact is output for small-batch production testing.

[0112] In one specific embodiment of the present invention, the full lifecycle management method further includes:

[0113] Receive the small-batch production test results obtained by the software test engineer, and generate a defect list based on the software prototype test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and R&D requirement IDs.

[0114] Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID;

[0115] The software code in the codebase is processed through a built-in pipeline to generate new software artifacts;

[0116] In response to the signal that the new software artifact has passed regression testing and review in sequence, the new software artifact is delivered.

[0117] In one specific embodiment of the present invention, the delivery of the new software artifact includes:

[0118] Package the new software artifacts, along with their corresponding software design specifications and test plans, to generate delivery materials.

[0119] Receive data from software system engineers to generate a delivery review report for the packaged delivery materials;

[0120] Archive the delivered materials and delivery review report.

[0121] The following is combined Figure 1 The present invention provides a detailed description of a specific implementation method for the full lifecycle management of software for engineering machinery industry products.

[0122] like Figure 1 As shown, the full lifecycle management method for product software in the engineering machinery industry according to this embodiment of the invention includes stages such as software requirements management, software design, software development, software prototype testing, small-batch production, software delivery, and software lifecycle management. Each stage is connected and controlled through an integrated ALM platform. See details. Figure 1 Product software development management process.

[0123] Step (1) Software Requirements Management Phase, specifically includes the following steps:

[0124] Step 1: The requester enters the original software requirements into the ALM platform. The ALM platform automatically generates a unique and traceable original requirement ID for the original software requirements. The ALM platform receives the initial software development requirement list obtained by the software system engineer through analysis of the original software requirements. The ALM platform synchronously records the entire process operation log of the requirements, realizing traceability of the source data of the requirements.

[0125] Step 2: The software systems engineer organizes the software development team and the requester to review the initial software development requirements list. After the review is passed, the initial software development requirements list is baselined on the ALM platform to obtain the final software development requirements list. The baselined requirements can only be modified after review, ensuring the controllability and traceability of requirement changes.

[0126] Step (2) Software design phase, specifically includes:

[0127] Step 1: The software system engineer conducts software design based on the baselined software development requirements list and obtains the software design specification.

[0128] Step 2: The software system engineer organizes the software development team to conduct an online review of the software design specification, obtains the reviewed software design specification, and enters the reviewed software design specification, review comments and modification records into the ALM platform for automatic archiving.

[0129] Step 3: The software system engineer fills in the software material attribute application software material number in the software material management module of the ALM platform, builds the software BOM, and obtains the software BOM structure.

[0130] Step (3) Software development phase, specifically includes:

[0131] Step 1: The software system engineer assigns tasks to the software development engineer and software testing engineer based on the reviewed software design specification.

[0132] Step 2: The software development engineer starts writing code according to the received task, and performs static checks and unit tests on the written code. The software code that passes the self-test of the software development engineer is sent to the code repository in the ALM platform. When entering the code repository, the corresponding R&D requirement ID is forcibly associated. The software artifact is generated online from the software code in the code repository through the built-in pipeline of the ALM platform, realizing the association and traceability between software code, software requirements and software artifacts.

[0133] Step 3: Based on the received tasks and baselined software development requirements, the software test engineer designs test cases on the ALM platform (mandatory association of requirement ID numbers when designing test cases) and sets up the test environment. The engineer also organizes and conducts test plan reviews, archives review comments and modification records on the platform, and obtains the test plan.

[0134] Step 4: Software test engineers conduct software testing based on the test plan and the software artifacts obtained in Step 2. Based on the test results, they enter defect information on the ALM platform. The ALM platform automatically associates each test defect with a unique defect ID, as well as test cases and development requirement IDs, to achieve traceability of defect information and test cases.

[0135] Step 5: The software development engineer fixes the software defects according to the software defect list. After the fix is ​​completed, the software code is merged into the code repository in the ALM platform (the defect ID and development requirement ID are associated when merging). After the software artifact is generated, it is handed over to the software test engineer for regression testing.

[0136] Step 6: After the regression test passes, conduct a software development review. If the product does not have a prototype or small-batch production stage after the review, proceed with development and release, release the software artifact, bind it to the software part number, and archive it to the ALM platform. If the product has a prototype or small-batch production stage, output the software artifact for prototype and small-batch production testing.

[0137] Step (4) Software prototype testing phase, specifically includes:

[0138] Step 1: The software artifact obtained in step (3) is filled into the prototype. The software test engineer conducts software prototype testing, obtains a defect list and enters it into the ALM platform. When entering the list, the test cases and R&D requirement IDs are associated.

[0139] Step 2: The software development engineer writes software code that can fix the software defects based on the software defect list, stores it in the code library of the ALM platform, and forcibly associates the software code with the defect ID and the development requirement ID; the software code in the code library is processed by the built-in pipeline of the ALM platform to generate new software artifacts, which are then handed over to the software test engineer for regression testing.

[0140] Step 3: The software test engineer conducts regression testing based on the new software artifact. After the regression test is passed, the software prototype test review is conducted. If the product does not have a small-batch production stage after the review is passed, the prototype is released, the software artifact is released and bound to the software part number. If the product has a small-batch production stage, the software artifact is output for small-batch production testing.

[0141] Step (5) Software small-batch production stage, specifically includes:

[0142] Step 1: The software test engineer conducts small-batch production testing of the software artifacts obtained in (4), obtains a defect list, and enters the defect information and associates the corresponding test cases and requirement IDs through the ALM platform.

[0143] Step 2: The software development engineer writes software code that can fix the software defects based on the software defect list, stores it in the code library of the ALM platform, and forcibly associates the software code with the defect ID and the development requirement ID; the software code in the code library is processed by the built-in pipeline of the ALM platform to generate new software artifacts, which are then handed over to the software test engineer for regression testing.

[0144] Step 3: The software test engineer conducts regression testing based on the new software artifact. After the regression test is passed, the software is reviewed for small-batch production. After the review is passed, the software artifact is released and bound to the software part number, providing a traceable source of the artifact for production and filling.

[0145] Step (6) Software delivery phase, specifically includes:

[0146] Step 1: The software development engineer prepares the delivery materials, including software artifacts, software design specifications, test plans, etc.

[0147] Step 2: The software systems engineer organizes the software development team to review the delivery materials and outputs a software delivery review report.

[0148] Step 3: The software system engineer archives the delivery materials and software delivery review report to the ALM platform to achieve full traceability and verification of the software development process.

[0149] Step (7) manages the software lifecycle phases, specifically including:

[0150] Step 1: The software system engineer collects the software change requirements at each stage of the software lifecycle and enters them into the ALM platform. At the same time, a unique and traceable software change requirement ID is automatically generated for each software change requirement. The software system engineer analyzes the software change requirements on the ALM platform to obtain an initial list of software change requirements.

[0151] Step 2: Baseline the initial change requirement list that has passed the review to obtain the final software change requirement list, and then close the loop on the software change requirements by referring to steps (2) to (6) above.

[0152] As can be seen, the software lifecycle management method in this embodiment of the invention spans multiple stages, including marketing, R&D, production, and service. The ALM system, as the core hub of software lifecycle management, collaborates with downstream systems such as QMS, MES, and PDM to support production quality control and product data management. Project information and requirements are disseminated within the project management system, while the ALM platform handles software-related requirements and manages software requirements. Upon receiving software requirements, the software development team conducts requirements analysis, software design, development activities, and testing activities on the ALM system. After software release, software assets are archived on the ALM platform. Based on the software part number applied for on the ALM platform, the corresponding software artifacts are distributed to QMS, PDM, and MES.

[0153] Example 2

[0154] Based on the same inventive concept as Embodiment 1, this invention provides a full lifecycle management device for product software in the engineering machinery industry, applied to an ALM platform, comprising:

[0155] The software development requirements list generation module is used to generate a software development requirements list based on the received original software requirements.

[0156] The software development requirements management module is used to sequentially perform software design, software development and software testing based on the software development requirements list, and generate a first software artifact, as well as a first test plan and a first software material number corresponding to the first software artifact;

[0157] The software change request list generation module is used to generate a software change request list based on the received software change requests.

[0158] The software change requirement management module is used to sequentially perform software design, software development, and software testing based on the software change requirement list, the first software artifact, and the first test plan, to generate a second software artifact, as well as a second test plan and a second software material number corresponding to the second artifact.

[0159] The specific functions of each module described above are explained in the relevant content of the method in Embodiment 1, and will not be repeated here.

[0160] Example 3

[0161] This invention provides a full lifecycle management system for product software in the construction machinery industry, such as... Figure 2 As shown, it includes an ALM platform, a quality management platform, a manufacturing execution platform, and a product data management platform;

[0162] The ALM platform is configured to perform the method described in any one of Embodiment 1;

[0163] The quality management platform, manufacturing execution platform, and product data management platform are respectively connected to the ALM platform and receive software artifacts issued by the ALM platform.

[0164] Example 4

[0165] This invention provides a full lifecycle management system for product software in the engineering machinery industry, including a storage medium and a processor;

[0166] The storage medium is used to store instructions;

[0167] The processor is configured to operate according to the instructions to execute the method according to any one of Embodiment 1.

[0168] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0169] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0170] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0171] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0172] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

[0173] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A method for full lifecycle management of product software in the engineering machinery industry, characterized in that, Applied to the ALM platform, including: Based on the received original software requirements, a software development requirements list is generated; Based on the software development requirements list, software design, software development and software testing are carried out in sequence to generate a first software artifact, as well as a first test plan and a first software material number corresponding to the first software artifact; Based on the received software change requests, generate a list of software change requests; Based on the software change requirement list, the first software artifact, and the first test plan, software design, software development, and software testing are carried out in sequence to generate the second software artifact, as well as the second test plan and the second software material number corresponding to the second software artifact.

2. The method for full lifecycle management of product software in the engineering machinery industry according to claim 1, characterized in that: The method for generating the software development requirements list includes: Receive the original software requirements from the requester and automatically generate a unique and traceable original requirement ID for the original software requirements; Receive the initial software development requirement list obtained by the software system engineer from analyzing the original software requirements, and automatically generate a unique and traceable development requirement ID for each software development requirement in the initial software development requirement list. The system receives the review results from the initial software development requirements list entered by software system engineers, performs baseline processing on the initial software development requirements list that has passed the review, and obtains the final software development requirements list.

3. The method for full lifecycle management of product software in the engineering machinery industry according to claim 1, characterized in that, The method for generating the software change request list includes: Receive software change requests from software system engineers at different stages of the software lifecycle, and automatically generate a unique and traceable software change request ID for each request. The software system engineer receives and analyzes the software change requirements to obtain an initial list of software change requirements, and automatically generates a unique and traceable development requirement ID for each software development requirement in the initial list of software change requirements. The system receives the review results from the initial software change requirement list entered by the software system engineer, performs baseline processing on the initial software change requirement list that has passed the review, and obtains the final software change requirement list.

4. A method for full lifecycle management of product software in the engineering machinery industry according to claim 2 or 3, characterized in that: The aforementioned software design, software development, and software testing include: The system receives the approved software design specifications entered by the software system engineer, as well as the review comments and modification records generated during the review process of the software design specifications. The software design specifications are obtained by conducting software design based on the final software development requirements list or the final software change requirements list. When applying for a software material number, if the software design specification is obtained based on the final software development requirements list, then the software material number is the first software material number; if the software design specification is obtained based on the final software change requirements list, then the software material number is the second software material number. Receive software code written by software development engineers based on the approved software design specification, store it in the code library, and forcibly associate the software code with the corresponding R&D requirement ID; The software code in the code library is processed by the built-in pipeline to generate software artifacts, realizing the correlation and traceability between software code, software development requirements and software artifacts; The system receives test plans designed by software test engineers based on the approved software design specifications. These test plans include test planning and test cases, and the test cases are forcibly associated with corresponding development requirement IDs. Receive the test results obtained by software test engineers based on the test plan and software artifacts, and generate a software defect list based on the test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and development requirement IDs. Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID; The software code in the codebase is processed through a built-in pipeline to generate new software artifacts; In response to the signal that the new software artifact has passed regression testing and review in sequence, the new software artifact is designated as either the first software artifact or the second software artifact.

5. The method for full lifecycle management of product software in the engineering machinery industry according to claim 4, characterized in that: The full lifecycle management method also includes: The first or second software artifact is filled into the prototype for use by software test engineers to conduct software prototype testing. Receive the software prototype test results obtained by the software test engineer, and generate a defect list based on the software prototype test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and R&D requirement IDs. Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID; The software code in the codebase is processed through a built-in pipeline to generate new software artifacts; In response to the signal that the new software artifact has passed regression testing and review in sequence, if there is no small-batch production stage, the software artifact is released and bound to a software part number; if there is a small-batch production stage, the software artifact is output for small-batch production testing.

6. The method for full lifecycle management of product software in the engineering machinery industry according to claim 5, characterized in that: The full lifecycle management method also includes: Receive the small-batch production test results obtained by the software test engineer, and generate a defect list based on the software prototype test results. The software defect list includes several test defects, each of which is forcibly associated with a unique defect ID, as well as test cases and R&D requirement IDs. Receive software code written by software development engineers based on the software defect list that can fix software defects, store it in the code library, and forcibly associate the software code with defect ID and R&D requirement ID; The software code in the codebase is processed through a built-in pipeline to generate new software artifacts; In response to the signal that the new software artifact has passed regression testing and review in sequence, the new software artifact is delivered.

7. A method for full lifecycle management of product software in the engineering machinery industry according to claim 6, characterized in that, The delivery of the new software artifact includes: Package the new software artifacts, along with their corresponding software design specifications and test plans, to generate delivery materials. Receive data from software system engineers to generate a delivery review report for the packaged delivery materials; Archive the delivered materials and delivery review report.

8. A device for managing the entire lifecycle of product software in the engineering machinery industry, characterized in that, Applied to the ALM platform, including: The software development requirements list generation module is used to generate a software development requirements list based on the received original software requirements. The software development requirements management module is used to sequentially perform software design, software development and software testing based on the software development requirements list, and generate a first software artifact, as well as a first test plan and a first software material number corresponding to the first software artifact; The software change request list generation module is used to generate a software change request list based on the received software change requests. The software change requirement management module is used to sequentially perform software design, software development, and software testing based on the software change requirement list, the first software artifact, and the first test plan, to generate a second software artifact, as well as a second test plan and a second software material number corresponding to the second artifact.

9. A full lifecycle management system for product software in the engineering machinery industry, characterized in that, This includes an ALM platform, a quality management platform, a manufacturing execution platform, and a product data management platform; The ALM platform is configured to perform the method according to any one of claims 1-7; The quality management platform, manufacturing execution platform, and product data management platform are respectively connected to the ALM platform and receive software artifacts issued by the ALM platform.

10. A full lifecycle management system for product software in the engineering machinery industry, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the method according to any one of claims 1-7.

Images