Software management method, configuration management platform and storage medium

Abstract

The invention provides a software management method, a configuration management platform and a storage medium, the software management method is applied to the configuration management platform, and the method comprises the steps of determining a to-be-reviewed target file in response to a review process initiated by a first user, and determining at least one review person for the target file; determining a first review file of the target file based on the data category of the target file; sending the first review file to at least one review person, and receiving the first review file and the first review result filled by the at least one review person; based on the first review file and the first review result filled by the at least one review person, determining whether review is passed or not; and if the review is passed, changing the state of the target file into a state of passing the review. According to the technical scheme, the review process is embedded into the configuration management platform, the complexity of review work is reduced, and follow-up checking and tracing are facilitated.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a software management method, a configuration management platform, and a storage medium. Background Art

[0002] With the advancement and development of aviation technology, the amount of software used in aircraft onboard systems and equipment is increasing. Due to the particularity of aircraft, the safety requirements for onboard software are relatively high. At present, there are still some problems in the management of the full life cycle process and output data of onboard software (for example, the management of verification data). Summary of the invention

[0003] In order to solve the above problems, the present application provides a software management method, a configuration management platform, and a storage medium.

[0004] In a first aspect, the present application provides a software management method, which is applied to a configuration management platform, and the method includes: in response to a review process initiated by a first user, determining a target file to be reviewed, and determining at least one reviewer for the target file; based on the data category of the target file, determining a first review file for the target file; sending the first review file to at least one reviewer, and receiving the first review file and first review result filled out by at least one reviewer; based on the first review file and first review result filled out by at least one reviewer, determining whether the review is passed; if the review is passed, changing the status of the target file to passed review.

[0005] In combination with the first aspect, the method also includes: if the status of the target file is passed, then in response to the review process initiated by the second user, entering the review process; or, if the status of the target file is any status before passed, not allowing entry into the review process.

[0006] In combination with the first aspect, in response to the review process initiated by the second user, before entering the review process, the method also includes: determining whether the target file needs review based on the data category of the target file; if the target file needs review, allowing entry into the review process; if the target file does not need review, not allowing entry into the review process.

[0007] In combination with the first aspect, the method also includes: if the status of the target file is any status after the review is passed, then in response to the problem reporting process initiated by the initiator, a problem reporting process for the target file is generated, and the target file is bound to the problem reporting process; the problem reporting process is transferred to the reviewer, and according to the solver selected by the reviewer, the problem reporting process is transferred to the solver; the solution proposed by the solver is sent to the reviewer, and based on the instructions allowed for modification determined by the reviewer, the status of the target file is changed to in progress, so that the solver can modify the target file; the target file modified by the solver is received, and the modified target file is bound to the problem reporting process.

[0008] In combination with the first aspect, the method also includes: based on the modified target file, in response to the review process initiated by the solver, determining a second review file of the modified target file; sending the second review file to at least one reviewer, and receiving the second review file and the second review result filled out by at least one reviewer; based on the second review file and the second review result filled out by at least one reviewer, determining whether the review is passed; if the review is passed, changing the status of the modified target file to passed review.

[0009] In a second aspect, the present application provides a software management method, which is applied to a configuration management platform, and the human-computer interaction interface of the configuration management platform can display the target file and the status of the target file. The method includes: in response to a review process initiated by a first user for the target file, retrieving a first review file of the target file and sending it to at least one reviewer, wherein the first review file is determined based on the data category of the target file; after receiving the first review file and the first review result filled out by at least one reviewer, determining whether the review is passed based on the first review file and the first review result filled out by at least one reviewer; if the review is passed, the status of the target file displayed on the human-computer interaction interface is changed to passed review; if the review is not passed, the status of the target file displayed on the human-computer interaction interface is any status before the review is passed.

[0010] In combination with the second aspect, the configuration management platform includes a software verification module, and the method also includes: storing the first review document and the first review result filled out by at least one reviewer in the software verification module; and / or, writing the storage address of the first review document and the first review result filled out by at least one reviewer into the target file in a linked manner, and displaying it in the human-computer interaction interface.

[0011] In combination with the second aspect, the configuration management platform also includes a software planning module, which retrieves the first review file of the target file and sends it to at least one reviewer, including: based on the data category of the target file, retrieving the first review file from the software planning module and sending it to at least one reviewer.

[0012] In combination with the second aspect, in response to a review process initiated by a second user for a target file, if the status of the target file displayed on the human-computer interaction interface is that the review is passed, the review process is entered; if the status of the target file displayed on the human-computer interaction interface is any status before the review is passed, the review process is not allowed to enter; and / or, in response to a problem reporting process initiated by the initiator, if the status of the target file displayed on the human-computer interaction interface is any status after the review is passed, a problem reporting process for the target file is generated, and at least one of the problem data, solution, and modified target file of the problem reporting process is displayed on the human-computer interaction interface.

[0013] In a third aspect, the present application provides a configuration management platform, comprising one or more project libraries, the project libraries including: a software planning module, a software development module and a software verification module; wherein the software planning module is used to support the activities of the software planning process and manage the life cycle data generated by the software planning process; the software development module is used for the development of software functions, the software development module includes at least a software requirement unit, a software design unit, a software code unit and a software integration unit; the software verification module is used for software testing and review analysis, the software verification module includes a verification evidence unit, the verification evidence unit stores at least one of the above-mentioned first review file and first review result, second review file and second review result.

[0014] In conjunction with the third aspect, when the target file is imported into or exported from the configuration management platform, the format of the target file remains consistent.

[0015] In a fourth aspect, the present application provides a storage medium having a computer program stored thereon. When the computer program is executed by a processor, the above-mentioned software management method is implemented.

