I need to tell the programmer how my complex system works. What is the best way to do this?

Question

Programming

I report the algorithm of my complex system in the form of drawn logic diagrams (neither a compiler, nor a simulator, just my understanding of the work). At the same time, the system is quite complex and often the algorithm has to be corrected => something is lost, forgotten, does not change when necessary, etc. .d. Ask! Tell me the environment (I tried Simulink - too loaded), in which you can quite clearly depict the principle of the system (> 50 input parameters and even more output parameters), while somehow doing this. I will be glad to any suggestions. If something is not completely clear, I will describe it.

Answer 1

Microsoft Visio there is a construction of flowcharts. But there is no animation and performance simulation.

Answer 2

Break the overall scheme into levels. General plans and details. Warn the developer about upcoming changes, and ask them to consider it.
If the changes themselves are not known, their nature is nonetheless known. "Everything can change" - this can also be safely documented.
Graphic formats will not save you. A simple document written jointly with a developer, in a conversation - yes. Just put on paper what you say out loud, that's the whole secret. Judging by the statement of the problem, now you are not doing this.

Answer 3

Good people from ELMA have translated the documentation of the BPMN 2.0 notation standard and the BPMN 2.0 business process model to a high standard .
Use either Visio or MID's good free version of Innovator .
If you learn how to use BPMN, then this will be a significant plus to your skills.

Answer 4

There is a course on the stepik "Statement of the problem"

Answer 5

Sequence diagram is how objects and classes interact in practice.
use case diagram - for a more abstract representation of the architecture.
class diagram - already for a more detailed analysis of classes, interactions and their parameters.
Since I understand that your architecture is too confusing and large, you can break it into modules. And provide parts. in sequence diagrams, at the same time, the full version at the abstract level in a user-case diagram.
Many large firms practice hybrid models, where they combine several types of diagrams from design practice into one (you really need to google here).
programs: For example MagicDraw