Are there Naming Conventions in Business Process Modeling?
I'm wondering if there are naming conventions in business process modeling. When I look at the sample processes provided on the site, I see nouns like "Vacation Leave" or "Accounts Payable" or "Help Desk".
Isn't a process a set of logically related tasks (possibly with events) delimited by a start and end node. Tasks are something you do, so they should be described using verbs, like "Fill form XYZ", "Obtain signature", etc. Folks, I have to admit, I come from IT, where methods of an object ("tasks" of the object) are commonly named like "GetDocumentByIdentifier", "SaveFile", you get the idea. Now you get in some difficulty when you try to name the process. The above mentioned samples like "Vacation Leave" or Accounts Payable" or Help Desk" are nouns and as such entities in my world of thinking, thus they are rather data, or objects.
Please point me to such rules, if there are any.
Currently, until I get the hint, I will name the proces, the logically connected tasks, in the gerund form, like "Organizational Performance Reporting", "Managing Accounts Payable", "Performing Help Desk Functions", "Obtaining Vacation Leave".