<?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="_ug-vkCc8Eea-8YkLqRAPAA" mediniIdentifier="_ug-vkCc8Eea-8YkLqRAPAA" name="Tasklist: Development of Technical Safety Concept (ISO26262:Part4)" version="31/05/2016 16:34">
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_Qdv9cBsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9cBsKEemHsZrTo6Qoyg" 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="_Qdv9cRsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9cRsKEemHsZrTo6Qoyg" 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="_Qdv9chsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9chsKEemHsZrTo6Qoyg" 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;If needed also check/update the mission profile(s) and the list of safety mechanism.&#xA;">
      <artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_-qR4UCO7Eem7IbokExUh5g" mediniIdentifier="_-qR4UCO7Eem7IbokExUh5g" 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="_DPbUkSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUkSc9Eea-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="_DPbUkic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUkic9Eea-8YkLqRAPAA" name="Functional Safety Requirements" user_Description="Functional Safety Requirements typically come from an OEM - if possible import from RMS (Requirements Management System) or use a model from an existing medini project. This shall at least include functional safety requirements and safety goals. The requirements shall be organized in the folder &quot;Functional 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="_DPbUkyc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUkyc9Eea-8YkLqRAPAA" name="Functional Safety Architecture" user_Description="This should come from OEM - 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.&#xD;&#xA;It shall be captured in the folder Functional Safety Architecture.">
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUlCc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUlCc9Eea-8YkLqRAPAA" name="(optional) System Level Functional Requirements" user_Description="This is the general requirements specification at system level - it should come from the systems requirements engineer- if possible import from RMS.&#xD;&#xA;These requirements shall be put into the folder 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="_DPbUlSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUlSc9Eea-8YkLqRAPAA" name="(optional) System Design" user_Description="This should come from the systems 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.&#xD;&#xA;It shall be captured in the folder Technical Safety Architecture.">
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
  </items>
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUlic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUlic9Eea-8YkLqRAPAA" name="Create Technical Safety Concept">
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUlyc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUlyc9Eea-8YkLqRAPAA" name="Technical Safety Requirements and Safety Mechanisms (TSR/SM)" user_Description="Define the technical solution for the safety of the item">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUmCc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUmCc9Eea-8YkLqRAPAA" name="Top Level TSR" user_Description="Use the graphical and/or the list editor for requirements as needed to define hierarchies and details for requirements. Use the requirements from the FSC as starting point and define appropriate contributing TSRs.">
        <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUmSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUmSc9Eea-8YkLqRAPAA" name="Define further TSR" user_Description="Detail the top-level TSR's - use sub-requirements and decomposition as needed (use Contributes relations 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="_Qdv9ixsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9ixsKEemHsZrTo6Qoyg" 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="_Qdv9jBsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9jBsKEemHsZrTo6Qoyg" 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="_DPbUmic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUmic9Eea-8YkLqRAPAA" name="Define/Derive System Level Safety Mechanisms" user_Description="Group them in a Safety Mechanism Collection and trace them to the related requirement(s). Use the &quot;Implemented-by property&quot; to associate the safety mechanisms to the architecture elements that implement them.">
        <artifactTypes href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//MeasureCatalog"/>
      </subItems>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUmyc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUmyc9Eea-8YkLqRAPAA" name="Technical Safety Architecture (TSA)" user_Description="The architecture should reflect the system level structure of the item implementation including the interfaces to the environment of the item. One of multiple functions should be defined for the elements of the architecture.&#xA;&#xA;Note: If an architecture has been specified using an external tool (e.g. SCADE Architect, Rational Rhapsody or Enterprise Architect) it can be imported into medini.">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_sGs5oBsOEemHsZrTo6Qoyg" mediniIdentifier="_sGs5oBsOEemHsZrTo6Qoyg" name="Organize Architecture model" user_Description="Use sub-diagrams to specify complex architectures. &#xD;&#xA;The dependency net editor may be used to define the relations between functions and elements.&#xD;&#xA;Note: Generally the relation type &quot;uses&quot; is used to describe relations, but for relations between functions the relation type &quot;requires&quot; is used."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUnCc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUnCc9Eea-8YkLqRAPAA" name="Specify type of architecture elements" user_Description="Choose HW/SW/Sensor/Actuator etc as needed"/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUnSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUnSc9Eea-8YkLqRAPAA" name="Define further properties" user_Description="Select whether an element is internal/external to the item;&#xA;Define the safety properties/indepedence properties&#xA;If needed define further independence requirements"/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUnic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUnic9Eea-8YkLqRAPAA" name="(optional) Specify the behaviour of functions" user_Description="Use Activity diagrams for main functionalities - or imported Matlab/Simulink models"/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_jVlHgGyIEeeozdK-b6rCJw" mediniIdentifier="_jVlHgGyIEeeozdK-b6rCJw" name="Indicate implementation of Safety Mechanisms" user_Description="For the safety mechanisms select the system elements which implement the mechanism.">
        <artifactTypes href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//MeasureCatalog"/>
      </subItems>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUnyc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUnyc9Eea-8YkLqRAPAA" name="Add know malfunctions and failure modes" user_Description="Use Guideword Analysis and/or failure net editor as needed"/>
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUoCc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUoCc9Eea-8YkLqRAPAA" name="Allocate requirements" user_Description="Allocate all Technical Safety requirements  to elements of the Technical Safety architecture. &#xD;&#xA;If necessary add additional elements to the architecture and/or modify the architecture.&#xD;&#xA;The Requirements List editor or the Allocate Elements matrix can be used to define the allocations.">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_Qdv9jxsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9jxsKEemHsZrTo6Qoyg" 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."/>
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
      <artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_HhsroBsOEemHsZrTo6Qoyg" mediniIdentifier="_HhsroBsOEemHsZrTo6Qoyg" name="(optional) Associate Functional and Technical architectures" user_Description="Use the Allocate Elements from the Functional Safety Architecture to associate the elements of the Functional Safety Architecture to elements of the Technical Safety Architecture.">
      <artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
    </subItems>
  </items>
  <items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUoSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUoSc9Eea-8YkLqRAPAA" 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 Technical Safety Architecture.">
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_Qdv9kRsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9kRsKEemHsZrTo6Qoyg" 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"/>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_Qdv9khsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9khsKEemHsZrTo6Qoyg" 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="_Qdv9kxsKEemHsZrTo6Qoyg" mediniIdentifier="_Qdv9kxsKEemHsZrTo6Qoyg" name="Perform Guideword Analysis" user_Description="Use Guideword Analysis to identify the potential malfunctions for the functions of the Technical Safety Architecture. Organize the Guideword tables in the subfolder Guideword Analysis for Architecture Functions of &quot;Safety Analyses&quot;. If required create additional subfolders."/>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUoic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUoic9Eea-8YkLqRAPAA" name="Perform FMEA" user_Description="Derive the FMEA Worksheet from the TSA - it shall always be revisited after updates in requirements/architecture.&#xD;&#xA;Depending on the focus the FMEA may be restricted to functions, components. Also other filters may be applied - use the cover page of the derived FMEA to adjust these settings.&#xD;&#xA;As this is a bottom-up method, start with setting the analysis level to &quot;Leafs&quot; and later change it to higher levels.">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUoyc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUoyc9Eea-8YkLqRAPAA" name="Investigate cause/effect chains for malfunctions and failure modes" user_Description="Bottom-up approach - the Severity will be automatically derived from the top-level effect. The Failure Net Editor should be used complementary for this activity.  Additional malfunctions or failure modes may be created in the course of this activity.&#xD;&#xA;Root causes discovered during the FMEA should be capture in a Failure Collection of type Error. Top Level Effects at vehicle level should be captured in a Failure Collection of type Hazard (may come also from OEM)."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUpCc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUpCc9Eea-8YkLqRAPAA" 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="_DPbUpSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUpSc9Eea-8YkLqRAPAA" 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="_DPbUpic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUpic9Eea-8YkLqRAPAA" name="Perform Qualitative FTA" user_Description="Perform the FTA at least for each safety goal - it shall be updated/revisited after changes in requirements and architecture">
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUpyc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUpyc9Eea-8YkLqRAPAA" name="Create Top-Level and intermediate events" user_Description="For each Safety goal derive an FTA model to investigate the potential to violate this safety goal. Break Down the top-level events into intermediate and/or base 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="_DPbUqCc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUqCc9Eea-8YkLqRAPAA" name="Create Leaf-events" user_Description="For the basic/leaf events drag&amp;drop the related components or failure modes/malfunctions from the architecture onto FTA gates. Also add in the same way safety mechanisms accordingly and combine them with failure modes/malfunctions using AND gates.&#xD;&#xA;New malfunctions/failure modes as well as safety mechanisms may be discovered/derived during this activity."/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUqSc9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUqSc9Eea-8YkLqRAPAA" name="Evaluate FTA" user_Description="Perform cut-set calculation /FTA evaluation for cut sets of size of at least 3"/>
      <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_DPbUqic9Eea-8YkLqRAPAA" mediniIdentifier="_DPbUqic9Eea-8YkLqRAPAA" 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."/>
      <artifactTypes href="http://www.ikv.de/medini/metamodels/FTA/2.0#//FTAModel"/>
    </subItems>
    <subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_e3EdUBsTEemHsZrTo6Qoyg" mediniIdentifier="_e3EdUBsTEemHsZrTo6Qoyg" 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="_FI7EIBsTEemHsZrTo6Qoyg" mediniIdentifier="_FI7EIBsTEemHsZrTo6Qoyg" name="Revisit Safety Analyses" user_Description="Each time changes have been made to requirements and/or architectures, the safety analyses should be revisited and updated accordingly."/>
  </items>
</de.ikv.analyze.checklist:Checklist>
