CUT TO:
INT. PROJECT ARCHIVE — STORYBOARD ROOM
The USER opens UNSW AUStronauts CubeSat.
DIVAKAR DESSAI
Let's run through the shots.
CASE FILE / Space Systems / Software Engineering
UNSW AUStronauts CubeSatStudent-Built Spacecraft Software Systems
Software and systems engineering work supporting UNSW AUStronauts and the development of a student-built CubeSat mission.
01–02 / OPENING SEQUENCE
Establishing the world
01 / Establishing Shot
The Problem
A CubeSat requires several software and hardware subsystems to operate together reliably under severe constraints on power, bandwidth, computing resources and physical space.
02 / Wide Shot
The Context
UNSW AUStronauts is a multidisciplinary student satellite team developing a CubeSat mission. Software development therefore sits within a larger systems-engineering process involving electrical, mechanical, communications and mission requirements.
03 / CHARACTER NOTE
DIVAKAR'S ROLE
Subject
Divakar Dessai
Production
UNSW AUStronauts CubeSat
Take
03 / Role
Role notes
DIVAKAR DESSAI
I contributed to the software systems team and worked on technical planning around onboard computing, telemetry, communications and the organisation of software development for the mission.
04 / CLOSE-UP
THE ENGINEERING CHALLENGE
Unlike a conventional web application, spacecraft software must operate with constrained hardware, limited communications bandwidth and intermittent contact with the ground while remaining reliable enough for mission operations.
05 / TRACKING SHOT
THE APPROACH
A plan emerges.
The software effort involved breaking spacecraft functionality into well-defined subsystems, evaluating onboard-computing options, considering telemetry and communication formats and designing software around the operational constraints of a CubeSat mission.
06 / INSERT SHOTS
KEY FEATURES
The system takes shape.
07 / DIRECTOR'S NOTES
DESIGN DECISIONS
Things we decided along the way
01
Treated software as part of the overall spacecraft system rather than as an isolated application.
02
Considered power, compute and bandwidth constraints when evaluating architecture.
03
Separated subsystem responsibilities to support parallel team development.
04
Designed communication around structured telemetry and command messages.
design decisions
somewhere mid-build
08 / RETAKES
WHAT WENT WRONG
Naturally, not everything cooperates.
09 / FINAL SHOT
THE OUTCOME
ProblemBuildOutcome
01
Contributed to the development of the CubeSat software architecture.
02
Helped define software-system responsibilities and interfaces.
03
Applied conventional software-engineering concepts within a spacecraft environment.
04
Gained experience working within a multidisciplinary systems-engineering project.
10 / PRODUCTION NOTES
TECH STACK
The tools behind the scenes.
CubeSat SoftwareOnboard ComputingTelemetryCommunicationsEmbedded SystemsSystems Engineering
FADE OUT.
USER closes the file.
One project down. A few more stories left.
DIVAKAR DESSAI
Pick another?