Scope: managed applications, ordinary applications.
Example of business process appearance:
1. General recommendations
1.1 Business processes are drawn from top to bottom . Another orientation (for example, from left to right) is allowed if it provides a better representation of the business process.
1.2 The standard grid is used with size of 20 points, and it is drawn with lines.
1.3 Bold and colored fonts are not used.
1.4 The number of connector bends must be kept to a minimum. If you can connect two points by bending a connector once, try to do that by adjusting the size and location of points.
1.5 When you place decorations and route points, it is recommended that you use a one-cell indent from the left and top of the flowchart.
1.6Keep the width of route points equal to an even number of cells. It is necessary for connectors to converge without extra bends. Try to keep size of points and decorations equal to proportions of a matchbox, for example, 3x6 cells. Avoid vertically or horizontally extended cells as they make it more difficult to see flowcharts properly.
1.7 Center the text in route points and decorations by default, except for comments. Align them left as a standard text.
1.8 It is recommended that you place route points and decorations so that they do not cross print sheet boundaries (menu Graphical schema - Page view mode).
2. Recommendations on appearence of separate items
2.1Set size of the Start and End points to 2x2 cells. Do not assign a description to them. The number of start and end points is unlimited. It is defined based on the business process logic. It is recommended that you use a two-cell indent from the start or end point to another business process point:
2.2 Set size of the Action, Automatic data processor, and Nested business process points according to the length of the text displayed in these points. The text must contain short instructions that answer the question "What needed to be done" (for example, "Issue invoice" rather than "Issue of invoice"). To the left of such point, place decorations that describe source or incoming data required to perform actions in this point. To the right of such point, place decorations that describe the result or outgoing data obtained upon performing actions in this point.
2.3 Place pictures of incoming documents, based on which actions in route points are performed, 2 cells to the left of the point. Connect them with a dotted-line arrow. Place outgoing documents resulting from actions in the route point two cells to the right of the point. Connect them with a dotted-line arrow. To draw a document, use the Document shape:
Proportions of a decoration that illustrates a document must be close to A4 (for example, 4x5 or 3x4 cells of the standard grid).
2.4 Comments to route points are to be placed two cells to the left of the route point if they relate to an incoming document or to the right of the route point if they relate to an outgoing document. Use the "vertical brackets" or "horizontal brackets" shape to add a comment. Connect it with the left or right edge of a route point with a dotted line without an arrow:
2.5 Condition points include a short text of a question, which ends with a question mark. Formulate questions so that they can be answered only with Yes or No (for example, Is the invoice available?, Is shipment allowed?, or ОК?). *Make condition points as compact as possible but not at the expense of visibility. This is because condition points are transition points rather than action points. Therefore, they are secondary for business process participants. The total length of condition point connectors (both incoming and outgoing) must be not less than two cells. It is necessary for Yes and No to be read properly, for example: