CN112416336B - Software architecture design method for aerospace embedded system - Google Patents
Software architecture design method for aerospace embedded system Download PDFInfo
- Publication number
- CN112416336B CN112416336B CN202011255709.8A CN202011255709A CN112416336B CN 112416336 B CN112416336 B CN 112416336B CN 202011255709 A CN202011255709 A CN 202011255709A CN 112416336 B CN112416336 B CN 112416336B
- Authority
- CN
- China
- Prior art keywords
- software
- component
- reusable
- embedded
- verification
- 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
- 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 design method for an aerospace embedded system, which comprises the following steps: generating an embedded software component library, wherein the embedded software component library comprises a multiplex component subjected to formal verification; selecting needed reusable components from the embedded software component library to construct an embedded software code frame; editing the embedded software code according to the embedded software code framework to generate executable software; performing defect detection on the generated executable software according to an expert knowledge base, positioning a defect position to generate a defect report, and performing defect repair; and monitoring the running process of the executable software on line, and performing autonomous diagnosis, fault positioning and fault repairing. The invention can enrich the software development automation technology, improve the software development efficiency, shorten the protocol development period, realize the on-line diagnosis and repair of faults and improve the safety and the robustness of codes.
Description
Technical Field
The invention belongs to the technical field of software engineering, and particularly relates to a software architecture design method 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 design method for an aerospace embedded system, which solves the problems that the general embedded system software architecture is lacking in the aerospace embedded software engineering field and the reliability of the software architecture is improved.
The invention discloses a software architecture design method for an aerospace embedded system, which comprises the following steps:
generating an embedded software component library, wherein the embedded software component library comprises a multiplex component subjected to formal verification;
selecting needed reusable components from the embedded software component library to construct an embedded software code frame;
editing the embedded software code according to the embedded software code framework to generate executable software;
performing defect detection on the generated executable software according to an expert knowledge base, positioning a defect position to generate a defect report, and performing defect repair;
and monitoring the running process of the executable software on line, and performing autonomous diagnosis, fault positioning and fault repairing.
Further, the generating the embedded software component library includes:
1) Extracting software key information in the space model software requirement, and establishing software form verification criteria in a classified manner;
2) Generating a reusable component of the software, wherein the reusable component realizes multi-level multiplexing from the software architecture;
3) Formalized verification is carried out on the reusable component according to established software formal verification criteria;
4) And packaging the verified components to obtain the embedded software component library.
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 level of the reusable component comprises a main control layer, a data management layer, a scheduling management layer and an interface driving layer; 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 formal verification includes the steps of:
1) Constructing a verifier for component attribute abstraction, modification and formal verification;
2) Verifying the reusable component using a verifier;
3) Judging whether the verification is passed or not; if the software component passes, storing the reusable component into a software component library; if not, revising the parameters of the reusable component, and returning to the step 2) for 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, abstract the modifiable attribute of the components in a form of a table aiming at each reusable 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 defect detection process includes:
performing word sense analysis and semantic analysis on the software codes, and extracting and calculating time sequence characteristics;
identifying functional semantics expressed by software, and ensuring correct and reasonable functional semantics;
and judging the cause of the occurrence of the problem for the discovered software defect by utilizing various information, positioning a program unit or statement of the occurrence of the defect, and generating a defect report.
Further, the expert knowledge base includes software design knowledge and related knowledge of software tests and software experiments related to the problem to be solved.
Further, the online monitoring of the executable software running process carries out autonomous diagnosis on SEU faults in software running, discovers faults in software running, and carries out 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 invention provides a software architecture design method for an aerospace embedded system, which can solve the problems of the prior art, 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 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.
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 flow chart of an embedded software architecture design method in a first embodiment;
FIG. 2 is a flowchart of a method for generating an embedded software component library according to the first embodiment;
FIG. 3 is a flowchart of a method for constructing a verifier in accordance with the first embodiment;
FIG. 4 is a flowchart of a software defect detection method according to the first embodiment;
fig. 5 is a flowchart of a CAN bus data management architecture design method in the second 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 an embedded software architecture design method for an aerospace embedded system, which comprises the following steps as shown in fig. 1:
step S101, generating an embedded software component library, wherein the embedded software component library comprises a multiplex component subjected to formal verification;
step S102, selecting needed reusable components from the embedded software component library to construct an embedded software code frame;
step S103, editing the embedded software code according to the embedded software code frame to generate executable software;
step S104, performing defect detection on the generated executable software according to an expert knowledge base, positioning a defect position to generate a defect report, and performing defect repair;
step S105, the running process of the executable software is monitored on line, and autonomous diagnosis, fault location and fault repair are performed.
Specifically, as shown in fig. 2, the method for generating the embedded software component library in step S101 includes:
step S201, according to the design description, the requirement specification, the interface communication protocol and other requirement documents of each space model software system, combining the space model software safety specification with clear requirements on system software in the current national army standard, analyzing the requirement commonality and the difference of the conventional functions in different models from the longitudinal latitude, summarizing and forming the general key information requirements (interface, time sequence operation and exchange relation) of the conventional functions, analyzing and researching the functional commonality of the different models from the transverse latitude, extracting the conventional basic function information such as RS422, CAN, 1553B, LVDS, multi-state concurrency, time constraint, nested calling, synchronous communication and the like, and establishing the software form verification criterion in a classified manner;
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.
Further, the software form verification criteria include in-demand interface verification criteria, timing verification criteria, and interaction relationship verification criteria.
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.
Step S202, generating a reusable component of software, wherein the reusable component realizes multi-level multiplexing from the basis of a software architecture;
specifically, the reusable level of the reusable component comprises a main control layer, a data management layer, a scheduling management layer and an interface driving layer; 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.
Step S203, formalized verification is carried out on the reusable component according to the established software formal verification criterion;
the formal verification includes the steps of:
1) Constructing a verifier for component attribute abstraction, modification and formal verification;
as shown in fig. 3, the specific construction method includes:
step S301, 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 S302, a reusable component XML file is established; determining the working state of a reusable component, triggering events, clock constraints, 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 component module;
step S303, 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 S304, the reusable component XML file is imported into a UPPAAL tool, and a verifier for component attribute abstraction, modification and formal verification is established.
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.
2) Verifying the reusable component using a verifier;
selecting formal verification criteria associated with the reusable component, and verifying the reusable component;
3) Judging whether the formal verification criterion is consistent with the state conversion and clock constraint of the reusable component, if so, storing the reusable component into a software component library; if the state transition is not matched, modifying the state parameters of the component module, if the clock constraint is not matched, modifying the time parameters of the component module, and returning to the step 2) for re-verification.
And step S204, packaging the verified components to finally obtain a reusable component library passing formal verification.
Specifically, in step S102, the user selects a corresponding formalized verified software component module from the modularized component resource library according to the embedded software requirement, and generates an embedded software code frame including a communication module by using a model-driven 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 reusable 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.
Specifically, in step S103, the user completes editing of the software code according to the rich software such as the business logic, the control logic, the algorithm logic, and the like of the software under the generated software architecture, and generates executable software.
Specifically, in step S104, the expert knowledge base includes software design knowledge, and related knowledge of software tests and software experiments related to the problem to be solved.
In step S104, the software defect detection method according to the expert knowledge base is as shown in fig. 4, and includes:
step S401, performing word sense analysis on a software code source file and a header file character stream according to a lexical rule of a software code language to identify individual words, performing semantic analysis on word information, extracting attribute information including types (constants, variables, arrays, labels and the like), types (integer, real type, logic type, character type and the like) and grammar trees intuitively representing grammar structures of source programs, and performing program optimization on the basis to obtain a complete set of program execution states;
step S402, searching corresponding node information on the abstract syntax tree according to the syntax constraint conditions specified by the expert knowledge base, identifying the functional semantics expressed by the software, and if the corresponding node information can be found on the abstract syntax tree, indicating that the defect exists in the program;
step S403, judging the cause of the problem of the discovered software defect, positioning the program unit or sentence of the defect, 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, in step S105, the software running process is monitored, an SEU fault in the software running is autonomously diagnosed, and a fault in the software running is found, so as to implement fault detection, fault positioning, and fault repair.
Example two
The embodiment specifically describes a design method of a data analysis layer CAN bus data management architecture, as shown in fig. 5, including the following steps:
step S501, generating a data management layer CAN bus data management reusable component library comprising the formalized verified reusable components;
the method specifically comprises the following steps:
1) Extracting CAN interface verification criteria in the requirements according to the design specifications, the requirement specification specifications, the interface communication protocol files and other requirement documents of the aerospace model software aerospace system;
2) Carrying out multiplexing component design on CAN bus data management of a data management layer from a software architecture level;
3) Formalized verification is carried out on the data management multiplexing component of the CAN bus of the data analysis layer according to the established CAN interface verification criteria,
4) And packaging the verified components to finally obtain the data management reusable component library of the data management layer CAN bus through formal verification.
Step S502, selecting a corresponding data management layer CAN bus data management component module subjected to formal verification according to the requirement of the embedded software, and generating an embedded software code frame containing an interface component;
step S503, under the generated software framework, the editing of the software codes is completed according to rich software such as business logic, control logic, algorithm logic and the like of the software;
step S504, performing software defect detection according to expert knowledge, realizing defect positioning, and generating a defect report;
step S505, monitoring the software running process, performing autonomous diagnosis on the SEU fault in the software running process, finding 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 design method for an aerospace embedded system is characterized by comprising the following steps:
generating an embedded software component library, wherein the embedded software component library comprises a multiplex component subjected to formal verification;
selecting needed reusable components from the embedded software component library to construct an embedded software code frame;
editing the embedded software code according to the embedded software code framework to generate executable software;
performing defect detection on the generated executable software according to an expert knowledge base, positioning a defect position to generate a defect report, and performing defect repair;
on-line monitoring the running process of executable software, and performing autonomous diagnosis, fault positioning and fault repairing;
the formal verification includes the steps of:
1) Constructing a verifier for component attribute abstraction, modification and formal verification;
2) Verifying the reusable component using a verifier;
3) Judging whether the verification is passed or not; if the software component passes, storing the reusable component into a software component library; if not, revising the parameters of the reusable component, and returning to the step 2) 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, abstract the modifiable attribute of the components in a form of a table aiming at each reusable 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 design method of claim 1, wherein the generating an embedded software component library comprises:
1) Extracting software key information in the space model software requirement, and establishing software form verification criteria in a classified manner;
2) Generating a reusable component of the software, wherein the reusable component realizes multi-level multiplexing from the software architecture;
3) Formalized verification is carried out on the reusable component according to established software formal verification criteria;
4) And packaging the verified components to obtain the embedded software component library.
3. The software architecture design method of claim 2, wherein the software form verification criteria include an interface verification criteria, a timing verification criteria, and an interaction relationship verification criteria.
4. A software architecture design method according to claim 3, wherein said interface verification criteria comprises a verification criteria of a physical interface 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.
5. The software architecture design method of claim 1, wherein the reusable level of reusable components comprises a master control layer, a data management layer, a schedule management layer, and an interface driver layer; 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.
6. The method of claim 1, wherein,
the defect detection process includes:
performing word sense analysis and semantic analysis on the software codes, and extracting and calculating time sequence characteristics;
identifying functional semantics expressed by software, and ensuring correct and reasonable functional semantics;
and judging the cause of the occurrence of the problem for the discovered software defect by utilizing various information, positioning a program unit or statement of the occurrence of the defect, and generating a defect report.
7. The method of claim 1, wherein,
the expert knowledge base includes software design knowledge and related knowledge of software tests and software experiments related to the problem to be solved.
8. The method of claim 1, wherein,
and the online monitoring of the running process of the executable software carries out autonomous diagnosis on SEU faults in the running process of the software, discovers faults in the running process of the software and carries out fault detection, fault positioning and fault repair.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011255709.8A CN112416336B (en) | 2020-11-11 | 2020-11-11 | Software architecture design method for aerospace embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011255709.8A CN112416336B (en) | 2020-11-11 | 2020-11-11 | Software architecture design method for aerospace embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112416336A CN112416336A (en) | 2021-02-26 |
| CN112416336B true CN112416336B (en) | 2023-04-28 |
Family
ID=74781549
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011255709.8A Active CN112416336B (en) | 2020-11-11 | 2020-11-11 | Software architecture design method for aerospace embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416336B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113190212B (en) * | 2021-04-26 | 2024-04-19 | 深圳易伙科技有限责任公司 | Domain demand modeling method and device for driving open ecological cloud ERP |
| CN116306276B (en) * | 2023-03-09 | 2024-06-14 | 北京理工大学 | Complex system architecture creation type generation method and system and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102136047A (en) * | 2011-02-25 | 2011-07-27 | 天津大学 | Software trustworthiness engineering method based on formalized and unified software model |
| CN102722601A (en) * | 2012-05-04 | 2012-10-10 | 华南理工大学 | Implementation method of formal semantic integration framework for model transformation of numerical control system |
| CN107292027A (en) * | 2017-06-21 | 2017-10-24 | 同济大学 | A kind of bounded model checking method of the linear period invariant based on extension |
| CN108829955A (en) * | 2018-06-01 | 2018-11-16 | 南京航空航天大学 | A kind of aero-engine seaworthiness security 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 |
| CN110134599A (en) * | 2019-05-09 | 2019-08-16 | 中国航空工业集团公司西安航空计算技术研究所 | A kind of system architecture misdeed verification method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090088883A1 (en) * | 2007-09-27 | 2009-04-02 | Rockwell Automation Technologies, Inc. | Surface-based computing in an industrial automation environment |
| US11327475B2 (en) * | 2016-05-09 | 2022-05-10 | Strong Force Iot Portfolio 2016, Llc | Methods and systems for intelligent collection and analysis of vehicle data |
-
2020
- 2020-11-11 CN CN202011255709.8A patent/CN112416336B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102136047A (en) * | 2011-02-25 | 2011-07-27 | 天津大学 | Software trustworthiness engineering method based on formalized and unified software model |
| CN102722601A (en) * | 2012-05-04 | 2012-10-10 | 华南理工大学 | Implementation method of formal semantic integration framework for model transformation of numerical control system |
| CN107292027A (en) * | 2017-06-21 | 2017-10-24 | 同济大学 | A kind of bounded model checking method of the linear period invariant based on extension |
| CN108829955A (en) * | 2018-06-01 | 2018-11-16 | 南京航空航天大学 | A kind of aero-engine seaworthiness security 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 |
| CN110134599A (en) * | 2019-05-09 | 2019-08-16 | 中国航空工业集团公司西安航空计算技术研究所 | A kind of system architecture misdeed verification method and device |
Non-Patent Citations (2)
| Title |
|---|
| Kleanthis Thramboulidis等.Towards an automated verification process for industrial safety applications.《2011 IEEE International Conference on Automation Science and Engineering》.2011,第482-487页. * |
| 李振松等.基于ＵＰＰＡＡＬ的ＡＡＤＬ行为模型验证方法研究.《计算机科学》.2012,第第39卷卷(第第2期期),第159-161、169页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112416336A (en) | 2021-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112416337B (en) | Software architecture development system for aerospace embedded system | |
| US9274924B2 (en) | Method for the computer-assisted analysis of software source code | |
| US6385765B1 (en) | Specification and verification for concurrent systems with graphical and textual editors | |
| Baldassari et al. | PROTOB: An object oriented methodology for developing discrete event dynamic systems | |
| TW200412495A (en) | A generic software testing system and mechanism | |
| CN109634600B (en) | Code generation method based on security extension SysML and AADL models | |
| CN112416336B (en) | Software architecture design method for aerospace embedded system | |
| CN106406881A (en) | Scalable methods for analyzing formalized requirements and localizing errors | |
| CN110221815B (en) | Automatic generation method of control software model based on ontology | |
| CN110222318A (en) | Data generating tool development approach based on XML | |
| Wang et al. | An approach to generate the traceability between restricted natural language requirements and AADL models | |
| CN110209389A (en) | A kind of data generating tool development system based on XML | |
| CN117931620A (en) | Automatic test method for reducing test technical threshold of intelligent terminal system | |
| Zhao et al. | Towards formal verification of UML diagrams based on graph transformation | |
| CN118466382A (en) | PLC controller capable of completing programming simulation | |
| Frehse et al. | A toolchain for verifying safety properties of hybrid automata via pattern templates | |
| Ratiu et al. | FASTEN: an extensible platform to experiment with rigorous modeling of safety-critical systems | |
| Nastov et al. | Towards V&V suitable domain specific modeling languages for MBSE: A tooled approach | |
| Pang et al. | Automatic model generation of IEC 61499 function block using net condition/event systems | |
| Friedrich et al. | Knowledge engineering for configuration systems | |
| Yoo et al. | Verification of PLC programs written in FBD with VIS | |
| Dietsch et al. | Formal requirements in an informal world | |
| Wilson et al. | Life cycles in software and knowledge engineering: a comparative review | |
| CN115033212A (en) | Avionics system primitive model integrated construction method and device and computer equipment | |
| Börger et al. | Requirements capture, documentation, and validation |
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 |