| 1 | 1a. Perform engineering software analysis techniques | 1.1 | Work safely at all times, complying with health and safety legislation, regulations and other relevant guidelines |
| 1.2 | Plan the software analysis activities before they start them |
| 1.3 | Prepare for the software analysis, 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) • start the appropriate software analysis tool • set up the analysis environment and select a suitable template/folder • identify relevant software to be analysed • identify the required standards and all relevant sources (such as software requirements, design and software coding standards) |
| 1.4 | Use appropriate sources to obtain the required information for the analysis activity |
| 1.5 | Access and use the correct software analysis tool |
| 1.6 | Use two of the following to obtain the necessary data to analyse correctly the software code: • technical publications • calculations • software requirements • quality requirements • technical notes (such as meetings/discussions, e-mail) • standards reference documents • specifications • regulations • software design • other available data |
| 1.7 | Carry out all of the following before performing the software analysis: • ensure that the data and information they have is complete and accurate • analyse the data and information to identify requirements of the analysis to be preformed • recognise and deal with problems (such as technical issues and lack of, or incorrect information) |
| 2 | 1b. Perform engineering software analysis techniques (continued) | 2.1 | Use references that follow the required conventions |
| 2.2 | Configure the software analysis tools to analyse the code, using three of the following: • data flow • control flow • code language subsets • metrics analysis • information flow • semantic analysis • execution time measurement • execution time analysis • test coverage analysis |
| 2.3 | Perform the software analysis using one of the following: • software analysis tool • code review • manual analysis |
| 2.4 | Check the analysis results for both of the following • completeness • completion |
| 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 comply with company procedures • save the results to an appropriate location (such as storage device, configuration database) • register and store the results in the appropriate company information system (where appropriate) • ensure that a separate backup copy is created and placed in safe storage |
| 2.6 | Review the findings of the analysis, using one of the following: • formal report • software quality report • metrics report • vendor software assessment • analysis tool generated report |
| 2.7 | Deal promptly and effectively with problems within their control, and seek help and guidance from the relevant people if they have problems that they cannot resolve |
| 3 | 2a. Know how to perform engineering software analysis techniques | 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 relevant sources and methods for obtaining any required technical information relevant to the software analysis (such as new model brief/request, drawing briefs, specification sheets, request for changes or modifications to code; technical publications; calculations; software requirements) |
| 3.4 | Explain the software analysis methodologies, and national, international and relevant company software analysis procedures (such as software analysis tool, code review, manual analysis) |
| 3.5 | Describe the identification of the correct version of the software analysis tool, and the various techniques that are supported by the tool |
| 4 | 2b. Know how to perform engineering software analysis techniques (continued) | 4.1 | Explain the application and use of the software analysis tools |
| 4.2 | Explain how to use and configure the software analysis tool |
| 4.3 | Explain how to access the specific code to be analysed |
| 4.4 | Explain how to analyse software code using the correct tools/methods |
| 4.5 | Explain how to access, recognise and use a wide range of standard components and symbol libraries from the tools |
| 4.6 | Explain the need for configuration control on all artefacts (such as ensuring that completed results are approved, labelled and stored on a suitable storage device) |
| 4.7 | Explain why it is necessary to be able to recall previous issues of analysis results |
| 4.8 | Describe when to act on their own initiative and when to seek help and advice from others |
Don't show this message again.