CUT TO:
INT. PROJECT ARCHIVE — STORYBOARD ROOM
The USER opens Satellite Network & File Transfer Simulator.
DIVAKAR DESSAI
Let's run through the shots.
CASE FILE / COMP2511 / Object-Oriented Design
Satellite Network & File Transfer SimulatorObject-Oriented Orbital Communication Simulation
Built an object-oriented Java simulation of satellites and devices communicating across an orbital network with movement, visibility, relays and incremental file transfers.
01–02 / OPENING SEQUENCE
Establishing the world
01 / Establishing Shot
The Problem
The assignment required modelling a dynamic network in which satellites and devices had different capabilities while interacting through movement, communication and file-transfer rules.
02 / Wide Shot
The Context
The project was completed for COMP2511 and focused on translating a large behavioural specification into an extensible object-oriented Java design.
03 / CHARACTER NOTE
DIVAKAR'S ROLE
Subject
Divakar Dessai
Production
Satellite Network & File Transfer Simulator
Take
03 / Role
Role notes
DIVAKAR DESSAI
I designed and implemented the simulation model, entity hierarchy, movement logic, communication reachability and stateful file-transfer behaviour.
04 / CLOSE-UP
THE ENGINEERING CHALLENGE
Communication depended simultaneously on satellite movement, range, geometric visibility and possible relay paths, while active file transfers also needed to respond to changing network conditions.
05 / TRACKING SHOT
THE APPROACH
A plan emerges.
I modelled common behaviour through abstract satellite and device abstractions and specialised implementations. Relay communication was handled through recursive graph-style traversal, while file transfers were maintained as simulation state and advanced incrementally each tick.
06 / INSERT SHOTS
KEY FEATURES
The system takes shape.
07 / DIRECTOR'S NOTES
DESIGN DECISIONS
Things we decided along the way
01
Used inheritance and polymorphism to model entity-specific behaviour.
02
Kept satellite movement behaviour within satellite implementations.
03
Used recursive traversal for relay-assisted communication.
04
Tracked visited entities during traversal to prevent duplicate exploration.
05
Represented file transfers as persistent simulation state rather than instantaneous operations.
design decisions
somewhere mid-build
08 / RETAKES
WHAT WENT WRONG
Naturally, not everything cooperates.
09 / FINAL SHOT
THE OUTCOME
ProblemBuildOutcome
01
Built a complete object-oriented network simulation.
02
Applied inheritance and polymorphism to a substantial domain model.
03
Implemented recursive graph-style connectivity logic.
04
Developed stronger experience modelling mutable simulation state.
10 / PRODUCTION NOTES
TECH STACK
The tools behind the scenes.
JavaGradleJUnitObject-Oriented Programming
11 / BEHIND THE SCENES
LINKS
FADE OUT.
USER closes the file.
One project down. A few more stories left.
DIVAKAR DESSAI
Pick another?