[0016] In a fifth aspect, the present application provides an electronic device, comprising: a processor; a memory, the memory being connected to the processor, the memory being used to store a computer program, and the computer program implementing the above-mentioned software management method when executed by the processor.

[0017] In a sixth aspect, the present application provides a computer program product, including computer program instructions, which implement the above-mentioned software management method when executed by a processor.

[0018] Through the above technical solution, the review process is embedded in the configuration management platform, providing optional review methods. Users can choose online review or offline review, reducing the complexity of the review work. In addition, the reviewers' review opinions are integrated into the review minutes and stored in the configuration management platform, which is convenient for subsequent inspection and tracing, and also reduces the difficulty of collecting review opinions offline, facilitating the tracking of documents and the tracing of verification evidence. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1a It is a flowchart of a software management method provided in one embodiment of the present application.

[0020] Figure 1b It is a schematic diagram of a document review process provided in an embodiment of the present application.

[0021] Figure 2a It is a flowchart of a software management method provided by another embodiment of the present application.

[0022] Figure 2b It is a schematic diagram of the document review process provided in one embodiment of the present application.

[0023] Figure 3a It is a flowchart of a software management method provided by another embodiment of the present application.

[0024] Figure 3b It is a schematic diagram of determining the review and / or approval process based on data category provided by an embodiment of the present application.

[0025] Figure 4a It is a flowchart of a software management method provided by another embodiment of the present application.

[0026] Figure 4b It is a schematic diagram of a problem reporting process provided in an embodiment of the present application.

[0027] Figure 5 It is a flowchart of a software management method provided by another embodiment of the present application.

[0028] Figure 6 It is a structural block diagram of a software management device provided in one embodiment of the present application.

[0029] Figure 7 It is a schematic diagram of a human-computer interaction interface provided in one embodiment of the present application.

[0030] Figure 8 It is a schematic diagram of a project library architecture provided in an embodiment of the present application.

[0031] Fig. 9 It is a schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0033] Due to the particularity of aircraft, the safety requirements for airborne software are relatively high. In the airworthiness certification of software, the management of the software's entire life cycle process and life cycle data is an especially important link. At present, in the aviation field, there are two ways to manage software life cycle data: one management method is to use a software life cycle management platform that is consistent with the aircraft-level R&D management platform, but no solution suitable for software airworthiness is proposed. There is a problem that the verification evidence of various software data cannot be intuitively reflected, and it is impossible to intuitively reflect the review records and other contents. The second management method is to build a management platform suitable for software, but the management platform does not propose a detailed plan and implementation method for the management of the software's entire life cycle process and data, and does not clearly provide an implementation plan for traceability between verification evidence and data.

[0034] In the face of the above technical problems, on the first aspect, an embodiment of the present application provides a software management method, which is applied to a configuration management platform, and the method includes: in response to the review process initiated by the first user, determining the target file to be reviewed, and determining at least one reviewer for the target file; based on the data category of the target file, determining the first review file of the target file; sending the first review file to at least one reviewer, and receiving the first review file and the first review result filled out by at least one reviewer; based on the first review file and the first review result filled out by at least one reviewer, determining whether the review is passed; if the review is passed, changing the status of the target file to the review passed. In an embodiment of the present application, the review process is embedded in the configuration management platform, providing the selectivity of the review method, and the user can choose online review or offline review, reducing the complexity of the review work. In addition, the reviewers' review opinions are integrated into the review minutes and stored in the configuration management platform, which is convenient for subsequent inspection and tracing, and also reduces the difficulty of collecting review opinions offline, and facilitates the tracking of files and the tracing of verification evidence.

[0035] Figure 1a is a flowchart of a software management method provided by an embodiment of the present application. The method is applied to a configuration management platform, such as Figure 1a As shown, the method includes the following steps.

[0036] Usually, the configuration management platform stores various types of files of the software. When using the configuration management platform to compile files, the format of the file cannot be adjusted, resulting in the file format of the configuration management platform not matching the company file template, and the consistency of the file cannot be guaranteed when importing or exporting files. In an embodiment of the present application, a file template rule that matches the company file template is designed in the configuration management platform, and the default template is embedded in the configuration management platform (specifically, secondary development is performed in the file import and file editing functions provided by the configuration management platform, and the company template format is embedded). It can be ensured that when the file is imported into the configuration management platform after offline compilation, while reading the file content, the format corresponding to the content is read and identified, and the format embedded in the platform is used to match the format of the corresponding file content, ensuring that the format remains unchanged; and when exporting files from the configuration management platform, the format is kept from being overwritten by the platform default format, so that when delivering software-related files, the consistency between files can be maintained. That is, in an embodiment of the present application, when the target file is imported or exported from the configuration management platform, the format of the target file remains consistent, so that the selectivity of online and offline development work of the configuration management platform can be achieved.

[0037] In the embodiment of the present application, a new data attribute is added to the configuration management platform: data category, which divides the software life cycle data into different categories. When the user imports the file into the configuration management platform, he selects or fills in the data category. In the embodiment of the present application, based on the data category and the preset numbering rule, each file is automatically provided with a unique identifier, that is, a file number. In addition, the data category can be used to match the corresponding review checklist, review process, and signing and review process for files of different data categories during the subsequent review. In the embodiment of the present application, the data categories of the software life cycle include: software qualification plan, software development plan, software verification plan, software quality assurance plan, software configuration management record, software requirement standard, software design standard, software coding standard, software requirement data, software architecture design, software component design, source code, software test case, software test procedure, software verification result, stack and storage analysis, worst run time analysis, structural coverage analysis, coupling coverage analysis, general documents, configuration management record, quality assurance record, etc. It can be understood that the data categories listed here are only examples and are not restrictive. Those skilled in the art can add or delete data categories according to actual needs.

