Academy Marketplace/Computing, Software & Digital Engineering/AST-D02-F01
Computing, Software & Digital Engineering · Descriptive & Exploratory Analytics Programmes

Data Engineering & Digital Systems

Develop the capability to design reliable data pipelines, digital data systems and practical engineering workflows.

Capability journey
1UNDERSTAND → 2APPLY → 3BUILD → 4PROVE → 5GROW
45 hoursDuration
6Modules
24Topics
72Subtopics
6Assessments
6Evidence
01 · Programme snapshot

Know what you are stepping into.

Before you enrol, understand the proposition in context: what the programme is designed around, where it sits in the Academy, how it can be experienced and what recognition pathway is attached to it.

Programme purpose

Data Engineering & Digital Systems

A flagship applied programme focused on data engineering foundations, data platforms, system design, quality, governance and a practical engineering demonstration.

Professional ProgrammeProfessionalHybrid
What this tells you: the published profile brings together the learner context, programme positioning, delivery characteristics and recognition pathway in one place.
DomainComputing, Software & Digital Engineering
Programme familyDescriptive & Exploratory Analytics Programmes
LevelL2
RecognitionAcademy credential pathway
02 · Fit & readiness

Is this programme for you?

Make the learner fit visible before you commit. These published definitions describe who the programme is intended for, what eligibility applies and what preparation is expected.

Readiness check

Who this is for

Learners seeking an applied interdisciplinary capability pathway; suitable for students, professionals and capability-development cohorts.

Eligibility

Open to learners who can engage with the stated programme level and complete the required learning activities.

Entry requirements

Basic digital literacy and readiness to undertake guided applied work; domain-specific prerequisites may be introduced in later programme revisions.

03 · Capability outcomes

What you will be able to demonstrate.

The programme is designed around demonstrable capability. These published outcomes show what the learning journey is intended to help you understand, apply, build and prove.

18published capability outcomes

Software Engineering Foundations

3 capability outcomes
01

Explain core software engineering concepts and lifecycle approaches.

02

Analyse software systems in terms of components, users, constraints and trade-offs.

03

Frame software work as an evidence-driven engineering discipline.

Requirements, Design & Architecture

3 capability outcomes
04

Elicit and structure requirements with traceability.

05

Translate requirements into modular designs and explicit interfaces.

06

Explain and document architecture decisions using clear rationale.

Implementation, Testing & Quality

3 capability outcomes
07

Apply maintainable implementation and version-control practices.

08

Design and execute an appropriate multi-level testing strategy.

09

Use engineering quality practices to identify and reduce defects.

Systems Integration & Delivery

3 capability outcomes
10

Design practical integration boundaries and contracts.

11

Explain environment, deployment and release considerations.

12

Assemble repeatable delivery workflows for a software system.

Security, Reliability & Responsible Engineering

3 capability outcomes
13

Identify common software security risks and controls.

14

Design for reliability, observability and recovery.

15

Apply privacy and responsible-engineering considerations to software decisions.

Engineering Capability Demonstration

3 capability outcomes
16

Define and scope a coherent software engineering problem.

17

Produce an integrated software artefact with supporting evidence.

18

Present, defend and reflect on demonstrated engineering capability.

04 · Capability architecture

Understand → Apply → Build → Prove → Grow.

This is more than a five-word model. It describes the learner movement through the programme — and the kind of participation Astraal SymbiOS is designed to support after enrolment.

01UNDERSTAND
Build the foundation before you act.In SymbiOS: Engage with the concepts, explanations and guided learning experiences that establish the knowledge needed for the programme.
02APPLY
Use what you have learned in context.In SymbiOS: Work through guided activities, examples, exercises or cases and connect the concepts to practical situations.
03BUILD
Turn understanding into something tangible.In SymbiOS: Create, practise or develop an artefact, solution, analysis or other applied work that demonstrates growing capability.
04PROVE
Demonstrate capability with evidence.In SymbiOS: Complete the relevant assessments and produce the evidence needed to show what you can actually do.
05GROW
Extend capability beyond the immediate task.In SymbiOS: Reflect, refine and transfer the capability into broader contexts so learning can continue beyond the individual programme activities.
What this means for the learner: the Marketplace tells you what the programme is and what capability it is designed to develop. After enrolment, Astraal SymbiOS becomes the execution environment where the detailed learning activities, practice, assessment and evidence journey are carried through.
05 · Programme architecture

See what you will actually move through.

Explore modules, topics, subtopics, outcomes, assessments, evidence and learning experiences before enrolment.

01

Software Engineering Foundations

Establish the principles, lifecycle thinking and engineering mindset required to build maintainable software.

7.00 hrs
Explore module content · 4 topics3 outcomes · 1 assessment · 1 evidence

Engineering Mindset

1.75 hrs

Understand software engineering as a disciplined socio-technical practice.

  • Engineering vs coding — Engineering vs coding
  • Quality as an engineering concern — Quality as an engineering concern
  • Socio-technical systems — Socio-technical systems

Software Development Lifecycles

1.75 hrs

Compare lifecycle patterns and understand how work progresses from idea to operation.

  • Sequential and iterative lifecycles — Sequential and iterative lifecycles
  • Agile delivery concepts — Agile delivery concepts
  • Feedback and change — Feedback and change

Systems Thinking for Software

1.75 hrs

See software as interacting components, users, data and operating environments.

  • Components and boundaries — Components and boundaries
  • Users and workflows — Users and workflows
  • Runtime context — Runtime context

Engineering Trade-offs

1.75 hrs

Recognise trade-offs among scope, quality, cost, time, risk and change.

  • Scope and prioritisation — Scope and prioritisation
  • Quality and technical debt — Quality and technical debt
  • Risk and uncertainty — Risk and uncertainty
Learning outcomes• Explain core software engineering concepts and lifecycle approaches.
• Analyse software systems in terms of components, users, constraints and trade-offs.
• Frame software work as an evidence-driven engineering discipline.
AssessmentEngineering Design Review

Module-level applied review of understanding, practice and evidence for Software Engineering Foundations.

EvidenceEngineering Foundations Record

Evidence demonstrating capability developed in Software Engineering Foundations.

Learning experience: Guided SymbiOS learning experience for Software Engineering Foundations within Data Engineering & Digital Systems. · Professional Programme · Hybrid
02

Requirements, Design & Architecture

Translate needs into explicit requirements, design decisions and architectural structures.

8.00 hrs
Explore module content · 4 topics3 outcomes · 1 assessment · 1 evidence

Requirements Discovery

2.00 hrs

Elicit, clarify and structure stakeholder needs.

  • Stakeholder identification — Stakeholder identification
  • Elicitation techniques — Elicitation techniques
  • Requirement traceability — Requirement traceability

Functional & Non-functional Requirements

2.00 hrs

Express behaviour, quality attributes and constraints precisely.

  • Behavioural requirements — Behavioural requirements
  • Quality attributes — Quality attributes
  • Constraints and acceptance criteria — Constraints and acceptance criteria

Software Design

2.00 hrs

Translate requirements into modular responsibilities and interfaces.

  • Separation of concerns — Separation of concerns
  • Modularity and interfaces — Modularity and interfaces
  • Design refinement — Design refinement

Architecture & Decision Records

2.00 hrs

Select and document architecture choices with explicit rationale.

  • Architectural styles — Architectural styles
  • Technology decisions — Technology decisions
  • Architecture decision records — Architecture decision records
Learning outcomes• Elicit and structure requirements with traceability.
• Translate requirements into modular designs and explicit interfaces.
• Explain and document architecture decisions using clear rationale.
AssessmentRequirements & Architecture Review

Module-level applied review of understanding, practice and evidence for Requirements, Design & Architecture.

EvidenceRequirements & Architecture Pack

Evidence demonstrating capability developed in Requirements, Design & Architecture.

Learning experience: Guided SymbiOS learning experience for Requirements, Design & Architecture within Data Engineering & Digital Systems. · Professional Programme · Hybrid
03

Implementation, Testing & Quality

Apply disciplined implementation practices and build quality into the development workflow.

9.00 hrs
Explore module content · 4 topics3 outcomes · 1 assessment · 1 evidence

Implementation Practices

