You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although this repository is named ST-DroneInterface, there aren't any real interfaces implemented.
Instead, most modules prefer a script-based runtime more common in experimental settings.
In software engineering, abstract interfaces are used to generalize functionality while hiding implementation details. In script-based implementations, developers are overexposed to the complexities of implementation when they may only need to understand high-level behaviors.
In order to make this code as reusable, grokkable, and testable as possible, I propose the implementation of an abstract Drone interface. The interface will define high level behaviors that maximize utility.
Once the definition of the interface is complete, we can do a concrete implementation class called STDrone that performs all the actions defined by the interface using code already written in this repository.
This is critical, foundational work that needs to happen before any further development occurs.
User Story:
As a drone controller developer
I only want to interface with high-level drone functionality without being concerned about implementation details
So that my code will work across all concrete drone implementations seamlessly
And so that I can test my code against simulated environments.
The text was updated successfully, but these errors were encountered:
Although this repository is named ST-DroneInterface, there aren't any real interfaces implemented.
Instead, most modules prefer a script-based runtime more common in experimental settings.
In software engineering, abstract interfaces are used to generalize functionality while hiding implementation details. In script-based implementations, developers are overexposed to the complexities of implementation when they may only need to understand high-level behaviors.
In order to make this code as reusable, grokkable, and testable as possible, I propose the implementation of an abstract
Drone
interface. The interface will define high level behaviors that maximize utility.Once the definition of the interface is complete, we can do a concrete implementation class called
STDrone
that performs all the actions defined by the interface using code already written in this repository.This is critical, foundational work that needs to happen before any further development occurs.
User Story:
As a drone controller developer
I only want to interface with high-level drone functionality without being concerned about implementation details
So that my code will work across all concrete drone implementations seamlessly
And so that I can test my code against simulated environments.
The text was updated successfully, but these errors were encountered: