Essential business process modeling
Ten years ago, groupware bundled with email and calendar applications helped track the flow of work from person to person within an organization. Workflow in today's enterprise means more monitoring and orchestrating massive systems. A new technology called Business Process Management, or BPM,...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol, California :
O'Reilly
2005.
|
| Edición: | 1st edition |
| Colección: | Theory in practice.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627115406719 |
Tabla de Contenidos:
- Essential Business Process Modeling; Assumptions This Book Makes; Contents of This Book; Conventions Used in This Book; Using Code Examples; Safari Enabled; We&d Like to Hear from You; Acknowledgments; I. Concepts; 1.2. BPM Acid Test: The Process-Oriented Application; 1.3. The Morass of BPM; 1.3.2. Vendors; 1.3.3. BPM Theory; 1.4. Workflow; 1.5. Roadmap; 1.6. Summary; 1.7. References; Two. Prescription for a Good BPM Architecture; 2.1.2. The Local Perspective Guided by the Global Contract; 2.1.3. Components of a Good Design; 2.1.4. Run It on an Application Server
- 2.2. Components of the Design2.2.2. Runtime Engine; 2.2.3. Human Interaction; 2.2.4. System Interaction; 2.2.4.2. The process is a web service; 2.2.5. Administration and Monitoring; 2.2.5.2. Process versioning basics; 2.2.5.3. BAM and process mining; 2.2.6. Local View of Choreography: WS-CDL Toolkit; 2.3. Standards; 2.4. Summary; 2.5. Reference; Three. The Scenic Tour of Process Theory; 3.2. The Pi-Calculus; 3.2.2. The Pi-Calculus and BPM; 3.3. Petri Nets; 3.3.1.2. Petri Net Extensions; 3.3.2. Petri Nets and BPM Patterns; 3.3.2.2. Dead path elimination; 3.3.3. Petri Nets and the Standards
- 3.4. State Machines and Activity Diagrams3.4.2. The Dualistic Activity Diagram: Flow Chart and State Machine; 3.4.3. State, Activity, and the Standards; 3.4.4. Event-Driven Process Chains; 3.5. Summary; 3.6. References; Four. Process Design Patterns; 4.2. Process Patterns and the P4; Advanced Branch and Join Patterns; Structural Patterns; Multiple Instances Patterns; State-Based Patterns; Cancellation Patterns; 4.3. Yet Another Workflow Language (YAWL); 4.4. Additional Patterns; 4.4.2. Human Workflow; 4.5. Process Coding Standards; 4.6. Summary; 4.7. References; II. Standards
- 5.2. BPEL Example5.3. BPEL in a Nutshell; 5.3.2. Variables and Assignments; 5.3.3. Exception Handling and Compensation; 5.3.3.2. Fault handler; 5.3.3.3. Event handler; 5.3.4. Split and Join; 5.3.3.5. flow; 5.3.3.5.2. Links and synchronization dependencies; 5.3.3.5.3. Dead path elimination; 5.3.5. Loops; 5.3.5.2. Implementing foreach; 5.3.6. Participant Exchange; 5.3.6.2. Partner links; 5.3.6.3. Partners; 5.3.6.4. Partner interactions; 5.3.6.4.2. receive; 5.3.6.4.3. reply; 5.3.6.4.4. pick; 5.3.6.5. Properties; 5.3.6.6. Correlation; 5.3.7. Transactions; 5.3.8. Extensions; 5.4. BPELJ
- 5.4.2. BPELJ Source Code5.4.3. Other Language Implementations; 5.5. BPEL and Patterns; 5.6. Summary; 5.7. References; Six. BPMI Standards: BPMN and BPML; 6.1.2. BPMN in a Nutshell; 6.1.2.2. Variables and assignments; 6.1.2.3. Exception handling and compensation; 6.1.2.4. Split and join; 6.1.2.5. Loops; 6.1.2.6. Participant exchange; 6.1.2.7. Transactions; 6.1.2.8. Extensions; 6.1.3. BPEL Mapping; 6.1.4. BPMN and Patterns; 6.2. BPML; 6.2.2. BPML in a Nutshell; 6.2.2.2. Variables and assignments; 6.2.2.3. Exception handling and compensation; 6.2.2.4. Split and join; 6.2.2.5. Loops
- 6.2.2.6. Participant exchange
