A software technical status management system

Abstract

The present invention relates to the field of product technology management and information technology, and in particular to a software technology status management system, including a software information review module, a software process planning module, a software MBOM building module, a software BBOM management module and a basic data configuration module. Through this system, the relevance and accuracy of the onboard software version are achieved, which can effectively solve the problem of being unable to trace the software and hardware association relationship.

Description

Technical Field

[0001] The present invention relates to the field of product technology management and information technology, and in particular to a software technology status management system. Background Art

[0002] At present, software management faces problems and challenges such as scattered software data, untimely coordination of supplier data, and inability to trace the relationship between software and hardware. It is urgent to use information technology to effectively support and control it. In order to improve the technical status management system, product data management covers the entire life cycle of product and software delivery assurance. The design institute manages the finished hardware and software separately, and includes the aircraft supporting software as a CI item in the BOM to ensure the controlled management of the technical status of the software throughout its life cycle. The software management system will serve as a unified information center and integrated framework for design and manufacturing during the model development process, supporting business personnel to manage all software data related processes involved in the manufacturing process, and ensure the integrity, consistency, validity and traceability of the software and software-related data. Summary of the invention

[0003] In order to solve the above technical problems, the present invention proposes a software technical status management system to achieve the relevance and accuracy of the onboard software version, which can effectively solve the problem of being unable to trace the software and hardware association relationship.

[0004] The present invention is achieved by adopting the following technical solutions:

[0005] A software technical status management system, characterized by: comprising a software information review module, a software process planning module, a software MBOM building module, a software BBOM management module and a basic data configuration module;

[0006] The software information review module is used to review the software information, that is, when the creation of the software is reviewed by the EBOM of the design institute, the software CI, DSI and its related files are synchronized to the manufacturing plant through the software ECP. After the manufacturing plant completes the processability review, the review opinions are fed back to the design institute to complete the software information review;

[0007] The software process planning module is used for the professional departments of the engineering department to conduct impact analysis on the released or modified software data during the software information review process, identify whether it is related to the profession, and formulate treatment measures, including: process planning process verification, software ECP process planning, process planning result viewing and SERP synchronization; wherein, the process planning process verification includes verification of integrity, verification of whether the ECP is zero change and verification of whether the CI major version in the ECP has an associated top-level change ECO; the software ECP process planning includes: review structure list acquisition and adjustment, setting review personnel, first-level process planning, second-level professional process planning, first-level professional chief review, project chief review review and circulation process;

[0008] The software MBOM construction module is used to start the software MCO after completing the process review and the first-level planning, complete the creation and update of the relationship between the finished product and the software, and generate the change record of the relationship between the finished product and the software. For the MCO caused by the change, the task is initiated to the corresponding process personnel to confirm the change information of the finished product and the software. When the MCO is released, the distribution and circulation process is started for the software circulation unit, and the MCO information is released to the SERP system;

[0009] The software BBOM management module is used to obtain the execution record in real time through the finished product or software DSI in the BBOM, and when the finished product is installed on the aircraft, determine the flight, and check the software filling and upgrade records associated with the finished product according to the AO where the resident finished product is located, so as to determine the software installation version information of the flight, and provide an interface for obtaining software upgrade and filling execution information within the institute;

[0010] The basic data configuration module is used to provide software distribution unit configuration function, software MCO reviewer configuration function and process review flow configuration function.

[0011] It also includes a software information viewing module and a software data statistics summary module. The software information viewing module is used to provide a finished product related software viewing function in the product EBOM\MBOM structure, display the finished product related software information, and filter by batch; the software data statistics summary module is used to provide software data statistics summary function, provide software version inventory report, software finished product related statistics report, software ECP statistics, whole machine software version configuration table and software executable file query statistics function.

