Software FMEA (Failure Mode and Effects Analysis) method based on Altarica formalized language
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
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
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]
PUM
Abstract
Description
Claims
Application Information
- R&D Engineer
- R&D Manager
- IP Professional
- Industry Leading Data Capabilities
- Powerful AI technology
- Patent DNA Extraction
Browse by: Latest US Patents, China's latest patents, Technical Efficacy Thesaurus, Application Domain, Technology Topic, Popular Technical Reports.
© 2024 PatSnap. All rights reserved.Legal|Privacy policy|Modern Slavery Act Transparency Statement|Sitemap|About US| Contact US: help@patsnap.com