They set the coursework at the university - building a code for DFD (Data Flow Diagram or data flow diagram). Having studied the subject area (in particular, here ), I came to the conclusion that diagrams of this type are logical diagrams that only model the area of ​​data streams. That is, to transfer this further, you need to build other diagrams, for example, UML, where you can already display areas marked on the DFD diagram.

Actually, the question is: tell me how wrong I am, and how they are doing it right, and also - is it possible (and is it actually being done that way) to build code using a DFD diagram? If yes, then you can sample software, or algorithm, whatever. Thank.

    1 answer 1

    That's right, this is not a matter of taste, experience, timing, financing, requirements, and so on.

    It is necessary to speak not about the "correctness" of approaches to creating software, but about meeting the requirements of the supplier of the task (whether it be a teacher or a customer).

    And to meet these requirements, if, according to the information provided, you are able to do what is required of you, then what else is needed (if that's understandable, then why produce extra bureaucracy and waste precious resources - time)?

    If, however, the information provided raises legitimate questions, then ask them - use different charts and diagrams, as well as apply methods for collecting and structuring requirements. And all this until the task (or her, independent of each other, parts) becomes clear to you.

    All this should be not in itself (not for the sake of ibd), but for the sake of one single goal - customer satisfaction, no more and no less.

    • A wonderful, wonderful answer! Thank you, I will remember as a quote (no sarcasm, I liked the words very much) - Range