[0012] The software information review module is specifically used for software top-level synchronization and initial issuance of software CI, software DSI and software data files; wherein software top-level synchronization specifically refers to: sending the aircraft PBS software top-level nodes and software CI in the system to the manufacturer in batches; once the software top-level nodes and software CI are issued, the software top-level node changes, software CI attribute changes, software CI additions and deletions are implemented through the top-level change ECO factory data synchronization process; the initial issuance of software CI, software DSI and software data files specifically refers to: issuing through zero-change software ECP, distributing and circulating after entering the manufacturer, and the specific distribution units are obtained according to the software circulation unit configuration.

[0013] The process planning process verification specifically includes: after the software ECP is sent to the manufacturing plant system, an integrity check is first performed to confirm whether the synchronized data contains all the ECP data. If incomplete, feedback is given to the design institute. If complete, the ECP is verified to be zero-changed. If not, process planning is required. If zero-changed, the CI major version in the ECP is verified to be associated with the top-level change ECO. If so, process planning is required. If not, the circulation process is directly started.

[0014] The software ECP process planning specifically includes:

[0015] Adjustment of the review structure list acquisition: obtain all the resident finished product information finished product list items according to the ECP-related CI list issued, as the list items in the process task; if there is no software CI associated with the ECP, then find the software DSI associated with the ECP, and find the CI according to the software DSI;

[0016] Set up reviewers: Assign the person in charge of the engineering technology department to the process review meeting, initialize the first-level and second-level reviewers, and set up reviewers according to the process review process configuration rules obtained according to the PBS codes of all DSIs based on all software CIs associated with the ECP, all finished product drawing numbers of the resident finished product information of each software CI, and the PBS codes of the DSIs on the EBOM where all the finished product drawing numbers are located;

[0017] Level 1 process planning: Flight management and avionics level 1 professionals are responsible for the allocation of level 1 process planning tasks. The allocated list obtains the software CI list from the associated objects of ECP, and obtains the finished product list containing the resident finished product information based on the software list.

[0018] Secondary professional process planning: Secondary professionals of flight control and avionics receive the first-level process planning task from ECP. When completing the task, they need to verify that the process planning information has been filled in;

[0019] First-level professional reviewer: After the second-level professional completes the process planning, the first-level professional reviewer reviews the first-level planning content filled in by the professional, and checks the planning content according to the software CI or professional dimension; if the process planning content is incomplete, the second-level professional can be rejected for modification;

[0020] Project Chief Review: The project chief reviewer receives the project chief review task. In the task, he / she checks the process planning chief review summary data. In the chief review summary, he / she checks the process planning opinions according to the finished product dimension or the professional dimension.

[0021] The creation and update of the relationship between the finished product and the software specifically refers to: after the software change MCO is created, the software CI-related finished product information is extracted to form a finished product and software relationship table, and the software CI involved in the change is compared with the finished product to form a finished product and software association change record; the method for generating the finished product and software association change record is: based on the finished product number + software CI number as the benchmark for comparison, if there is no record before, it is a new addition, if there is a record, it is a modification; if it is a new addition, there will be a value only after the change, if it is a modification, it is determined whether the attributes have changed before and after the change, and if there is a change, the values ​​before and after the change are displayed; among them, the DSI number, if the CI is upgraded, it is necessary to obtain the DSI numbers corresponding to the two CI versions as before and after the change, if the DSI is upgraded, the DSI numbers are listed before and after the change.

[0022] The software BBOM management module includes a module for obtaining software execution records, that is, obtaining the resident finished product number according to the software DSI; finding the finished product installation record according to the batch and finished product number, and obtaining the finished product quality number; and obtaining the software filling and upgrade records according to the finished product quality number.

[0023] This system uses standard REST for data interaction, and the underlying REST uses XML for data exchange.

[0024] It also includes a data management module for realizing data exchange, data tracking and data format conversion.

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

[0026] 1. The present invention realizes factory software design collaboration through software information review, realizes software process management through software MBOM construction, realizes software change impact analysis and change planning through software process planning, and realizes software physical status control through software BBOM management, thereby realizing full process control of the technical status of airborne software, constructing a software technical status control environment, realizing effective control of the technical status of airborne software, realizing the relevance and accuracy of airborne software versions, and meeting the demand for tracing the relationship between software and hardware. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments, wherein:

