In unser dreiteiligen Blogserie „Kampf der Notationen“ werden wir der Frage nachgehen, ob sich ein Umstieg vom Aktivitätsdiagramm der UML 2.3 auf die BPMN 2.0 wirklich lohnt oder ob nicht.

Inspiring.

As traditionally written, requirements are designed to produce conflict. It is an item for IT and “the business” (to use the common IT term) to negotiate when money and timelines take center stage. That they were hastily written in the first place only makes the conflict more likely. It also sets the designer up to be the fall guy for a poorly conceived system. Recognizing their inherently conflict-driving nature, the designer can work to diffuse the situation and get a seat at the table when the next project starts.

"As I coach new developers, I've taken to scribbling out the same useful diagram for visualizing the creative process again and again on coffee-ringed napkins. In order to limit my future abuse of culinary paper wares, I've reproduced my images in a more formal fashion in this essay."

http://www.lostgarden.com/2010/08/visualizing-creative-process.html

"Years ago I dropped a simple illustration into a proposal to convey the design process to a client. It was meant to illustrate the characteristics of the process we were to embark on, making it clear to them that it might be uncertain in the beginning, but in the end we’d focus on a single point of clarity. It seemed to work. And from then on, I’ve used it since. Many many times."

http://centralstory.com/about/squiggle/