Potential occupational standard
Occupational standard in development
Approved occupational standard
Occupational standard without apprenticeship
Custom occupational card
Apprenticeship
Higher Technical Qualification
T Level
Career starter apprenticeship
Royal apprenticeship
Occupational progression
Technical education progression
Mid green occupation
Dark green occupation
Favourite occupation
home Digital
Software developer

Software developer

Digital

Level 4 - Higher Technical Occupation

Building and testing simple, high-quality code for software.

Reference: OCC0116

Status: assignment_turned_inApproved occupation

Average (median) salary: £45,508 per year

SOC 2020 code: 2134 Programmers and software development professionals

SOC 2020 sub unit groups:

  • 2134/03 Software developers
  • 2132/05 IT test managers
  • 2132/07 Software development managers
  • 2133/02 Data architects
  • 2133/03 Data engineers
  • 2134/02 Computer programmers
  • 2135/04 Secure system development specialists
  • 2139/03 Webmasters and website managers
  • 2141/01 Application designers
  • 3131/04 Software technicians
  • 3133/01 Database administrators

Technical Education Products

ST0116:

Software developer

(Level 4)

Approved for delivery

Employers involved in creating the standard:

Fujitsu, Exclaimer , FRFL, Risual, Lloyds Bank, Autotrader, DEFRA

Summary

This occupation is found across every sector for example, Financial Services, Computer Gaming, Retail, Transport, Security and Defence in organisations ranging from large multi-nationals, public sector bodies and government projects developing multi-billion-pound software solutions to support key projects to small consultancy firms designing bespoke software solutions for clients.

The broad purpose of the occupation is to understand a client's requirements as provided in design specification and then build and test high-quality code solutions to deliver the best outcome.

Software developers are the creative minds behind computer programs. Some develop the applications that allow people to do specific tasks on a computer or another device. Others develop the underlying systems that run the devices or that control networks.

For example, a software developer may work on Transport ticketing systems, traffic light control systems, customer-facing websites for journey planning and account management, internal websites for monitoring the status of train and road networks. Bespoke asset management systems.

In a computer gaming context, a software developer may work with a creative digital design team to give life to the teams ideas through the delivery of effective code to provide an attractive gaming experience that can give the product a commercial advantage.

In a retail context a software developer may work on delivering coding solutions to deliver online retail opportunities for businesses that provide a responsive and secure trading environment for customers to purchase goods and interact with the retailer.

Organisations use software to ensure that their operations become ever more effective and robustly reduce the incidence of downtime by building quality tested software solutions to give a better service. For example, in commercial organisations this can give them a competitive advantage by being able to analyse significant amounts of data quickly and efficiently to provide the business with information and management systems. This can save time and help the business spot profit making opportunities. For public sector bodies the right software solution can drive up performance and help target scarce resources more effectively and ensure that customer expectations are more likely to be met.

A software developer in a medium to large organisation will typically be working as part of a larger team, in which they will have responsibility for some of the straightforward elements of the overall project. In a smaller enterprise a software developer may be working as the only developer on a project but under direct supervision. A software developer will interpret design documentation and specifications provided by more experienced or specialist members of the team, such as a business analyst or technical architect.

In their daily work, a Software Developer interacts with internal and external parties including users/customers (to understand their needs and test the software developed through user testing) and team members from a range of specialist fields including designers, developers, engineers, analysts and project/delivery managers (to ensure the effective implementation of software solutions). A developer will typically be working as part of a larger team, in which they will have responsibility for some of the straightforward elements of the overall project. The developer will need to be able to interpret design documentation and specifications. The customer requirements will typically be defined and agreed by more experienced or specialist members of the team, such as a business analyst or technical architect.

A Software Developer is typically office-based however field-based research and testing may require periods of time working in the environments of the clients whose needs they are seeking to meet.

An employee in this occupation will be responsible for developing software solutions across the full software development life cycle from research and development, through continuous improvement, to product/service retirement. They may work both autonomously and as part of wider teams, typically reporting to a more senior member of their team.

Employers involved in creating the standard:

Fujitsu, Exclaimer , FRFL, Risual, Lloyds Bank, Autotrader, DEFRA

Typical job titles include:

Application developer
Mobile application developer
Software developer
Web developer

Keywords:

Coding
Design
Developer
Digital
Ict
Software
Software Developer

Knowledge, skills and behaviours (KSBs)

K1: all stages of the software development life-cycle (what each stage contains, including the inputs and outputs)
K2: roles and responsibilities within the software development lifecycle (who is responsible for what)
K3: the roles and responsibilities of the project life-cycle within your organisation, and your role
K4: how best to communicate using the different communication methods and how to adapt appropriately to different audiences
K5: the similarities and differences between different software development methodologies, such as agile and waterfall.
K6: how teams work effectively to produce software and how to contribute appropriately
K7: software design approaches and patterns, to identify reusable solutions to commonly occurring problems
K8: organisational policies and procedures relating to the tasks being undertaken, and when to follow them. For example the storage and treatment of GDPR sensitive data.
K9: algorithms, logic and data structures relevant to software development for example:- arrays- stacks- queues- linked lists- trees- graphs- hash tables- sorting algorithms- searching algorithms- critical sections and race conditions
K10: principles and uses of relational and non-relational databases
K11: software designs and functional or technical specifications
K12: software testing frameworks and methodologies