[0028] Figure 1 It is a schematic diagram of the process of the present invention;

[0029] Figure 2 It is a schematic diagram of the synchronization process of the software data factory in the present invention;

[0030] Figure 3 It is a schematic diagram of the software process planning process in the present invention;

[0031] Figure 4 This is a schematic diagram of the software MBOM review process in the present invention;

[0032] Figure 5 It is a schematic diagram of the BBOM data flow of the software in the present invention. DETAILED DESCRIPTION

[0033] Example 1

[0034] As a basic implementation mode of the present invention, the present invention includes a software technical status management system, including a software information review module, a software process planning module, a software MBOM construction module, a software BBOM management module and a basic data configuration module.

[0035] Among them, the software information review module is used to review the software information. That is, when the creation of the software is reviewed by the design institute's EBOM, the software CI, DSI and its related files are synchronized to the manufacturing plant through the software ECP. After the manufacturing plant completes the process review, the review opinions are fed back to the design institute to complete the software information review.

[0036] The software process planning module is used for the professional departments of the engineering department to conduct impact analysis on the released or modified software data during the software information review process, identify whether it is related to the profession, and formulate treatment measures. Specifically including: process planning process verification, software ECP process planning, process planning results viewing and synchronization SERP. Among them, the process planning process verification includes verification of integrity, verification of whether the ECP is zero change, and verification of whether the CI major version in the ECP has an associated top-level change ECO. The software ECP process planning includes: obtaining and adjusting the review structure list, setting reviewers, first-level process planning, second-level professional process planning, first-level professional chief review, project chief review review and circulation process.

[0037] The software MBOM construction module is used to start the software MCO after completing the process review and the first-level planning, complete the creation and update of the relationship between the finished product and the software, and generate a record of the change of the relationship between the finished product and the software. For the MCO caused by the change, the task is initiated to the corresponding process personnel to confirm the change information of the finished product and the software. When the MCO is released, the distribution and circulation process is started for the software circulation unit, and the MCO information is published to the SERP system.

[0038] The software BBOM management module is used to obtain execution records in real time through finished products or software DSI in BBOM. When the finished product is installed on the aircraft, the software filling and upgrade records associated with the finished product are checked according to the AO where the finished product resides, so as to determine the software installation version information of the flight. At the same time, an interface is provided for obtaining software upgrade and filling execution information within the institute.

[0039] The basic data configuration module is used to provide software distribution unit configuration function, software MCO reviewer configuration function and process review flow configuration function.

[0040] Example 2

[0041] As a preferred embodiment of the present invention, the present invention includes a software technical status management system, including a software information review module, a software process planning module, a software MBOM building module, a software BBOM management module, a basic data configuration module, a software information viewing module and a software data statistics summary module. In this embodiment, BOM is a bill of materials, MBOM is a manufacturing bill of materials, BBOM is an installed bill of materials, EBOM is a design bill of materials, and MCO is an engineering change order.

[0042] Among them, the software information review module is used to review the software information. That is, when the creation of the software is reviewed by the design institute's EBOM, the software CI, DSI and its related files are synchronized to the manufacturing plant through the software ECP. After the manufacturing plant completes the process review, the review opinions are fed back to the design institute to complete the software information review.

[0043] The software process planning module is used for the professional departments of the engineering department to conduct impact analysis on the released or modified software data during the software information review process, identify whether it is related to the profession, and formulate treatment measures. Specifically including: process planning process verification, software ECP process planning, process planning results viewing and synchronization SERP. Among them, the process planning process verification includes verification of integrity, verification of whether the ECP is zero change, and verification of whether the CI major version in the ECP has an associated top-level change ECO. The software ECP process planning includes: obtaining and adjusting the review structure list, setting reviewers, first-level process planning, second-level professional process planning, first-level professional chief review, project chief review review and circulation process.

[0044] The software MBOM construction module is used to start the software MCO after completing the process review and the first-level planning, complete the creation and update of the relationship between the finished product and the software, and generate a record of the change of the relationship between the finished product and the software. For the MCO caused by the change, the task is initiated to the corresponding process personnel to confirm the change information of the finished product and the software. When the MCO is released, the distribution and circulation process is started for the software circulation unit, and the MCO information is published to the SERP system.

[0045] The software information viewing module is used to provide the associated software viewing function of finished products in the product EBOM\MBOM structure, display the associated software information of finished products, and filter by batch.

[0046] The software data statistics summary module is used to provide software data statistics summary functions, including software version inventory reports, software finished product related statistics reports, software ECP statistics, full-machine software version configuration tables, and software executable file query statistics functions.

[0047] The software BBOM management module is used to obtain execution records in real time through finished products or software DSI in BBOM. When the finished product is installed on the aircraft, the software filling and upgrade records associated with the finished product are checked according to the AO where the finished product resides, so as to determine the software installation version information of the flight. At the same time, an interface is provided for obtaining software upgrade and filling execution information within the institute.

[0048] The basic data configuration module is used to provide software distribution unit configuration function, software MCO reviewer configuration function and process review flow configuration function.

[0049] Example 3

[0050] As the best embodiment of the present invention, the present invention includes a software technical status management system, Figure 1 And the instruction manual Figure 2 , including software information review module, software process planning module, software MBOM construction module, software BBOM management module, basic data configuration module, software information viewing module, software data statistics summary module and data management module. The following is a detailed description of each module:

[0051] Software Information Review Module: It is used to review software information. Specifically, when the creation of the software is reviewed by the design institute's EBOM, the software CI, DSI and its associated files are synchronized to the manufacturing plant through the software ECP. After the manufacturing plant completes the processability review, the review opinions are fed back to the design institute to complete the software information review.

[0052] Software top-level synchronization. The initial construction of the software top-level structure is similar to the hardware top-level synchronization to the factory. The aircraft PBS software top-level nodes and software CIs in the system are sent to the factory in batches. Once the software top-level nodes and software CIs are issued. If the software top-level nodes are changed, the software CI attributes are changed, and the software CIs are added or deleted, they should be implemented through the top-level change ECO factory data synchronization process.

[0053] Software CI, software DSI and software data files are issued for the first time. Software CI, software DSI and software data files are issued for the first time through zero-change software ECP. They are distributed and circulated after entering the factory. The specific distribution units are obtained according to the configuration of the software circulation unit.

[0054] Software process planning module: During the software information review process, after the software ECP is issued to the factory, the factory starts the first-level planning process. Each professional department of the engineering department conducts an impact analysis on the released or modified software data, identifies whether it is related to this profession, and formulates treatment measures. Figure 3 , specifically including:

[0055] Process planning process verification. After the software ECP is sent to the manufacturing plant system, an integrity check is first performed to confirm whether the synchronized data contains all the ECP data. If it is incomplete, feedback is given to the design institute. If it is complete, the ECP is verified to be zero-changed. If it is not zero-changed, process planning is required. If it is zero-changed, the CI major version in the ECP is verified to be related to the top-level change ECO. If it is related, process planning is required. If it is not related, the circulation process is directly started.

[0056] Software ECP process planning. Adjustments are made based on the factory change process review process, integrity verification is retained, and the review structure list is adjusted. Obtain all resident finished product information and finished product list items based on the ECP-related CI list issued as the list items in the process task. If there is no software CI associated with the ECP, then find the software DSI associated with the ECP, and find the CI based on the software DSI. The person in charge of the engineering and technology department is assigned to the process review and initialize the first-level and second-level reviewers. According to all software CIs associated with the ECP, all finished product drawing numbers of the resident finished product information of each software CI, and the PBS code of the DSI on the EBOM where all finished product drawing numbers are located, the process review process configuration rules are obtained according to the PBS codes of all DSIs to set the reviewers. Create and set the first-level process planning status.

[0057] The first-level flight control and avionics professionals perform the first-level process planning task assignment, in which the assigned list obtains the software CI list from the associated object of ECP. The finished product list with resident finished product information is obtained based on the software list.

[0058] The second-level majors of flight control and avionics receive the first-level process planning task from ECP. When completing the task, they need to verify that the process planning information has been filled in. Field description for filling in process planning. The number corresponds to the finished product drawing number, and the confidentiality level corresponds to the confidentiality level of the finished product. The finished product model corresponds to the model of the finished product, the finished product name corresponds to the name of the finished product, and the finished product location obtains all the DSIs where the finished product is located. CI list The list of software CIs associated with ECP. If there is no software CI associated with ECP, then find the software DSI associated with ECP and find CI according to the software DSI. Validity Obtain the flight validity of the software CI. The change type of CI is checked by the user for each CI. Whether it is related to this major is checked by the user by "Yes" or "No". Only when "Yes" is selected, the first-level planning information below needs to be filled in. If "No" is selected, the following fields that need to be filled in will not be displayed. Whether there is filling work is checked by the user by "Yes" or "No". Whether there is off-site upgrade, the user checks "Yes" or "No". The off-site upgrade is a required item. The associated CI is selected by the user, and multiple selections are allowed. In the pop-up window, you can enter the number and name to search the CI list in the system, and display the number, name, and version. If there are multiple versions, they will be displayed separately, and multiple selections are allowed. The matching changes are selected by the user and are required. If the user selects "No matching", no filling is required. If the user selects "Hardware matching" or "Software matching", if "Hardware matching" is selected, you need to select the matching ECP. In the pop-up window, you can enter the number and name to search the software ECP list in the system, and display the number and name, and multiple selections are allowed. And the matching finished product model is automatically brought out. The user can manually enter the ECP number and the matching finished product model. If "Software matching" is selected, you need to select the matching ECP. In the pop-up window, you can enter the number and name to search the software ECP list in the system, and display the number and name, and multiple selections are allowed. And the matching finished product model is automatically brought out, that is, the "resident finished product model" of ECP. After the upgrade, you can add a line to select the test unit and execution content, or delete a line of test unit and execution content. The test unit is selected by the user, and the selection range of the test unit is consistent with the execution unit of the ECO first-level planning. The execution content is filled in by the user.

[0059] The first-level professional chief reviewer reviews the first-level planning content filled in by the professional. After the second-level professional completes the process planning, the task is transferred to the first-level professional chief review stage. The first-level professional chief reviewer can review the first-level planning content filled in by the professional, and can view the planning content by software CI or professional dimension. If the process planning content is incomplete, the second-level professional can be rejected for modification. If the review is passed, the task can be completed and the task will be transferred to the project chief review stage.

[0060] After the first-level professional is passed, the project chief reviewer receives the project chief review task. In the task, the process planning chief review summary data can be viewed. In the chief review summary, the process planning opinions can be viewed according to the finished product dimension or professional dimension. After the project chief review is passed, the process planning process ends and the circulation process is started for the software distribution unit.

[0061] View process planning results. After completing process planning, you can view the process planning results through the process planning page on the ECP details page of the software.

[0062] Synchronize SERP. After the ECP process planning project is approved, the software ECP first-level planning content will be sent to SERP through system integration.

[0063] MBOM software building blocks: refer to the manual Figure 4 Because software does not exist independently and must be matched with finished products, software does not plan segments and MCI separately, and does not consume materials. It is reflected in the MBOM as the relationship between finished products and software. After the EBOM software management information is released, that is, after the process review and first-level planning are completed, the MCO associated with the finished product and the software is triggered, and the relationship between the finished product and the software is established.

[0064] Software MCO task assignment. After the software change MCO is created, if it is determined that the submission task needs to be started, the reviewer is obtained from the software MCO reviewer configuration according to the finished product prefix associated with the software CI in the MCO and the submission task is started. The subsequent reviewer is selected by the submitter. MCO number return. After the MCO is created, in the process, add a function to return the MCO number to the associated ECP attribute "MCO number".

