101 lines
21 KiB
XML
101 lines
21 KiB
XML
<?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="_re7ecLH9EeCQYIKxeQ-Alw" mediniIdentifier="_re7ecLH9EeCQYIKxeQ-Alw" name="Tasklist: Development of Functional Safety Concept (ISO26262:Part3)" version="19/07/2011 13:53">
|
|
<items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_YK7nQLrzEeG74PAEAJO_Uw" mediniIdentifier="_YK7nQLrzEeG74PAEAJO_Uw" 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="_gPodgLrzEeG74PAEAJO_Uw" mediniIdentifier="_gPodgLrzEeG74PAEAJO_Uw" name="Specify Project properties" user_Description="Select the project and fill in all custom specific properties for the project using the tab "Profile" 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="_4t0I4NAWEeGs3dSo9EKp0w" mediniIdentifier="_4t0I4NAWEeGs3dSo9EKp0w" name="Check/Update Operational situations catalog(s) and other settings" user_Description="In the Project Settings check whether the Operational Situations catalog(s) are sufficient for the item and are up-to-date. Add additional situations and/or catalogs as required.
Also review the Guideword templates, the dynamic constraints and the risk matrix settings to ensure they are sufficient for the project.
">
|
|
<artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJPackage"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_14ggsCO7Eem7IbokExUh5g" mediniIdentifier="_14ggsCO7Eem7IbokExUh5g" 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="_s-zVwLH9EeCQYIKxeQ-Alw" mediniIdentifier="_s-zVwLH9EeCQYIKxeQ-Alw" name="Specify the item" note="The item definition defines the scope of the work by defining at a high level the item, its functions as well as the relations/interfaces to other vehicle level systems.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_xi7oQLH9EeCQYIKxeQ-Alw" mediniIdentifier="_xi7oQLH9EeCQYIKxeQ-Alw" name="Textual/Verbal item description" user_Description="Open the "Item Description" in the folder "Item Definition". Rename it according to the item under investigation and fill in the appropriate fields in the form editor. Optionally include and trace external documents/images etc or external references for more detailed descriptions. All external documents/references should be put in the folder "Item Definition > Additional Material"
">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/HazardAnalysis/1.0#//PlainItem"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_7-qAQLH9EeCQYIKxeQ-Alw" mediniIdentifier="_7-qAQLH9EeCQYIKxeQ-Alw" name="Item functions" user_Description="Capture the main functions of the item in the "Item Functions" model by creating new functions from the context menu of the folder "Vehicle Level Functions". This should be done for all functions of the item which are directly observable/perceivable at vehicle level.
Specify the Base properties of the different functions using the function form editor or using the Properties view of the function.">
|
|
<artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_B2C-ALr1EeG74PAEAJO_Uw" mediniIdentifier="_B2C-ALr1EeG74PAEAJO_Uw" name="Supporting Functions (optional)" user_Description="Optionally capture the supporting functions of the item in the "Item Functions" model by creating new functions from the context menu of the folder "Supporting Functions". This should be done for all functions of the item which are required to describe the vehicle level functions.
Specify the Base properties of the different functions using the function form editor or using the Properties view of the function.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="__08HUBl4EemHsZrTo6Qoyg" mediniIdentifier="__08HUBl4EemHsZrTo6Qoyg" name="Create dependencies between Vehicle Level and Supporting Functions" user_Description="For each Vehicle Level Function use the "Show Dependency Net" and create "Requires" Relations to the appropriate Supporting Functions.">
|
|
<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="_2NZMQLH9EeCQYIKxeQ-Alw" mediniIdentifier="_2NZMQLH9EeCQYIKxeQ-Alw" name="Draft item architecture" user_Description="Use the graphical editor for the "Item Architecture" to create a high-level black-box or grey-box model of the item's architecture. Ports should be used to define the interface to other systems/items. Also fill in Description field for each element of the architecture using the properties view.
Components which are implemented in other technology (e.g. mechanic or hydraulic components) or which are outside of the item should be marked in the Profile tab of the Properties view as "External".">
|
|
<artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_XzLDgLITEeCQYIKxeQ-Alw" mediniIdentifier="_XzLDgLITEeCQYIKxeQ-Alw" name="Assign functions to architecture elements" user_Description="Use "Allocate elements" for the Item Functions model and associate all functions to elements of the Architecture (usually the vehicle level functions would be allocated directly to the item, whereas the supporting functions would be allocated to components of the item).
This can also be visualized/defined using the Dependency Net for the individual functions (select the "Allocate" dependency from the drawing palette to create new allocations)">
|
|
<artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_C5efALr3EeG74PAEAJO_Uw" mediniIdentifier="_C5efALr3EeG74PAEAJO_Uw" name="Add known malfunctions" user_Description="For each function add all commonly known malfunctions using the tab Malfunctions of the Properties view of the function. If no malfunctions are known up-front, this step can be skipped.">
|
|
<artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_FWA9cLr4EeG74PAEAJO_Uw" mediniIdentifier="_FWA9cLr4EeG74PAEAJO_Uw" name="Add known hazards" user_Description="Use "Hazards and Top-Level Effects" in the Hazard Analysis and Risk Assessment Folder to capture all known hazards or other unwanted effects related to the item.">
|
|
<artifactTypes href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//Hazard"/>
|
|
<artifactTypes href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//FailureCollection"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_A9Nk8LH-EeCQYIKxeQ-Alw" mediniIdentifier="_A9Nk8LH-EeCQYIKxeQ-Alw" name="Additional documents" user_Description="Organize in "Additional Material" Folder; Create and use sub-folders if necessary">
|
|
<artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJExternalDocument"/>
|
|
</subItems>
|
|
</items>
|
|
<items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_K7vZgLayEeCrBLXbfpJ2Hw" mediniIdentifier="_K7vZgLayEeCrBLXbfpJ2Hw" name="Hazard Analysis and Risk Assessment" note="This activity will identify and classify the risk of the malfunctiong behavior of the item and will result in the safety goals for the item." user_Description="">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_NOABILH-EeCQYIKxeQ-Alw" mediniIdentifier="_NOABILH-EeCQYIKxeQ-Alw" name="Identification of malfunctions" note="A systematic approach shall be applied to identify the malfunctiong behavior for all functions of the item.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_Q_Ma0LH-EeCQYIKxeQ-Alw" mediniIdentifier="_Q_Ma0LH-EeCQYIKxeQ-Alw" name="Perform Guideword Analysis for all Item Functions" user_Description="Perform an Guideword Analysis to systematically investigate the potential for malfunctioning behavior.
Create a new Guideword Analysis in folder Guideword Analysis in the Hazard Analysis and Risk Assessment Folder based on an appropriate template. Drag&Drop one or multiple functions into the Guideword table and check for each keyword whether it will induce a malfunction. If yes, create a malfunction.
Multiple Guideword Analysistables may be used e.g. to organize the Guideword Analysis along Vehicle level and Supporting Functions.">
|
|
<artifactTypes href="http://www.ikv.de/medini/metamodels/ProjectModel#//PJPackage"/>
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/HazopAnalysis/1.0#//HazopAnalysisModel"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_BZiJwBl9EemHsZrTo6Qoyg" mediniIdentifier="_BZiJwBl9EemHsZrTo6Qoyg" name="Ensure traceability for Malfunctions" user_Description="Create traces between the Guideword Analysis and the related functions as required"/>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_XDCHILKvEeCOE5TD-bq2gA" mediniIdentifier="_XDCHILKvEeCOE5TD-bq2gA" name="Perform Function FMEA (optional)" user_Description="Malfunctions of Supporting functions may cause malfunctions of other Supporting Functions and/or of Vehicle Level Functions. Malfunctions of "Vehicle Level" functions may cause Hazards. The cause-effect relations shall be investigated using individual Failure Nets for the Malfunctions or using a (simplified) Function-FMEA (derived from the "Item Functions" model).
Create new malfunctions/hazards if necessary.">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/FMEA/1.0#//FMEAWorksheet"/>
|
|
</subItems>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_2hA-sBmVEemHsZrTo6Qoyg" mediniIdentifier="_2hA-sBmVEemHsZrTo6Qoyg" name="Perform HARA" user_Description="At least for all malfunctions which directly cause hazards the HARA should be performed by combining them with all relevant operational situations.
Start with situations from catalog and add further situations when required.
Use the HARA table view and/or the HARA matrix view as it is convenient.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_JLqGgLazEeCrBLXbfpJ2Hw" mediniIdentifier="_JLqGgLazEeCrBLXbfpJ2Hw" name="Organize HARA tables" user_Description="Organize HARA tables in multiple tables (e.g. along the different functions or along different situations)">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/HazardAnalysis/1.0#//HazardAnalysisModel"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_f8PMMBl_EemHsZrTo6Qoyg" mediniIdentifier="_f8PMMBl_EemHsZrTo6Qoyg" name="Organize Hazards" user_Description="Collect/organize all Hazards detected during HARA in the collection "Hazards and Top-Level Effects""/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_nulIILd1EeCrBLXbfpJ2Hw" mediniIdentifier="_nulIILd1EeCrBLXbfpJ2Hw" name="Organize Safety Goals" user_Description="Create all Safety Goals determined druing HARA in "Functional Safety Requirements" model">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
|
|
</subItems>
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/HazardAnalysis/1.0#//HazardAnalysisModel"/>
|
|
</items>
|
|
<items xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_zXXQgLdyEeCrBLXbfpJ2Hw" mediniIdentifier="_zXXQgLdyEeCrBLXbfpJ2Hw" name="Create Functional Safety Concept" note="The Functional Safety Concept consists of the Safety Goals, the Functional Safety Requirements, the Functional Safety Architecture and the relations between the goals, requirements and architecture elements.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_60EfYBmBEemHsZrTo6Qoyg" mediniIdentifier="_60EfYBmBEemHsZrTo6Qoyg" name="Complete the definition of Safety Goals" user_Description="For all Safety Goals complete the definition by filling in the additional properties and attributes using the Properties View for the Safety Goal or using the "Safety Goals List Editor"">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_Y1GycLd1EeCrBLXbfpJ2Hw" mediniIdentifier="_Y1GycLd1EeCrBLXbfpJ2Hw" name="Create Functional Safety Requirements" user_Description="For each Safety Goal at least one Functional Safety Requirement should be specified as contributing requirement. Various techniques as FTA and FMEA may be used to identify requirements. Moreover, already existing requirements may be included in the list of functional safety requirements. and connected to the safety goal(s) by Contributes-Relations.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_4ekyMBmCEemHsZrTo6Qoyg" mediniIdentifier="_4ekyMBmCEemHsZrTo6Qoyg" name="Organize Requirements" user_Description="One or multiple diagrams should be used to organize/manage the safety goals and related 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.">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_UjWpkBmZEemHsZrTo6Qoyg" mediniIdentifier="_UjWpkBmZEemHsZrTo6Qoyg" name="(Optional) Synchronize with RMS" user_Description="Requirements may be imported/exported synchronized with Requirements Management Systems like Doors NG, PTC Integrity, JAMA ..."/>
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/SafetyGoals/1.0#//SafetyRequirementsModel"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_1q0g4LdyEeCrBLXbfpJ2Hw" mediniIdentifier="_1q0g4LdyEeCrBLXbfpJ2Hw" name="Specify Functional Safety Architecture" user_Description="The architecture should reflect the basic structure of the item. Interfaces of the item to the environment shall be defined. Dependencies on other elements outside of the item or on elements which are implemented in different technology shall be defined. For each element of the architecture at least one function should be allocated (using Allocate Elements for the function model and selecting the architecture model as target) or directly defined in the architecture model.
For the definition of relations between the functions (requires relations) as well as between elements of the architecture (ports) and functions (e.g. uses-relations) the dependency net editor may be used.
Note: If an architecture has been specified using an external tool (SCADE Architect, Rational Rhapsody or Enterprise Architect), it can be imported into medini.">
|
|
<artifactTypes href="http://www.ikv.de/medini/sysml/1.0#//SysMLContainerPackage"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_xqFnoLd4EeCrBLXbfpJ2Hw" mediniIdentifier="_xqFnoLd4EeCrBLXbfpJ2Hw" name="Allocate requirements" user_Description="Allocate all Functional Safety requirements to elements of the Functional Safety architecture. 
If necessary add additional elements to the architecture and/or modify the architecture.
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="_c-bSEBmREemHsZrTo6Qoyg" mediniIdentifier="_c-bSEBmREemHsZrTo6Qoyg" name="Determine ASIL for functions and elements " user_Description="Use the "Compute ASIL" 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="_AF8OYBmSEemHsZrTo6Qoyg" mediniIdentifier="_AF8OYBmSEemHsZrTo6Qoyg" name="Perform Safety Analyses" note="The Safety Analyses serve as a justification that the Functional Safety Concept is sufficient to achieve the safety goals." user_Description="This is an iterative activity which may have to be done multiple times as it will result in new requirments and subsequently in changes in the Functional Safety Architecture.">
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_kXam8BmTEemHsZrTo6Qoyg" mediniIdentifier="_kXam8BmTEemHsZrTo6Qoyg" name="Perform a Project Validation" user_Description="Use Validate from the context menu of the project. Investigate and handle each of the errors & warnings produced by the validation"/>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_8SjisBmZEemHsZrTo6Qoyg" mediniIdentifier="_8SjisBmZEemHsZrTo6Qoyg" 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="_EeEFMBmSEemHsZrTo6Qoyg" mediniIdentifier="_EeEFMBmSEemHsZrTo6Qoyg" name="Perform Guideword Analysis" user_Description="Use Guideword Analysis to identify the potential malfunctions for the functions of the Functional Safety Architecture. Organize the Guideword tables in the subfolder Guideword Analysis for Architecture Functions of "Safety Analyses". If required create additional subfolders.">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/HazopAnalysis/1.0#//HazopAnalysisModel"/>
|
|
<artifactTypes href="http:///de/ikv/analyze/checklist.ecore#//Checklist"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_KJv70Ld2EeCrBLXbfpJ2Hw" mediniIdentifier="_KJv70Ld2EeCrBLXbfpJ2Hw" name="Perform FTA" user_Description="Perform qualitative FTA at least for all safety goals with ASIL C&D. Perform a cutset calculation/Evaluation of the Fault Tree and derive new Functional Safety Requirements as needed (e.g. to avoid single point faults by requiring safety mechanims or architectural changes).
">
|
|
<artifactTypes href="http://www.ikv.de/medini/metamodels/FTA/2.0#//FTAModel"/>
|
|
</subItems>
|
|
<subItems xsi:type="de.ikv.analyze.checklist:StaticChecklistItem" xmi:id="_HjBIwL6KEeCjWpiztGejJA" mediniIdentifier="_HjBIwL6KEeCjWpiztGejJA" name="Perform FMEA" user_Description="Perform an FMEA for the Architecture and/or build the failure net to identify the cause-effect chains as well as the root causes (systematic faults). Additional malfunctions may be created in the course of this activity. To handle the causes for safety critical faults make sure appropriate requirements (and/or detection/prevention measures) are defined and added to the Functional Safety Requirements.">
|
|
<artifactTypes href="http://www.ikv.de/analyze/metamodels/FMEA/1.0#//FMEAWorksheet"/>
|
|
</subItems>
|
|
</subItems>
|
|
</items>
|
|
</de.ikv.analyze.checklist:Checklist>
|