Potential occupational standard
Occupational standard in development
Approved occupational standard
Occupational standard without apprenticeship
Custom occupational card
Apprenticeship
Higher Technical Qualification
T Level
Technical Qualification
Career starter apprenticeship
Royal apprenticeship
Occupational progression
Technical education progression
Mid green occupation
Dark green occupation
Favourite occupation
home Engineering and manufacturing
High integrity software engineer

High integrity software engineer

Engineering and manufacturing

Level 6 - Professional Occupation

Developing software to support safety critical industries.

Reference: OCC0013

Status: assignment_turned_inApproved occupation

Average (median) salary: £42,906 per year

SOC 2020 code: 2126 Aerospace engineers

SOC 2020 sub unit groups:

  • 2126/02 Aircraft engineers (professional)
  • 2134/03 Software developers

Technical Education Products

ST0013:

High integrity software engineer

(Level 6)

Approved for delivery

Employers involved in creating the standard:

BAE Systems, Defence Science and Technology Laboratory (DSTL), Leonardo, Rolls Royce plc

Summary

This occupation is predominately found in safety critical industries where software failure may cause serious damage or danger to life including aerospace, nuclear, automotive and process control sectors. The occupation can be found in large, medium and small employers across the world. High integrity software engineers may work on specific safety critical software products. They may also work on bespoke tooling and associated integrated environments and infrastructure. Employment fields include:

  • aerospace manufacturers
  • nuclear reactor controls manufacturers
  • automotive safety critical software systems
  • industrial process control systems

The broad purpose of the occupation is to design, develop and test, real-time safety-critical software. They develop embedded high integrity systems software and stand-alone applications used in sector specific support. They develop and test tools that support the creation of high integrity software. They support customers and suppliers by maintaining and improving software utilities and tools. They develop processes for the development and test of products. They review performance, design, test and use project management and continuous improvement techniques. They proactively find solutions to problems and identify areas for business improvement.

High integrity software engineers are typically office-based. They may be required to work in simulation rig testing facilities, or in operational environments. 

In their daily work, an employee in this occupation may interact with customers. They may also interact with system operators, other specialist engineers, technicians, partners and suppliers.  They also interact with colleagues across other areas in their organisation. For example, manufacturing, project management, quality assurance, finance, human resources, procurement and safety.

They typically report to senior engineers, senior specialists or chief engineers depending on the organisation.

An employee in this occupation is responsible for working ethically and professionally. They may work to regulatory requirements for sector specific industries. They must meet statutory and company regulations. For example, health and safety, environment and sustainability, cost, quality, accuracy and efficiency. High integrity software engineers work individually and as part of a team. They are responsible for the safety and security of the product they create. Depending on the size and structure of the organisation they may manage software technicians or teams of engineers.

Employers involved in creating the standard:

BAE Systems, Defence Science and Technology Laboratory (DSTL), Leonardo, Rolls Royce plc

eco

Mid Green occupation

Typical job titles include:

Aerospace software designereco
Aerospace software engineereco
Embedded software engineereco
High integrity software engineereco
Safety embedded software engineereco
Senior safety engineereco
Software engineereco
Systems engineereco

Keywords:

Code
Coding
Degree
Modelling
Simulation
Systems

Knowledge, skills and behaviours (KSBs)

K1: Mathematics: the mathematical techniques and analytical methods required to model software and hardware systems: algebra, calculus, geometry, Boolean Logic, trigonometry and statistics.
K2: Software requirements development: the requirement lifecycle from concept to release; gathering, specifications, validation.
K3: Software requirements engineering: maintenance, operating environment, identification of software security, modelling, human computer interaction, and identification of system safety.
K4: Software architecture: operating system concepts and architectural considerations.
K5: Software design development: structures, methodologies, techniques and validation.
K6: Software design engineering: software functions and interconnection, flexibility, coupling and cohesion, readability, maintainability, testability, safety, security and design verification.
K7: Modelling and simulation: creation and simulation of design models.
K8: Software implementation development: creation of executable code.
K9: Software implementation engineering: underlying concepts of computational thinking, abstraction, representation and modelling, language specifications including assembler, analysis, and inspection methodologies.
K10: Testing the software solution: test environments; debugging and profiling facilities.
K11: Test methodologies: methods used to test software; criticality.
K12: Configuration control: configuration management methods, software build processes, tools and change control.
K13: Software development environment: tool configurations, library functions, operating environment, compiler process and options, scripting and hardware or software integration.
K14: System security: statutory, regulatory, organisational and certification principles in a software product.
K15: Principles of quality: process conformations and assurance in a high integrity software engineering environment.
K16: Continuous improvement principles and techniques: Plan-do-check-act (PDCA), Lean, 6 Sigma, and Statistical Process Control (SPC). Lean manufacturing tools. Process mapping.
K17: Safety requirements: statutory, regulatory, organisational and certification principles (software safety integrity levels) in a high integrity software environment.
K18: Teamwork: conflict management, people development techniques, performance management, diversity and inclusivity.
K19: Information technology: general data protection regulation (GDPR), digital tools for presentation of data, digital communication and collaboration packages.
K20: Communication techniques: verbal, written and presentations.
K21: Time management techniques.
K22: Environment and sustainability: role of software design and implementation in the end-to-end value chain for sustainable products; optimising energy and resource consumption; relationship between obsolescence and sustainability.
K23: Project management: project planning, management of risks, commercial awareness, financial management and resourcing.
K24: Report writing techniques and methods. IT applications for technical reporting.
K25: Problem solving tools and techniques: lateral thinking, root cause analysis (RCA).
K26: Software development techniques: Waterfall, Agile, and Hybrid.
K27: Software integration techniques.

