I am making this independent drone control system that a user can start and stop. When the program is started, the connected drone takes off, hovers, and turns to face the other side. At first I though of a use case diagram like this:
The issue with this is that it seems as if the developer can execute "Take off" etc. even though this is only done by the system. At least, that's how I interpret it from most example use case diagrams. In this other question the included use case was something done solely by the system as well, but was deemed unsuitable for the use case diagram. Therefore,
- Do I remove the included use cases?
- Do I still describe these in the main flow of the "Start" and "Stop" use cases if I remove them?
For example, the main flow of the "Start" use case:
The developer starts the program. The drone takes off. The drone hovers in the air. The drone yaws to face the opposite direction.
- Do I keep them but add a "FlightController" actor that connects to the included use cases?