Software FMEA (Failure Mode and Effects Analysis) method based on Altarica formalized language
What is Al technical title?
Al technical title is built by PatSnap Al team. It summarizes the technical point description of the patent document.
An analysis method and basic software technology, applied in the field of software FMEA analysis based on the Altarica formal language, can solve the problems of heavy workload, analysis quality depends on knowledge level, unable to effectively guarantee analysis quality, etc., to reduce the workload. Effect
Active Publication Date: 2017-05-31
CHINA TECHENERGY +1
View PDF3 Cites 4 Cited by
Summary
Abstract
Description
Claims
Application Information
AI Technical Summary
This helps you quickly interpret patents by identifying the three key elements:
Problems solved by technology
Method used
Benefits of technology
Problems solved by technology
However, due to the characteristics of the software itself, when using the FMEA analysis method, there are problems such as the analysis granularity cannot be grasped, and the workload is huge; the analysis quality depends heavily on the knowledge level of the analysts, and the analysis quality cannot be effectively guaranteed
Method used
the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
View more
Image
Smart Image Click on the blue labels to locate them in the text.
Viewing Examples
Smart Image
Click on the blue label to locate the original text in one second.
Reading with bidirectional positioning of images and text.
Smart Image
Examples
Experimental program
Comparison scheme
Effect test
Embodiment 1
[0034] A kind of software FMEA analysis method based on Altarica formal language of the present invention comprises the following steps:
[0035] Step 1: Identify the software data flow and draw a data flow diagram,
[0036] Identify the information that the software needs to transmit, find the source of the information, and draw a data flow diagram according to the data transmission path between each functional block;
[0037] Step 2: Modeling for the software to be analyzed,
[0038] Build a common basic software model:
[0039] ①Abstract software behavior as data receiving and sending;
[0040] ②Describe the state of the software from three aspects of time, space, and behavioral connotation, that is, whether the data is the latest data, whether the data space is full, and whether the meaning of the data represents execution, non-execution or unknown;
[0041] ③Relationship between software state and software behavior: when the data is new in time and not empty in space, ...
Embodiment 2
[0051] Software description: execute software configuration data reading (from FLASH), analyze and write the analyzed data into dual-port RAM.
[0052] 1. Identify the data flow and draw a data flow diagram, such as figure 2 shown.
[0053] 2. Formal description of the configuration function
[0054]
[0055]
[0056]
[0057] 3. Define the error of writing data into dual-port RAM as the failure of the configuration function and describe it in a formal language
[0058] [(Out.action=failure)&(s=finishing)]
[0059] 4. Use tools to search for state transition paths that meet the requirements, such as image 3 .
[0060] 5. Analyze the cause and probability of the failure mode and fill in the FMEA form, such as Figure 4 .
[0061] The FMEA form is as follows:
[0062]
the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
Login to view more
PUM
Login to view more
Abstract
The invention discloses a software FMEA (Failure Mode and Effects Analysis) method based on an Altarica formalized language. The software FMEA method comprises the following steps: step 1: identifying data streams of software to be analyzed and drawing a data stream graph; step 2: establishing a basic software model for the software to be analyzed; step 3: defining failures of the software to be analyzed, and describing the failures of the software to be analyzed by utilizing each state of the basic software model established in the step 2; step 4: searching all state transmission paths which meet a failure definition of the software to be analyzed, wherein each transmission path is a failure mode; step 5: analyzing each state transmission path meeting the failure definition of the software to be analyzed and filling an FMEA table. According to the software FMEA method disclosed by the invention, a software function unit is modularized, and a formalized tool is used for analyzing, so that the working amount is reduced; the software function unit is modularized, so that the model is reutilized. Aiming at different software function units, verification attributes are summarized and concluded, and accumulation and sharing of knowledge are realized.
Description
technical field [0001] The invention relates to the technical field of software reliability analysis of nuclear safety level digital instrument and control equipment in the nuclear power industry, in particular to a software FMEA analysis method based on the Altarica formal language. Background technique [0002] Software reliability is the ability of a software product to complete specified functions under specified conditions and within a specified time interval. At present, there are two main categories of software reliability analysis methods, qualitative analysis methods and quantitative analysis methods. Among them, the quantitative analysis method is based on probability statistics, but due to the characteristics of software itself, the confidence level of quantitative analysis of software reliability is not high at this stage, and qualitative analysis of software is generally based on classical reliability analysis methods such as FMEA, FTA, etc. [0003] FMEA means...
Claims
the structure of the environmentally friendly knitted fabric provided by the present invention; figure 2 Flow chart of the yarn wrapping machine for environmentally friendly knitted fabrics and storage devices; image 3 Is the parameter map of the yarn covering machine
Login to view more
Application Information
Patent Timeline
Application Date:The date an application was filed.
Publication Date:The date a patent or application was officially published.
First Publication Date:The earliest publication date of a patent with the same application number.
Issue Date:Publication date of the patent grant document.
PCT Entry Date:The Entry date of PCT National Phase.
Estimated Expiry Date:The statutory expiry date of a patent right according to the Patent Law, and it is the longest term of protection that the patent right can achieve without the termination of the patent right due to other reasons(Term extension factor has been taken into account ).
Invalid Date:Actual expiry date is based on effective date or publication date of legal transaction data of invalid patent.
Login to view more 
Login to view more