Update Too technical / system focussed. Amend, Change Create Too technical / system focussed. Generate, Produce Read Too technical / system focussed. Retrieve, Obtain Delete Too technical / system focussed. Remove Record Too technical / system focussed. Capture, Log, Register Download Too technical / system focussed. Retrieve Transmit Too technical / system focussed. Send Process Too generic, would not reflect the specific Depends on the objective of objectives of the process. the process but could be Handle Assess, Coordinate, Review Manage Maintain Usually indicates a Create, Read, Update, Depends on the objective of Delete (CRUD) transaction that is ICT-specific the process not business. Additionally, if it does indicate CRUD then would be separate business events, so one process would be incorrect. Receive The recipient must do more than just receive Depends on the objective of some information. It should be what the receiver the process does after receiving the information. Input Implies data entry. Why are we entering the Depends on the objective of information? the process The table below lists words which should not be used in process, sub-process or task names. Word Do not use because… and, or Indicates more than one process. to, for, by Implied by the lane it is flowing to. data Too technical. Use information or details. from, of, Should be detailed in the process description documentation. when Events If the event type is known (e.g. if it is a message or timer) then the appropriate trigger type should be displayed for the event. All events are to be named. An event name should: Clearly reflect the type of event (start, end, timer, etc.), for example: Start event: Invoice Received, Application Received (suggests that it is a message)
Update Too technical / system focussed. Amend, Change Create Too technical / system focussed. Generate, Produce Read Too technical / system focussed. Retrieve, Obtain Delete Too technical / system focussed. Remove Record Too technical / system focussed. Capture, Log, Register Download Too technical / system focussed. Retrieve Transmit Too technical / system focussed. Send Process Handle Manage Too generic, would not reflect the specific objectives of the process. Depends on the objective of the process but could be Assess, Coordinate, Review Maintain Usually indicates a Create, Read, Update, Delete (CRUD) transaction that is ICT-specific not business. Additionally, if it does indicate CRUD then would be separate business events, so one process would be incorrect. Depends on the objective of the process Receive The recipient must do more than just receive some information. It should be what the receiver does after receiving the information. Depends on the objective of the process Input Implies data entry. Why are we entering the information? Depends on the objective of the process The table below lists words which should not be used in process, sub-process or task names. Word Do not use because… and, or Indicates more than one process. to, for, by Implied by the lane it is flowing to. data Too technical. Use information or details. from, of, when Should be detailed in the process description documentation. Events If the event type is known (e.g. if it is a message or timer) then the appropriate trigger type should be displayed for the event. All events are to be named. An event name should: Clearly reflect the type of event (start, end, timer, etc.), for example: Start event: Invoice Received, Application Received (suggests that it is a message)