This standard identifies the competences you need to establish a software implementation as part of the product definition activity, in accordance with approved procedures. You will be given a detailed brief or a request for change/modification order, and you will be required to access these requirements and to extract all necessary information in order to carry out the production of the software implementation. You will need to select the appropriate software development tool to use, based on the type and complexity of the software functions to be developed. You will be expected to use current British, European, international and company standards to produce the software implementation.  Peer review feedback will also need to be evaluated and undertaken, and any lessons learned from the activity will need to be shared within the business.

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 development procedures. You will understand the system and software used, and its application, and will know about the various tools and techniques used to produce the software implementation, in adequate depth to provide a sound basis for carrying out the activities to the required specification.

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 the software implementation activities before you start them
3. use appropriate sources to obtain the required information for the executable to be created
4. access and use the correct software development environment
5. identify and use the required coding standards, as defined by company procedures
6. produce the software code with sufficient detail to allow compilation and execution
7. undertake and evaluate peer review feedback, and identify what lessons can be learned from the feedback
8. provide technical feedback on the engineering software implementation activity undertaken including lessons learnt and those lessons which can be shared within the business
9. make sure that the software code produced is checked and approved by the appropriate person
10. save and store the software code of the appropriate file, type and location
11. use appropriate techniques to create an executable
12. save the executable as the appropriate file type and in the correct location
13. 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 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)
2. the importance of good housekeeping arrangements (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 (such as drawing briefs, specification sheets, request for changes or modifications to models; technical information)
4. identification of the correct version of software tools, and the coding techniques that are supported by the tool
5. how to access the specific software code to be used
6. the documentation required for the software code (such as new request, change order/modification request, technical publications, calculations, software requirements)
7. the national, international and organisational standards and conventions that are used for the models/drawings
8. the application and use of development tools (including compilers, translators or build scripts)
9. how to access, recognise and use a wide range of standard components from the development tools
10. how to evaluate and undertake any peer review feedback and how any lessons learned from the engineering software activity can be shared within the business
11. the need for document control (such as ensuring that completed executables are approved, labelled and stored on a suitable storage device)
12. why it is necessary to be able to recall previous issues of modified code
13. when to act on your own initiative and when to seek help and advice from others

---

---

​

1. Prepare for the software implementation activities, by carrying out all of the following:

   1. check that all the software development environment hardware is in a safe, tested and usable working condition (such as cables undamaged, correctly connected, safely routed)
   2. start the software development environment
   3. set up the development environment and select a suitable template/folder
   4. identify relevant software requirements/design artefact/software code to be implemented/modified
   5. identify the required standards and all relevant sources (such as software requirements, existing design and naming convention)

2. Use four of the following to obtain the necessary data to produce the required software implementation:

   1. new software implementation request     
   2. regulations
   3. change order/modification request       
   4. previous software code
   5. technical publications                             
   6. standards reference documents
   7. calculations                                            
   8. technical notes (such as meetings/discussions, e-mail)
   9. software design                                        
   10. other specific available data

3. Demonstrate how the software implementation takes account of six of the following:

   1. function                                  
   2. cost                                  
   3. operating environment
   4. testing method                            
   5. lifetime of the product             
   6. interfaces (such as interrupts)
   7. resources (such as memory, performance and bandwidth)
   8. algorithm accuracy                   
   9. safety
   10. software architecture                 
   11. coding standards

4. Carry out all of the following before producing the software implementation:

   1. ensure that the data and information you have is complete and accurate
   2. analyse the data and information to identify the requirements of the task
   3. recognise and deal with problems (such as technical issues and lack of information, or incorrect information)

5. Create/modify the software source code using five of the following:

   1. design objects                           
   2. procedures                   
   3. types
   4. requirements functionality        
   5. functions                          
   6. data
   7. change requests                        
   8. parameters
   9. classes                                    
   10. control structures

6. Check the software source code for all of the following:

   1. complexity                                  
   2. readability                        
   3. accuracy
   4. coherence                                  
   5. traceability

7. Create the software executable using one of the following:

   1. compiler tool (such as integrated development tool)
   2. build scripts
   3. translator

8. Save and store software source code files, source code review evidence and executable in appropriate locations, to include carrying out all of the following:

   1. ensure that your software code/code review evidence/executable has been checked to your company procedure
   2. check that the code/code review evidence/executable is correctly titled, referenced and annotated
   3. save the code/code review evidence/executable to an appropriate location (such as storage device, configuration database)
   4. create a separate backup copy, and place it in safe storage (where appropriate)
   5. register and store the software code/code review evidence/executable in the appropriate company information system (where appropriate)
   6. record and store any changes to the software code/code review evidence/executable in the appropriate company information system

9. Produce software code/executable which complies with one of the following:

   1. company standards and procedures
   2. customer standards and requirements
   3. statutory regulations and codes of practice
   4. software standards
   5. BS, ISO or BSEN standards and procedures
   6. other international standards

---

---

---

​​Additional Information

You will be able to apply the appropriate behaviours required in the workplace to meet the job profile and overall company objectives, such as:

• strong work ethic
• positive attitude
• team player
• dependability
• responsibility
• honesty
• integrity
• motivation
• commitment

---

---

---

---

---

1

---

01 Apr 2020

---

Current

---

Original

---

Semta

---

SEMEM451

---

Corporate Managers and Senior Officials, Engineering, Engineering and Manufacturing Technologies, Functional Managers

---

1121

---

engineering; leading; design objects; requirements; functionality; data; procedures; functions

---