[0065] Generate association relationships. After the software change MCO is created, extract the software CI-related finished product information to form a finished product and software association relationship table, and compare the software CI involved in the change with the finished product to form a finished product and software association change record. The method for generating a finished product and software association change record is as follows: use the finished product number + software CI number as the benchmark for comparison. If there is no record before, it is a new addition. If there is a record, it is a modification. If it is a new addition, there will only be a value after the change. If it is a modification, determine whether the attributes have changed before and after the change. If there is a change, display the values ​​before and after the change. Among them, the DSI number, if the CI is upgraded, it is necessary to obtain the DSI numbers corresponding to the two CI versions as before and after the change. If the DSI is upgraded, the DSI numbers are listed before and after the change.

[0066] View the change records of the finished product and software association. On the software change MCO review task and details page, the function of viewing the MCO change record is provided. When opened, the finished product and software association change records corresponding to the MCO are displayed. When viewing the MCO change record, the software CI version column is not displayed; on the software change MCO details page, the function of opening MPE and invalidating MCO is not provided.

[0067] When the software change MCO is released, the finished product and software association table and the finished product and software association change record table are published to the global database, and the SERP interface is called to push the MCO notification. When released, the circulation process is started for the software distribution unit, and the circulation unit obtains it from the software distribution unit configuration.

[0068] Software information viewing module: In the product EBOM\MBOM structure, the function of viewing the associated software of the finished product is provided to display the associated software information of the finished product. It can also be filtered by batch. Under model control, in the product EBOM / MBOM structure, an associated software tab is added to the right side of the finished product to display all the software information associated with the finished product. From the finished product and software association table, the associated software is obtained by the finished product CP code and displayed in the associated software list. If the batch batch number has a value, only the entries containing the input batch number are displayed in the associated software list.

[0069] Software data statistics summary module: Model control - statistical report, add software statistical report function, provide software version inventory report, software finished product related statistical report, software ECP statistics, whole machine software version configuration table, software executable file query statistics and other functions.

[0070] The software BBOM management module: refer to the instruction manual Figure 5 After the physical filling, installation and upgrade of the software are completed, the corresponding software upgrade and filling records will be generated. In the BBOM, the execution records can be obtained in real time through the finished product or software DSI. Because the software does not exist independently, it must be matched with the finished product. The flight can only be determined after the finished product is installed on the aircraft. According to the AO where the resident finished product is located, the software filling and upgrade records associated with the finished product are checked to determine the software installation version information of the flight. At the same time, an interface is provided for the institute to obtain software upgrade and filling execution information.

[0071] Get the software execution record. Get the resident finished product number based on the software DSI, find the finished product installation record based on the batch and finished product number, and get the finished product quality number. Get the software filling and upgrade records based on the finished product quality number.

[0072] Execution information feedback. The software technical status management system provides an interface for the design institute to obtain software upgrade and filling execution information in real time, so as to clarify the execution status of related software and support the design institute to conduct design change impact analysis.

[0073] The basic data configuration module: software circulation unit configuration. In the menu of model control-system support-system maintenance, in the system configuration function, configure the newly added type of software distribution, and add the configuration of software distribution unit. Section is the software distribution unit, the key value is the name of the distribution unit, such as the inspection and testing department, the purchasing department, etc., and the value value is the unit code.

[0074] In System Support - System Maintenance - System Configuration, in Software Distribution Type, add Software MCO Reviewer Configuration, and configure MCO Reviewers based on the CI prefix. Fill in the Software MCO Reviewer in Section, the key value is the flexible CI prefix, and the value is the reviewer employee number.

[0075] Data management module: Provides data exchange functions. Based on open standards, the finished product technical status management system for manufacturing provides common functions such as service search, access, routing, etc. It also has built-in XML-based data objects to facilitate data interaction and interoperability between services, and supports information (data) integration, process integration and application integration. Support enterprise-level service quality. The enterprise-level service quality supported includes message security, failure recovery, status diagnosis, service management, service auditing, reliable message transmission, transaction integrity, etc., and provides data exchange process and data tracking capabilities. Provide data format conversion function. Provides a graphical visualization of heterogeneous data format conversion mapping tool that can easily and quickly convert data from one format to another. Input data and output data can be converted between different formats, such as structured XML, non-XML or Java object data, so that heterogeneous applications can be quickly integrated without considering the format used to represent the data. Provides full support for REST. It supports REST access provided by different systems and can encapsulate existing business applications into REST for reuse. Supports common REST standard protocols. Uses standard REST for data interaction. Standard REST is a relatively mature data exchange method suitable for cross-platforms. It can reduce the connection technology requirements and operating platform restrictions. REST uses XML for data exchange at the bottom layer, which is easy to maintain and interact.

[0076] The system also integrates a variety of commonly used system adapters and provides adapter customization and development capabilities: it integrates a variety of common adapters in enterprise applications, such as file adapters that support structured and unstructured file reading and writing, supports multiple database access such as Oracle, DB2, SQL Server, SyBase, MySql, Excel, Access and other database adapters, supports multiple communication protocols such as FTP, SMTP / POP3, REST and other communication adapters, etc. Through ready-made adapters, it reduces the programmer's development workload and achieves rapid application integration capabilities.

[0077] The system also integrates monitoring and management functions: it provides a browser-based management console that can query the status of monitoring nodes, services, components and business processes and monitor and manage them.

[0078] In summary, after reading the present invention document, ordinary technicians in this field can make various other corresponding transformation schemes based on the technical scheme and technical concept of the present invention without creative mental labor, which all fall within the scope of protection of the present invention.

Claims

1. A software technical status management system, characterized by: It includes software information review module, software process planning module, software MBOM construction module, software BBOM management module and basic data configuration module; The software information review module is used to review the software information, that is, when the creation of the software is reviewed by the EBOM of the design institute, the software CI, DSI and its related files are synchronized to the manufacturing plant through the software ECP. After the manufacturing plant completes the processability review, the review opinions are fed back to the design institute to complete the software information review; The software process planning module is used for the professional departments of the engineering department to conduct impact analysis on the released or modified software data during the software information review process, identify whether it is related to the profession, and formulate treatment measures, including: process planning process verification, software ECP process planning, process planning result viewing and SERP synchronization; wherein, the process planning process verification includes verification of integrity, verification of whether the ECP is zero change and verification of whether the CI major version in the ECP has an associated top-level change ECO; the software ECP process planning includes: review structure list acquisition and adjustment, setting review personnel, first-level process planning, second-level professional process planning, first-level professional chief review, project chief review review and circulation process; The software MBOM construction module is used to start the software MCO after completing the process review and the first-level planning, and complete the creation and update of the association relationship between the finished product and the software; the creation and update of the association relationship between the finished product and the software specifically refers to: after the software change MCO is created, the software CI-associated finished product information is extracted to form a finished product and software association relationship table, and for the software CI involved in the change, its association with the finished product is compared to form a finished product and software association change record; for the MCO caused by the change, the task is initiated to the corresponding process personnel to confirm the change information of the finished product and the software, and when the MCO is released, the distribution and circulation process is started for the software circulation unit, and the MCO information is released to the SERP system at the same time; The software BBOM management module is used to obtain the execution record in real time through the finished product or software DSI in the BBOM, and when the finished product is installed on the aircraft, determine the flight, and check the software filling and upgrade records associated with the finished product according to the AO where the resident finished product is located, so as to determine the software installation version information of the flight, and provide an interface for obtaining software upgrade and filling execution information within the institute; The basic data configuration module is used to provide software distribution unit configuration function, software MCO reviewer configuration function and process review flow configuration function.

2. A software technical status management system according to claim 1, characterized in that: It also includes a software information viewing module and a software data statistics summary module. The software information viewing module is used to provide a finished product related software viewing function in the product EBOM\MBOM structure, display the finished product related software information, and filter by batch; the software data statistics summary module is used to provide software data statistics summary function, provide software version inventory report, software finished product related statistics report, software ECP statistics, whole machine software version configuration table and software executable file query statistics function.

