Events Modeling
Good Practices
Start and End Events
•It is recommended to always use the start and end events in each process and subprocess to represent its beginning and end.
Name
•The start and end events must not be tagged when they are unique. It is very common to name them as "Start of the process" and "End of the process" but this is redundant and unnecessary.
•Events must be identified when multiple start or end events are used.
•The start events must have labels indicating the condition or fact that triggers the start of the process.
•The end events must be named indicating the final state of the process. In general the name must use a noun, which is the business object, along with a verb in the past tense. For example: "Request approved", "Request canceled", etc.
•It is recommended to identify the final successful and unsuccessful states.
•Terminal end events must only be used when strictly necessary. They are used to model situations where multiple alternative paths are enabled and only the completion of one of them is required to complete the entire process.
