Best way to describe a threaded application ? (diagrams)
-
Nagy Vilmos wrote:
There's a useful UML diagram, not sequence
more from me | GALex: C++ Library for Advanced Genetic Algorithms
I agree. I read martin Fowler's UML distilled a while ago and activity diagrams are suitable for showing multiple threads. You can branch off and join up again. They look like flowcharts. I think that's the closest UML one for what you want
-
I agree. I read martin Fowler's UML distilled a while ago and activity diagrams are suitable for showing multiple threads. You can branch off and join up again. They look like flowcharts. I think that's the closest UML one for what you want
I have a good book called "Doing Hard Time" by Bruce Powel Douglass - he uses quite a few different types of UML diagrams, but I think Chapter 8 on "Architectural Design" is most relevant here. The Concurrent Sequence Diagram on p378 is also known as a swim lane diagram; he then shows the same (robot -based) example as a Concurrent Collaboration Diagram and a Concurrent Timing Diagram. He also describes a lot of real-time patterns like watchdogs and monitor-actuators. He provides a swim-lane representation of each pattern.