business process flowchart symbols
There is not anything more confusing in a recruit everyone in the project with many different terms to outline a concept or thing, or everyone who uses a term that encompasses many different concepts or objects.
An example:
I am currently at the bottom of a repository of Business Process Diagram, which is basically a database backend containing diagrams and annexes symbols that communicate business processes graphically in a flowchart (BPMI) Plot: The processes that describe how a employee must perform a task, for example, induce a new employee in the establishment.
The application vendor provides the database schema using the name of 'Encyclopedia'. I call it a "database" when dealing with the Architecture team, other people call it a "dictionary". The first time I heard someone discussion about a dictionary in a meeting, I thought they were discussion about the hash table construction. The labeling becomes more confusing though.
Surrounded by the diagrams that there are five levels of imagery that form a hierarchy are called:
– Form – Agency – Level 3 Sub Process – Level 4 Sub Process – Level 5 Diagrams
According to a group of our project, the diagrams are really level 5 level 6 and the "real" level 5 is a level 4 and the 'real' Level 4 is missing, and have proven this argument right. According to a different group, level 5 is not a level 6 to level 6 would be a sub-process consisting of a level 5. In response the description of the last group of the hierarchy, the first group questioned if anyone could see the irony in the description of the latter group? Just point.
When printing intelligence, Level 5 is known as a Level 2 and Level 4 is now known as Level 1. (???)
What made the initial requirement specifications described? Nobody knows because when I and the new architectural team came on board we found there was no citations decisions made or approved designs.
WHAT WENT WRONG == ==
Two parties at the start met to recruit their taxonimise business processes and freely agreed a set of terms used to talk about their concepts. Shortly in the development of the other party got together and realized that it that had been made as classification of not attending to their business needs and redefine the terms to meet their business process models.
The programmer initial call to all objects surrounded by the application again differently due to the confusion.
The coding has become an effort to interpret what the client requests according to their own flavor of the vernacular.
Our system of corporate knowledge management has become a case management risk.
== How could this have been avoided ==
An initial glossary of terms with their definitions should have been approved and in print for all to see and use. This amounts to a apparent communication of business and providing appropriate programming solutions.
This is probably the worst case of miscommunication that I have experienced and highlights the need for any project to make it a priority to build a dictionary of terms to use and then publish them before the construction of a system starts.
About the Author:
Did you find this article useful? For more useful tips and hints, points to ponder and keep in mind, techniques, and insights pertaining to Internet Business, do please browse for more information at our websites.
http://www.allhottips.com
http://www.bookstoretoday.com
Article Source: ArticlesBase.com – Is it 1 Thing Masquerading as Many or is it Many Equipment Masquerading as 1?