[0038] In the prior art, it is impossible to initiate a review process in the configuration management platform, and the review process can only be initiated directly. When the members involved in the review have different opinions, the file will circulate repeatedly in the review process, which greatly increases the difficulty of the file review. In an embodiment of the present application, a file review process is embedded in the configuration management platform, and a corresponding review checklist is generated according to the data category so that reviewers can conduct reviews, which can save time and cost, and reduce the difficulty of confirming and modifying review opinions. In an embodiment of the present application, files in all modules of the project library can use online review. Users can choose online or offline review according to file characteristics and project conditions. Online review includes the following steps.

[0039] Step S110 , in response to the review process initiated by the first user, determining a target file to be reviewed, and determining at least one reviewer for the target file.

[0040] In an embodiment of the present application, the first user may be the person responsible for compiling the target file, or other relevant personnel. When the target file needs to be reviewed, the first user initiates a review process in the configuration management platform and designates reviewers. For example, when the first user initiates the review process, the reviewers are selected at a fixed position in the review process. In an embodiment of the present application, the reviewers form a review group, including review group members and a review group leader. In response to the review process initiated by the first user, the target file to be reviewed is obtained, and the corresponding reviewers are determined.

[0041] Step S120: determining a first review file of the target file based on the data category of the target file.

[0042] When airborne software is undergoing airworthiness certification, different target requirements for different files are different. For example, the software requirement document requires that the document contain high-level software requirements and performance requirements, etc.; another example is the software development plan, which requires the standards to be followed in software development to be stated. Therefore, files of different data categories have different focuses during the review. In an embodiment of the present application, different data categories correspond to different review files, which facilitates reviewers to review files of different data categories, improves the efficiency of the review, and increases the confidence in the review results. The first review file includes a review checklist and a review minutes. In an embodiment of the present application, a review checklist is generated for each reviewer so that the reviewers can fill in their respective review checklists.

[0043] Step S130, sending the first review document to at least one reviewer, and receiving the first review document and the first review result filled out by at least one reviewer.

[0044] Specifically, the review checklist in the first review file is sent to each reviewer, and the reviewer can view the target file through the configuration management platform and fill in the checklist or other review opinions; receive the first review file (for example, the review checklist) and the first review result (for example, the review is passed, the review is not passed) filled in by each reviewer, and the filled in first review file (for example, the review checklist) and the first review result are stored in the configuration management platform for subsequent inspection. Optionally, the filled in review checklist and the first review result are sorted into the review minutes, and the review minutes of the target file are generated for subsequent inspection. In addition, each reviewer can view the review checklist and review opinions of other reviewers in the review group. In the embodiment of the present application, the reviewer can review at any time through the platform, fill in the review checklist and review opinions, and view the review checklist and review opinions of other reviewers, so that the time of offline review and communication of opinions can be saved, and the difficulty of review opinion confirmation and review opinion modification is also reduced.

[0045] Step S140, determining whether the review is passed based on the first review document and the first review result filled out by at least one reviewer.

[0046] After receiving the first review document and the first review result of each reviewer, determine whether the review is passed. For example, the review team leader checks the review checklist and the first review result of each review team member, and conducts a review analysis to determine whether the review is passed (for example, the first review result of each reviewer is a passed review, etc.). If the review is passed, select the review passed on the configuration management platform. If the review is passed, execute step S150. In step S150, change the status of the target file to passed review. If the review is not passed, the first user can modify the content of the target file and then re-initiate the review process.

[0047] In the embodiment of the present application, the review process is embedded in the configuration management platform, providing the optional review method. Users can choose online review or offline review, reducing the complexity of the review work. In addition, the reviewers' review opinions are integrated into the review minutes and stored in the configuration management platform, which is convenient for subsequent inspection and tracing, and also reduces the difficulty of collecting review opinions offline, which facilitates the tracking of documents.

[0048] Figure 1b FIG. 1 is a schematic diagram of a document review process provided by an embodiment of the present application. Figure 1bAs shown, the document review process includes: the data responsible person (i.e., the first user) initiates the review process; determines whether the review group members have completed the configuration; if not, returns to the previous step, and the data responsible person completes the configuration of the review group members and then initiates the review process again; if so, the platform (configuration management platform) generates review minutes and checklists; the review process flows to each review group member; the review group members log in to the platform to fill out the checklist; determines whether all review group members have completed the checklist; if not, returns to the previous step; if so, the review group leader evaluates; determines whether the review is passed; if so, the review is completed, and the file status is changed to passed review; if not, returns to the first step, and the data responsible person re-initiates the review after modification. It can be understood that Figure 1b This is only a specific implementation of the review process, not the only implementation. Those skilled in the art may adjust the steps therein (for example, add or delete steps) according to actual conditions.

[0049] In order to avoid the problem that the file enters the review process before the review is initiated, causing the file to circulate repeatedly in the review process, the embodiment of the present application adds a function to judge the status of the file before initiating the review process. Figure 2a shown.

[0050] Figure 2a FIG. 1 is a flowchart of a software management method provided by another embodiment of the present application. Figure 2a As shown, the method includes the following steps.

[0051] Step S210, determining whether the status of the target file is review passed.

[0052] In the embodiment of the present application, according to the file processing flow, the status of the target file includes: draft, in progress, quality review, online / offline review, team leader review, review passed, proofreading, review, counter-signed, approved, published, etc. If the status of the target file is any status before the review is passed (for example, draft, in progress, quality review, online / offline review, team leader review, etc.), step S230 is executed, and the review process is not allowed to enter. For example, the configuration management platform does not open the review option, so that files that have not passed the review cannot initiate the review process.

[0053] If the status of the target file is passed, execute step S220. In step S220, in response to the review process initiated by the second user, the review process is entered. For example, the configuration management platform opens the review process and allows users to initiate the review. In an embodiment of the present application, the second user can be the same as the first user, for example, both are the compilers of the file. The second user also needs to select at least one review member to enter the review process. In the review process, the process flows to proofreading, review, and counter-signing in sequence. When all counter-signers have completed the signature, the process flows to review and approval. After passing, the status of the file is changed to frozen. At this time, the file is in a published state and cannot be modified at will. If you want to modify it, you need to initiate a problem reporting process.

[0054] In the embodiment of the present application, since the document is only signed and reviewed after passing the review, the quality of the document is guaranteed; in addition, the document has a corresponding review checklist and review minutes, and the review checklist and review minutes can be shown to the authority as verification evidence, ensuring the integrity of the verification evidence.

[0055] Figure 2b Schematic diagram of the document review process provided by an embodiment of the present application. Figure 2b As shown, the software review process includes: determining whether the file has passed the review; if so, the file owner (i.e., the second user) initiates the file review; determining whether the review owner has been selected; if not, returning to the previous step, and the file owner selects the review owner; if so, the review process flows to proofreading; the review process flows to auditing; the review process flows to co-signing; determining whether all co-signers have completed the signature; if not, returning to the previous step and remaining in the co-signing process until everyone has completed the signature; if so, the review process flows to standard review; the review process flows to approval; determining whether it has been approved; if so, changing the file status to frozen; if not, modifying the file and re-initiating the review / review process (for example, returning to the first step). It can be understood that Figure 1b This is only a specific implementation of the document review process, and is not the only implementation. Those skilled in the art can adjust the steps therein (for example, add or delete steps) according to actual conditions.

[0056] In the airworthiness certification of airborne software, different files have different target requirements. Therefore, the review and sign-off process for files of different data categories is also different. For example, source code only needs to be reviewed, not signed. Requirement documents need to be reviewed and signed. Therefore, before signing, it is necessary to determine whether the target file needs to be signed. This is shown in Figure 3.

[0057] Fig. 3 is a flowchart of a software management method provided by another embodiment of the present application. As shown in Fig. 3, the method includes the following steps.

[0058] Step S310, determining whether the status of the target file is review passed.

[0059] If the status of the target file is any status before the review is passed, step S350 is executed. In step S350, the signing and review process is not allowed to be entered.

[0060] If the status of the target file is approved, execute step S320. In step S320, determine whether the target file needs to be reviewed based on the data category of the target file. For different data categories, the configuration management platform stipulates whether review is allowed. Therefore, it can be determined whether the target file needs to be reviewed based on the data category of the target file. If the target file does not need to be reviewed, execute step S350. In step S350, it is not allowed to enter the review process.

[0061] If the target file needs to be reviewed, step S330 is executed to allow the review process to be entered. Then step S340 is executed to enter the review process in response to the review process initiated by the second user. For more descriptions of the review process, please refer to step S220, which will not be repeated here.

[0062] In the embodiment of the present application, the target requirements of files of different data categories are different, so the review and / or approval process of the files are also different; for example, source code only needs to be reviewed, not approved. To this end, matching checklists and processes are automatically generated for files according to data categories, and it is determined whether the files need to be approved. Figure 3b FIG. 1 is a schematic diagram of determining the review and / or approval process based on data category according to an embodiment of the present application. Figure 3b As shown, the process includes: importing files into the configuration management platform or creating new files in the configuration management platform; selecting data categories; the system records data categories; users initiate a review process; the system reads the data categories and searches the project library for checklists and review minutes templates corresponding to the data categories; generating multiple checklists and review minutes based on the review team members; passing the review; judging whether the file needs to be reviewed based on the data category; if not, entering data release; if so, entering the file review process; after completing the review process, entering data release.

[0063] In the prior art, a problem report cannot be directly linked to the file where the problem was discovered, and the file where the problem was discovered can only be read through the text description of the person filling out the problem report. Furthermore, only after the problem is confirmed can the problem-solving process be manually initiated to remove the file where the problem was discovered from the warehouse, and then re-enter the warehouse after modification and verification. This operation is cumbersome and it is easy to miss files. To this end, an embodiment of the present application provides a problem reporting process that directly links the file where the problem was discovered and the problem report in a linked manner, and at the same time, directly binds the status of the file to the problem report, eliminating the need to manually execute the file removal process. Specifically, Figure 4a shown.

[0064] Figure 4a FIG. 1 is a flowchart of a software management method provided by another embodiment of the present application. Figure 4a As shown, the method includes the following steps.

[0065] Step S410, determining whether the status of the target file is any status after the review is passed.

[0066] In the embodiment of the present application, the status after the review is passed includes review passed, proofreading, reviewing, countersigning, approved, and released. That is, the status of the target file may be review passed, in the review process, completed review pending release, or completed release. At this time, since the target file has completed the review, it is necessary to limit the modification of the content of the target file. Otherwise, the modified file will not be reviewed, which may affect the quality of the file.

[0067] If the status of the target file is any status after the review is passed, execute step S420. In step S420, in response to the problem reporting process initiated by the initiator, a problem reporting process for the target file is generated, and the target file is bound to the problem reporting process. In an embodiment of the present application, the initiator can be anyone who has the authority to initiate a problem report. When initiating the problem reporting process, the initiator needs to clearly describe the problem and the target file, and display the target file in the problem reporting process in the form of a hyperlink in the human-computer interaction interface of the configuration management platform (that is, bind the target file to the problem reporting process).

[0068] Step S430, the problem reporting process is transferred to the reviewer, and according to the solver selected by the reviewer, the problem reporting process is transferred to the solver.

