Systems design
Systems design involves creating the specification and design of systems to meet defined business needs.
Levels
- 1. Awareness
You can:
- assist as part of a team in the design of components of larger systems
- 2. Working
You can:
- translate logical designs into physical designs
- produce detailed designs
- effectively document all work using required standards, methods and tools, including prototyping tools where appropriate
- design systems characterised by managed levels of risk, manageable business and technical complexity, and meaningful impact
- work with well understood technology and identify appropriate patterns
- 3. Practitioner
You can:
- design systems characterised by medium levels of risk, impact, and business or technical complexity
- select appropriate design standards, methods and tools, and ensure they are applied effectively
- review the systems designs of others to ensure the selection of appropriate technology, efficient use of resources and integration of multiple systems and technology
- 4. Expert
You can:
- design systems characterised by high levels of risk, impact, and business or technical complexity
- control system design practice within an enterprise or industry architecture
- influence industry-based models for the development of new technology applications
- develop effective implementation and procurement strategies, consistent with business needs
- ensure adherence to relevant technical strategies, policies, standards and practices
Contains public sector information from the UK Government Digital and Data Profession Capability Framework (https://understand-digital-data-roles-skills.service.gov.uk/), licensed under the Open Government Licence v3.0. © Crown copyright.
Closest ESCO skills
Contains ESCO v1.2.1 data (https://esco.ec.europa.eu/). © European Union. Reuse authorised under Commission Decision 2011/833/EU.
Role levels that expect this skill
| Role level | Role | Band | Expected level |
|---|---|---|---|
| Junior DevOps engineer | DevOps engineer | 5 | Awareness |
| DevOps engineer | DevOps engineer | 6 | Working |
| Senior DevOps engineer | DevOps engineer | 7 | Practitioner |
| Lead DevOps engineer | DevOps engineer | 8b | Practitioner |
| Principal DevOps engineer | DevOps engineer | 8c | Practitioner |
| Associate infrastructure engineer | Infrastructure engineer | 4 | Awareness |
| Infrastructure engineer | Infrastructure engineer | 6 | Working |
| Senior infrastructure engineer | Infrastructure engineer | 7 | Practitioner |
| Lead infrastructure engineer | Infrastructure engineer | 8a | Practitioner |
| Principal infrastructure engineer | Infrastructure engineer | 8b | Expert |
| Integration engineer | Integration engineer (health interoperability) | 6 | Working |
| Senior integration engineer | Integration engineer (health interoperability) | 7 | Practitioner |
| Lead integration engineer | Integration engineer (health interoperability) | 8a | Expert |
| Associate network architect | Network architect | 6 | Working |
| Network architect | Network architect | 7 | Practitioner |
| Lead network architect | Network architect | 8a | Expert |
| Junior software developer | Software developer | 5 | Awareness |
| Software developer | Software developer | 6 | Working |
| Senior software developer | Software developer | 7 | Practitioner |
| Lead software developer | Software developer | 8a | Practitioner |
| Principal software developer | Software developer | 8b | Expert |