Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm drawing a flow diagram which should visualize the communication between 4 services I created.

Now I've got a question I'm not quite sure about. There are two ways the services could be started. Is it allowed to have multiple starting-points in a flow chart?

And: do I have to visualize error handling, like a service not being available? I think this doesn't belong in a flow chart, perhaps?

share|improve this question
A flowchart is not the tool for the job. – Tulains Córdova Nov 25 '12 at 22:42
up vote 2 down vote accepted

If you are using flowcharts, then you can have 3 separate flowcharts. 1 to represent the overall view showing the decision that leads to initiating the service in the 2 different ways you say you have in your case. The other two diagrams will detail the process in each scenario. Flow charting is a loose technique with hardly any rules beyond what the shapes mean. This causes an inconsistency problem sometimes.

For documenting OO systems, I suggest you use UML 2.0+ and in particular Activity diagrams (similar to flow charts) and Sequence diagrams as well as use cases.

share|improve this answer
But there is no 'best practice', isn't it? I'm not quite sure how to display the communication over a MOM in an activity diagramm – verbose-mode Nov 25 '12 at 20:31
I am not familiar with MOM. – NoChance Nov 25 '12 at 22:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.