<?xml version="1.1" encoding="UTF-8"?>
<de.ikv.analyze.checklist:Checklist xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:de.ikv.analyze.checklist="http:///de/ikv/analyze/checklist.ecore" xmi:id="_EN-yECc-Eea-8YkLqRAPAA" mediniIdentifier="_EN-yECc-Eea-8YkLqRAPAA" name="Tasklist: Development of HW Safety Concept (ISO26262:Part5)" version="31/05/2016 16:43">
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJESOsEem7IbokExUh5g" mediniIdentifier="_32yJESOsEem7IbokExUh5g" name="Generic Tasks" note="This activity sets up the general information for the safety project." user_Description="">
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJEiOsEem7IbokExUh5g" mediniIdentifier="_32yJEiOsEem7IbokExUh5g" name="Specify Project properties" user_Description="Select the project and fill in all custom specific properties for the project using the tab &quot;Profile&quot; of the Properties View">
      <artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJEyOsEem7IbokExUh5g" mediniIdentifier="_32yJEyOsEem7IbokExUh5g" name="Check/Update general settings" user_Description="In the Project Settings check the Guideword templates, the dynamic constraints and the risk matrix settings to ensure they are sufficient for the project.&#xA;Also check/update the mission profile(s) and the list of safety mechanisms and add the required Failure Rate Catalogs&#xA;">
      <artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_BeE1oCO8Eem7IbokExUh5g" mediniIdentifier="_BeE1oCO8Eem7IbokExUh5g" name="Adjust Tasklist" user_Description="Adjust this Tasklist according to the project scope and the company specific process">
      <artifactTypes href="http:///de/ikv/analyze/checklist.ecore#//Checklist"/>
    </subItems>
  </items>
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvyQSc-Eea-8YkLqRAPAA" mediniIdentifier="_JFvyQSc-Eea-8YkLqRAPAA" name="Preparation Activities" note="This activities capture and organize the prerequisite and supporting information" user_Description="Make sure all required input work products are available">
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJFSOsEem7IbokExUh5g" mediniIdentifier="_32yJFSOsEem7IbokExUh5g" name="Technical Safety Requirements" user_Description="Add the TSRs which are related to the HW. If possible import from RMS or use a model from an existing medini project. This shall at least include technical safety requirements which shall be implemented  and safety goals. These requirements shall be organized in the folder &quot;Technical Safety Requirements&quot;">
      <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJFiOsEem7IbokExUh5g" mediniIdentifier="_32yJFiOsEem7IbokExUh5g" name="Technical Safety Architecture" user_Description="If possible this can be imported from an external Architecture Design Tool or from an existing medini project. Otherwise the architecture modeling capabilities of medini can be used to create this architecture.&#xA;It shall be captured in the folder Technical Safety Architecture.">
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DDOhcCOvEem7IbokExUh5g" mediniIdentifier="_DDOhcCOvEem7IbokExUh5g" name="(optional) System Level Safety Analyses" user_Description="If available add system level safety analyses (FMEA, FTA) which are based on the Technical Safety Architecture. These could come from a separate medini project or be imported from 3rd party tools (e.g. as MSR-FMEA).">
      <artifactTypes href="http://www.ikv.de/analyze/metamodels/FMEA/1.0#//FMEAWorksheet"/>
      <artifactTypes href="http://www.ikv.de/medini/metamodels/FTA/2.0#//FTAModel"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJFyOsEem7IbokExUh5g" mediniIdentifier="_32yJFyOsEem7IbokExUh5g" name="(optional) HW Level Functional Requirements" user_Description="This is the general requirements specification at HW level - it should come from the HW requirements engineer- if possible import from RMS.&#xA;These requirements shall be put into the folder HW Safety Requirements.">
      <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJGCOsEem7IbokExUh5g" mediniIdentifier="_32yJGCOsEem7IbokExUh5g" name="(optional) HW Block Level System Design" user_Description="This should come from the HW engineering/architecture team - if possible they can be imported from an external Architecture Design Tool or from an existing medini project. Otherwise the architecture modeling capabilities of medini can be used to create this architecture.&#xA;It shall be captured in the folder Hardware Safety Architecture.">
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvyQic-Eea-8YkLqRAPAA" mediniIdentifier="_JFvyQic-Eea-8YkLqRAPAA" name="Import/Update HW Part Library" user_Description="If such a library does not exist, it has to be created as a separate medini project (see template &quot;HWLibraryTemplate_With_FailureModeLibrary&quot;). The library shall be imported into the folder &quot;Hardware Safety Architecture&quot;">
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
  </items>
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJGSOsEem7IbokExUh5g" mediniIdentifier="_32yJGSOsEem7IbokExUh5g" name="Create HW Safety Concept" user_Description="">
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJGiOsEem7IbokExUh5g" mediniIdentifier="_32yJGiOsEem7IbokExUh5g" name="HW Safety Requirements and Safety Mechanisms (HW-SR/SM)" user_Description="Define the HW solution for the safety of the item">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJGyOsEem7IbokExUh5g" mediniIdentifier="_32yJGyOsEem7IbokExUh5g" name="Top Level HW-SR" user_Description="&#xA;Use the graphical and/or the List editor for requirements as needed to define hierarchies and details for requirements. Drag&amp;Drop the appropriate TSC onto the diagram as a starting point to create HW safety requirements.">
        <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJHCOsEem7IbokExUh5g" mediniIdentifier="_32yJHCOsEem7IbokExUh5g" name="Define further HW-SR" user_Description="Break-down the top-level HW-Safety Requirements into more details - use sub-requirements and decomposition as needed; use Contributes only for relations crossing hierarchies &#xA;Various techniques as FTA and FMEA may be used to identify requirements. Moreover, already existing requirements may be included in the list of technical safety requirements.">
        <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJHSOsEem7IbokExUh5g" mediniIdentifier="_32yJHSOsEem7IbokExUh5g" name="Organize Requirements" user_Description="One or multiple diagrams should be used to organize/manage the safety goals and functional safety requirements. Use Sub-requirments relations and contributes relations as needed. The details of the requirements should be captured using the properties view and/or the Requirements List Editor."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJHiOsEem7IbokExUh5g" mediniIdentifier="_32yJHiOsEem7IbokExUh5g" name="(Optional) Synchronize with RMS" user_Description="Requirements may be imported/exported synchronized with Requirements Management Systems like Doors NG, PTC Integrity, JAMA ..."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJHyOsEem7IbokExUh5g" mediniIdentifier="_32yJHyOsEem7IbokExUh5g" name="Define/Derive System HW Safety Mechanisms" user_Description="Group them in a Safety Mechanism Collection and trace them to the related requirement(s). Optionally relations to system level SM can be specified by traces.">
        <artifactTypes href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//SafetyMechanism"/>
        <artifactTypes href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//MeasureCatalog"/>
      </subItems>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJICOsEem7IbokExUh5g" mediniIdentifier="_32yJICOsEem7IbokExUh5g" name="HW Safety Architecture " user_Description="The architecture should be based on the BOM for the HW solution. If possible it should be structured into packages or components following the HW block level architecture resp. the organization of the PCB design into circuit blocks.">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvySCc-Eea-8YkLqRAPAA" mediniIdentifier="_JFvySCc-Eea-8YkLqRAPAA" name="Attach  BOM and schematics as external files" user_Description="Put them into the folder System Design -&gt; Hardware Safety Architecture">
        <artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJExternalDocument"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_E1DZkPABEemxD416Z3DJbQ" mediniIdentifier="_E1DZkPABEemxD416Z3DJbQ" name="Add the appropriate HW Part Library to the project" user_Description="In the HW design folder USe Import -&gt; Import element library.">
        <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvyRic-Eea-8YkLqRAPAA" mediniIdentifier="_JFvyRic-Eea-8YkLqRAPAA" name="Create BOM based HW Architecture" user_Description="Create an new System Model in the HW design folder and Import the BOM via &quot;Import-&gt; Elements from CSV/Excel&quot;.  Use the imported HW library as a look-up database for the reliability&amp;failure information. Map for the import the reference id of the BOM to the element name in medini and the part number of the BOM to part number in medini. If circuit block information are available in the BOM, they should be mapped to the medini property circuit block.">
        <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_LMki8CO2Eem7IbokExUh5g" mediniIdentifier="_LMki8CO2Eem7IbokExUh5g" name="(Optional) Update Model with a new version of the BOM" user_Description="In case a new version of the BOM is available, the HW Architecture has to be updated using &quot;Update Elements from CSV/Excel&quot;. Use the same mapping as for the initial import. ">
          <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
        </subItems>
        <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvySSc-Eea-8YkLqRAPAA" mediniIdentifier="_JFvySSc-Eea-8YkLqRAPAA" name="Organize BOM model using packages and/or traces to components of the TSA" user_Description="If circuit block information have been imported, use &quot;Execute-&gt;Restucture HW Model&quot; from the Architecture model to automatically structure the imported BOM elements. Otherwise manually create appropriate folders or components and move the HW elements into their containers.">
        <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvyRyc-Eea-8YkLqRAPAA" mediniIdentifier="_JFvyRyc-Eea-8YkLqRAPAA" name="Assign mission profile to BOM model and calculate failure rates" user_Description="Mission profiles can be assigned to individual folders/components as well as to the complete architecture model. Afterwards the failure rate calculation can be triggered. Note, the calculation has to be triggered after any of the following events, update of the architecture, update of the imported library, or any change in the mission profiles. Any failure reported during the failure rate calculation shall be handled!&#xD;&#xA;For IEC62380 and FIDES the mission profiles are required, for othe reliability standards this is optional.">
        <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJJSOsEem7IbokExUh5g" mediniIdentifier="_32yJJSOsEem7IbokExUh5g" name="Indicate implementation of Safety Mechanisms" user_Description="For the safety mechanisms select the system or HW elements which implement the mechanism."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJJyOsEem7IbokExUh5g" mediniIdentifier="_32yJJyOsEem7IbokExUh5g" name="Allocate requirements" user_Description="Allocate all HW Safety requirements  to elements of the HW Safety architecture. Usually an allocation to components/folders corresponding to the circuit blocks is sufficient.&#xA;The Allocate Elements matrix or the Requirements List editor can be used to define the allocations.">
        <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
        <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJKCOsEem7IbokExUh5g" mediniIdentifier="_32yJKCOsEem7IbokExUh5g" name="Determine ASIL for functions and elements " user_Description="Use the &quot;Compute ASIL&quot; function from the Safety context menu of the architecture. Review the ASIL of the different elements and adjust the independence property in the Safety tab of the Property view of the architecture elements. Toggle the display of the ASIL in the diagram(s) as required."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJKSOsEem7IbokExUh5g" mediniIdentifier="_32yJKSOsEem7IbokExUh5g" name="(optional) Associate Technical architecture and BOM based architecture" user_Description="Use the Allocate Elements from the Technical Safety Architecture to associate the elements of the Technical Safety Architecture to elements of the HW Safety Architecture (at block level)."/>
    </subItems>
  </items>
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJKiOsEem7IbokExUh5g" mediniIdentifier="_32yJKiOsEem7IbokExUh5g" name="Perform Safety Analyses" user_Description="This is an iterative activity which may have to be done multiple times as it will result in new requirements and subsequently in changes in the HW Safety Architecture. Also a continuous switch between the different safety analyses may be helpfull to take over information from one analysis into another one.">
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJKyOsEem7IbokExUh5g" mediniIdentifier="_32yJKyOsEem7IbokExUh5g" name="Perform a Project Validation" user_Description="Use Validate from the context menu of the project. Investigate and handle each of the errors &amp; warnings produced by the validation. Such a validation should be repeated also after completing all safety analyses."/>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJLCOsEem7IbokExUh5g" mediniIdentifier="_32yJLCOsEem7IbokExUh5g" name="Organize Safety Analyses" user_Description="As needed create subfolders in the different packages of the Safety Analyses folder to organize the safety analyses tables and diagrams/models."/>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJLiOsEem7IbokExUh5g" mediniIdentifier="_32yJLiOsEem7IbokExUh5g" name="Perform FMEA" user_Description="Derive the FMEA Worksheet from the BOM based Architecture - it shall be revisited after updates in requirements/architecture.&#xA;Depending on the focus the FMEA may be restricted to functions, components. Also other filters may be applied - use the Coverpage of the derived FMEA to adjust these settings. As this is a bottom-up method, start with setting the analysis level to &quot;Leafs&quot; and later change it to higher levels.&#xA;Note: If an FMEA is already available from external sources  (as medini project or MSR-FMEA) it can be imported or merged into the project.">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJLyOsEem7IbokExUh5g" mediniIdentifier="_32yJLyOsEem7IbokExUh5g" name="Investigate cause/effect chains for malfunctions and failure modes" user_Description="Bottom-up approach - the Severity will be derived from the top-level effect. The Failure Net Editor should be used complementary for this activity. Additional malfunctions may be created in the course of this activity.&#xA;Root causes discovered during the FMEA should be capture in a Failure Collection of type Error.  Effects for failures of HW elements should be selected from malfunctions or failure modes of the related elements in the Technical Safety Architecture."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJMCOsEem7IbokExUh5g" mediniIdentifier="_32yJMCOsEem7IbokExUh5g" name="Add Detection/Prevention measures for systematic faults" user_Description="For the root causes define appropriate Detection/Prevention measures. These should be organized in one or two Measure Collection(s) of type General Measure for Prevention and Detection measures.&#xA;Derive or trace to technical requirements to implement the measures.&#xA;Specify the detection value for the measures as well as the occurrence value(s) for the root causes."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJMSOsEem7IbokExUh5g" mediniIdentifier="_32yJMSOsEem7IbokExUh5g" name="Evaluate FMEA result" user_Description="Use the Risk-graph and/or the RPN to evaluate the FMEA results."/>
      <artifactTypes href="http://www.ikv.de/analyze/metamodels/FMEA/1.0#//FMEAWorksheet"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JFvyTSc-Eea-8YkLqRAPAA" mediniIdentifier="_JFvyTSc-Eea-8YkLqRAPAA" name="Perform Diagnostic Coverage / SPF&amp;LF Metrics Calculation" user_Description="This shall be done at least for all Safetygoals with ASIL (B), C, D.&#xD;&#xA;Derive the FMEDA Worksheet from the BOM based Architecture using Derive-&gt;Diagnostic Coverage Worksheet. The following settings at the worksheet cover page are recommended:&#xD;&#xA;     Metrics at level: leafs&#xD;&#xA;     Show only safety mechansisms ...: Active&#xD;&#xA;     Hide transient failures: Active&#xD;&#xA;     Hide Ports: Active">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_hMjZkCO8Eem7IbokExUh5g" mediniIdentifier="_hMjZkCO8Eem7IbokExUh5g" name="Organize Metric calculation" user_Description="Decide how to organize FMEDA in case of multiple safety goals. Medini does support three options:1. Individual DC Worksheets for the safety goals; 2. Multiple Safety goals within a single Worksheet; 3. Multiple Safety Goals with individual evaluations within a single worksheet"/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_oJ3J8CO8Eem7IbokExUh5g" mediniIdentifier="_oJ3J8CO8Eem7IbokExUh5g" name="Fill in safety data into the Worksheet" user_Description="For each failure mode in the worksheet the following topics have to be evaluated and filled in: &#xD;&#xA;1. Safety Related; &#xD;&#xA;2. Safe Fault Fraction; &#xD;&#xA;3. Violates Safety goals as SPF (if yes, applied safety mechanisms can be selected); &#xD;&#xA;4. Violates Safety goals as LF (if yes, applied safety mechanisms can be selected)&#xD;&#xA;The information in columns Effect, Top-Level-Effect and related FTA event can be used as additional justification. Also additional remarks/justifications may be added to the Comments cells for component and for failure mode."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_t3QxoCO8Eem7IbokExUh5g" mediniIdentifier="_t3QxoCO8Eem7IbokExUh5g" name="Evaluate Metrics result" user_Description="Check the results of the calculation in the Metrics Section of the worksheet. In case the target values are not achieved, the Total &amp; Importance columns can be used to identify  weak points (insufficient HW parts o SM).&#xD;&#xA;An overview of the SPF&amp;LF metric calculation for all Safety Goals will also be given in the Safety Goals List Editor.&#xD;&#xA;Also review the usage of safety mechanisms in the Safety Mechanism page of the DC Worksheet."/>
      <artifactTypes href="http://www.ikv.de/analyze/metamodels/DiagnosticCoverage/1.0#//DCWorksheet"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJMiOsEem7IbokExUh5g" mediniIdentifier="_32yJMiOsEem7IbokExUh5g" name="Perform Quantitative FTA /PMHF Metrics Calculation" user_Description="Perform the FTA at least for each safety goal  with ASIL (B), C, D- it shall be updated/revisited after changes in the architecture">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJMyOsEem7IbokExUh5g" mediniIdentifier="_32yJMyOsEem7IbokExUh5g" name="Create Top-Level and intermediate events" user_Description="If available, a copy of the FTA of the system level should be created and used as starting point. Otherwise for each Safety Goal derive an FTA model to investigate the potential to violate this Safety Goal. Break Down the top-level events into the different causing events by using the available gates for the FTA and by following the technical architecture."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJNCOsEem7IbokExUh5g" mediniIdentifier="_32yJNCOsEem7IbokExUh5g" name="Create Leaf-events" user_Description="For the basic/leaf events drag&amp;drop the related HW elements or failure modes from the BOM based architecture onto FTA gates. Also add in the same way safety mechanisms accordingly and combine them with failure modes/malfunctions using AND gates.&#xA;New malfunctions/failure modes as well as safety mechanisms may be discovered during this activity."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJNSOsEem7IbokExUh5g" mediniIdentifier="_32yJNSOsEem7IbokExUh5g" name="Evaluate FTA" user_Description="Perform cut-set calculation /FTA evaluation for cut sets of size of at least 3. Make sure the correct mission time is used and the checkmarks for &quot;Compute reliability ...&quot; and &quot;Calculate importance measures&quot; are set.&#xD;&#xA;The resulting cutsets shall be stored in the FTA model (make sure only one evaluation result is stored there - if required remove older/interims results)."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJNiOsEem7IbokExUh5g" mediniIdentifier="_32yJNiOsEem7IbokExUh5g" name="Investigate cutsets" user_Description="Investigate all cut sets of size 1 and  2 (single point and dual faults) and derive appropriate requirements. Update architectures and requirements accordingly. Check whether the PMHF value meets the target value for the related safety goal - if not, use the importance measures/criticalities to identify the weak points and apply measures to reduce the failure rate.">
        <artifactTypes href="http://www.ikv.de/medini/metamodels/FTA/2.0#//AnalysisModel"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_f7Fi8CPCEem7IbokExUh5g" mediniIdentifier="_f7Fi8CPCEem7IbokExUh5g" name="Add PMHF metric results to Safety Goals overview" user_Description="In the Safety Goals List editor select for each Safety Goal in the column &quot;FTA used for PMHF&quot; the appropriate Fault Tree Model and refresh the information in the table using F5 key">
        <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
        <artifactTypes href="http://www.ikv.de/medini/metamodels/FTA/2.0#//FTAModel"/>
      </subItems>
      <artifactTypes href="http://www.ikv.de/medini/metamodels/FTA/2.0#//FTAModel"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJNyOsEem7IbokExUh5g" mediniIdentifier="_32yJNyOsEem7IbokExUh5g" name="Perform DFA" user_Description="A DFA shall be performed for all elements where a common cause or cascading failure may have an impact on the safety/safety goal violation. In the folder &quot;Safety Analyses -&gt; Dependent Failure Analyses&quot; create a new Checklist based on the template &quot;Tasklist: Dependent Failure Analysis (ISO26262-2nd Ed.:Part9 )&quot; and add it as Related Element to the checklist entry.&#xD;&#xA;Follow the steps specified in the newly created tasklist.">
      <artifactTypes href="http:///de/ikv/analyze/checklist.ecore#//Checklist"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_32yJOCOsEem7IbokExUh5g" mediniIdentifier="_32yJOCOsEem7IbokExUh5g" name="Revisit Safety Analyses" user_Description="Each time changes have been made to requirements and/or architecture, the safety analyses should be revisited and updated accordingly."/>
  </items>
</de.ikv.analyze.checklist:Checklist>