[0069] In an embodiment of the present application, after the initiator initiates the problem reporting process, the auditor needs to determine whether it is a problem (i.e., whether the target file needs to be modified). Specifically, the auditor can click on a hyperlink to view the target file. If no modification is required, the problem reporting process ends directly. If modification is required, the auditor selects a solver. According to the solver selected by the auditor, the problem reporting process is transferred to the solver. Usually, the solver is the compiler of the file.

[0070] Step S440, the solution proposed by the solver is sent to the reviewer, and based on the instruction determined by the reviewer to allow modification, the status of the target file is changed to "in progress" so that the solver can modify the target file.

[0071] When the problem reporting process flows to the solver, the solver determines the content that needs to be modified in the target file and proposes a solution. In an embodiment of the present application, the solution proposed by the solver is sent to the reviewer. After the reviewer confirms that the solution is feasible, he clicks "approved", which issues an instruction to allow modification. Based on the instruction to allow modification determined by the reviewer, the status of the target file is changed to "in work" so that the solver can modify the target file.

[0072] Step S450, receiving the target file modified by the solver, and binding the modified target file with the problem reporting process.

[0073] Optionally, after the solver modifies the target file, the modified target file is displayed in the problem reporting process in the form of a hyperlink, so that the modified target file is bound to the problem reporting process.

[0074] In an embodiment of the present application, when a problem is found, the initiator must modify the problem in the file through the problem reporting process. Binding the target file and the modified target file to the problem reporting process solves the problem that the problem tracking process is not intuitive. The user can directly read the target file or the modified target file by viewing the problem reporting process and clicking on a hyperlink to check whether the problem has been modified. It can trace the changes and reasons for the changes in the target file, that is, each change in the target file can be traced, ensuring that the problems in the project process are recorded and corrected, reducing the difficulty of problem management and improving the confidence of the project. In addition, the status of the data is associated with the problem reporting process. The data that has been reviewed and approved must be modified by initiating a problem report. There is no need to frequently perform file outbound and inbound operations, reducing the manual workload.

[0075] Figure 4b FIG. 1 is a schematic diagram of a problem reporting process provided by an embodiment of the present application. Figure 4b As shown, the problem reporting process includes: discovering a problem; the user initiates a problem report and fills in the problem discovery data; determining whether it is a problem; if not, it is determined to be an invalid problem; if so, a problem solver is designated; the problem solver fills in the information and selects the data to be modified; determining whether modification is allowed; if not, returning to the previous step, the problem solver fills in the information again; if so, the file status changes, allowing the file to be modified; fill in the modified file; determining whether the modification is completed; if so, the review team confirms the status; completed. It can be understood that Figure 4b This is only a specific implementation of the problem reporting process, not the only implementation. Those skilled in the art can make adjustments or modifications based on this.

[0076] In the embodiment of the present application, the modified target file also needs to initiate a review / sign-off process. Figure 5 shown.

[0077] Figure 5 FIG. 1 is a flowchart of a software management method provided by another embodiment of the present application. Figure 5 As shown, the method includes the following steps.

[0078] Step S510, determine whether the status of the target file is any status after the review is passed. If the status of the target file is any status after the review is passed, execute step S520. In step S520, in response to the problem reporting process initiated by the initiator, a problem reporting process for the target file is generated, and the target file is bound to the problem reporting process. Step S530, transfer the problem reporting process to the reviewer, and according to the solver selected by the reviewer, transfer the problem reporting process to the solver. Step S540, send the solution proposed by the solver to the reviewer, and based on the instructions allowed to be modified determined by the reviewer, change the status of the target file to in work, so that the solver can modify the target file. Step S550, receive the target file modified by the solver, and bind the modified target file to the problem reporting process.

[0079] In the embodiment of the present application, for the specific description of steps S510 to S550, please refer to steps S410 to S450, which will not be repeated here.

[0080] Step S560 , based on the modified target file, in response to the review process initiated by the solver, determining a second review file of the modified target file.

[0081] In the embodiment of the present application, after the solver modifies the target file, it is necessary to review the modified target file. The review process can be initiated by the solver, or other relevant personnel initiate the review process, and the embodiment of the present application is not limited. Because the data category of the target file and the modified target file does not change, therefore, the review checklist and the review minutes in the second review file are the same in format as the review checklist and the review minutes in the first review file.

[0082] Step S570: Send the second review document to at least one reviewer, and receive the second review document filled out by at least one reviewer and the second review result of each reviewer.

[0083] The specific implementation of step S570 may refer to step S130 and will not be described in detail here.

[0084] Step S580, based on the second review document and the second review result filled in by at least one reviewer, determine whether the review is passed. If the review is passed, execute step S590. In step S590, the status of the modified target file is changed to passed review. In some embodiments, if the target file still needs to be signed and reviewed, after the review is passed, the sign-in and review process can be entered in response to the sign-in and review process initiated by the solver.

[0085] In a second aspect, an embodiment of the present application also provides a software management method, which is applied to a configuration management platform, and a human-computer interaction interface of the configuration management platform can display a target file and the status of the target file. The method includes: in response to a review process initiated by a first user for a target file, scheduling a first review file of the target file and sending it to at least one reviewer, wherein the first review file is determined based on the data category of the target file; after receiving the first review file and the first review result filled out by at least one reviewer, determining whether the review is passed based on the first review file and the first review result filled out by at least one reviewer; if the review is passed, the status of the target file displayed on the human-computer interaction interface is changed to passed review; if the review is not passed, the status of the target file displayed on the human-computer interaction interface is any status before the review is passed.

[0086] Optionally, the configuration management platform includes a software verification module, and the method further includes: storing a first review document and a first review result filled out by at least one reviewer in the software verification module; and / or writing the storage address of the first review document and the first review result filled out by at least one reviewer into a target file in a linked manner, and displaying them in a human-computer interaction interface.