S1: Apply analytical methods; use mathematics and associated toolsets to characterise properties and behaviour of software.
S2: Read, interpret and use software engineering data. For example, requirements, design, code, test and release documentation.
S3: Develop and apply algorithms. For example, produce specification, design and implementation for algorithms.
S4: Select the design approach and tools for a given software engineering application and environment.
S5: Apply model-based techniques. For example, using simulations to verify the compliance to the parent requirements.
S6: Produce system and software designs. For example, produce state machine diagrams.
S7: Setup and configure tools and the environment. For example, verification tool to target hardware requirements, management tool to design tool, and configuration tool to development tools.
S8: Implement functional software solutions. For example, developing software solutions that incorporate new, legacy or commercial components.
S9: Develop and execute high integrity software test plans.
S10: Analyse and review high integrity software outputs. For example, design reviews, code walkthroughs, test script reviews.
S11: Use problem solving tools and techniques. For example: lateral thinking, root cause analysis (RCA), Kaizen, Lean manufacturing and Kanban.
S12: Apply configuration management and software build processes.
S13: Communicate with internal and external stakeholders; verbal and written.
S14: Write reports. For example, data, technical information, drawings, outcomes and recommendations.
S15: Present information. For example, presenting project progress and key performance indicators (KPI's) such as cost, quality, time, risk and opportunities. Presenting technical results into design reviews.
S16: Use information technology: digital tools for presentation of data, digital communication and collaboration packages.
S17: Use continuous improvement techniques and make recommendations. For example, Kaizen, Lean manufacturing and Kanban.
S18: Use project management techniques. For example, in estimating, risk, cost and budget control, time management and resource management.
S19: Identify and comply with legal and statutory requirements. For example: cyber security, software certification requirements, data protection, high integrity software safety, environmental protection and sustainability.
S20: Plan and manage own time.
S21: Apply and uphold ethical principles.
S22: Apply team working principles.
S23: Apply software development techniques. For example, Waterfall, Agile, or Hybrid.
S24: Apply software integration techniques. For example, networks, hardware or system integration.

B1: Lead by example and promote health and safety.
B2: Lead by example and promote environment, ethical and sustainable practices.
B3: Adapt to challenging or changing situations and be resilient to the effects.
B4: Collaborate and promote teamwork across disciplines.
B5: Lead by example to promote accessibility, diversity and inclusion.
B6: Commits to their own and others' professional development.

Duties

Duty D1

Define and maintain the engineering plan detailing the implementation of software engineering solutions. In collaboration with multidisciplinary teams and organisational stakeholders.

Duty D2

Identify, evaluate, derive, analyse and maintain software requirements for customer and projects.

Duty D3

Define and maintain the architecture and design of software products, tools, utilities and applications to meet project requirements.

Duty D4

Implement high integrity software design from combinations of new, modified and existing components to meet project requirements.

Duty D5

Develop, define and execute testing of high integrity software products to verify functionality and performance.

Duty D6

Analyse and review the high integrity software outputs.

Duty D7

Undertake and complete build, configure and release of the high integrity software product.

Duty D8

Verify that software processes and procedures comply with standards throughout the life cycle. These include local, national and international regulatory, legislative, customer and company standards. For example, cyber security, development, environmental, anti-bribery and corruption. Official Secrets Act, export control, safety standards.

Duty D9

Review the in-service performance of software products, processes and systems. Assess the cause of any faults or problems and propose solutions.

Duty D10

Manage stakeholders by communicating project status, technical and commercial information. For example, communicate success, risks and issues to all levels of the business.

Duty D11

Define, monitor and co-ordinate the continuous improvement of software processes and methods.

Occupational Progression

This occupational progression map shows technical occupations that have transferable knowledge and skills.

In this map, the focused occupation is highlighted in yellow. The arrows indicate where transferable knowledge and skills exist between two occupations. This map shows some of the strongest progression links between the focused occupation and other occupations.

It is anticipated that individuals would be required to undertake further learning or training to progress to and from occupations. To find out more about an occupation featured in the progression map, including the learning options available, click the occupation.

Progression decisions have been reached by comparing the knowledge and skills statements between occupational standards, combined with individualised learner movement data.

Technical Occupations

Levels 2-3

Higher Technical Occupations

Levels 4-5

Professional Occupations

Levels 6-7

Progression link into focused occupation.
assignment_turned_in

Level 3

Progression link into focused occupation.
assignment_turned_in

Level 3

Progression link into focused occupation.
assignment_turned_in

Level 4

This is the focused occupation.
assignment_turned_in

Level 6

eco
Progression link from focused occupation.
assignment_turned_in

Level 6

Progression link from focused occupation.
assignment_turned_in

Level 6

Progression link from focused occupation.
assignment_turned_in

Level 7

Construction and the built environment

Digital

Engineering and manufacturing