2.25 hrs

Apply readable, maintainable and reviewable implementation practices.

  • Readable code — Readable code
  • Error handling and defensive design — Error handling and defensive design
  • Refactoring — Refactoring

Version Control & Collaboration

2.25 hrs

Use version control and collaborative workflows to manage change.

  • Branches and commits — Branches and commits
  • Pull requests and review — Pull requests and review
  • Conflict resolution — Conflict resolution

Testing Strategy

2.25 hrs

Design tests across unit, integration and system levels.

  • Unit testing — Unit testing
  • Integration testing — Integration testing
  • System and acceptance testing — System and acceptance testing

Quality Engineering

2.25 hrs

Use reviews, static analysis and quality gates to reduce defects.

  • Code review — Code review
  • Static analysis — Static analysis
  • Quality gates and defect prevention — Quality gates and defect prevention
Learning outcomes• Apply maintainable implementation and version-control practices.
• Design and execute an appropriate multi-level testing strategy.
• Use engineering quality practices to identify and reduce defects.
AssessmentImplementation & Test Review

Module-level applied review of understanding, practice and evidence for Implementation, Testing & Quality.

EvidenceCode & Test Evidence

Evidence demonstrating capability developed in Implementation, Testing & Quality.

Learning experience: Guided SymbiOS learning experience for Implementation, Testing & Quality within Data Engineering & Digital Systems. · Professional Programme · Hybrid
04

Systems Integration & Delivery

Integrate components and establish repeatable delivery practices.

7.00 hrs
Explore module content · 4 topics3 outcomes · 1 assessment · 1 evidence

Integration Patterns

1.75 hrs

Connect application components and services through explicit interfaces.

  • APIs and contracts — APIs and contracts
  • Synchronous and asynchronous integration — Synchronous and asynchronous integration
  • Error handling across boundaries — Error handling across boundaries

Data & Persistence Integration

1.75 hrs

Design reliable interaction with data stores and external data sources.

  • Data modelling — Data modelling
  • Transactions and consistency — Transactions and consistency
  • External data integration — External data integration

Deployment Environments

1.75 hrs

Understand development, test, staging and production environments.

  • Environment configuration — Environment configuration
  • Configuration and secrets — Configuration and secrets
  • Release promotion — Release promotion

Continuous Delivery

1.75 hrs

Structure repeatable build, release and deployment workflows.

  • Build automation — Build automation
  • Deployment automation — Deployment automation
  • Rollback and release control — Rollback and release control
Learning outcomes• Design practical integration boundaries and contracts.
• Explain environment, deployment and release considerations.
• Assemble repeatable delivery workflows for a software system.
AssessmentIntegration & Delivery Review

Module-level applied review of understanding, practice and evidence for Systems Integration & Delivery.

EvidenceIntegrated Delivery Artefact

Evidence demonstrating capability developed in Systems Integration & Delivery.

Learning experience: Guided SymbiOS learning experience for Systems Integration & Delivery within Data Engineering & Digital Systems. · Professional Programme · Hybrid
05

Security, Reliability & Responsible Engineering

Engineer software with security, resilience, maintainability and responsible-use considerations.

6.00 hrs
Explore module content · 4 topics3 outcomes · 1 assessment · 1 evidence

Secure Software Design

1.50 hrs

Identify threats and incorporate security into design and implementation.

  • Threat modelling — Threat modelling
  • Authentication and authorisation — Authentication and authorisation
  • Input and dependency security — Input and dependency security

Reliability & Resilience

1.50 hrs

Design for failure, recovery and continuity of service.

  • Failure modes — Failure modes
  • Recovery and retries — Recovery and retries
  • Capacity and continuity — Capacity and continuity

Observability & Operations

1.50 hrs

Use logs, metrics, traces and operational signals to understand systems.

  • Logs and structured events — Logs and structured events
  • Metrics and health signals — Metrics and health signals
  • Tracing and diagnosis — Tracing and diagnosis

Privacy & Responsible Engineering

1.50 hrs

Account for privacy, user impact, maintainability and responsible use.

  • Data minimisation — Data minimisation
  • User impact and accessibility — User impact and accessibility
  • Maintenance and accountability — Maintenance and accountability