[0087] Optionally, the configuration management platform also includes a software planning module, which retrieves the first review file of the target file and sends it to at least one reviewer, including: based on the data category of the target file, retrieving the first review file from the software planning module and sending it to at least one reviewer.

[0088] Optionally, in response to a review process initiated by a second user for a target file, if the status of the target file displayed on the human-computer interaction interface is that the review is passed, the review process is entered; if the status of the target file displayed on the human-computer interaction interface is any status before the review is passed, the review process is not allowed to be entered; and / or, in response to a problem reporting process initiated by the initiator, if the status of the target file displayed on the human-computer interaction interface is any status after the review is passed, a problem reporting process for the target file is generated, and at least one of the problem data, solution, and modified target file of the problem reporting process is displayed on the human-computer interaction interface.

[0089] For more descriptions about the configuration management platform, review process, review process, and problem reporting process, please refer to other parts of this application, which will not be repeated here.

[0090] In a third aspect, an embodiment of the present application provides a software management device, which is applied to a configuration management platform.

[0091] Figure 6 1 is a structural block diagram of a software management device provided by an embodiment of the present application. Figure 6 As shown, the software management device 600 includes a determination module 610 , a transmission module 620 , a state change module 630 , and a binding module 640 .

[0092] The determination module 610 is used to determine a target file to be reviewed and at least one reviewer for the target file in response to the review process initiated by the first user.

[0093] The determination module 610 is further configured to determine a first review file of the target file based on the data category of the target file.

[0094] The transmission module 620 is used to send the first review document to at least one reviewer, and receive the first review document and the first review result filled out by at least one reviewer.

[0095] The determination module 610 is further used to determine whether the review is passed based on the first review document and the first review result filled out by at least one reviewer.

[0096] The status change module 630 is used to change the status of the target file to "review passed" if the review is passed.

[0097] Optionally, the determination module 610 is also used to enter the review process in response to the review process initiated by the second user if the status of the target file is passed; or, if the status of the target file is any status before passed, not allowing entry into the review process.

[0098] Optionally, the determination module 610 is further used to determine whether the target file needs to be reviewed based on the data category of the target file; if the target file needs to be reviewed, the review process is allowed to begin; if the target file does not need to be reviewed, the review process is not allowed to begin.

[0099] The binding module 640 is used to generate a problem reporting process for the target file in response to the problem reporting process initiated by the initiator if the status of the target file is any status after the review is passed, and bind the target file to the problem reporting process. The transmission module 620 is used to transfer the problem reporting process flow to the reviewer, and transfer the problem reporting process flow to the solver according to the solver selected by the reviewer. The transmission module 620 is also used to send the solution proposed by the solver to the reviewer, and the state change module 630 is also used to change the status of the target file to "in work" based on the instructions allowed to be modified determined by the reviewer, so that the solver can modify the target file. The transmission module 620 is also used to receive the target file modified by the solver, and the binding module 640 is also used to bind the modified target file to the problem reporting process.

[0100] The determination module 610 is also used to determine the second review file of the modified target file based on the modified target file in response to the review process initiated by the solver. The transmission module 620 is also used to send the second review file to at least one reviewer, and receive the second review file and the second review result filled out by at least one reviewer. The determination module 610 is also used to determine whether the review is passed based on the second review file and the second review result filled out by at least one reviewer. The status change module 630 is also used to change the status of the modified target file to passed if the review is passed.

[0101] The specific working principle and benefits of the software management device provided in the embodiment of the present application are similar to the specific working principle and benefits of the software management method provided in the embodiment of the present application, and will not be repeated here.

[0102] In a fourth aspect, an embodiment of the present application provides a configuration management platform. The configuration management platform includes a review unit for reviewing files, wherein the review includes the following steps: in response to a review process initiated by a first user, determining a target file to be reviewed, and determining at least one reviewer for the target file; based on the data category of the target file, determining a first review file for the target file; sending the first review file to at least one reviewer, and receiving the first review file and the first review result filled out by at least one reviewer; based on the first review file and the first review result filled out by at least one reviewer, determining whether the review is passed; if the review is passed, changing the status of the target file to passed review.

[0103] Optionally, the configuration management platform also includes a review unit for reviewing documents, wherein the review includes the following steps: if the status of the target document is passed, then in response to the review process initiated by the user, the review process is entered; or, if the status of the target document is any status before passed, then the review process is not allowed to enter.

[0104] Optionally, the configuration management platform also includes a problem reporting unit for modifying the target file, and the modification includes the following steps: if the status of the target file is any status after the review is passed, then in response to the problem reporting process initiated by the initiator, a problem reporting process for the target file is generated, and the target file is bound to the problem reporting process; the problem reporting process is transferred to the reviewer, and the problem reporting process is transferred to the solver according to the solver selected by the reviewer; the solution proposed by the solver is sent to the reviewer, and based on the instructions allowed for modification determined by the reviewer, the status of the target file is changed to in progress, so that the solver can modify the target file; the target file modified by the solver is received, and the modified target file is bound to the problem reporting process.

[0105] In the fifth aspect, the embodiment of the present application also provides a configuration management platform, which can accurately and efficiently manage the configuration information of the product. In the embodiment of the present application, the entire life cycle data of the software and the information required for airworthiness are all placed on the configuration management platform for management, that is, the configuration management platform can manage the files of the entire life cycle of the software, and is a fully integrated platform. The configuration management platform includes one or more project libraries, and the project library includes: a software planning module, a software development module, and a software verification module. Among them, the software planning module is used to support the activities of the software planning process and manage the life cycle data generated by the software planning process. The software development module is used for the development of software functions, and the software development module at least includes a software requirement unit, a software design unit, a software code unit, and a software integration unit. The software verification module is used for software testing and review analysis, and the software verification module includes a verification evidence unit, and the verification evidence unit stores at least one of a first review file (for example, a review checklist, a review minutes) and a first review result, a second review file (for example, a review checklist and a review minutes) and a second review result. Optionally, the verification evidence unit also stores at least one of a software test case and a test procedure, a test result, and an analysis report. The project library also includes software quality assurance module, software configuration management module and certification module. Among them, the software quality assurance module is used to store software quality assurance related files. The software configuration management module is used to store software configuration management related files. The certification module is used to store information interacted with the authority.

