A diagram

Havn’t been blogging much lately as there’s been too much comment spam. Hopefully it has been fixed now. Though, dear reader, I need your help. Could you please tell me what you think I’m communicating via this diagram? Update: I’ve already modified the diagram, based on some feedback. More is appreciated.


Guess what the image means

I’m giving a similar (or modified) image to my second year students. I’d like to know if I’m actually communicating what I intend to communicate. Consider this a usability test(ish).

4 Responses to “A diagram”

  1. Des Traynor says:

    Can’t help you here I’m afraid. I can get as far as The dot (.) pings the subnet, and listens for accept.

    Then one of three things happen, or all three things happen in an order, or all three things can happen, but none of them are guaranteed. I have no idea whats happening there.

    Also, for the sake of a better diagram, if all three things end in shutdown, why move that outside, unless the shutdown method is different for each of the three cases, in which case you should clarify that.

    Bear in mind, people usually read top to bottom, left to right, so a diagrams typical flow should usually be that way.

    If one of three things is going to happen, have one box, with three outward arrows. If all three things must happen in order, have it as a chain of actions.

  2. Bart B says:

    I have to say I’m stumped. Is this some for of state diagram, a sw=equence diagram, a networking diagram … what? If it relates to software my advice would be to re-do it as some form of UML diagram. UML is standard so even if the kiddies don’t get it the first time if they get this diagram explained to them they learn two things, what ever you are teaching them and some UML, which is a good thing for students to get familiar with!

  3. phil says:

    Hmm.
    A thread sends a message to the subnet, and then listens for accept. Now, the original thread is joined by two other, unrelated threads. It gets an accept, acknowledges it, and shuts down. Or else the 3 middle sections relate to the flow of events when an accept is received. But I still can’t see what order they execute in.
    Its possible that theres an explanation for all this, with context, but really I think you need to start from scratch.

  4. Neal Chant says:

    I can see where you’re going. The path to your nirvana is both rocky and muddy.

    The flow doesn’t seem right, you have Listen for Accept twice? With the 3 boxes aligned it *appears* that all 3 processes could be simultaneous, or, if that’s not the case then there is no indication of how logic takes place.

    Neal :)

Leave a Reply