000			03629nam a2200289 i 4500
003			MIUC
005			20191127092714.0
008			161103s2011 cau||||| |||| 001 | eng d
020			_a9780982368114
040			_aMIUC _beng _cMIUC
082	0		_a658.4
100	1		_92673 _aSilver, Bruce _q(Bruce Richard)
245	1	0	_aBPMN method and style : _bwith BPMN implementer's guide / _cBruce Silver.
250			_a2nd ed.
260			_aUSA : _bCody-Cassidy Press, _c2011.
300			_axii, 269 p. : _bill. b&w ; _c24 cm.
500			_aIncludes index.
505	0		_aPt. 1. What is BPMN? -- Ch. 1. Bad BPMN, good BPMN -- Ch. 2. How does a model mean? -- Pt. 2. Method and style – Level 1 -- Ch. 3. BPMN by example -- Ch. 4. The level 1 palette -- Ch. 5. The method -- Ch. 6. BPMN style -- Pt. 3. Method and style – Level 2 -- Ch. 7. Events -- Ch. 8. Iteration and instance alignment -- Ch. 9. Process splitting and merging -- Ch. 10. Transactions -- Ch. 11. The rules of BPMN -- Pt. 4. BPMN implementer's guide – Non-executable BPMN -- Ch. 12. BPMN 2.0 metamodel and schema -- Ch. 13. Process modeling conformance subclasses -- Ch. 14. BPMN serialization basics -- Ch. 15. Serializing process elements -- Ch. 16. Serializing data flow -- Ch. 17. The BPMNDI graphical model -- Ch. 18. BPMN-I -- Pt. 5. BPMN implementer's guide -- Executable BPMN -- Ch. 19. What is executable BPMN? -- Ch. 20. Variables and data mapping -- Ch. 21. Services, messages, and events -- Ch. 22. Human tasks -- Ch. 23. Executable BPMN in practice -- Ch. 24. Aligning executable design with BPMN method and style.
520			_aBPMN 2.0 is the industry standard diagramming language for business process models. The meaning of the business process diagram is the same, regardless of the tool used to create it. But creating models that are correct, complete, and clear demands more than a dictionary of BPMN shapes and symbols. It also requires a methodology for translating process logic consistently into the diagram. And it requires a measure of modeling style as well, conventions that ensure that the process logic is unambiguous from the diagram by itself. In short, "good BPMN" requires a disciplined approach called "method and style." In this book, Bruce Silver explains which BPMN elements process modelers need to understand, in two levels, including exactly where and how to use each element. Level 1 (the Descriptive modeling subclass of BPMN 2.0) is a palette of shapes and symbols largely carried over from traditional flowcharting. Level 2 (the Analytic subclass) expands the palette to be able to describe event-triggered behavior, critical to modeling exception handling. The book explains the real meaning of BPMN's most basic concepts - like activity, process, and end state - essential to using the language correctly, and provides a step-by-step methodology for going from a blank page to a complete end-to-end BPMN model, developed from the top down in a hierarchical structure. From the top-level diagram you can see on a single page exactly how the process starts, its possible end states, what the instance represents, and communications with the Customer, service providers, and other processes. From there you can drill down to see the details of any part of the process.
650		0	_91040 _aProcess control _xData processing
650		0	_92674 _aWorkflow _xManagement
650		0	_91041 _aManagement information systems
650		0	_9320 _aBusiness planning
650		0	_914 _aBusiness _xData processing
650		0	_91413 _aReengineering (Management)
942			_2ddc _cBK