[0106] In order to facilitate understanding of the technical solution of the present application, the software development work of the configuration management platform is explained by taking the project library as an example.

[0107] First, according to the project situation, a project library is established on the configuration management platform. The project library includes multiple functional modules. The human-computer interaction interface is designed, and the project library is used as an optional item. When there are multiple projects, the user can click to select the project library according to the actual situation. At the same time, all modules in the project library are displayed on the human-computer interaction interface.

[0108] In order to achieve multi-person collaboration in the project team and meet the company's internal review requirements, the configuration management platform server is connected to the company's local area network to ensure the access rights of internal members of the company. When an authorized user logs in, he can select the project library in the human-computer interaction interface. After selection, each module can be viewed on the human-computer interaction interface. When creating a new file or importing a file, select the corresponding module in the human-computer interaction interface, and the file can be stored in the corresponding module. During the internal review, the data stored in each module can be viewed one by one through the human-computer interaction interface to determine the integrity of each process data. For example, the schematic diagram of the human-computer interaction interface is shown as follows: Figure 7 As shown, users can select different project libraries by clicking the drop-down box next to the project name, and enter the module by clicking the drop-down option next to each module in the project. With this project library planning method, users can view the status of data in each module in the project library, and can know the current R&D progress and which life cycle stage it is in, which is convenient for project team members to check the integrity of life cycle data.

[0109] In the embodiment of the present application, a document review process, a document signing and review process, and a problem reporting process are established. In the process, the permissions of the project team members need to be limited. Specifically, the file modification permission is only for the file preparer, and other personnel have no permission to modify. Reviewers and signers can annotate the file. Reviewers can modify the content of the checklist. The quality engineer can finally close the problem report to ensure that the quality engineer tracks the problem.

[0110] In the embodiment of the present application, the project library includes a software planning module, a software development module, a software verification module, a software quality assurance module, a software configuration management module and a qualification certification module, as shown in the following figure: Figure 8 shown.

[0111] Optionally, the software planning module is used to support the activities of the software planning process and manage the life cycle data generated by the planning process. The module provides a human-machine operation interface for software project team members to import or edit software plan-related files offline. Exemplarily, the software planning module includes at least the data shown in Table 1.

[0112] Table 1 Software planning module data

[0113]

[0114]

[0115] Optionally, the software development module is used for the development of software functions. To fully reflect the software development process, the software development module includes: software requirement unit, software design unit, software code unit, software integration unit, etc. Exemplarily, the software development module includes at least the data shown in Table 2.

[0116] Table 2 Software development module data

[0117]

[0118] Optionally, in order to clearly present the verification work, the software verification module is used for software testing and review analysis. The software verification module includes a verification evidence unit. The software verification unit mainly stores software test cases and test procedures, as well as review checklists, review minutes, test results and analysis reports for storing all data. The verification evidence unit provides a human-machine interface for software verification personnel to import or edit software verification related files offline. For example, when the user initiates the review process, the system reads the checklist template stored in the software plan module of the project library according to the data category, selects the checklist corresponding to the data (or file), and creates a checklist for each review group member in combination with the review group members selected by the user. At the same time, a review minute is established for the data (or file). The checklist and review minutes are stored in the verification evidence module. At the same time, there is a link relationship between the checklist and the review minutes and the data (or file). When the user views the data (or file) in the human-computer interaction interface, the user can view the checklist and review minutes corresponding to the data (or file) at the same time. Click the link to jump to the corresponding checklist and review minutes content page. Exemplarily, the software verification module includes at least the data shown in Table 3.

[0119] Table 3 Software verification module data

[0120] Serial number data 1 Software Test Cases 2 Software Testing Procedures 3 Software testing procedure execution record 4 Checklists and review minutes for each document 5 Analytical Report 6 Traceability reports between test cases, test procedures and requirements

[0121] Optionally, the software quality assurance module is provided to the software quality assurance engineer to import or edit the software quality assurance related files offline, and provide the software quality assurance engineer with a space to store the quality assurance process data. By viewing the data in the software quality assurance module, the supervision of each process by the software quality assurance engineer can be visually viewed, and whether there are omissions in the work can also be visually viewed. The quality assurance module contains various types of quality assurance checklist data.

[0122] Optionally, the software configuration management module is provided to the software configuration management engineer to import software configuration management related files offline or edit them online, and provides the software configuration management engineer with space for storing configuration management process data.

[0123] Optionally, the certification module is used to store all information interacting with the authority during the project process.

[0124] Below, reference Fig. 9 To describe an electronic device according to an embodiment of the present application. Fig. 9 It is a schematic diagram of the structure of an electronic device provided in one embodiment of the present application.

[0125] like Fig. 9 As shown, the electronic device 900 includes one or more processors 901 and a memory 902 .

[0126] The processor 901 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 900 to perform desired functions.

[0127] The memory 902 may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 901 may run the program instructions to implement the software management method of each embodiment of the present application described above and / or other desired functions. Various contents such as target files, data categories, and review files may also be stored in the computer-readable storage medium.

[0128] In one example, the electronic device 900 may further include: an input device 903 and an output device 904 , and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0129] The input device 903 may include, for example, a keyboard, a mouse, etc.

[0130] The output device 904 can output various information to the outside, including review results, etc. The output device 904 can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, and the like.