S1: create logical and maintainable code
S2: develop effective user interfaces
S3: link code to data sets
S4: test code and analyse results to correct errors found using unit testing
S5: conduct a range of test types, such as Integration, System, User Acceptance, Non-Functional, Performance and Security testing.
S6: identify and create test scenarios
S7: apply structured techniques to problem solving, debug code and understand the structure of programmes in order to identify and resolve issues
S8: create simple software designs to effectively communicate understanding of the program
S9: create analysis artefacts, such as use cases and/or user stories
S10: build, manage and deploy code into the relevant environment
S11: apply an appropriate software development approach according to the relevant paradigm (for example object oriented, event driven or procedural)
S12: follow software designs and functional or technical specifications
S13: follow testing frameworks and methodologies
S14: follow company, team or client approaches to continuous integration, version and source control
S15: communicate software solutions and ideas to technical and non-technical stakeholders
S16: apply algorithms, logic and data structures
S17: interpret and implement a given design whist remaining compliant with security and maintainability requirements

B1: Works independently and takes responsibility. For example, has a disciplined and responsible approach to risk and stays motivated and committed when facing challenges
B2: Applies logical thinking. For example, uses clear and valid reasoning when making decisions related to undertaking work instructions
B3: Maintains a productive, professional and secure working environment
B4: Works collaboratively with a wide range of people in different roles, internally and externally, with a positive attitude to inclusion & diversity
B5: Acts with integrity with respect to ethical, legal and regulatory ensuring the protection of personal data, safety and security.
B6: Shows initiative and takes responsibility for solving problems within their own remit, being resourceful when faced with a problem to solve.
B7: Communicates effectively in a variety of situations to both a technical and non-technical audience.
B8: Shows curiosity to the business context in which the solution will be used, displaying an inquisitive approach to solving the problem. This includes the curiosity to explore new opportunities, techniques and the tenacity to improve methods and maximise performance of the solution and creativity in their approach to solutions.
B9: Committed to continued professional development.

Duties

Duty D1

Take and interpret given software development requirements to estimate effort to deliver the work product to enable accurate costs to be established.

Duty D2

Break software development activities down into logical units of work to enable sequencing and ensure the best possible structuring of activities to deliver a high quality product right first time.

Duty D3

Report progress accurately throughout the development life-cycle stages to ensure adequate audit trails of key worksteps such that the organisation can demonstrate how the product has been created for quality and commercial purposes.

Duty D4

Identify and report any impediments to software development activities and propose practical solutions.

Duty D5

Convert customer requirements into technical requirements, both functional and non-functional to ensure that customers' expectations are accurately reflected in the software products developed.

Duty D6

Identify and select the most appropriate technical solution, taking into consideration coding best practice and appropriate quality standards.

Duty D7

Communicate software development solutions to a range of internal or external stakeholders to ensure clear understanding of requirements and how they have been met or adjusted.

Duty D8

Consider security implications of proposed design to ensure that security considerations are built in from inception and throughout the development process.

Duty D9

Write logical and maintainable software solutions to meet the design and organisational coding standards (Software Development Lifecycle -Implementation and Build phase).

Duty D10

Apply security best practice to the software solution throughout the software development life-cycle.

Duty D11

Create and maintain appropriate project documentation to explain the development process and resources used.

Duty D12

Apply appropriate recovery techniques to ensure the software solution being developed is not lost (Software Development Lifecycle -Implementation and Build phase).

Duty D13

Implement appropriate change control to ensure that software development changes may be tracked and quality risks managed.

Duty D14

Undertake unit testing of solutions, with appropriate levels of test code coverage, to identify and, where necessary, resolve issues (Software Development Lifecycle -Implementation and Build phase).

Duty D15

Perfom testing of the software solution to ensure a high quality output (Software Development Lifecycle -Test phase).

Duty D16

Deliver a suitably documented deployable solution to the customer for their use (Software Development Lifecycle -Deploy phase).

Duty D17

Support delivery of one or more software deployment phases, such as trials and final release, to ensure that software developer outcomes are deployed correctly.

Duty D18

Provide support during software trials and after final release to ensure that customers understand and can correctly apply the product, and risks are mitigated.

Duty D19

Respond appropriately to given Service Level Agreements (SLAs) to ensure that time and resources invested in software development activity are allocated appropriately to deliver good customer service.

Duty D20

Apply suitable 'bug fix', appropriate to the severity and priority of the software development issue identified.

Duty D21

Practice continuous self learning to keep up to date with technological developments to enhance relevant skills and take responsibility for own professional development.

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

This is the focused occupation.
assignment_turned_in

Level 4

Progression link from focused occupation.
assignment_turned_in

Level 4

Progression link from 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 7

Progression link from focused occupation.
assignment_turned_in

Level 7

Digital

Engineering and manufacturing