EngTree
Back to the Pathways spine
Engineering and manufacturingLevel 6Green occupationOCC0013 · ST0013

High integrity software engineer

Design and development engineer · Professional · Engineering, design and development

The official framework — 57 requirements.

Every Knowledge, Skill and Behaviour below is the verbatim regulatory text of the High integrity software engineer apprenticeship standard (v1.2). On EngTree, each one becomes a node — verified knowledge entries, training modules and End-Point Assessment evidence all map back to it.

Knowledge (27)

What the apprentice must understand

  • 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.

Skills (24)

What the apprentice must be able to do

  • 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.

Behaviours (6)

How the apprentice must conduct themselves

  • 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.

This framework is where Pathways
meets verified knowledge.

Scenarios practise these requirements. Verified entries teach them. The evidence portfolio proves them. One spine, three surfaces.