Overview
​
FMEDA objects are most commonly mapped to design instances. For parts and subparts instance boundaries are always sufficient, but for FM mapping there are cases where module boundaries don’t exist or don’t provide the right level of precision:
-
When a leaf instance doesn’t provide enough resolution – as created by the designer.
-
When a leaf instance doesn’t provide enough resolution – when created by synthesis by flattening a design hierarchy.
-
When an instance is not a leaf, but more resolution is needed for its own (sparse) logic (less common).
In such cases the safety engineer is interested in performing an analysis on design instances to extract elementary functions from the design logic. These are extracted based on selecting points on the design when server as functionality end points or design constraint, and then performing a “cone of logic” analysis.
 Safety Planner |  TD Control |  Design System |  First Baby |  Spark |
|---|---|---|---|---|
 Day2Gift |  Orad |  ProSet |