[0131] Of course, to simplify, Fig. 9 Only some of the components related to the present application in the electronic device 900 are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application situations, the electronic device 900 may also include any other appropriate components.

[0132] In addition to the above-mentioned methods and devices, an embodiment of the present application may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the software management method according to various embodiments of the present application described above in this specification.

[0133] The computer program product may be written in any combination of one or more programming languages ​​to write program codes for performing the operations of the embodiments of the present application, including object-oriented programming languages, such as Java, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0134] In addition, an embodiment of the present application may also be a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor executes the steps of the software management method according to various embodiments of the present application described above in this specification.

[0135] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0136] The basic principles of the present application are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present application are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present application. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, not for limitation, and the above details do not limit the present application to being implemented by adopting the above specific details.

[0137] The block diagrams of the devices, apparatuses, equipment, and systems involved in this application are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagram. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including", "comprising", "having", etc. are open words, referring to "including but not limited to", and can be used interchangeably with them. The words "or" and "and" used here refer to the words "and / or" and can be used interchangeably with them, unless the context clearly indicates otherwise. The words "such as" used here refer to the phrase "such as but not limited to", and can be used interchangeably with them.

[0138] It should also be noted that in the apparatus, device and method of the present application, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present application.

[0139] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present application. Therefore, the present application is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0140] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present application to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A software management method, characterized in that: Applied to a configuration management platform, the method comprises: In response to the review process initiated by the first user, determining a target file to be reviewed, and determining at least one reviewer for the target file; Determining a first review file for the target file based on the data category of the target file; Sending the first review document to the at least one reviewer, and receiving the first review document and the first review result filled out by the at least one reviewer; Determining whether the review is passed based on the first review document and the first review result filled out by the at least one reviewer; If the review is passed, the status of the target file is changed to passed.

2. The method according to claim 1, characterized in that Also includes: If the status of the target file is that the review is passed, responding to the review process initiated by the second user, entering the review process; If the status of the target file is any status before passing the review, it will not be allowed to enter the review process.

3. The method according to claim 2, characterized in that Before entering the review process in response to the review process initiated by the second user, the method further includes: Determine whether the target file needs to be reviewed based on the data category of the target file; If the target document needs to be reviewed, the review process is allowed; If the target file does not require review, the review process will not be allowed.

4. The method according to any one of claims 1 to 3, characterized in that: Also includes: If the status of the target file is any status after the review is passed, in response to the problem reporting process initiated by the initiator, a problem reporting process for the target file is generated, and the target file is bound to the problem reporting process; Transferring the problem report process to the auditor, and transferring the problem report process to the solver according to the solver selected by the auditor; Sending the solution proposed by the solver to the reviewer, and based on the instruction determined by the reviewer to allow modification, changing the status of the target file to "in progress" so that the solver can modify the target file; The target file modified by the solver is received, and the modified target file is bound to the problem reporting process.

5. The method according to claim 4, characterized in that Also includes: Based on the modified target file, in response to a review process initiated by the solver, determining a second review file of the modified target file; Sending the second review document to the at least one reviewer, and receiving the second review document and the second review result filled out by the at least one reviewer; Determining whether the review is passed based on the second review document filled out by the at least one reviewer and the second review result; If the review is passed, the status of the modified target file is changed to passed.

6. A software management method, characterized in that: Applied to a configuration management platform, the human-computer interaction interface of the configuration management platform can display a target file and the status of the target file, and the method includes: In response to a review process initiated by a first user for the target file, a first review file of the target file is retrieved and sent to at least one reviewer, wherein the first review file is determined based on a data category of the target file; After receiving the first review document and the first review result filled out by the at least one reviewer, determine whether the review is passed based on the first review document and the first review result filled out by the at least one reviewer; if the review is passed, the status of the target file displayed on the human-computer interaction interface is changed to passed review; if the review is not passed, the status of the target file displayed on the human-computer interaction interface is any status before passed review.

7. The method according to claim 6, characterized in that The configuration management platform includes a software verification module, and the method further includes: storing the first review document and the first review result filled out by the at least one reviewer in the software verification module; and / or, writing the storage address of the first review document and the first review result filled out by the at least one reviewer into the target file in a linked manner, and displaying them on the human-computer interaction interface.

8. The method according to claim 6, characterized in that The configuration management platform further includes a software planning module, wherein the step of retrieving the first review file of the target file and sending the first review file to at least one reviewer includes: Based on the data category of the target file, the first review file is retrieved from the software planning module and sent to the at least one reviewer.

9. The method according to claim 6, characterized in that In response to the review process initiated by the second user for the target file, if the status of the target file displayed on the human-computer interaction interface is that the review is passed, then entering the sign-up and review process; If the status of the target file displayed on the human-computer interaction interface is any status before the review is passed, the document will not be allowed to enter the review process; and / or, In response to the problem reporting process initiated by the initiator, if the status of the target file displayed on the human-computer interaction interface is any status after passing the review, a problem reporting process for the target file is generated, and at least one of the problem data, solution, and modified target file of the problem reporting process is displayed on the human-computer interaction interface.

10. A configuration management platform, characterized in that: One or more project libraries are included, the project libraries comprising: A software planning module for supporting the activities of the software planning process and managing the lifecycle data generated by the software planning process; A software development module, used for the development of software functions, wherein the software development module comprises at least a software requirement unit, a software design unit, a software code unit and a software integration unit; A software verification module is used for software testing and review analysis, and the software verification module includes a verification evidence unit, and the verification evidence unit stores at least one of the first review file and the first review result in claim 1 and / or the second review file and the second review result in claim 5.

11. The configuration management platform according to claim 10, characterized in that: When the target file is imported into or exported from the configuration management platform, the format of the target file remains consistent.

12. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by the processor, the software management method according to any one of claims 1 to 5 is implemented.

Images