List of Figures

• 1-1. From conceptualization via design to implementation
• 2-1. The entity types Shop and Delivery.
• 2-2. Adding properties and operations.
• 2-3. Adding a property constraint and an operation constraint.
• 2-4. Object and event types as two different categories of entity types.
• 2-5. A BPMN Process Diagram for a pizza service company
• 2-6. A DPMN Process Diagram for a pizza service company
• 3-1. A basic DPMN Process Diagram showing an Object Event Graph.
• 3-2. A basic OE class model defining an object type and three event types.
• 3-3. A DPMN-A process model and its underlying OE class model
• 3-4. A DPMN-A process model with an RDAS arrow and its underlying OE class model
• 3-5. A DPMN-A process model of a Load-Haul-Dump business process
• 3-6. A process design for the Make-and-Deliver-Pizza business process.
• 3-7. An enriched process design model
• 3-8. An OE class design model for the Make-and-Deliver-Pizza business process.
• 5-1. A basic DPMN Process Diagram showing an OEG.
• 5-2. A basic OE class model defining an object type and three event types.
• 7-1. A conceptual information model of a manufacturing workstation system
• 7-2. A conceptual process model of a manufacturing workstation system
• 7-3. An information design model
• 7-4. A process design model in the form of a DPMN Process Diagram
• An example of a simple AN
• 8-1. Introducing an activity type in a conceptual information model of a single workstation system.
• 8-2. Introducing an activity type in a conceptual process model of a single workstation system.
• 8-3. Going from basic OEM to OE class models by introducing activity types.
• 8-4. Going from basic DPMN to DPMN-A process models by introducing Activity rectangles.
• 8-5. Allocating the workstation as a resource of Processing activities
• 9-1. Typically, the performer of an activity is a resource object.
• 9-2. Activity types may have special properties representing resource roles.
• 9-3. A conceptual information model of the activity type "examinations" with resource roles.
• 9-4. A conceptual process model based on the information model of Figure 9-3.
• 9-5. A conceptual information model with doctors and patients as people.
• 9-6. Adding the activity type "walks to room" to the conceptual information model.
• 9-7. A conceptual process model based on the information model of Figure 9-6.
• 9-8. An improved process model based on the information model of Figure 9-6.
• 9-9. Displaying the process owner and activity performers in a conceptual process model.
• 9-10. Adding parallel participation multiplicities for rooms participating both in walks and examinations at the same time.
• 9-11. An information model for the simplified design with the resource counters nmrOfRooms and nmrOfDoctors.
• 9-12. A process design model based on the information design model of Figure 9-11.
• 9-13. An OE class model with resource object types for modeling resource roles and pools.
• 9-14. A process design model based on the information design model of Figure 9-13.
• 9-15. Any resource type R extends the pre-defined object type Resource
• 9-16. A simplified version of the model of Figure 9-13
• 9-17. An OE Class Diagram modeling a single workstation system with resource-constrained processing activities
• 9-18. An information design model for decoupling the allocation of rooms and doctors.
• 9-19. A process design model based on the information design model of Figure 9-18.
• 9-20. Representing the process owner as a Pool and activity performers as Lanes in a process design model.
• 9-21. A conceptual modeling pattern for a sequence of resource-constrained activities
• 9-22. Using RDAS arrows in a conceptual process model.
• 9-23. Displaying the implicit allocate-release steps.
• 9-24. Modeling WorkStation as a resource type
• 9-25. A simplified version of the workstation process model using an RDAS arrow.
• 9-26. A simplified version of the medical department information model with Doctor and Room as resource types
• 9-27. A simplified version of the medical department process model using RDAS arrows.
• 9-28. Doctors perform examinations.
• 9-29. An examination requires two resources: a room and a doctor.
• 9-30. The class Examination implementing the corresponding activity type.
• 9-31. The loading of a truck requires at least one, and can be handled by at most two, wheel loaders.
• 9-32. The class LoadTruck implementing the corresponding activity type.
• 9-33. An examination room may be used by up to 3 examinations at the same time.
• 9-34. The teaching of a course is performed by teachers.
• 10-1. An information design model defining object, event and activity types.
• 10-2. A process design for the Make-and-Deliver-Pizza business process
• 10-3. An enriched process design model
• 10-4. A DPMN process design model for the Make-and-Deliver-Pizza business process.
• 10-5. An AnyLogic process diagram for the Make-and-Deliver-Pizza business process.
• 10-6. A DPMN process design model for the Make-and-Deliver-Pizza business process.
• 10-7. A Simio process diagram for the Make-and-Deliver-Pizza business process.
• 10-8. A conceptual OE class model describing object, event and activity types.
• 10-9. A refined conceptual process model.
• 10-10. An information design model for the Load-Haul-Dump system.
• 10-11. A computationally complete process design for the Load-Haul-Dump business process.
• 10-12. A design model for the HaulRequest event rule.
• 10-13. A design model for the GoToLoadingSite event rule.
• 10-14. A design model for the Load event rule.
• 10-15. A design model for the Haul event rule.
• 10-16. A design model for the Dump event rule.
• 10-17. A design model for the GoBackToLoadingSite event rule.
• 10-18. An AnyLogic process diagram for the Load-Haul-Dump business process.
• 10-19. An Simio process diagram for the Load-Haul-Dump business process.
• Resource-constrained activities involving processing objects are processing activities.
• 11-1. A conceptual OEM class model defining built-in types for conceptual PN modeling
• 11-2. A PN model using the new DPMN modeling elements of PN Node rectangles, Processing Flow arrows and Object-Event Flow arrows
• 11-3. A DPMN-PN process diagram with an Event Scheduling arrow
• 12-1. An OEM class design model defining built-in types for making PN design models
• 12-2. A PN model of a workstation system using PN Node rectangles and PN Flow arrows
• 12-3. A PN model of a workstation system where parts may have to be reworked
• 12-4. A PN model using the new DPMN modeling elements of PN Node rectangles and PN Flow arrows