My advice is keep your audience in mind. With a swim lane you generally want to use a lane for each department/system involved in the process. I prefer not to have "system" swim lanes, just groups, but it depends on the process your modeling.

Check out my article on process mapping and flow charts. http://randomcrates.com/the-art-of-the-flow/

The graphics are too small to make out the content, but this reminds me of that scene in Amadeus where the Emperor feels he should make some comment on the piece he has just listened to:

Emperor: It's very good! Of course, now and then, ju-ju-just now and then it, it seems a touch... how should one say? How shall one say, Director?
Director: Er, too many swim lanes, your Majesty.
Emperor: Exactly, very well put. Too many swim lanes.
Mozart: I don't understand, there are just as many swim lanes, Majesty, as I require, neither more nor less...
Emperor: My dear young man, don't take it too hard. Your work is ingenious. It's quality work. And there are simply too many swim lanes - that's all. Just cut a few and it will be perfect.
Mozart: Which few did you have in mind, Majesty?

How many swim lanes does the reader require in order to understand the information presented?

Thanks Eric.

I'll add new s/shots so things are clearer. Was up to 2am doing the final touches. Brain slightly melted.

The lines from Amadeus are great, aren't they?

Wonder what happened to the actor who played him?


Regards,
Ivan Walsh
Twitter: @ivanwalsh
Facebook: http://www.facebook.com/ivanwalsh/
Flickr: http://www.flickr.com/photos/ivanwalsh/
Web: http://www.klariti.com & http://www.ivanwalsh.com