Performing engineering software analysis techniques

​

This standard identifies the competences you need to analyse software, in accordance with approved procedures, in order to demonstrate that the software is free from structural defects. You will be given a detailed brief on specific analysis techniques, and will be required to perform and report on the specific software analysis. You will need to select the appropriate software analytical method to use, based on the type and complexity of the software functions. You will be expected to use current British, European, international and company standards to analyse the software.

Your responsibilities will require you to comply with organisational policy and procedures for working in the software development team. You will be required to report any problems with the computer hardware, software or procedures that you cannot personally resolve, or that are outside your permitted authority, to the relevant people. You will be expected to work to verbal/written instructions and draft specifications, with a minimum of supervision, taking personal responsibility for your own actions and for the quality and accuracy of the work that you carry out.

Your underpinning knowledge will provide a good understanding of your work, and will provide an informed approach to applying software analysis procedures. You will understand the computer system and software used, and its application, and will know, in adequate depth, about the various tools and techniques used to analyse the software.

You will understand the safety precautions required when working in the software development team. You will be required to demonstrate safe working practices throughout, and will understand the responsibility you owe to yourself and others in the workplace.

---

​

1. work safely at all times, complying with health and safety legislation, regulations, directives and other relevant guidelines
2. plan and prepare the software analysis activities before you start them
3. use appropriate sources to obtain the required information for the analysis activity
4. access and use the correct software analysis tool
5. use references that follow the required conventions
6. perform the software analysis
7. check the output from the review
8. save and store the software analysis results as the appropriate file type and in the correct location
9. review and report your findings on the software analysis performed
10. 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

---

​

1. the specific safety precautions to be taken when working with software development environment hardware (to include such items as safety guidance relating to the use of visual display unit (VDU) equipment and work station environment; repetitive strain injury (RSI); the dangers of trailing leads and cables; how to spot faulty or dangerous electrical leads, plugs and connections)
2. how to return the work area to a safe and useable condition (such as cleaning down work surfaces; putting media, manuals and unwanted items of equipment into safe storage; leaving the work area in a safe and tidy condition)
3. 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)
4. software analysis methodologies, and national, international and relevant company software analysis procedures (such as software analysis tool, code review, manual analysis)
5. identification of the correct version of the software analysis tool, and the various techniques that are supported by the tool
6. the application and use of the software analysis tools
7. how to use and configure the software analysis tool
8. how to access the specific code to be analysed
9. how to analyse software code using the correct tools/methods
10. how to access, recognise and use a wide range of standard components and symbol libraries from the tools
11. the need for configuration control on all artefacts (such as ensuring that completed results are approved, labelled and stored on a suitable storage device)
12. why it is necessary to be able to recall previous issues of analysis results
13. when to act on your own initiative and when to seek help and advice from others

---

​

1. Prepare for the software analysis, by carrying out all of the following:
   1. check that the working environment is in a safe and appropriate condition and that all working equipment is in a safe, tested and usable condition (such as cables undamaged, correctly connected, safely routed)
   2. start the appropriate software analysis tool
   3. set up the analysis environment and select a suitable template/folder
   4. identify relevant software to be analysed
   5. identify the required standards and all relevant sources (such as software requirements, design and software coding standards)
2. Use two of the following to obtain the necessary data to analyse correctly the software code:
   1. technical publications
   2. standards reference documents
   3. calculations
   4. specifications
   5. software requirements
   6. regulations
   7. quality requirements
   8. software design
   9. technical notes (such as meetings/discussions, e-mail)
   10. other specific available data
3. Carry out all of the following before performing the software analysis:
   1. ensure that the data and information you have is complete and accurate
   2. analyse the data and information to identify requirements of the analysis to be preformed
   3. recognise and deal with problems (such as technical issues and lack of information, or incorrect information)
4. Configure the software analysis tools to analyse the code, using three of the following:
   1. data flow
   2. metrics analysis
   3. execution time measurement
   4. control flow
   5. information flow
   6. execution time analysis
   7. code language subsets
   8. semantic analysis
   9. test coverage analysis
5. Perform the software analysis using one of the following:
   1. software analysis tool
   2. code review
   3. manual analysis
6. Check the analysis results for both of the following:
   1. completeness
   2. completion
7. Save and store the results in appropriate locations, to include carrying out all of the following:
   1. check that the results are correctly titled, referenced and annotated
   2. ensure that the results have been checked and comply with organisational procedures
   3. save the results to an appropriate location (such as storage device, configuration database)
   4. register and store the results in the appropriate company information system (where appropriate)
   5. ensure that a separate backup copy is created and placed in safe storage
8. Review the findings of the analysis, using one of the following:
   1. formal report
   2. software quality report
   3. metrics report
   4. vendor software assessment
   5. analysis tool generated report

---

---

---

---

---

---

---

---

---

3

---

01 Mar 2024

---

Current

---

Original

---

Enginuity

---

SEMETS366

---

Engineering, Engineering and Manufacturing Technologies, Engineering Technicians

---

3113

---

engineering; technical; support; data flow; control flow; calculations; metrics analysis; information flow

---