Pokaż stronęPoprzednie wersjeOdnośnikiCopy this pageDo góry Indeks Indeks wszystkich dostępnych stron pogrupowany według katalogów. en concept rule Align process and activities instances Model alternative paths with splitting and merging gateways Don't use timer event to depict expected activity duration Don't use mixed gateways Error event may be used to model business exceptions Check subprocess result on exit Use collapsed subprocesses Use conditional event to model collaboration Attach a sequence flow to any side of the activity box A subprocess and a control branch may be used as an alternative to the attached event Diagram should fit one page Activities performed in different rhytms belong to different processes Disconnected sequence flows not allowed Don't save on gateways Don't use "flows with diamonds" Don't use converging inclusive gateways without a paired exclusive gateway Don't overuse black box pools Don't play with elements size Avoid double negations End event name should answer the question "how did the case end?" Model processes end-to-end Use event gateways with caution Make parallel merge explicit Make parallel split explicit Use a dedicated process to catch the event initiated by external participant Model handover by a sequence flow Show the happy path Arrange diagrams horizontally Use task plus gateway to model human-made decisions Intermediate event name should answer the question "what happened?" Keep activities names short Avoid micromanagement Avoid sequence flows overlapping Don't overuse terminate event Name process as a service Don't place more than one expanded pool at one diagram Make process start and end explicit Start event name should answer the question "what happened?" Rules of "Good" BPMN Follow structured modeling rules Use the same naming templates for processes and subprocesses Subprocess must be started by none event Task name should answer the question "what should we do?" Time should flow left to right Use default flow only in executable models Main process flow in a properly organized diagram tends to be V-shaped Use a subprocess with a terminate or error error event to model veto power Model work by activity term tool wiki Welcome to BPMNbox ru tag wiki ostatnio zmienione: 2025-04-01 11:25(edycja zewnętrzna)