The arrow does not go anywhere
Posted: Thu Jan 23, 2025 8:47 am
It, as an output device, outputs a certain result (material or information). And here, too, we must concentrate on the question of what we output, and not be interested in where the exit is, or study the moments before and after the exit. That is, output is the correct and accurate word. The next mistake is the translation of the name of the Control arrow, which for some reason everyone calls a control or management arrow. I suppose that this is just a mistake, which, by the way, I also made in my first review of IDEF0.
But even when I used the name from the publications afghanistan whatsapp number data I read earlier, I couldn’t figure out why this control? Control is too general and imprecise a concept. By the way, this question became my first step towards studying English-language documentation. And then everything fell into place. The word Control is translated as control. And Control arrows are what controls, what limits the function. It is wrong to say control arrows. After all, they don’t actually control anything. Usually, a person controls something, sometimes a mechanism, in the animal world, the leader of the pack.
But it is always someone or something. And if we talk about control, we are talking about restrictions. That is, Control arrows show what restrictions we have (this becomes clear from the text of the standard itself). For example, for the function "create a program" we can have a requirement for the speed of work as a limitation. However, it is somewhat absurd to call the speed of work a control. This parameter does not control anything, but it limits our choice. This conceptual point migrates from translation to translation, resulting in confusion and making it more difficult for people to study and understand IDEF0 diagrams.
But even when I used the name from the publications afghanistan whatsapp number data I read earlier, I couldn’t figure out why this control? Control is too general and imprecise a concept. By the way, this question became my first step towards studying English-language documentation. And then everything fell into place. The word Control is translated as control. And Control arrows are what controls, what limits the function. It is wrong to say control arrows. After all, they don’t actually control anything. Usually, a person controls something, sometimes a mechanism, in the animal world, the leader of the pack.
But it is always someone or something. And if we talk about control, we are talking about restrictions. That is, Control arrows show what restrictions we have (this becomes clear from the text of the standard itself). For example, for the function "create a program" we can have a requirement for the speed of work as a limitation. However, it is somewhat absurd to call the speed of work a control. This parameter does not control anything, but it limits our choice. This conceptual point migrates from translation to translation, resulting in confusion and making it more difficult for people to study and understand IDEF0 diagrams.