![]() Nothing could actually be farther from the reality. They got the impression doing "something wrong", or maybe suboptimal "object oriented design". DFDs scale well to several layers of abstraction, they can be defined with a clear and strict semantics, and they can be even used for model driven approaches and code generation.īut since this diagram type was missing in UML, I have seen several people hesitating to use DFDs. ![]() Data flow diagrams are essential for modeling any kind of system which contains data processing components, with some input data, some processing and some output data (and disclaimer: these were >95% of the systems I had to deal with over the last 30 years). UML was lacking data flow diagrams for decades (which was - in my eyes - probably the biggest single mistake the UML designers ever made). I have also no idea if there is any tool other than some general diagramming tools like Visio or Dia that supports visual extension of UML, theoretically granted by profiles. I am not sure if StarUML supports ports and if you can stereotype them there. The other option is to use Profiles to extend the UML and, actually still by stereotyping, change its visualisation to have a small arrow inside indicating data flow. One is to use stereotypes for ports, marking them as > or > respectively. First of all, you should depict the components with ports (shown as small rectangles, from which the interface lines protrude rather than coming directly from the component itself). If you still insist on showing the data flow direction on the same diagram, there are two related possibilities. I would go for a sequence diagram (probably a few of them), however some other behaviour diagrams might do as well. ![]() To show the data flow, that is a dynamic (behavioural) part of your system you should use some other diagram(s). The only information about the direction of data flow that can be read from it is who actually initiates the communication but does not depict the direction of the data flow. The Components Diagram is a static view of the system. This is usually happening when you try to indicate the whole model on just one diagram. The root of many problems is trying to show information on a diagram that is not intended to use it this way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |