| 1 | 1a. Perform engineering software safety assessments | 1.1 | Work safely at all times, complying with health and safety legislation, regulations and other relevant guidelines |
| 1.2 | Plan the software safety assessment activities before they start them |
| 1.3 | Prepare for the software safety assessment, by carrying out all of the following: • check that the working environment is in a safe and appropriate condition and that all working equipment is in a safe and usable condition (such as cables undamaged, correctly connected, safely routed) • identify all potential hazards to which the software can contribute • identify the severity of each hazard (such as catastrophic, severe, minor, negligible) • identify the software’s worst case contribution to the hazard (such as direct cause, cause in conjunction with other failure, one of several independent contributors, no contribution) • identify the required standards and all relevant sources (such as customer (contractual) standards and requirements, recognised compliance agency/body’s standards, software safety requirements, software design and code standards) |
| 1.4 | Use appropriate sources to obtain the required information for the safety assessment activity |
| 1.5 | Review four of the following to obtain sources of data to assess correctly the software safety: • change order/modification request • hazard identification and analysis documentation • Failure Modes and Effects Analysis (FMEA) documentation • software safety requirements • software design • software process definition documentation • software test and analysis reports • standards reference documents |
| 1.6 | Use references that follow the required conventions |
| 1.7 | Determine the evidence required to achieve the necessary level of software integrity |
| 2 | 1b. Perform engineering software safety assessments (continued) | 2.1 | Carry out all of the following before performing the software safety assessment: • ensure that the data and information they have is current, complete and under configuration control • confirm that the system level hazard identification and analysis have been performed • recognise and deal with problems (such as technical issues and lack of, or incorrect, information) |
| 2.2 | Perform software safety assessment using four of the following: • change order/modification request • hazard identification and analysis documentation • Failure Modes and Effects Analysis (FMEA) documentation • software safety requirements • software design • software process definition documentation • software test and analysis reports • standards reference documents |
| 2.3 | Review and report on a sample of the software safety related evidence for all of the following: • completeness • accuracy • traceability • adequacy |
| 2.4 | Report their findings on the safety assessment performed |
| 2.5 | Save and store the results in appropriate locations, to include carrying out all of the following: • check that the results are correctly titled, referenced and annotated • ensure that the results have been checked and that they comply with the company procedure • save the results to an appropriate location (such as storage device, configuration database) • ensure that a separate backup copy is created and placed in safe storage |
| 2.6 | Deal promptly and effectively with problems within your control, and seek help and guidance from the relevant people if you have problems that you cannot resolve |
| 3 | 2a. Know how to perform engineering software safety assessments | 3.1 | Explain the specific safety precautions to be taken when working with software development environment hardware (to include such things as safety guidance relating to the use of visual display unit (VDU) equipment and work station environment such as lighting, seating, positioning of equipment; repetitive strain injury (RSI); the dangers of trailing leads and cables; how to spot faulty or dangerous electrical leads, plugs and connections) |
| 3.2 | Explain the importance of good housekeeping arrangements (such as cleaning down work surfaces; putting disks, manuals and unwanted items of equipment into safe storage; leaving the work area in a safe and tidy condition) |
| 3.3 | Describe the documentation required for the software safety analysis (such as hazard identification analysis documentation, FMEA documentation, software safety requirements, software test and analysis reports) |
| 3.4 | Explain the basic principles of software safety assessments |
| 3.5 | Describe the system hazard analysis methodologies, and national, international and relevant company software development procedures, methods and tools |
| 4 | 2b. Know how to perform engineering software safety assessments (continued) | 4.1 | Explain the identification of the correct version of software tool, and the various techniques that are supported by the tool |
| 4.2 | Explain how to use and configure the software safety analysis tools |
| 4.3 | Explain how to access the specific code analysis results |
| 4.4 | Explain how to access, recognise and use a wide range of standard components and symbol libraries from the tools |
| 4.5 | Explain the need for configuration control on all components (such as ensuring that completed results are approved, labelled and stored on a suitable storage device) |
| 4.6 | Explain why it is necessary to be able to recall previous issues of analysis results |
| 4.7 | Describe when to act on their own initiative, and when to seek help and advice from others |
Don't show this message again.