I will try to use the terminology they are used to
Posted: Thu Jan 23, 2025 5:45 am
For example, if they are used to saying "potential client", I will not write "lead", even though it is the same thing. In the draft version, you can also use words like "платежка" instead of payment order, etc. At this stage, the most important thing is mutual understanding. And people always understand the slang they are accustomed to faster. In the final version and description document, it is already worth using correct terminology and attaching a dictionary of terms (glossary). What is the best notation to describe a business process? I think it is best to use either BPMN or IDEF3.
I will not talk about them in detail here, but the singapore whatsapp number data main difference is that in IDEF3 you can decompose elements, while in BPMN this is not possible. On the other hand, in BPMN you can create about 40-50 elements, i.e. describe a large process in detail. In IDEF3, the permissible number of elements is smaller. Therefore, it will not be possible to depict a large business process here, but you can represent some of the processes as “black boxes”, and then decompose them into subprocesses. What is Business Process Notation Today, it is hard for me to even imagine that I have never used notations.
I use them almost everywhere: when studying the organization of a company's work, when choosing and implementing software systems, when starting work on a new project. Even when writing articles, I periodically first create a notation, and then write the text of the article based on it. But when meeting a new client, I very often have to explain what notations are and why they are needed. Almost always, at first, graphical notation causes some confusion, then, during the discussion, understanding and acceptance of the advantages of such an approach comes. In this article, I decided to sum up these numerous discussions, and collect all the pros, cons, and whys together.
I will not talk about them in detail here, but the singapore whatsapp number data main difference is that in IDEF3 you can decompose elements, while in BPMN this is not possible. On the other hand, in BPMN you can create about 40-50 elements, i.e. describe a large process in detail. In IDEF3, the permissible number of elements is smaller. Therefore, it will not be possible to depict a large business process here, but you can represent some of the processes as “black boxes”, and then decompose them into subprocesses. What is Business Process Notation Today, it is hard for me to even imagine that I have never used notations.
I use them almost everywhere: when studying the organization of a company's work, when choosing and implementing software systems, when starting work on a new project. Even when writing articles, I periodically first create a notation, and then write the text of the article based on it. But when meeting a new client, I very often have to explain what notations are and why they are needed. Almost always, at first, graphical notation causes some confusion, then, during the discussion, understanding and acceptance of the advantages of such an approach comes. In this article, I decided to sum up these numerous discussions, and collect all the pros, cons, and whys together.