CN112416337B - Software architecture development system for aerospace embedded system - Google Patents
Software architecture development system for aerospace embedded system Download PDFInfo
- Publication number
- CN112416337B CN112416337B CN202011255814.1A CN202011255814A CN112416337B CN 112416337 B CN112416337 B CN 112416337B CN 202011255814 A CN202011255814 A CN 202011255814A CN 112416337 B CN112416337 B CN 112416337B
- Authority
- CN
- China
- Prior art keywords
- software
- module
- verification
- reusable component
- reusable
- 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
- 238000011161 development Methods 0.000 title claims abstract description 28
- 238000012795 verification Methods 0.000 claims abstract description 66
- 238000004806 packaging method and process Methods 0.000 claims abstract description 23
- 238000000605 extraction Methods 0.000 claims abstract description 7
- 230000007547 defect Effects 0.000 claims description 57
- 238000000034 method Methods 0.000 claims description 30
- 238000004458 analytical method Methods 0.000 claims description 24
- 238000013523 data management Methods 0.000 claims description 18
- 230000006854 communication Effects 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 17
- 230000006870 function Effects 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 14
- 238000003745 diagnosis Methods 0.000 claims description 13
- 238000012986 modification Methods 0.000 claims description 12
- 230000004048 modification Effects 0.000 claims description 12
- 230000008439 repair process Effects 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 9
- 238000010200 validation analysis Methods 0.000 claims description 9
- 238000012300 Sequence Analysis Methods 0.000 claims description 7
- 239000008186 active pharmaceutical agent Substances 0.000 claims description 6
- 238000006243 chemical reaction Methods 0.000 claims description 6
- 238000007726 management method Methods 0.000 claims description 6
- 230000007704 transition Effects 0.000 claims description 5
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 4
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 238000010276 construction Methods 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 230000002452 interceptive effect Effects 0.000 claims description 3
- 230000004807 localization Effects 0.000 claims 1
- 238000005067 remediation Methods 0.000 claims 1
- 238000012546 transfer Methods 0.000 claims 1
- 238000013461 design Methods 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000013522 software testing Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- 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/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a software architecture development system for an aerospace embedded system, which comprises: the information extraction module is used for extracting and classifying software key information in the space model software requirement document; the modeling verification module is used for formally modeling, verifying and packaging the key information of the software to obtain a reusable component of the software; a software component library for storing the reusable component; a frame generation module for constructing a software code frame, the code frame being composed of reusable components called from a software component library; the software code editing module is used for editing the software code according to the business logic, the control logic and the algorithm logic of the software under the software code framework to generate the executable software.
Description
Technical Field
The invention belongs to the technical field of software engineering, and particularly relates to a software architecture development system for an aerospace embedded system, which is applied to the development process of the aerospace embedded software.
Background
With the high-speed development of aerospace application, the complex task demands require algorithms and processes of the aerospace embedded software to be highly integrated and intelligent, the software scale and complexity are further improved, and higher requirements are put on the uniformity of a software architecture and the reliability of the software. At present, the development of the space embedded software mainly adopts a task customization development mode, and because different software architectures are used, the inheritance among model software is weaker, and the development efficiency of the software and the quality of software products are affected.
For the software development architecture problem, even if the software architecture of the former model is inherited, the reliability and safety design problems such as inconsistent implementation, inconsistent time sequence and the like of the common resource module interface in the software architecture can influence the reliability of software and the quality of software products, and the problems are difficult to be found by only relying on simple software development and software testing work.
Disclosure of Invention
In view of the above analysis, the invention aims to disclose a software architecture development system for an aerospace embedded system, which solves the problems that the general embedded system software architecture is lacking in the field of aerospace embedded software engineering and the reliability of the software architecture is improved.
The invention discloses a software architecture development system for an aerospace embedded system, which comprises:
the information extraction module is used for extracting and classifying software key information in the space model software requirement document;
the modeling verification module is used for formally modeling, verifying and packaging the key information of the software to obtain a reusable component of the software;
a software component library for storing the reusable component;
a frame generation module for constructing a software code frame, the code frame being composed of reusable components called from a software component library;
and the software code editing module is used for editing the software code according to the business logic, the control logic and the algorithm logic of the software under the software code framework to generate executable software.
Further, the system also comprises a software defect discovery module, which is used for carrying out defect detection on the generated executable software according to an expert knowledge base, and locating the defect position to generate a defect report so as to assist the defect repair of the executable software.
Further, the system also comprises an autonomous diagnosis module for monitoring the running process of the executable software on line and performing autonomous diagnosis, fault location and fault repair.
Further, the modeling verification module comprises a verification criterion sub-module, a modeling sub-module, a verifier and a packaging sub-module;
the verification criterion submodule is used for establishing a software form verification criterion according to the software key information;
the method comprises the steps of building a sub-module, wherein the sub-module is used for generating a reusable component of software, and the reusable component realizes multi-level multiplexing from a software architecture;
the verifier is used for formally verifying the reusable component according to established software formal verification criteria;
the packaging submodule is used for packaging the reusable component passing the verification;
specifically, the verifier judges whether the formal verification criterion accords with the state transition and the clock constraint of the reusable component, if so, the reusable component is output to the packaging submodule for packaging; if the state transition is not matched or/and the clock constraint is not matched, the reusable component is returned to the building sub-module to carry out state parameter modification or/and time parameter modification, and then returned to the verifier to carry out re-verification.
Further, the construction process of the verifier comprises the following steps:
establishing a modifiable attribute table; according to the functional characteristics, interface states and communication processes realized by the reusable components, abstracting the modifiable attribute of the reusable components in a form of a table aiming at each component;
establishing a reusable component XML file; determining the working state of the reusable components, triggering events, clock constraint, control flow setting and state conversion events, modeling by using a formalization method of a time automaton model, and generating a reusable component XML file by each reusable component;
establishing an association relation; associating the modifiable attribute table with the reusable component XML file through field matching; the user realizes the automatic modification of the reusable component XML file by modifying the component attribute table;
the reusable component XML file is imported into the UPPAAL tool, creating a validator for component property abstraction, modification and formal validation.
Further, the software form verification criteria include interface verification criteria, timing verification criteria, and interaction relationship verification criteria.
Further, the interface verification criteria include the verification criteria of the physical interface including the bus interface and the data transmission interface;
the time sequence verification criteria comprise verification criteria including state bounded response, multi-state concurrency, time constraint and sequence;
the interactive relationship verification criteria include verification criteria including answer communication, nested call, multicast communication, synchronous communication.
Further, the reusable component comprises a main control layer, a data management layer, a scheduling management layer and an interface driving layer;
wherein,,
the interface driving layer is used for completing initial configuration and loading of interfaces, providing a bottom layer interface service and providing a normal running basis for software;
the scheduling management layer is used for realizing a service bridge between the interface driving layer and the data management layer, and the service comprises a function call service, an interrupt processing service, a task query service, an event service and a bus service;
the data management layer is used for packaging different data processing function modules, including functions for realizing specific functions, and providing callable APIs to the main control layer;
and the main control layer is used for controlling the business processing flow by calling the API.
Further, the software defect discovery module comprises an analysis module, an identification module, a defect judgment module and a defect report generation module;
the analysis module is used for performing word meaning analysis and semantic analysis on the software codes, extracting and calculating time sequence characteristics and performing time sequence analysis;
the identification module is used for identifying the functional semantics expressed by the software codes;
the defect judging module is used for judging defects in the software through word meaning analysis, semantic analysis and time sequence analysis results and functional semantic recognition results;
the defect report generating module is used for judging the reasons of occurrence of defects in software, positioning program units or sentences of occurrence of the defects and generating a defect report.
Further, the software autonomous diagnosis module is used for performing autonomous diagnosis on the SEU fault in the software operation in the executable software operation process, discovering the fault in the software operation, and performing fault detection, fault positioning and fault repair.
The invention can realize at least one of the following beneficial effects:
compared with the prior art, the software architecture development system for the aerospace embedded system provided by the invention can enrich software development automation technology, improve software development efficiency, shorten protocol development period, realize online fault diagnosis and repair, has SEU fault tolerance capability, can save a large amount of manual cost, reduce workload of coding personnel, avoid some code defects, and improve safety and robustness of codes.
The invention takes the space embedded system software as a research object, and combines the architecture design with the actual engineering practice, thereby having more practicability. Meanwhile, formal verification of the components is introduced in the architecture design, so that the method is more accurate, and the reliability of the architecture is effectively ensured at the component level.
Drawings
The drawings are only for purposes of illustrating particular embodiments and are not to be construed as limiting the invention, like reference numerals being used to refer to like parts throughout the several views.
Fig. 1 is a schematic diagram illustrating the connection of the software architecture development system according to the first embodiment;
FIG. 2 is a flowchart of a method for constructing a verifier in accordance with the first embodiment;
fig. 3 is a flowchart of a method for designing a CAN bus data management architecture based on a software architecture development system in the first embodiment.
Detailed Description
Preferred embodiments of the present invention are described in detail below with reference to the attached drawing figures, which form a part of the present application and, together with the embodiments of the present invention, serve to explain the principles of the invention.
Example 1
The embodiment discloses a software architecture development system for an aerospace embedded system, as shown in fig. 1, which comprises:
the information extraction module is used for extracting and classifying software key information in the space model software requirement document;
the modeling verification module is used for formally modeling, verifying and packaging the key information of the software to obtain a reusable component of the software;
a software component library for storing the reusable component;
a frame generation module for constructing a software code frame, the code frame being composed of reusable components called from a software component library;
and the software code editing module is used for editing the software code according to the business logic, the control logic and the algorithm logic of the software under the software code framework to generate executable software.
The space model software requirement documents comprise space system design specifications, requirement specification specifications, interface communication protocol files, space model software safety specifications and other requirement documents.
Specifically, in the information extraction module, according to the requirement documents such as the design description, the requirement specification and the interface communication protocol of each space model software system, the space model software safety specification which is definitely required by the system software in the current national army standard is combined, the requirement commonality and the requirement differentiability of the conventional functions in different models are analyzed from the longitudinal dimension, the general key information requirements (interface, time sequence operation and exchange relation) of the conventional functions are summarized and formed, the functional commonality of the software of different models is researched from the transverse dimension analysis, and the conventional basic function information such as RS422, CAN, 1553B, LVDS, multi-state concurrency, time constraint, nested calling and synchronous communication is extracted.
The information extraction module outputs the extracted software key information to the modeling verification module;
the modeling verification module comprises a verification criterion sub-module, a modeling sub-module, a verifier and a packaging sub-module;
the verification criterion submodule is used for establishing a software form verification criterion according to the software key information;
specifically, the software form verification criteria include an interface verification criterion, a timing verification criterion and an interaction relationship verification criterion in demand.
Specifically, the interface verification criteria refer to verification criteria of various physical interfaces common to aerospace embedded systems, and the various physical interfaces comprise bus interfaces such as 1553 and B, CAN, and data transmission interfaces such as RS422 and LVDS.
The time sequence verification criteria comprise verification criteria such as state bounded response, multi-state concurrency, time constraint, sequence and the like.
The interactive relation verification criteria comprise verification criteria such as response communication, nested call, multicast communication, synchronous communication and the like.
The method comprises the steps of building a sub-module, wherein the sub-module is used for generating a reusable component of software, and the reusable component realizes multi-level multiplexing from a software architecture;
specifically, the reusable component comprises a main control layer, a data management layer, a scheduling management layer and an interface driving layer;
wherein,,
the interface driving layer is used for completing initial configuration and loading of interfaces, providing a bottom layer interface service and providing a normal running basis for software;
the scheduling management layer is used for realizing a service bridge between the interface driving layer and the data management layer, and the service comprises a function call service, an interrupt processing service, a task query service, an event service and a bus service;
the data management layer is used for packaging different data processing function modules, including functions for realizing specific functions, and providing callable APIs to the main control layer;
and the main control layer is used for controlling the business processing flow by calling the API.
The verifier is used for formally verifying the reusable component according to established software formal verification criteria;
as shown in fig. 2, the specific verifier construction method includes:
step S201, a modifiable attribute table is established; according to the functional characteristics, interface states and communication processes realized by the reusable components, abstract the modifiable attribute of the components in a form of a table aiming at each component, wherein the modifiable attribute comprises a state parameter and a time parameter;
step S202, a reusable component XML file is established; determining the working state of the reusable components, triggering events, clock constraint, control flow setting and state conversion events, modeling by using a formalization method of a time automaton model, and generating an XML file by each reusable component;
step S203, establishing an association relation; the method comprises the steps that through field matching, a form with a changeable attribute is associated with an XML file, and according to project requirements, a user modifies the component attribute form to realize automatic modification of the XML file;
step S204, importing the reusable component XML file into a UPPAAL tool to establish a verifier for component attribute abstraction, modification and formal verification.
The upaal tool has an integrated environment that is easy for the user to operate and use, and the graphical user interface includes three parts: a system editor (system editor), a Simulator (Simulator), and a Verifier (Verifier). The system editor is used to create and edit a system to be analyzed, a system being described as a series of process templates, some global declarations, process assignments, and a system definition. The simulator is a validation tool that checks the built system model for possible execution errors, so that errors can be found before verification. The validator checks clock constraints and liveness etc. in the reusable component XML file by quickly searching the state space of the system. Upaal provides a visual interface describing automata.
The verification process applied to the present embodiment includes the steps of:
1) Importing formal verification criteria and reusable components into a verifier;
2) The verifier judges whether the formal verification criterion accords with the state conversion and the clock constraint of the reusable component, if so, the reusable component is output to the packaging submodule for packaging;
3) If the state transition is not matched or/and the clock constraint is not matched, the reusable component is returned to the building sub-module to carry out state parameter modification or/and time parameter modification, and then the reusable component is input into the verifier again to carry out re-verification.
And the packaging sub-module is used for packaging the verified reusable component.
Specifically, the verified reusable component is packaged into a visual graphical form, the graph and the reusable component are matched, and when a user selects the graph, the user is automatically linked to the reusable component XML file corresponding to the graph.
The software component library is used for storing the formalized and verified and packaged reusable components for direct calling when the software code frame is reconstructed later. The use of the packaged reusable component improves the efficiency of the software code frame, and the quality of the software code frame can be ensured because the called reusable component is verified and packaged empirically.
Specifically, a user selects a corresponding formalized verified software component module from a modularized reusable component library according to the requirement of embedded software in a frame generation module, and an embedded software code frame containing a communication module is generated by adopting a model-driven-based component code automatic generation technology;
the automatic generation technology of the component codes based on the model driving;
code automatic generation employs a code generation technique based on a model driven architecture (model driven architecture, MDA). The application models of MDA include a computation independent model (computational independent model, CIM), a platform independent model (platform independent model, PIM) and a platform specific model (platform specific model, PSM). The method comprises the steps of firstly writing PIM according to a component, then writing conversion rules according to the PIM and a target platform, automatically converting the PIM into PSM by an MDA code generation engine according to the conversion rules, and finally converting the PSM into codes. In order to ensure that the generated code accords with the aerospace safety specification, a code constraint rule which accords with software safety design, model software reliability safety design rule, aerospace model software C language safety programming specification and the like is added in the safety mapping process of the PSM model to the code, and finally, a component code of a standard specification is generated.
And editing the software code in a software code editing module according to the business logic, the control logic and the algorithm logic of the software based on the software code frame generated by the frame generating module, and finally generating executable software.
In order to enable the executable software to meet the reliability requirements of aerospace models, the executable software is required to be subjected to piece defect detection and online software operation monitoring.
Preferably, the software architecture development system of the present embodiment further includes: a software defect discovery module and an autonomous diagnosis module;
and the software defect discovery module is used for carrying out defect detection on the generated executable software according to an expert knowledge base, and locating the defect position to generate a defect report so as to assist in defect repair of the executable software.
Specifically, the software defect discovery module comprises an analysis module, an identification module, a defect judgment module and a defect report generation module;
the analysis module is used for performing word meaning analysis and semantic analysis on the software codes, extracting and calculating time sequence characteristics and performing time sequence analysis;
specifically, the analysis module performs word sense analysis on the software code source file and the header file character stream according to the word sense rule of the software code language to identify individual words, performs word sense analysis and semantic analysis on word information, extracts attribute information including types (constant, variable, array, label and the like), types (integer, real type, logic type, character type and the like) and grammar trees intuitively showing grammar structures of source programs, extracts and calculates time sequence characteristics on the basis, performs time sequence analysis, optimizes programs and obtains a complete set of program execution states;
the identification module is used for identifying the functional semantics expressed by the software codes;
specifically, in the identification module, corresponding node information is searched on the abstract syntax tree according to the syntax constraint condition specified by the expert knowledge base, and the functional semantics expressed by the software are identified.
The expert knowledge base includes expert knowledge for providing knowledge of the software design, and knowledge related to software testing and software experiments related to the problem to be solved.
The defect judging module is used for judging defects in the software through word meaning analysis, semantic analysis and time sequence analysis results and functional semantic recognition results;
specifically, searching corresponding node information on the abstract syntax tree, and in the process of identifying functional semantics expressed by software, if the corresponding node information cannot be found on the abstract syntax tree, indicating that defects exist in the program.
The defect report generating module is used for judging the reasons of occurrence of defects in software, positioning program units or sentences of occurrence of the defects and generating a defect report.
The defect positioning is to use various information for the discovered software defects to judge the cause of the occurrence of the problem and position the program units or sentences of the occurrence of the defects.
The defect report can analyze a software fault model according to the software fault phenomenon and the defect position causing the software fault, determine the cause of the software fault, analyze the fault influence range and the fault hazard level, and carry out error prompt on the corresponding defect.
Specifically, the autonomous diagnosis module monitors the software running process, performs autonomous diagnosis on the SEU fault in the software running, discovers the fault in the software running, and realizes fault detection, fault positioning and fault repair.
In summary, compared with the prior art, the software architecture development system of the embodiment can enrich the software development automation technology, improve the software development efficiency, shorten the protocol development period, realize the online diagnosis and repair of faults, has the SEU fault tolerance capability, can save a great deal of manual cost, reduce the workload of encoding personnel, avoid some code defects, and improve the safety and robustness of codes.
The invention takes the space embedded system software as a research object, and combines the architecture design with the actual engineering practice, thereby having more practicability. Meanwhile, formal verification of the components is introduced in the architecture design, so that the method is more accurate, and the reliability of the architecture is effectively ensured at the component level.
Example two
The software architecture development system of the present embodiment develops a data analysis layer CAN bus data management architecture, as shown in fig. 3, specifically includes the following steps:
s1, extracting and classifying software key information in a space model software requirement document by using an information extraction module;
extracting software key information of the CAN bus interface according to the design specification, the requirement specification, the CAN bus interface communication protocol file and other requirement documents of the aerospace model software aerospace system;
step S2, carrying out formal modeling, verification and encapsulation on key information of the CAN bus interface software by using a modeling verification module to obtain a reusable component of the software;
specifically, according to software key information of the CAN bus interface, extracting a CAN interface verification criterion in the demand;
carrying out multiplexing component design on CAN bus data management of a data management layer from a software architecture level;
performing formal verification on the CAN bus data management reusable component of the data analysis layer according to the established CAN interface verification criterion;
packaging the verified assembly to obtain a packaged formalized verification CAN bus data management reusable assembly;
s3, storing the packaged and formalized verification CAN bus data management reusable component into a reusable component library;
s4, in the frame generation module, selecting a corresponding data management layer CAN bus data management reusable component subjected to formal verification from a reusable component library according to the requirement of embedded software, and generating an embedded software code frame containing an interface component;
s5, in the software code editing module, under the generated software framework, editing the software code is completed according to rich software such as business logic, control logic, algorithm logic and the like of the software;
s6, in the software defect discovery module, performing software defect detection according to expert knowledge, realizing defect positioning and generating a defect report;
and S7, in an autonomous diagnosis module, monitoring a software running process, performing autonomous diagnosis on the SEU fault in the software running process, finding out the fault in the software running process, and realizing fault detection, fault positioning and fault repair.
The present invention is not limited to the above-mentioned embodiments, and any changes or substitutions that can be easily understood by those skilled in the art within the technical scope of the present invention are intended to be included in the scope of the present invention.
Claims (8)
1. A software architecture development system for an aerospace embedded system, comprising:
the information extraction module is used for extracting and classifying software key information in the space model software requirement document;
the modeling verification module is used for formally modeling, verifying and packaging the key information of the software to obtain a reusable component of the software;
a software component library for storing the reusable component;
a frame generation module for constructing a software code frame, the code frame being composed of reusable components called from a software component library;
the software code editing module is used for editing a software code according to the business logic, the control logic and the algorithm logic of the software under the software code framework to generate executable software;
the modeling verification module comprises a verification criterion sub-module, a modeling sub-module, a verifier and a packaging sub-module;
the verification criterion submodule is used for establishing a software form verification criterion according to the software key information;
the method comprises the steps of building a sub-module, wherein the sub-module is used for generating a reusable component of software, and the reusable component realizes multi-level multiplexing from a software architecture;
the verifier is used for formally verifying the reusable component according to established software formal verification criteria;
the packaging submodule is used for packaging the reusable component passing the verification;
specifically, the verifier judges whether the formal verification criterion accords with the state transition and the clock constraint of the reusable component, if so, the reusable component is output to the packaging submodule for packaging; if the state transition is not matched or/and the clock constraint is not matched, returning the reusable component to the building sub-module for state parameter modification or/and time parameter modification, and returning to the verifier for re-verification;
the construction process of the verifier comprises the following steps:
establishing a modifiable attribute table; according to the functional characteristics, interface states and communication processes realized by the reusable components, abstracting the modifiable attribute of the reusable components in a form of a table aiming at each component;
establishing a reusable component XML file; determining the working state of the reusable components, triggering events, clock constraint, control flow setting and state conversion events, modeling by using a formalization method of a time automaton model, and generating a reusable component XML file by each reusable component;
establishing an association relation; associating the modifiable attribute table with the reusable component XML file through field matching; the user realizes the automatic modification of the reusable component XML file by modifying the component attribute table;
the reusable component XML file is imported into the UPPAAL tool, creating a validator for component property abstraction, modification and formal validation.
2. The software architecture development system of claim 1 further comprising a software defect discovery module for performing defect detection on the generated executable software based on an expert knowledge base, locating a defect location to generate a defect report to assist in defect repair of the executable software.
3. The software architecture development system of claim 2 further comprising an autonomous diagnostic module for on-line monitoring of the running process of the executable software for autonomous diagnostics, fault localization, and fault remediation.
4. The software architecture development system of claim 1 wherein the software form validation criteria include interface validation criteria, timing validation criteria, and interaction relationship validation criteria.
5. The software architecture development system of claim 4 wherein the interface validation criteria includes a physical interface validation criteria including a bus interface, a data transfer interface;
the time sequence verification criteria comprise verification criteria including state bounded response, multi-state concurrency, time constraint and sequence;
the interactive relationship verification criteria include verification criteria including answer communication, nested call, multicast communication, synchronous communication.
6. The software architecture development system of claim 1 wherein the reusable component comprises a master control layer, a data management layer, a schedule management layer, and an interface driver layer;
wherein,,
the interface driving layer is used for completing initial configuration and loading of interfaces, providing a bottom layer interface service and providing a normal running basis for software;
the scheduling management layer is used for realizing a service bridge between the interface driving layer and the data management layer, and the service comprises a function call service, an interrupt processing service, a task query service, an event service and a bus service;
the data management layer is used for packaging different data processing function modules, including functions for realizing specific functions, and providing callable APIs to the main control layer;
and the main control layer is used for controlling the business processing flow by calling the API.
7. The software architecture development system of any one of claims 2-6 wherein the software defect discovery module includes an analysis module, an identification module, a defect determination module, and a defect report generation module;
the analysis module is used for performing word meaning analysis and semantic analysis on the software codes, extracting and calculating time sequence characteristics and performing time sequence analysis;
the identification module is used for identifying the functional semantics expressed by the software codes;
the defect judging module is used for judging defects in the software through word meaning analysis, semantic analysis and time sequence analysis results and functional semantic recognition results;
the defect report generating module is used for judging the reasons of occurrence of defects in software, positioning program units or sentences of occurrence of the defects and generating a defect report.
8. The software architecture development system of any one of claims 3-6 wherein,
and the software autonomous diagnosis module is used for performing autonomous diagnosis on the SEU fault in the software operation in the executable software operation process, discovering the fault in the software operation, and performing fault detection, fault positioning and fault repair.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011255814.1A CN112416337B (en) | 2020-11-11 | 2020-11-11 | Software architecture development system for aerospace embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011255814.1A CN112416337B (en) | 2020-11-11 | 2020-11-11 | Software architecture development system for aerospace embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112416337A CN112416337A (en) | 2021-02-26 |
| CN112416337B true CN112416337B (en) | 2023-05-02 |
Family
ID=74781616
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011255814.1A Active CN112416337B (en) | 2020-11-11 | 2020-11-11 | Software architecture development system for aerospace embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416337B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947902B (en) * | 2021-04-25 | 2023-05-12 | 广州佳禾科技股份有限公司 | System development management platform |
| CN114741052B (en) * | 2022-04-21 | 2024-04-12 | 中国航空无线电电子研究所 | Formalized semantic analysis and inspection method for demand form model |
| CN115002189A (en) * | 2022-04-21 | 2022-09-02 | 上海蓝箭鸿擎科技有限公司 | Spacecraft-oriented high-separation distributed system software architecture |
| CN114995226B (en) * | 2022-05-26 | 2023-05-26 | 中国科学院国家空间科学中心 | Flow control system and method for aerospace embedded equipment |
| CN115658021B (en) * | 2022-11-07 | 2023-12-12 | 苏州数设科技有限公司 | Determination method and device of dynamic model, storage medium and electronic equipment |
| CN117421009B (en) * | 2023-12-19 | 2024-04-19 | 深圳市航盛电子股份有限公司 | Signal code generation method, device, terminal equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107817970A (en) * | 2017-10-23 | 2018-03-20 | 云南大学 | A kind of construction system modeling and its dynamic evolution consistency verification method |
| CN109976712A (en) * | 2019-03-12 | 2019-07-05 | 中山大学 | One kind doing formalization verification method to network physical system requirements based on UPPAAL-SMC |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1928816A (en) * | 2006-09-26 | 2007-03-14 | 武汉大学 | Model drive for embedded system software and component development method |
| CN100382026C (en) * | 2006-10-13 | 2008-04-16 | 上海科泰世纪科技有限公司 | Method for adapting and extending XML tag and assembly in structural software system |
| CN100461132C (en) * | 2007-03-02 | 2009-02-11 | 北京邮电大学 | Software safety code analyzer based on static analysis of source code and testing method therefor |
| CN100492287C (en) * | 2007-07-12 | 2009-05-27 | 浙江大学 | Software applied frame system facing data analysing instrument, and device and method for developing embedded system using the frame system |
| CN101122856A (en) * | 2007-07-12 | 2008-02-13 | 浙江大学 | Embedded type software application frame facing network monitoring instrument and its uses |
| CN102136047A (en) * | 2011-02-25 | 2011-07-27 | 天津大学 | Software trustworthiness engineering method based on formalized and unified software model |
| CN102567163B (en) * | 2011-12-16 | 2013-11-27 | 华东师范大学 | Method for identifying cooperative behaviors of components of real-time embedded system based on UPPAAL tool |
| CN103593326B (en) * | 2013-11-07 | 2017-02-08 | 国家电网公司 | IEC61850 software library assembly for network processing unit chip and achieving method of IEC61850 software library assembly |
| US10346140B2 (en) * | 2015-08-05 | 2019-07-09 | General Electric Company | System and method for model based technology and process for safety-critical software development |
| CN106933580B (en) * | 2017-03-02 | 2020-12-29 | 北京天恒长鹰科技股份有限公司 | Embedded software architecture system |
-
2020
- 2020-11-11 CN CN202011255814.1A patent/CN112416337B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107817970A (en) * | 2017-10-23 | 2018-03-20 | 云南大学 | A kind of construction system modeling and its dynamic evolution consistency verification method |
| CN109976712A (en) * | 2019-03-12 | 2019-07-05 | 中山大学 | One kind doing formalization verification method to network physical system requirements based on UPPAAL-SMC |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112416337A (en) | 2021-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112416337B (en) | Software architecture development system for aerospace embedded system | |
| US10817409B2 (en) | System and method for testing software applications in a software defined network | |
| CN106777101B (en) | Data processing engine | |
| US20040143819A1 (en) | Generic software testing system and mechanism | |
| CN109634600B (en) | Code generation method based on security extension SysML and AADL models | |
| CN111459821A (en) | Software automation unit testing method based on TestNG | |
| CN110221815B (en) | Automatic generation method of control software model based on ontology | |
| CN112416336B (en) | Software architecture design method for aerospace embedded system | |
| CN110222318A (en) | Data generating tool development approach based on XML | |
| Mongiello et al. | Modelling and verification of BPEL business processes | |
| Zhao et al. | Towards formal verification of UML diagrams based on graph transformation | |
| CN113868120A (en) | Industrial software debugging method and device, computer equipment and storage medium | |
| Friedrich et al. | Knowledge engineering for configuration systems | |
| KR102418796B1 (en) | FMEA failure mode recommend system | |
| Moscato et al. | The software architecture of the OsMoSys multisolution framework | |
| Mian et al. | Model transformation for analyzing dependability of AADL model by using HiP-HOPS | |
| Pang et al. | Automatic model generation of IEC 61499 function block using net condition/event systems | |
| KR102268053B1 (en) | Intelligent safety fault diagnostic system of robotic process automation | |
| Lochmann et al. | An integrated view on modeling with multiple domain-specific languages | |
| CN115033212A (en) | Avionics system primitive model integrated construction method and device and computer equipment | |
| Krichen et al. | Towards a runtime standard-based testing framework for dynamic distributed information systems | |
| Salay et al. | Managing related models in vehicle control software development | |
| Addouche et al. | Methodology for UML modeling and formal verification of real-time systems | |
| Zhang et al. | A method of automatic code generation based on AADL model | |
| CN114647401A (en) | Model verification method suitable for distributed system of SysML, Simulink and AADL |
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 |