CN112416337A - Software architecture development system for aerospace embedded system - Google Patents
Software architecture development system for aerospace embedded system Download PDFInfo
- Publication number
- CN112416337A CN112416337A CN202011255814.1A CN202011255814A CN112416337A CN 112416337 A CN112416337 A CN 112416337A CN 202011255814 A CN202011255814 A CN 202011255814A CN 112416337 A CN112416337 A CN 112416337A
- Authority
- CN
- China
- Prior art keywords
- software
- module
- verification
- reusable component
- defect
- 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.)
- Granted
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
Abstract
The invention relates to a software architecture development system for a spaceflight embedded system, which comprises: the information extraction module is used for extracting and classifying software key information in the aerospace model software requirement document; the modeling verification module is used for performing formal modeling, verification and encapsulation on the software key information to obtain a reusable component of the software; the software component library is used for storing the reusable components; the framework generation module is used for constructing a software code framework, and the code framework is formed by reusable components called from a software component library; the software code editing module is used for editing software codes according to the service logic, the control logic and the algorithm logic of the software under the software code framework to generate 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 a space embedded system, which is applied to the development process of the space embedded software.
Background
With the high-speed development of aerospace application, the complex task requirements of the aerospace embedded software require that the algorithm and processing of the aerospace embedded software tend to be highly integrated and intelligent, the software scale and complexity are further improved, and higher requirements are provided for the uniformity of a software architecture and the reliability of the software. At present, a task customization development mode is mainly adopted in the development of aerospace embedded software, and because different software architectures are used, the inheritance among model software is weak, and the development efficiency of the software and the quality of software products are influenced.
For the problem of software development architecture, even if the software architecture of the previous model is inherited, the problems of reliability and safety design such as inconsistent realization of common resource module interfaces, inconsistent timing sequence and the like in the software architecture can affect the reliability of software and the quality of software products, and the problems are difficult to discover only by relying on simple software development and software testing work.
Disclosure of Invention
In view of the above analysis, the present invention aims to disclose a software architecture development system for an aerospace embedded system, which solves the problems that the aerospace embedded software engineering field lacks a general embedded system software architecture and the reliability of the software architecture is improved.
The invention discloses a software architecture development system for a spaceflight embedded system, which comprises:
the information extraction module is used for extracting and classifying software key information in the aerospace model software requirement document;
the modeling verification module is used for performing formal modeling, verification and encapsulation on the software key information to obtain a reusable component of the software;
the software component library is used for storing the reusable components;
the framework generation module is used for constructing a software code framework, and the code framework is formed by reusable components called from a software component library;
and the software code editing module is used for editing the software code according to the service logic, the control logic and the algorithm logic of the software under the software code framework to generate executable software.
And the software defect finding module is used for detecting the defects of the generated executable software according to the expert knowledge base, positioning the defect positions and generating a defect report so as to assist in repairing the defects of the executable software.
And the system further comprises an autonomous diagnosis module which is used for monitoring the running process of the executable software on line and carrying out 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 formal verification criterion according to the software key information;
the modeling submodule is used for generating a reusable component of the software, and the reusable component realizes multi-level reuse from a software architecture;
the verifier is used for performing formal verification on the reusable component according to the established software formal verification criterion;
the packaging sub-module is used for packaging the reusable component which passes the verification;
specifically, the verifier judges whether the formal verification criterion conforms to the state conversion and clock constraint of the reusable component, and if so, the verifier outputs the reusable component 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 modeling submodule for state parameter modification or/and time parameter modification, and then returned to the verifier for re-verification.
Further, the construction process of the verifier comprises the following steps:
establishing a changeable attribute table; abstracting the alterable attribute of the reusable component in a table form aiming at each component according to the functional characteristics, the interface state and the communication process realized by the reusable component;
establishing a reusable component XML file; determining the working state of the reusable components, triggering events, clock constraints, control flow settings and state transition events, modeling by using a formalization method of a time automata model, and generating a reusable component XML file by each reusable component;
establishing an association relation; associating the attribute table capable of being changed with the XML file of the reusable component through field matching; the user realizes the automatic modification of the XML file of the reusable component by modifying the attribute table of the component;
and importing the reusable component XML file into a UPPAAL tool, and establishing a verifier for abstract, modification and formalized verification of the component property.
Further, the software formal verification criteria include interface verification criteria, timing verification criteria, and interaction relationship verification criteria.
Further, the interface verification criterion comprises the verification criterion of physical interfaces including a bus interface and a data transmission interface;
the time sequence verification criterion comprises verification criteria including state bounded response, multi-state concurrency, time constraint and sequence;
the interactive relation verification criterion comprises verification criteria of response communication, nested calling, multicast communication and synchronous communication.
Furthermore, the reusable component comprises a main control layer, a data management layer, a scheduling management layer and an interface driving layer;
wherein the content of the first and second substances,
the interface driving layer is used for completing the initial configuration and loading of the interface, providing bottom interface service and providing a normal operation 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 services comprise function call service, interrupt processing service, task query service, event service and bus service;
the data management layer is used for packaging different data processing function modules, including functions for realizing specific functions and providing a callable API (application program interface) to the main control layer;
and the main control layer is used for realizing the control of the business processing flow by calling the API.
Further, the software defect finding 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 the defects in the software according to the results of word meaning analysis, semantic analysis and time sequence analysis and the recognition result of functional semantics;
and the defect report generation module is used for judging the cause of the defect in the software, positioning the program unit or statement of the defect and generating a defect report.
Further, the software self-diagnosis module is used for performing self-diagnosis on the SEU fault in the software operation process in the executable software operation process, finding the fault in the software operation process, 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, which is provided by the invention, 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 large amount of manual cost, reduce the workload of coding personnel, avoid certain code defects and improve the safety and the robustness of codes.
The invention takes the aerospace embedded system software as a research object, and has more practicability by combining the architectural design with the actual engineering practice. Meanwhile, formal verification of the components is introduced into the architecture design, so that the method is more accurate, and the reliability of the architecture is effectively guaranteed 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, wherein like reference numerals are used to designate like parts throughout.
Fig. 1 is a connection diagram illustrating a software architecture development system in the first embodiment;
FIG. 2 is a flowchart illustrating a method for constructing a verifier according to an embodiment of the present invention;
fig. 3 is a flowchart of a design method of a CAN bus data management architecture based on a software architecture development system in the first embodiment.
Detailed Description
The preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form a part hereof, and which together with the embodiments of the invention serve to explain the principles of the invention.
Example one
The embodiment discloses a software architecture development system for an aerospace embedded system, as shown in fig. 1, including:
the information extraction module is used for extracting and classifying software key information in the aerospace model software requirement document;
the modeling verification module is used for performing formal modeling, verification and encapsulation on the software key information to obtain a reusable component of the software;
the software component library is used for storing the reusable components;
the framework generation module is used for constructing a software code framework, and the code framework is formed by reusable components called from a software component library;
and the software code editing module is used for editing the software code according to the service logic, the control logic and the algorithm logic of the software under the software code framework to generate executable software.
The aerospace model software requirement documents comprise aerospace system design specifications, requirement specification specifications, interface communication protocol files, aerospace model software safety specifications and other requirement documents.
Specifically, in the information extraction module, according to requirement documents such as design specifications, requirement specification specifications, interface communication protocols and the like of each aerospace model software system, and in combination with aerospace model software safety specifications which have clear requirements on system software in the current state military standard, the requirement commonality and difference of conventional functions in different models are analyzed from the longitudinal dimension, the key information requirements (interfaces, time sequence operation and exchange relation) common to the conventional functions are summarized and formed, the functionality commonality of the software with different models is analyzed and researched from the transverse dimension, and the conventional basic function information covering RS422, CAN, 1553B, LVDS, multi-state concurrence, time constraint, nested calling, synchronous communication and the like 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 an encapsulation sub-module;
the verification criterion submodule is used for establishing a software formal verification criterion according to the software key information;
specifically, the software formal verification criteria include interface verification criteria, timing verification criteria and interaction relationship verification criteria in the requirements.
Specifically, the interface verification criterion refers to the verification criterion of various common physical interfaces of the aerospace embedded system, and the various physical interfaces include bus interfaces such as 1553B, CAN and data transmission interfaces such as RS422 and LVDS.
The time sequence verification criterion comprises state bounded response, multi-state concurrency, time constraint, sequence and other verification criteria.
The interactive relation verification criterion comprises verification criteria of response communication, nested calling, multicast communication, synchronous communication and the like.
The modeling submodule is used for generating a reusable component of the software, and the reusable component realizes multi-level reuse 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 content of the first and second substances,
the interface driving layer is used for completing the initial configuration and loading of the interface, providing bottom interface service and providing a normal operation 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 services comprise function call service, interrupt processing service, task query service, event service and bus service;
the data management layer is used for packaging different data processing function modules, including functions for realizing specific functions and providing a callable API (application program interface) to the main control layer;
and the main control layer is used for realizing the control of the business processing flow by calling the API.
The verifier is used for performing formal verification on the reusable component according to the established software formal verification criterion;
as shown in fig. 2, the specific verifier constructing method includes:
step S201, establishing a changeable attribute table; abstracting the alterable attribute of the component in a table form aiming at each component according to the functional characteristics, the interface state and the communication process realized by the reusable component, wherein the alterable attribute comprises a state parameter and a time parameter;
step S202, establishing a reusable component XML file; determining the working state of the reusable components, triggering events, clock constraints, control flow settings and state transition events, modeling by using a formalization method of a time automata model, and generating an XML file for each reusable component;
step S203, establishing an association relation; through field matching, the form with changeable attributes is associated with the XML file, and the user can automatically modify the XML file by modifying the component attribute form according to the project requirement and the project requirement;
and step S204, importing the reusable component XML file into a UPPAAL tool, and establishing a verifier for abstract, modification and formalization verification of the component attribute.
The UPPAAL worker has an integrated environment which is easy for the user to operate and use, and the main graphical user interface comprises three parts: system editor (system editor), Simulator (Simulator) and Verifier (Verifier). A system editor is used to create and edit a system to be analyzed, a system is 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 possible execution of the built system model for errors in order to find errors before verification. The verifier checks the reusable component XML file for clock constraints and liveness, etc. by quickly searching the state space of the system. UPPAAL provides a visual interface that describes the automaton.
The verification process applied to the present embodiment includes the following steps:
1) importing formal verification criteria and reusable components into a verifier;
2) the verifier judges whether the formal verification criterion is in accordance with the state conversion and clock constraint of the reusable component, and if so, the verifier outputs the reusable component 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 modeling submodule to be subjected to state parameter modification or/and time parameter modification, and then the reusable component is input into the verifier again to be subjected to re-verification.
And the packaging submodule is used for packaging the reusable component which passes the verification.
Specifically, the verified reusable components are packaged into a visual graphical form, a matching relation is established between the graphs and the reusable components, and when the graphs are selected by a user, the graphs are automatically linked to the XML files of the reusable components corresponding to the graphs.
The software component library is used for storing the reusable components which are formally verified and packaged, so that the reusable components can be directly called when a software code framework is subsequently reconstructed. The efficiency of the software code framework is improved by using the encapsulated reusable components, and the quality of the software code framework can be ensured because the invoked reusable components are verified by experience and encapsulated.
Specifically, a framework generation module user selects a corresponding formalized verified software component module from a modular reusable component library according to embedded software requirements, and an embedded software code framework containing a communication module is generated by adopting a model-driven component code automatic generation technology;
the model-driven component code-based automatic generation technique;
the code automatic generation adopts a code generation technology based on Model Driven Architecture (MDA). Application models for MDA include a Computational Independent Model (CIM), a Platform Independent Model (PIM), and a Platform Specific Model (PSM). The method comprises the steps of firstly writing PIM according to components, 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 conforms to the aerospace safety specification, a code constraint rule formed by software safety design, model software reliability safety design criteria, aerospace model software C language safety programming specifications and the like is added in the safety mapping process from the PSM to the code, and finally, a component code of a standard specification is generated.
And editing the software code in the software code editing module according to the service 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 the executable software.
In order to enable the executable software to meet the reliability requirement of the aerospace model, piece defect detection and online software operation monitoring are required to be carried out on the executable software.
Preferably, the software architecture development system of this embodiment further includes: a software defect finding module and an autonomous diagnosis module;
and the software defect finding module is used for detecting the defects of the generated executable software according to an expert knowledge base, positioning the defect positions and generating a defect report so as to assist in repairing the defects of the executable software.
Specifically, the software defect finding 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 semantic 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 words, performs semantic analysis and semantic analysis on word information, extracts attribute information including types (constants, variables, arrays, labels and the like), types (integer, real, logic, character and the like) and a syntax tree visually representing a syntax structure of a source program, extracts and calculates a time sequence feature on the basis of the syntax tree, performs time sequence analysis, optimizes a program, 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 recognition module, according to a grammatical constraint condition specified by an expert knowledge base, corresponding node information is searched on an abstract syntax tree, and functional semantics expressed by software are recognized.
The expert knowledge base includes expert knowledge for providing software design knowledge, and knowledge related to software testing and software experimentation related to the problem to be solved.
The defect judging module is used for judging the defects in the software according to the results of word meaning analysis, semantic analysis and time sequence analysis and the recognition result of functional semantics;
specifically, in the process of searching corresponding node information on the abstract syntax tree and identifying the functional semantics expressed by the software, if the node information corresponding to the node information cannot be found on the abstract syntax tree, the program has defects.
And the defect report generation module is used for judging the cause of the defect in the software, positioning the program unit or statement of the defect and generating a defect report.
The defect positioning is to utilize various information for the found software defects, judge the cause of the problem and position the program unit or statement of the defect.
The fault report can analyze a software fault model according to a software fault phenomenon and a fault position causing a software fault, determine a software fault reason, analyze a fault influence range and a fault hazard level, and perform error prompt on a corresponding fault.
Specifically, the self-diagnosis module monitors the software running process, performs self-diagnosis on the SEU fault in the software running process, finds the fault in the software running process, and realizes fault detection, fault location and fault repair.
In summary, compared with the prior art, the software architecture development system of the embodiment can enrich software development automation technology, improve software development efficiency, shorten protocol development period, and implement fault online diagnosis and repair, has SEU fault tolerance capability, can save a large amount of manual cost, reduce workload of encoding personnel, avoid some code defects, and improve security and robustness of codes.
The invention takes the aerospace embedded system software as a research object, and has more practicability by combining the architectural design with the actual engineering practice. Meanwhile, formal verification of the components is introduced into the architecture design, so that the method is more accurate, and the reliability of the architecture is effectively guaranteed at the component level.
Example two
In this embodiment, a software architecture development system based on the first embodiment develops a data analysis layer CAN bus data management architecture, as shown in fig. 3, specifically includes the following steps:
step S1, extracting and classifying software key information in the aerospace model software requirement document by using an information extraction module;
extracting software key information of the CAN bus interface according to requirement documents such as a design specification, a requirement specification, a CAN bus interface communication protocol file and the like of the aerospace model software aerospace system;
s2, performing 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 the software key information of the CAN bus interface, extracting the CAN interface verification criterion in the requirement;
performing reusable component design on data management of a CAN bus of a data management layer from a software architecture level;
carrying out 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 component to obtain a packaged formalized verification CAN bus data management reusable component;
step S3, storing the encapsulated and formalized verification CAN bus data management reusable assembly into a reusable assembly library;
step S4, in the frame generating module, selecting corresponding data management layer CAN bus data management reusable components which are formally verified from the reusable component library according to embedded software requirements, and generating an embedded software code frame containing interface components;
step S5, in the software code editing module, under the generated software framework, the software code editing is completed according to rich software such as service logic, control logic, algorithm logic and the like of the software;
step S6, in the software defect finding module, detecting software defects according to expert knowledge, realizing defect positioning and generating a defect report;
and step S7, in the self-diagnosis module, monitoring the software operation process, performing self-diagnosis on the SEU fault in the software operation, finding the fault in the software operation, and realizing fault detection, fault positioning and fault repair.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention.
Claims (10)
1. A software architecture development system for an aerospace embedded system is characterized by comprising:
the information extraction module is used for extracting and classifying software key information in the aerospace model software requirement document;
the modeling verification module is used for performing formal modeling, verification and encapsulation on the software key information to obtain a reusable component of the software;
the software component library is used for storing the reusable components;
the framework generation module is used for constructing a software code framework, and the code framework is formed by reusable components called from a software component library;
and the software code editing module is used for editing the software code according to the service logic, the control logic and the algorithm logic of the software under the software code framework to generate executable software.
2. The software architecture development system of claim 1, further comprising a software defect finding module, configured to perform defect detection on the generated executable software according to an expert knowledge base, locate a defect position, and 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 autonomic diagnosis module for monitoring the running process of the executable software online for autonomic diagnosis, fault location and fault repair.
4. The software architecture development system of claim 1, wherein the modeling validation module comprises a validation criteria sub-module, a modeling sub-module, a validator, and a packaging sub-module;
the verification criterion submodule is used for establishing a software formal verification criterion according to the software key information;
the modeling submodule is used for generating a reusable component of the software, and the reusable component realizes multi-level reuse from a software architecture;
the verifier is used for performing formal verification on the reusable component according to the established software formal verification criterion;
the packaging sub-module is used for packaging the reusable component which passes the verification;
specifically, the verifier judges whether the formal verification criterion conforms to the state conversion and clock constraint of the reusable component, and if so, the verifier outputs the reusable component 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 modeling submodule for state parameter modification or/and time parameter modification, and then returned to the verifier for re-verification.
5. The software architecture development system of claim 4, wherein the construction process of the validator comprises:
establishing a changeable attribute table; abstracting the alterable attribute of the reusable component in a table form aiming at each component according to the functional characteristics, the interface state and the communication process realized by the reusable component;
establishing a reusable component XML file; determining the working state of the reusable components, triggering events, clock constraints, control flow settings and state transition events, modeling by using a formalization method of a time automata model, and generating a reusable component XML file by each reusable component;
establishing an association relation; associating the attribute table capable of being changed with the XML file of the reusable component through field matching; the user realizes the automatic modification of the XML file of the reusable component by modifying the attribute table of the component;
and importing the reusable component XML file into a UPPAAL tool, and establishing a verifier for abstract, modification and formalized verification of the component property.
6. The software architecture development system of claim 4, wherein the formal verification criteria include interface verification criteria, timing verification criteria, and interaction verification criteria.
7. The software architecture development system of claim 6, wherein the interface validation criteria include validation criteria for physical interfaces including bus interfaces, data transfer interfaces;
the time sequence verification criterion comprises verification criteria including state bounded response, multi-state concurrency, time constraint and sequence;
the interactive relation verification criterion comprises verification criteria of response communication, nested calling, multicast communication and synchronous communication.
8. The software architecture design method of claim 1, wherein the reusable component comprises a master control layer, a data management layer, a scheduling management layer and an interface driver layer;
wherein the content of the first and second substances,
the interface driving layer is used for completing the initial configuration and loading of the interface, providing bottom interface service and providing a normal operation 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 services comprise function call service, interrupt processing service, task query service, event service and bus service;
the data management layer is used for packaging different data processing function modules, including functions for realizing specific functions and providing a callable API (application program interface) to the main control layer;
and the main control layer is used for realizing the control of the business processing flow by calling the API.
9. The software architecture design method of any one of claims 2-8, wherein the software defect finding 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 the defects in the software according to the results of word meaning analysis, semantic analysis and time sequence analysis and the recognition result of functional semantics;
and the defect report generation module is used for judging the cause of the defect in the software, positioning the program unit or statement of the defect and generating a defect report.
10. The software architecture design method of any one of claims 3-8,
and the software self-diagnosis module is used for self-diagnosing SEU faults in software operation, finding the faults in the software operation and carrying out fault detection, fault positioning and fault repair in the executable software operation process.
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 true CN112416337A (en) | 2021-02-26 |
| CN112416337B 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) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947902A (en) * | 2021-04-25 | 2021-06-11 | 西安瑞思达信息科技有限公司 | System development management platform |
| CN114741052A (en) * | 2022-04-21 | 2022-07-12 | 中国航空无线电电子研究所 | Requirement table model-oriented formalized semantic analysis and inspection method |
| CN115002189A (en) * | 2022-04-21 | 2022-09-02 | 上海蓝箭鸿擎科技有限公司 | Spacecraft-oriented high-separation distributed system software architecture |
| CN114995226A (en) * | 2022-05-26 | 2022-09-02 | 中国科学院国家空间科学中心 | Flow control system and method for aerospace embedded equipment |
| CN115658021A (en) * | 2022-11-07 | 2023-01-31 | 苏州数设科技有限公司 | Method and device for determining dynamic model, storage medium and electronic equipment |
| CN117421009A (en) * | 2023-12-19 | 2024-01-19 | 深圳市航盛电子股份有限公司 | Signal code generation method, device, terminal equipment and storage medium |
Citations (12)
| 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 |
| CN1932759A (en) * | 2006-10-13 | 2007-03-21 | 上海科泰世纪科技有限公司 | Method for adapting and extending XML tag and assembly in structural software system |
| CN101017458A (en) * | 2007-03-02 | 2007-08-15 | 北京邮电大学 | Software safety code analyzer based on static analysis of source code and testing method therefor |
| CN101089814A (en) * | 2007-07-12 | 2007-12-19 | 浙江大学 | Software applied frame for data analysing instrument equipment and device and method for developing embedded system using the frame |
| 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 |
| CN102567163A (en) * | 2011-12-16 | 2012-07-11 | 华东师范大学 | Method for identifying cooperative behaviors of components of real-time embedded system based on UPPAAL tool |
| CN103593326A (en) * | 2013-11-07 | 2014-02-19 | 国家电网公司 | IEC61850 software library assembly for network processing unit chip and achieving method of IEC61850 software library assembly |
| GB201613356D0 (en) * | 2015-08-05 | 2016-09-14 | Gen Electric | System and method for model based technology and process for safety-critical software development |
| CN106933580A (en) * | 2017-03-02 | 2017-07-07 | 北京天恒长鹰科技股份有限公司 | A kind of embedded-type software architecture system |
| 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 |
-
2020
- 2020-11-11 CN CN202011255814.1A patent/CN112416337B/en active Active
Patent Citations (12)
| 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 |
| CN1932759A (en) * | 2006-10-13 | 2007-03-21 | 上海科泰世纪科技有限公司 | Method for adapting and extending XML tag and assembly in structural software system |
| CN101017458A (en) * | 2007-03-02 | 2007-08-15 | 北京邮电大学 | Software safety code analyzer based on static analysis of source code and testing method therefor |
| CN101089814A (en) * | 2007-07-12 | 2007-12-19 | 浙江大学 | Software applied frame for data analysing instrument equipment and device and method for developing embedded system using the frame |
| 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 |
| CN102567163A (en) * | 2011-12-16 | 2012-07-11 | 华东师范大学 | Method for identifying cooperative behaviors of components of real-time embedded system based on UPPAAL tool |
| CN103593326A (en) * | 2013-11-07 | 2014-02-19 | 国家电网公司 | IEC61850 software library assembly for network processing unit chip and achieving method of IEC61850 software library assembly |
| GB201613356D0 (en) * | 2015-08-05 | 2016-09-14 | Gen Electric | System and method for model based technology and process for safety-critical software development |
| CN106933580A (en) * | 2017-03-02 | 2017-07-07 | 北京天恒长鹰科技股份有限公司 | A kind of embedded-type software architecture system |
| 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 |
Non-Patent Citations (2)
| Title |
|---|
| H. TOETENEL,ETC.: "A timed automata semantics for real-time UML specifications" * |
| 张富为: "基于构件的软件复用技术的研究与应用" * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947902A (en) * | 2021-04-25 | 2021-06-11 | 西安瑞思达信息科技有限公司 | System development management platform |
| CN112947902B (en) * | 2021-04-25 | 2023-05-12 | 广州佳禾科技股份有限公司 | System development management platform |
| CN114741052A (en) * | 2022-04-21 | 2022-07-12 | 中国航空无线电电子研究所 | Requirement table model-oriented formalized semantic analysis and inspection method |
| CN115002189A (en) * | 2022-04-21 | 2022-09-02 | 上海蓝箭鸿擎科技有限公司 | Spacecraft-oriented high-separation distributed system software architecture |
| CN114741052B (en) * | 2022-04-21 | 2024-04-12 | 中国航空无线电电子研究所 | Formalized semantic analysis and inspection method for demand form model |
| CN114995226A (en) * | 2022-05-26 | 2022-09-02 | 中国科学院国家空间科学中心 | Flow control system and method for aerospace embedded equipment |
| CN115658021A (en) * | 2022-11-07 | 2023-01-31 | 苏州数设科技有限公司 | Method and device for determining dynamic model, storage medium and electronic equipment |
| CN115658021B (en) * | 2022-11-07 | 2023-12-12 | 苏州数设科技有限公司 | Determination method and device of dynamic model, storage medium and electronic equipment |
| CN117421009A (en) * | 2023-12-19 | 2024-01-19 | 深圳市航盛电子股份有限公司 | Signal code generation method, device, terminal equipment and storage medium |
| CN117421009B (en) * | 2023-12-19 | 2024-04-19 | 深圳市航盛电子股份有限公司 | Signal code generation method, device, terminal equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112416337B (en) | 2023-05-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112416337B (en) | Software architecture development system for aerospace embedded system | |
| Brottier et al. | Metamodel-based test generation for model transformations: an algorithm and a tool | |
| Rasool et al. | Flexible design pattern detection based on feature types | |
| TW200412495A (en) | A generic software testing system and mechanism | |
| CN110222318B (en) | XML-based data generation tool development method | |
| CN109634600B (en) | Code generation method based on security extension SysML and AADL models | |
| Usman et al. | A survey of consistency checking techniques for UML models | |
| CN110209389B (en) | XML-based data generation tool development system | |
| CN112416336B (en) | Software architecture design method for aerospace embedded system | |
| Pastor et al. | From object oriented conceptual modeling to automated programming in java | |
| Zhao et al. | Towards formal verification of UML diagrams based on graph transformation | |
| Krishnan et al. | An integrated system design and safety framework for model-based safety analysis | |
| Ratiu et al. | FASTEN: an extensible platform to experiment with rigorous modeling of safety-critical systems | |
| Friedrich et al. | Knowledge engineering for configuration systems | |
| Kirby et al. | SCR: A practical approach to building a high assurance COMSEC system | |
| Pang et al. | Automatic model generation of IEC 61499 function block using net condition/event systems | |
| Brottier et al. | Producing a global requirement model from multiple requirement specifications | |
| KR102399597B1 (en) | Intelligent safety analysis technology using AI | |
| Salay et al. | Managing related models in vehicle control software development | |
| Meedeniya | Correct model-to-model transformation for formal verification | |
| Grunske et al. | An automated dependability analysis method for COTS-based systems | |
| CN114647401A (en) | Model verification method suitable for distributed system of SysML, Simulink and AADL | |
| KR20220073151A (en) | FMEA failure mode recommend system | |
| Nagoya et al. | Developing a web dictionary system using the SOFL three-step specification approach | |
| George et al. | Improving design quality by automatic verification of activity diagram syntax |
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 |