3. A software technical status management system according to claim 1, characterized in that: The software information review module is specifically used for software top-level synchronization and initial issuance of software CI, software DSI and software data files; wherein software top-level synchronization specifically refers to: sending the aircraft PBS software top-level nodes and software CI in the system to the manufacturer in batches; once the software top-level nodes and software CI are issued, the software top-level node changes, software CI attribute changes, software CI additions and deletions are implemented through the top-level change ECO factory data synchronization process; the initial issuance of software CI, software DSI and software data files specifically refers to: issuing through zero-change software ECP, distributing and circulating after entering the manufacturer, and the specific distribution units are obtained according to the software circulation unit configuration.

4. A software technical status management system according to claim 1, characterized in that: The process planning process verification specifically includes: after the software ECP is sent to the manufacturing plant system, an integrity check is first performed to confirm whether the synchronized data contains all the ECP data. If incomplete, feedback is given to the design institute. If complete, the ECP is verified to be zero-changed. If not, process planning is required. If zero-changed, the CI major version in the ECP is verified to be associated with the top-level change ECO. If so, process planning is required. If not, the circulation process is directly started.

5. A software technical status management system according to claim 1, characterized in that: The software ECP process planning specifically includes: Adjustment of the review structure list acquisition: obtain all the resident finished product information finished product list items according to the ECP-related CI list issued, as the list items in the process task; if there is no software CI associated with the ECP, then find the software DSI associated with the ECP, and find the CI according to the software DSI; Set up reviewers: Assign the person in charge of the engineering technology department to the process review meeting, initialize the first-level and second-level reviewers, and set up reviewers according to the process review process configuration rules obtained according to the PBS codes of all DSIs based on all software CIs associated with the ECP, all finished product drawing numbers of the resident finished product information of each software CI, and the PBS codes of the DSIs on the EBOM where all the finished product drawing numbers are located; Level 1 process planning: Flight management and avionics level 1 professionals are responsible for the allocation of level 1 process planning tasks. The allocated list obtains the software CI list from the associated objects of ECP, and obtains the finished product list containing the resident finished product information based on the software list. Secondary professional process planning: Secondary professionals of flight control and avionics receive the first-level process planning task from ECP. When completing the task, they need to verify that the process planning information has been filled in; First-level professional reviewer: After the second-level professional completes the process planning, the first-level professional reviewer reviews the first-level planning content filled in by the professional, and checks the planning content according to the software CI or professional dimension; if the process planning content is incomplete, the second-level professional can be rejected for modification; Project Chief Review: The project chief reviewer receives the project chief review task. In the task, he / she checks the process planning chief review summary data. In the chief review summary, he / she checks the process planning opinions according to the finished product dimension or the professional dimension.

6. A software technical status management system according to claim 1, characterized in that: The method for generating change records associated with finished products and software is: compare the finished product number + software CI number as the benchmark. If there is no previous record, it is a new addition. If there is a record, it is a modification. If it is a new addition, there will be a value only after the modification. If it is a modification, determine whether the attributes have changed before and after the modification. If there is a change, display the values ​​before and after the modification. Among them, the DSI number, if the CI is upgraded, it is necessary to obtain the DSI numbers corresponding to the two CI versions as before and after the modification. If the DSI is upgraded, the DSI numbers are listed before and after the modification.

7. A software technical status management system according to claim 1, characterized in that: The software BBOM management module includes a module for obtaining software execution records, that is, obtaining the resident finished product number according to the software DSI; finding the finished product installation record according to the batch and finished product number, and obtaining the finished product quality number; and obtaining the software filling and upgrade records according to the finished product quality number.

8. A software technical status management system according to claim 1, characterized in that: This system uses standard REST for data interaction, and the underlying REST uses XML for data exchange.

9. A software technical status management system according to claim 1, characterized in that: It also includes a data management module for realizing data exchange, data tracking and data format conversion.

Images