CN111190819B - State control method for airborne software test project - Google Patents
State control method for airborne software test project Download PDFInfo
- Publication number
- CN111190819B CN111190819B CN201911359037.2A CN201911359037A CN111190819B CN 111190819 B CN111190819 B CN 111190819B CN 201911359037 A CN201911359037 A CN 201911359037A CN 111190819 B CN111190819 B CN 111190819B
- Authority
- CN
- China
- Prior art keywords
- state
- library
- test
- item
- project
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a state control method of an onboard software test project, which comprises the following steps: establishing a state library of the test items according to a preset basic library of the test items, and determining the key point states of the software test items in the test process; determining the corresponding relation between the test items and the states according to the state library of the test items; according to the unique identification of the basic library and the test items in the basic library, establishing a problem library of the test items, extracting problem information of the test items in the basic library, and identifying a problem state; carrying out zero-resetting treatment on the non-zero-resetting problem in the problem library, and mapping the zero-resetting state into a state library; and performing item junction processing on the key point states in the state library according to the item junction conditions of the test items. The embodiment of the invention solves the problems of unclear change test state and problem state of multi-version software, uncontrolled multi-round software test process of software test project, return-to-zero time of project legacy problem, uncertainty of trace source and the like.
Description
Technical Field
The present application relates to the field of, but not limited to, on-board software testing technology, and in particular, to a method for controlling a state of an on-board software test project.
Background
With the development of modern aircrafts, the requirements for functions, performance, safety and the like of aircrafts are also changed and increased, and even on the same type of machine type, each system may show a plurality of different states.
During development of an aircraft system, changes in the top level requirements may result in changes in the state of system software, changes in the state of system hardware, even changes in the state of other systems cross-linked thereto, and so forth. While on-board software acts as a key component of the aircraft system, changes in its state directly affect the functionality, performance and safety of the aircraft.
The on-board software test is an important link in the life cycle of the software, is a key step of software quality assurance, and is an important assurance of the software before the software is put into operation. However, with the existing different installment states of the same aircraft and different system function requirements, a plurality of software version states are generated, and meanwhile, the functions are overlapped, and the problems of left projects of different versions are caused due to software design factors, software testing environment factors and the like. Because modern work output requirements are high, project nodes are urgent, user demands change fast, software test project members are forced to put most of time into software test technology and test work, and no attention is paid to test project states of all versions of airborne software, problem tracking of left problems, management of zeroing states and the like, so that projects are free of traceability, unobservable, state confusion, disorder of problem management and untracked zeroing possibly occur in serious cases, and software reliability and aircraft safety are affected.
Disclosure of Invention
In order to solve the technical problems, the embodiment of the invention provides a state control method for an airborne software test project, which is used for improving the state management efficiency of the airborne software test project and solving the problems of unclear change test state and problem state of multi-version software, uncontrolled multi-round software test process of the software test project, return-to-zero time of project legacy problems, uncertainty of trace-back sources and the like.
The embodiment of the invention provides a state control method of an airborne software test project, which comprises the following steps:
establishing a state library of the test item according to a preset basic library of the test item, and determining the key point state of the software test item in the test process;
determining the corresponding relation between the test items and the states according to the state library of the test items;
according to the unique identification of the basic library and the test items in the basic library, establishing a problem library of the test items, extracting problem information of the test items from the basic library, and identifying a problem state;
carrying out zero-resetting treatment on the non-zero-resetting problem in the problem library, and mapping a zero-resetting state into the state library;
and performing item junction processing on the key point states in the state library according to item junction conditions of the test items.
Optionally, in the state control method of the on-board software test item as described above, the method further includes:
establishing a basic library of test items, and determining unique identifiers of the test items according to information in the basic library, wherein the unique identifiers of the test items comprise: model name, system name, subsystem name, software name, and version number.
Optionally, in the state control method of the on-board software test item as described above,
the keypoint states include: configuring a management state, a quality assurance state, a multiple regression testing state, a testing document state, a project problem state and a project legacy problem zeroing state;
optionally, in the state control method of the on-board software test item as described above, the method further includes:
and establishing a mapping relation between the key point state in the state library and the state in the basic library.
Optionally, in the method for controlling the state of the on-board software test item as described above, the problem information of the test item includes a problem type, a level and a content of the test item, and the problem state includes zero-returning and non-zero-returning.
Optionally, in the method for controlling the state of the on-board software test item as described above, the performing a zeroing process on the non-zeroed problem in the problem library includes:
and defining the problem with the state of non-return to zero in the problem library as a project leave-in problem, and carrying out state control on the project leave-in problem.
Optionally, in the method for controlling the status of the on-board software test project as described above, the performing status control on the problem left by the project includes:
extracting problem information of the project legacy problem;
carrying out zeroing treatment on the project legacy problems according to the extracted problem information and the content of the onboard software, wherein the zeroing treatment comprises modifying the content of the onboard software according to the extracted problem information;
according to the extracted problem information and the content of the zeroed airborne software, testing and verifying the zeroed airborne software;
and establishing a return-to-zero traceability relation according to the test verification result, and changing the state of the project legacy problem to return-to-zero.
Optionally, in the method for controlling the state of the on-board software test item as described above, the performing the item-joining process on the key point states in the state library according to the item-joining condition of the test item includes:
extracting a decisive state in the test process from the state library, carrying out logic operation on the decisive state, and judging whether a test item meets a junction item condition according to an operation result;
when the test item does not accord with the item connection condition, searching a state affecting the item connection through a user interface, and processing the state to finish the state;
and when the test item meets the item connection condition, determining that the test item completes the item connection.
The state control method of the airborne software test project solves the problems of unclear state and problem state change of multi-version software, uncontrollable multi-round software test process of the software test project, uncertainty of return time and trace source of the project problem, and the like of the software test project, ensures that the state of each software test project is clear, the processing result of the project problem is clear, the traceability of the project problem is strong, directly improves the state management efficiency of the airborne software test project, and indirectly improves the reliability of the software, aiming at the software test project with more system/software requirement changes, more software states, incapacity of timely processing the project problem and long return period of the project problem. The scheme of the embodiment of the invention has the following advantages:
a) The state of the on-board software test project can be accurately checked in real time, and unfinished process nodes can be accurately checked;
b) Specific information and zeroing states of the problems can be checked in a problem database according to the uniqueness of the onboard software;
c) Carrying out problem tracking on the carry-over problems of each version state of the airborne software test project, and tracing the carrier state after zeroing;
d) The user interface is defined, so that the state information of the item focused by the user can be viewed in a concise and clear mode;
e) The workload of the testers is reduced, and the testing efficiency and the accuracy are improved;
f) The method is high in universality and can be applied to management methods with uncertain user requirements and multiple finished product states in other fields;
g) The human resources are reduced, and the state management efficiency and the correctness of the airborne software test project are improved.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate and do not limit the invention.
FIG. 1 is a flow chart of a method for controlling the state of an onboard software test project according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a method for controlling the status of an on-board software test item according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a mapping relationship between a state library and a base library according to an embodiment of the present invention;
FIG. 4 is a flow chart of status control for project legacy issues in accordance with an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail hereinafter with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be arbitrarily combined with each other.
The following specific embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Fig. 1 is a flowchart of a method for controlling a state of an airborne software test item according to an embodiment of the present invention, and fig. 2 is a schematic diagram of a method for controlling a state of an airborne software test item according to an embodiment of the present invention. The state control method for the airborne software test project provided in the embodiment may include the following steps:
s110, establishing a state library of a test item according to a preset basic library of the test item, and determining the key point state of the software test item in the test process;
s120, determining the corresponding relation between the test items and the states according to the state library of the test items;
s130, establishing a problem base of the test item according to the unique identifiers of the base and the test item in the base, extracting problem information of the test item in the base, and identifying a problem state;
s140, carrying out zero-resetting treatment on the non-zero problem in the problem library, and mapping the zero-resetting state into the state library;
s150, performing item junction processing on the key point states in the state library according to item junction conditions of the test items.
Optionally, before S110, the method provided by the embodiment of the present invention may further include:
s100, a basic library of test items is established, unique identifiers of the test items are determined according to information in the basic library, and the unique identifiers of the test items comprise: model name, system name, subsystem name, software name, and version number.
Optionally, the key point states in the embodiment of the present invention may include: configuring a management state, a quality assurance state, a multiple regression testing state, a testing document state, a project problem state and a project legacy problem zeroing state;
correspondingly, the method provided by the embodiment of the invention can further comprise the following steps:
and establishing a mapping relation between the key point state in the state library and the state in the basic library. Fig. 3 is a schematic diagram of a mapping relationship between a state library and a base library according to an embodiment of the present invention.
Optionally, the problem information of the test item in the embodiment of the present invention includes a problem type, a level and a content of the test item, and the problem state includes zero-reset and non-zero-reset.
Optionally, the implementation manner of performing the zeroing processing on the non-zeroed problem in the problem base in S140 in the embodiment of the present invention may include:
and defining the problem with the state of non-return to zero in the problem library as a project leave-in problem, and performing state control on the project leave-in problem.
FIG. 4 is a flow chart of status control for project legacy issues in accordance with an embodiment of the present invention. In practical applications, as shown in fig. 4, a specific embodiment for performing state control on a project legacy problem may include:
s1, extracting problem information of project legacy problems;
s2, carrying out zeroing treatment on project legacy problems according to the extracted problem information and the content of the airborne software, wherein the zeroing treatment comprises the step of modifying the content of the airborne software according to the extracted problem information;
s3, testing and verifying the zeroed airborne software according to the extracted problem information and the content of the zeroed airborne software;
and S4, establishing a return-to-zero traceability relation according to the test verification result, and changing the state of the project legacy problem to return to zero.
Optionally, the implementation manner of S150 in the embodiment of the present invention may include:
s1, extracting a decisive state in the test process from a state library, carrying out logic operation on the decisive state, and judging whether a test item meets a junction item condition according to an operation result; the logical operation may be a logical AND, that is, all states are complete conditions, and are considered complete;
s2, when the test item does not accord with the item connection condition, searching the state affecting the item connection through a user interface, and processing the state to finish the state;
and S3, when the test item meets the junction item condition, determining that the test item finishes the junction item.
The embodiment of the invention provides a state management method of an onboard software test project for the first time, which aims at the software test project with multiple system/software requirement changes, multiple software states, incapability of timely processing project problems and long return-to-zero period of project problem, solves the problems of unclear change test states and problem states of multi-version software, uncontrollable multi-round software test processes of the software test project, uncertainty of return-to-zero time and trace source of the project problem and the like, ensures that the states of each software test project are clear, the project problem processing result is clear, the traceability of the project problem is strong, directly improves the state management efficiency of the onboard software test project, and indirectly improves the reliability of software.
The state management method of the on-board software test project has the following characteristics:
a) A management method with more changes and more software states based on system/software requirements;
b) The whole management process is optimized in a flow mode through the uniqueness of the project, and the condition that the project is judged by repeatedly consulting related data is avoided;
c) Establishing information association concerned by a manager through the uniqueness of the item, and displaying the state information of the item through an interface;
d) The problem state of the project and the zeroing condition of the left-over problem are effectively managed;
e) Correctly tracking the carrier after the project leaving problem is zeroed;
f) The method has strong universality and can be applied to management methods with uncertain user demands and multiple finished product states in other fields;
g) The human resources are reduced, and the state management efficiency and the correctness of the airborne software test project are improved.
The following describes, by way of a specific implementation example, an implementation manner of a state control method for an on-board software test item provided by an embodiment of the present invention. The schematic diagram of the state management method of the on-board software test project is shown in fig. 2, and the specific implementation mode is as follows:
step 1, a test item basic library is established for multi-state airborne software test items, and the item basic library information comprises model names, system names, subsystem names, software names, versions, testers, quality assurance personnel, software levels, management state classification and the like; determining the unique identifier of the software test item, namely the uniqueness of the test item according to the component elements in the basic library, and establishing a direct relation with other elements through the identifier of each test item, so that a user can conveniently and intuitively check the related information of a certain software test item in real time at a user interface; determining 'model name & system name & subsystem name & software name & version' as a unique identifier of the on-board software test item;
step 2, establishing a state demand library of the airborne software test project, and determining key points in the airborne software test project process, such as configuration management state, quality assurance state, multiple-round regression test state, test document state, project problem state, project legacy problem return-to-zero state and the like; the state data source is taken from a basic library of the test project, and a mapping relation is established between key names in the state demand library and management states in the project basic library, so that data input of a manager and data viewing of a user are facilitated; FIG. 3 is a mapping relationship diagram of a status requirement library and a project base library;
step 3, establishing an item problem library according to the unique identification of the software test item, extracting information such as item problem types, levels, contents and the like from an item base library, and identifying the problem state: zero-return problem, non-zero-return problem; defining the problem with the state of non-return to zero as a project leave-in problem, and carrying out state management on the project leave-in problem;
step 4, the software development side takes information such as the type, the level, the content and the like of the project legacy problems as zeroing input, correspondingly changes the source program/document and zeroes the problems; the software testing party verifies and confirms whether the problem returns to zero, establishes a return-to-zero tracking relationship in a corresponding project legacy problem database, and traces back a return-to-zero source so as to be convenient for later reference; FIG. 4 is a flow chart of project carryover problem and return-to-zero tracking;
step 5, according to the management requirement of the project junction of the airborne software test project, decisive elements are extracted from the project state demand library, logic operation is carried out on the decisive elements, and whether the software test project is completed/junction is judged, so that the expected state is achieved; if not, the user/manager can check the factors influencing the result through the user interface, so that the software test items are in a controllable range, and the software test items can be finished according to the quality guarantee of the nodes, thereby directly improving the state management efficiency of the airborne software test items and indirectly improving the reliability of the software.
Although the embodiments of the present invention are described above, the embodiments are only used for facilitating understanding of the present invention, and are not intended to limit the present invention. Any person skilled in the art can make any modification and variation in form and detail without departing from the spirit and scope of the present disclosure, but the scope of the present disclosure is to be determined by the appended claims.
Claims (6)
1. The state control method of the on-board software test project is characterized by comprising the following steps of:
establishing a state library of the test item according to a preset basic library of the test item, and determining the key point state of the software test item in the test process; the keypoint states include: configuring a management state, a quality assurance state, a multiple regression testing state, a testing document state, a project problem state and a project legacy problem zeroing state;
determining the corresponding relation between the key point state of the test item and the corresponding state in the basic library according to the state library of the test item, so as to establish a mapping relation between the key point state in the state library and the state in the basic library;
according to the unique identification of the basic library and the test items in the basic library, establishing a problem library of the test items, extracting problem information of the test items from the basic library, and identifying a problem state;
carrying out zero-resetting treatment on the non-zero-resetting problem in the problem library, and mapping a zero-resetting state into the state library;
and performing item junction processing on the key point states in the state library according to item junction conditions of the test items.
2. The method for controlling the state of an on-board software test item according to claim 1, further comprising:
establishing a basic library of test items, and determining unique identifiers of the test items according to information in the basic library, wherein the unique identifiers of the test items comprise: model name, system name, subsystem name, software name, and version number.
3. The method of claim 1, wherein the problem information of the test item includes a problem type, a level, and a content of the test item, and the problem status includes zero-reset and non-zero-reset.
4. The method for controlling the status of an on-board software test item according to claim 3, wherein the zeroing the non-zeroed problem in the problem library comprises:
and defining the problem with the state of non-return to zero in the problem library as a project leave-in problem, and carrying out state control on the project leave-in problem.
5. The method for controlling the status of an on-board software test item according to claim 4, wherein said performing status control on said item-carried-over problem comprises:
extracting problem information of the project legacy problem;
carrying out zeroing treatment on the project legacy problems according to the extracted problem information and the content of the onboard software, wherein the zeroing treatment comprises modifying the content of the onboard software according to the extracted problem information;
according to the extracted problem information and the content of the zeroed airborne software, testing and verifying the zeroed airborne software;
and establishing a return-to-zero traceability relation according to the test verification result, and changing the state of the project legacy problem to return-to-zero.
6. The method for controlling the state of an on-board software test item according to claim 1, wherein the performing the item-joining process on the key point states in the state library according to the item-joining condition of the test item comprises:
extracting a decisive state in the test process from the state library, carrying out logic operation on the decisive state, and judging whether a test item meets a junction item condition according to an operation result;
when the test item does not accord with the item connection condition, searching a state affecting the item connection through a user interface, and processing the state to finish the state;
and when the test item meets the item connection condition, determining that the test item completes the item connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911359037.2A CN111190819B (en) | 2019-12-25 | 2019-12-25 | State control method for airborne software test project |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911359037.2A CN111190819B (en) | 2019-12-25 | 2019-12-25 | State control method for airborne software test project |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111190819A CN111190819A (en) | 2020-05-22 |
| CN111190819B true CN111190819B (en) | 2023-05-23 |
Family
ID=70707595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911359037.2A Active CN111190819B (en) | 2019-12-25 | 2019-12-25 | State control method for airborne software test project |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111190819B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009252167A (en) * | 2008-04-10 | 2009-10-29 | Ricoh Co Ltd | Test item creation device, test item creation system, test item creation method and test item creation program |
| CN103257918A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Project test procedure management method based on software testing and evaluation platform |
| CN103530232A (en) * | 2013-10-24 | 2014-01-22 | 北京经纬恒润科技有限公司 | Method and device for building software testing management framework |
| CN106709656A (en) * | 2016-12-28 | 2017-05-24 | 中国航空工业集团公司西安飞机设计研究所 | System architecture-based avionics system technology state control method |
| CN108573365A (en) * | 2017-03-07 | 2018-09-25 | 北京空间技术研制试验中心 | The service-oriented and flow state digitized management method of integration test |
| CN109657224A (en) * | 2019-01-04 | 2019-04-19 | 北京空间技术研制试验中心 | Spacecraft-testing based on Data Analysis Platform reports automatic generation method |
| US10318412B1 (en) * | 2018-06-29 | 2019-06-11 | The Travelers Indemnity Company | Systems, methods, and apparatus for dynamic software generation and testing |
| CN109889585A (en) * | 2019-02-01 | 2019-06-14 | 中电科仪器仪表有限公司 | A kind of the operating status remote supervision system and method for electronic testing instrument |
| US10387297B1 (en) * | 2016-06-15 | 2019-08-20 | Amdocs Development Limited | System, method, and computer program for end-to-end test management of a software testing project |
-
2019
- 2019-12-25 CN CN201911359037.2A patent/CN111190819B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009252167A (en) * | 2008-04-10 | 2009-10-29 | Ricoh Co Ltd | Test item creation device, test item creation system, test item creation method and test item creation program |
| CN103257918A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Project test procedure management method based on software testing and evaluation platform |
| CN103530232A (en) * | 2013-10-24 | 2014-01-22 | 北京经纬恒润科技有限公司 | Method and device for building software testing management framework |
| US10387297B1 (en) * | 2016-06-15 | 2019-08-20 | Amdocs Development Limited | System, method, and computer program for end-to-end test management of a software testing project |
| CN106709656A (en) * | 2016-12-28 | 2017-05-24 | 中国航空工业集团公司西安飞机设计研究所 | System architecture-based avionics system technology state control method |
| CN108573365A (en) * | 2017-03-07 | 2018-09-25 | 北京空间技术研制试验中心 | The service-oriented and flow state digitized management method of integration test |
| US10318412B1 (en) * | 2018-06-29 | 2019-06-11 | The Travelers Indemnity Company | Systems, methods, and apparatus for dynamic software generation and testing |
| CN109657224A (en) * | 2019-01-04 | 2019-04-19 | 北京空间技术研制试验中心 | Spacecraft-testing based on Data Analysis Platform reports automatic generation method |
| CN109889585A (en) * | 2019-02-01 | 2019-06-14 | 中电科仪器仪表有限公司 | A kind of the operating status remote supervision system and method for electronic testing instrument |
Non-Patent Citations (5)
| Title |
|---|
| 基于CMMI的软件测试项目过程管理;刘文红等;《飞行器测控学报》;20060630(第03期);全文 * |
| 基于CPN的多步骤攻击警报关联方法;吕林涛等;《计算机工程》;20081205(第23期);全文 * |
| 大型交互式领域应用软件白盒测试的组织和实施;柳永坡等;《计算机应用研究》;20071015(第10期);全文 * |
| 测试状态控制系统在航天领域中的应用与研究;胡博等;《中国设备工程》;20181025(第20期);全文 * |
| 航天器数字化综合测试状态管理系统设计;张威等;《航天器工程》;20170815(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111190819A (en) | 2020-05-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108614770B (en) | Automatic test assertion method, device, storage medium and equipment | |
| US8151248B1 (en) | Method and system for software defect management | |
| US8151247B2 (en) | Test data management | |
| CN111563041B (en) | Test case on-demand accurate execution method | |
| CN105354239A (en) | Configuration data processing model based processing center data stream processing method | |
| CN111736865B (en) | Database upgrading method and system | |
| CN112131116B (en) | Automatic regression testing method for embedded software | |
| CN109101410B (en) | Risk drive testing method and device and computer readable storage medium | |
| US20160314061A1 (en) | Software Defect Detection Identifying Location of Diverging Paths | |
| CN114116801A (en) | Data list checking method and device | |
| KR102418796B1 (en) | FMEA failure mode recommend system | |
| CN111190819B (en) | State control method for airborne software test project | |
| CN112506802A (en) | Test data management method and system | |
| CN116795425A (en) | Chip front-end development system and method based on git | |
| CN109165155B (en) | Software defect repairing template extraction method based on cluster analysis | |
| CN111176995A (en) | Test method and test system based on big data test case | |
| CN112256978B (en) | Data processing method, device and medium based on data model | |
| CN114169544A (en) | Management method for MSI analysis of civil aircraft planned maintenance requirements | |
| CN114329116A (en) | Artificial intelligence-based intelligent park resource matching degree analysis method and system | |
| CN110177006B (en) | Node testing method and device based on interface prediction model | |
| CN112948956A (en) | Vehicle parameter generation method, device and equipment | |
| CN112347095B (en) | Data table processing method, device and server | |
| CN116401113B (en) | Environment verification method, device and medium for heterogeneous many-core architecture acceleration card | |
| US20180239661A1 (en) | Generating targeted analysis results in a support system | |
| CN113610117B (en) | Underwater sensing data processing method and system based on depth data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |