| 1 | 1a. Measure engineering software quality | 1.1 | Work safely at all times, complying with health and safety legislation, regulations and other relevant guidelines |
| 1.2 | Plan the software quality measurement activities before they start them |
| 1.3 | Prepare for the software quality measurement activities by carrying out all of the following: • check that the working environment is in a safe and suitable condition and that all working equipment is in a safe and usable condition (such as cables undamaged, correctly connected, safely routed) • identify an appropriate software metric (such as lines of code, software test coverage) • set up the analysis environment • identify the relevant software code to be analysed • identify the relevant software process to be reviewed • 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 measurement activities |
| 1.5 | Use two of the following as sources of data to collect software metrics: • change order/modification requests • process and quality documents • software requirements • standards reference documents • testing tools • technical notes • software design • software analysis • code |
| 1.6 | Access and use the correct software components |
| 1.7 | Use appropriate techniques to create the software tests |
| 1.8 | Use references that follow the required conventions |
| 2 | 1b. Measure engineering software quality (continued) | 2.1 | Carry out all of the following before measuring software quality: • ensure that the data and information they have is complete and accurate • analyse the data and information to identify requirements of the quality analysis to be preformed • recognise and deal with problems (such as technical issues and lack of, or incorrect, information) |
| 2.2 | Check the output from the quality reviews |
| 2.3 | Collect metrics, as required by one of the following: • BS or ISO 9000 standards and procedures • other accepted international standards • customer (contractual) standards and requirements • company standards and procedures • recognised compliance agency/body’s standards |
| 2.4 | 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.5 | Review the quality metrics for all of the following: • completeness • traceability • accuracy |
| 2.6 | Review the findings of the software analysis, using one of the following: • formal report • software quality report • metrics report • software vendor code assessment |
| 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 measure engineering software quality | 3.1 | Explain the specific safety precautions to be taken when working in a software quality measuring environment (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 quality measurement (such as new model brief/request, drawing briefs, specification sheets, request for changes or modifications to code; technical publications; calculations; software requirements; audit reports) |
| 4 | 2b. Know how to measure engineering software quality (continued) | 4.1 | Explain software quality standards and levels |
| 4.2 | Explain software quality methodologies: national, international and relevant company software procedures |
| 4.3 | Explain software quality measurements |
| 4.4 | Explain the collection and use of software metrics |
| 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 liaise with other engineers to establish software qualities |
| 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.