Also, I think these logic flowcharts probably belong with the software API documentation and overview (/docs in the rivercontrolsystem repo), along with Patrick's diagrams. This allows them to be shown with the rest of the software documentation for consistency.
We could also link to these from the Software Design Spec. Thoughts?
Software Design Documentation To-Do (March 2022 onwards)
Re: Software Design Documentation To-Do (March 2022 onwards)
Note: Patrick wrote state diagrams for his logic, not flowcharts, so there are still flowcharts to be created at some point.
Owing to the very object-orientation-heavy design pattern he used in this logic, I suspect it will be best for me to write the flowcharts.
Owing to the very object-orientation-heavy design pattern he used in this logic, I suspect it will be best for me to write the flowcharts.
Hamish