Analysis BPM

The Analysis language is the base language of the PowerDesigner BPM, an implementation neutral notation for analyzing your systems and decomposing your processes to any level of detail.

Having developed your model, you can select Tools > Generate Business Process Model to generate a model targeting another process language.

• Process Hierarchy Diagrams (Analysis)
  A process hierarchy diagram (or functional decomposition diagram) provides a graphical view of the functions of a system and helps you decompose them into a tree of sub-processes.
• Business Process Diagrams (Analysis)
  A business process diagram (or process flow diagram) provides a graphical view of the control flow (the sequence of execution) or data flow (the exchange of data) between processes at any level in your system.
• Processes (BPM)
  A process is a manual or automated action, such as "Process order", or "Send a mail". Processes are the core object in the BPM. Processes can be atomic (without subprocesses) or decomposed/composite (containing subprocesses). Each decomposed process contains its own business process diagram, which shows its subprocesses as part of its control flow.
• Organization Units ( BPM)
  An organization unit can represent a company, a system, a service, an organization, a user or a role, which is responsible for a process. It can also be a business partner who uses high level processes.
• Starts and Ends (BPM )
  A start is a starting point of the flow represented in the diagram, and an end is a termination point of the flow.
• Decisions (BPM )
  A decision specifies which path to take, when several paths are possible. A decision can have one or more input flows and one or more output flows, each labeled with a distinct guard condition, which must be satisfied for its associated flow to execute some action. Your guard conditions should avoid ambiguity by not overlapping, yet should also cover all possibilities in order to avoid process freeze.
• Synchronizations (BPM )
  A synchronization enables the splitting or synchronization of control between two or more concurrent actions.
• Flows (BPM )
  A flow is a route the control flow takes between objects (potentially with the exchange of data). The routing of the control flow is made using guard conditions defined on flows. If the condition is true, the control is passed to the next object.
• Message Formats (BPM)
  A message format can be an XML document or a list of parameters, which defines the format of the data exchanged between processes.
• Data (BPM)
  A data object is a piece of information exchanged, at a high conceptual level, between processes using flows or between processes and resources using resource flows.
• Resources (BPM)
  A resource is a data store. It can be a database, a document, a data, or a component to which a process have access. You access the data stored in a resource using a resource flow.