Learning outcomes• Identify common software security risks and controls.
• Design for reliability, observability and recovery.
• Apply privacy and responsible-engineering considerations to software decisions.
AssessmentResponsible Engineering Review

Module-level applied review of understanding, practice and evidence for Security, Reliability & Responsible Engineering.

EvidenceSecurity & Reliability Evidence

Evidence demonstrating capability developed in Security, Reliability & Responsible Engineering.

Learning experience: Guided SymbiOS learning experience for Security, Reliability & Responsible Engineering within Data Engineering & Digital Systems. · Professional Programme · Hybrid
06

Engineering Capability Demonstration

Demonstrate integrated software engineering capability through a documented build.

8.00 hrs
Explore module content · 4 topics3 outcomes · 1 assessment · 1 evidence

Problem & Solution Definition

2.00 hrs

Define a bounded engineering problem and target solution.

  • Problem statement — Problem statement
  • Success criteria — Success criteria
  • Solution scope — Solution scope

Architecture & Implementation Artefact

2.00 hrs

Produce the core solution and supporting engineering artefacts.

  • Architecture artefact — Architecture artefact
  • Implemented capability — Implemented capability
  • Engineering documentation — Engineering documentation

Verification & Operational Evidence

2.00 hrs

Demonstrate quality, integration and operational readiness.

  • Test evidence — Test evidence
  • Quality review — Quality review
  • Operational readiness — Operational readiness

Technical Presentation & Reflection

2.00 hrs

Defend engineering decisions and identify next capability steps.

  • Solution walkthrough — Solution walkthrough
  • Decision defence — Decision defence
  • Reflection and next steps — Reflection and next steps
Learning outcomes• Define and scope a coherent software engineering problem.
• Produce an integrated software artefact with supporting evidence.
• Present, defend and reflect on demonstrated engineering capability.
AssessmentCapstone Engineering Demonstration

Module-level applied review of understanding, practice and evidence for Engineering Capability Demonstration.

EvidenceCapstone Software Engineering Portfolio

Evidence demonstrating capability developed in Engineering Capability Demonstration.

Learning experience: Guided SymbiOS learning experience for Engineering Capability Demonstration within Data Engineering & Digital Systems. · Professional Programme · Hybrid
06 · The Astraal difference

From programme discovery to demonstrable capability.

Astraal separates the public marketplace experience from the detailed learning execution — so learners can understand the proposition before they enrol and know what happens next.

Marketplace → SymbiOS

Academy Marketplace helps you discover the programme, understand its purpose, structure, capability outcomes and access pathway. Astraal SymbiOS takes over after enrolment for the detailed learning, practice, assessment and evidence journey.

Capability → Evidence → Recognition

The programme is not presented as content alone. Its outcomes connect to learning activities, assessments and evidence so that capability can move from learning to demonstration and, where applicable, to recognition.

Your Astraal learner pathway
DISCOVER
UNDERSTAND
ENROL
EXECUTE IN SYMBIOS
PROVE
RECOGNISE

What changes after enrolment: the Marketplace remains your programme reference, while SymbiOS becomes the environment in which you engage with the detailed experiences, practice, assessment and evidence required by the published programme architecture.

07 · Recognition

Turn learning into something you can demonstrate.

The programme connects capability development with evidence, assessment and — where the published programme provides for it — Academy recognition.

Recognition pathway

Capability can become a credential.

The credential layer gives the learner a visible endpoint for demonstrated achievement. The credential names shown here come directly from the published V2 programme record.

Learn→ Demonstrate→ Recognise
Programme Credential
Evidence matters

Show what you can demonstrate.

6evidence

Evidence is part of the published programme architecture. It gives the learner a concrete way to show what has been produced, applied or demonstrated across the learning journey.

6module assessments
6evidence items
Engineering Foundations Record
Requirements & Architecture Pack
Code & Test Evidence
Evidence is not an extra layer added after learning. It is part of the programme architecture that connects learning, assessment and demonstrable capability.

Ready to explore the pathway?

Review the published access offer and take the next step into this programme. Detailed learning execution continues in Astraal SymbiOS after enrolment.