How do I get from requirements document to final code / program in Python?
That's the subject for a book, or even multiple books.
Kinda hard to give you a useful response in this forum, except for: hire a consultant to help you.
Geert
Yes, quite true.
But I am not looking for quick fix.
I am trying to use EA for a python software project development.
Here is another way of looking at it.
Rather long winded...
After the days of punched cards and hex keying of hand assembled code, I graduated to simple text editors.
That is, we got rid of handwriting quality, manual assembly and fragility of cards.
To make it more readable, an editor that has syntax highlighting was the next step.
Now we have IDEs, which also include build, run, step through....
Throw in static analysis and any competent and experienced programmer becomes highly productive.
The gap left is from documentation to code generation and testing, the last manual step.
I have used flowcharts for a few decades and UML (mainly Visual Paradigm) for the past decade+.
But VP by their own admission cannot generate code from flow/ activity diagram, only from state charts.
So, which UML profile should I use for end-to-end solution in EA?
If necessary, I am ready to give up requirements diagram (that is SYSML).
That is, go back to creating just State/ Activity and Sequence diagrams to generate code.
The Architecture design gap is easy to bridge because both done by persons with a higher level of experience and competence.
Now if I can generate even a well-documented code or code skeleton, I will be making juniors very productive.
