There are 9 different intermediate events in BPMN. One of them, called the none intermediate event, is “undefined” in that it doesn’t specify a distinct behavior. Unlike the other intermediate events, the none intermediate event has a single interpretation, and will only be used with a specific methodology.
Monthly Archives: August 2006

Posted in Business Process Modeling, Requirements, Requirements gathering
Tagged bpmn, bpmn changing state, bpmn diagram example, bpmn diagrams, bpmn example, bpmn intermediate event, bpmn intermediate event example, bpmn none intermediate event, bpmn none intermediate event example, bpmn symbols, bpmn tutorial, business process modeling diagrams, managing data
Leave a comment

John Henry, Manual Tester
There’s a piece of North American folklore about John Henry, who was a manual laborer during the expansion of the railroads in our country. His job was being replaced by steam-driven heavy equipment, as the railroad industry applied technology to become more efficient. The same dynamics are happening today with manual testers. We need to make sure that manual testers avoid John Henry’s fate – read on to see why.

Posted in Business Process Modeling, Requirements, Requirements gathering
Tagged bpmn, bpmn compensation end event, bpmn diagrams, bpmn example, bpmn examples, bpmn link end event, bpmn multiple end event, bpmn symbols, bpmn terminate end event, bpmn tutorial, business process modeling diagram, business process modeling diagrams, business process modeling example, business process modeling examples, managing data
Leave a comment

Posted in Business Process Modeling, Requirements, Requirements gathering
Tagged bpmn artifact, bpmn artifacts, bpmn diagramming, bpmn diagramming artifacts, bpmn diagrams, bpmn symbols, bpmn tutorial, business process modeling artifacts, business process modeling diagram, managing data, pbmn diagram artifact
2 Comments

Posted in Requirements, Requirements gathering, Software development, Testing
Tagged managing data, quality and requirements, quality requirements, requirements and quality, requirements elicitation, requirements errors, requirements quality, writing good requirements, writing quality requirements
Leave a comment




