A
Abstract task: A task where no specific type of task is defined.
Activity Cost Worksheet: A process-oriented approach A to analyze the various costs of a set of activities that are listed on the vertical axis and data about outputs, costs, times and problems are described for each activity.
Actor(s): An actor is a term used in a Bonita Studio process design to refer to the end user(s) of a process. It is the Human end user that operates the form in User XP.
Add: Found in Application tab. Function button to create a new form
And gate: All inputs must arrive at the Gate before Process passes through. If there are multiple outputs, all will fire (unless Conditions are defined in Transitions).
Ad Hoc Workflow Systems: Workflow systems that wait on users to indicate what should happen next. An insurance system might pull up documents for an underwriter only on request. Compare with Administrative and Transaction or Production Workflow Systems.
API: Application Programming Interface. It serves as an interface between different software programs and enables their interaction. (API) is a set of definitions of the ways one piece of computer software communicates with another, a method of achieving abstraction, usually (but not necessarily) between lower-level and higher-level software.
Application: Tabs for Form creator and transient data.
Artifact (R&D): Bonita artifacts are elements used in BOS. – need to export all / import all artifacts during upgrade migration.
Artifact (BPMN): BPMN 2.0: “Extra information in a process which does not affect the Process execution”. e.g. Text annotation.
Automatic Task: Task processed and launched by Bonita Execution Engine without the need for human intervention (see Human task).
Asynchronous Process: One activity sends a message to another, but does not wait until it gets a response.
Atomic Activity: An activity that cannot be subdivided. An activity that consists of a single step or action.
B
Balanced scorecard: A movement, method and technique for aligning measures from an organization’s strategic goals to specific process measures.
BAM: Business Activity Monitoring. Pulls data from a data base to show reports.
.bar: Bonita Archive Package containing all processes in the diagram and all their dependencies. When a BAR is deployed, only the process with the same name as the BAR file will be deployed.
A process is saved in the .bar format as a compressed file. It can be imported into or exported from the Studio.
Batch processing: In either human or computer processes, a step where lots of items are accumulated and then processed together. In contrast to continuous processing where items are processes as soon as possible.
Benchmarks: As used in business process redesign, data about process measures obtained for specific types of processes. Many companies seek benchmark data on processes they seek to redesign in order to determine how well other companies manage the process
Bonita Execution Engine: Processes, powered by Runtime engine, designed and deployed with Bonita Open Solution.
Batch processing: In human or computer processes, a step where lots of items are accumulated first, then processed together, is called a batch. In contrast to continuous processing where items are processes as soon as possible.
Bonita Studio: Bonita Studio is one component of Bonita Open Solution based on Eclipse technology. Bonita Studio is the graphic user interface (GUI) where processes are designed.
BonitaSoft: A company that develops the open source Bonita Open Solution and provides training, consulting, support and expert services for this solution.
Bonitasoft User Experience: Provides a user and administration portal designed for managing and deploying running processes, cases and reports.
Bonita: Abbreviated term for technology underlying Bonita Open Solution; also refers to Bonita v.4, a precursor to Bonita Open Solution.
Bonita Open Solution: An integrated business process management solution, comprises Bonita Studio, Bonita User Experience an Bonita Execution Engine.
BPEL: Business Process Execution Language BPMN language is used to execute a process Processes export/import information using a web service interface. (see web application).
BPM System: A management practice that provides for governance of a business's process environment toward the goal of improving agility and operational performance.
BPMN: Business Process Management Notation.
A standardized graphical representation for specifying and designing business processes based on flowchart modeling technique.
BPMN 2.0: BPMN2 is an open source component of the Model Development Tools (MDT) subproject to provide a metamodel implementation based on the forthcoming Business Process Model and Notation (BPMN) 2.0 OMG specifications.
Business Analytics: Aggregated information on business processes that enables managers to analyze process trends, view performance metrics, and respond to organizational change.
Business Intelligence (BI): Software systems and tools that seek to extract useful patterns or conclusions from masses of data.
Business Process Automation: Processes can be completely automated by the use of computer systems and software.
Business Process Change Cycle: A general description of the lifecycle of business processes.
Business Process Design or Redesign: Making major changes in an existing process, or creating a new process.
Business Process Improvement (BPI): Business process improvement focuses on incrementally improving existing processes. BPI is usually narrowly focused and repeated over and over again during the life of each process.
Business Process Management Initiative (BPMI): Consortium of business process modeling tools vendors and user companies that are working together to develop an XML-based business process language (BPMI), a notation for the language (BPMN) and a query language (BPQL).
Business Process Modeling Tool: A software tool that lets managers or analysts create business process diagrams.
Business Process Outsourcing: Many companies outsource business processes to other companies to manage and execute.
Business Process Reengineering (BPR): Starting from a blank sheet and completely reconceptualizing major business processes and using information technology in order to obtain breakthrough improvements in performance.
Business Process Tools: Worksheets, rules-of-thumb and software tools used to help in business process change.
Business Rules: A statement describing a business policy or decision procedure.
c
Case: Single instance of a Process
CIM: Movement, techniques and tools for integrating manufacturing processes with computers and Software.
COBOL: The computer language in which the majority of mainframe applications have been written.
Collaborative BPM: BPM created using a collaborative business process language (usually ebXML). It is particularly suitable to describe the collaborations between partners that are all considered at the same level.
Collaborative Modeling: Bonita Studio allows you to create workspaces on a remote server so they can be shared. Team members can work on the same Process to develop a complete design.
Collaborative Tools: Tools like discussion forums, dynamic workspaces, and message boards that are provided within the BPM suite framework and are designed to remove intra- and inter-departmental communication barriers.
Competitive Advantage: Occurs when one company can make more profits selling its products or services than its competitors.
Composite Process Application: Using a BPM suite platform to solve a particular business problem, such as complying with regulatory standards or managing a company's assets.
Computer Aided Software Engineering (CASE): Software methods and tools designed to generate code from models.
Condition: An expression in Groovy script to define the behavior of a transition at a Gateway.
Connector: A Connector is a plug-in which links Bonitasoft process tasks to external applications, data bases, etc. It needs to have settings configured to work.
Connector repository: A workspace where the Connectors are stored and compiled.
Connector wizard: A Connector wizard is an interface containing a step-by-step process to create connections between tasks in a process and external applications.
Context: Contexts are useful to handle different “environments/status/contexts” of a process; for example, to test a Process in a test environment before deploying it.
By defining a Test Context and a Production Context and associating the appropriate variables to each Context, there is no need to change values in Connectors, Forms, or other places where variables differ in different environments.
A Context is a set of key-value pairings.Context keys (which will be replaced by a predefined value) can be used as input in most text variables. Before deploying or exporting a Process, select which predefined Context to use. When the Process is Run, the keys are replaced by the appropriate values.
Context palette: Tools surrounding a task which appear when selected
Core Business Process: Core processes are the processes that rely on the unique knowledge and skills of the owner and that contribute to the owner's competitive advantage. Contrast with subsidiary business processes.
Cost Leadership: A competitive strategy that emphasizes offering the product or service at the cheapest price. This can be done by creating the most efficient manufacturing price, by economies of scale, or by control of suppliers and channels.
COULD Process: Also sometimes Can-Be Process. Description of one of two or more alternative redesigns that are being considered.
CRM: A number of packaged or tailored applications or tools designed to help with sales, tracking customers, or managing information gained from customer interactions.
Curly brackets ${ }: Curly brackets. Delimiter for a Groovy expression { Write a script inside of them}.
Customer-Oriented e-Business Applications: A generic way of talking about business processes and Internet applications that use Web sites or portal to allow customers to access the company over the Internet for information or commerce.
D
Dashboard: A user interface that resembles the dashboard of an automobile. Dashboards contain small graphs, charts, and gauges that provide data on key information within an organization.
Data: Information provided as the process case is run.
Database: A collection of records stored in a computer in a systematic way, such that a computer program
called a database management system (DBMS) can consult it to answer questions.
Data objects: Data Objects show the reader which data is required or produced in an activity.
Data Management Editor: Writes Groovy scripts easily with the Data Management Editor - development assistance and testing capabilities.
Data Type: The type of information data used to create a new variable.
Data Warehouse: A record of an enterprise's past transactional and operational information, stored in a database.
Decision Point or Diamond: A diamond or hexagonal figure used on process diagrams to show when a decision leads to a branching in the flow of information, control or materials.
Default flow: The default Transition that is used, when all other Transition conditions evaluate to “false”.
Default value: Predefined value used e.g. “Now” for the present time and date to be used.
Delegee: Assigned to a Step when the designated User is unavailable
Dependencies: Java libraries needed for process to run: connectors, validators, third-party libraries, my scripts.
Details panel: Panel at the lower right of Bonita Studio, which contains multiple sets of tabs to configure details for design and execution of Process elements.
Diagram: A graphical representation of one or more processes. (Designed on the Whiteboard).
DMAIC (Define, Measure, Analyze, Improve, Control): An acronym used by Six Sigma practitioners to remind them of the steps in a Six Sigma improvement project.
Document Management: A system for storing and securing electronic documents, images, and other files within an organization.
E
Edit Expression: Open editor to create or edit a Groovy script.
Electronic Data Interchange (EDI): A pre-Internet system for exchanging data between organizations. EDI requires that organizations standardize terms and invest heavily in computers and the maintenance of the EDI software.
End event: Elements in the Process design that are neither Tasks nor Gateways; e.g. Start, stop, intermediate action.
Expression: Script written in Groovy code.
Extension: A list of items that include: community contributions, jar management, BOS artifacts.
Enterprise Alignment: (Enterprise Alignment Cycle). Enterprise Alignment refers to the ongoing process every company goes through to keep the elements of the organization aligned with the organization's strategy and goals.
Enterprise Application: As used by software designers, an enterprise system is a major software application that is designed to be used or accessed by many different departments and is usually maintained at the corporate level.
ERP-Driven Design: When a company elects to use an ERP application, it is getting an application that already makes assumptions about the inputs and outputs it will receive.
Exceptions Processing: To adjust and repair transactions that were unable to be completed. Without automation, organizations find that exceptions processing is one of the more costly and time-
consuming efforts within their business.
F
Feedback: Refers to passing information from one person to another person that performed some task earlier, or from one process or system or another process or system that has already occurred.
Filter: Pre-selects certain data which is sent from one process to another or from one step to another.
Form Builder: The Form Builder is used to create and customize forms which are deployed via a standalone Web based application.
Form template: A model for creating forms.
Function-Process Matrix: A diagram that lists functions or departments on the horizontal axis and value chains or business processes on the horizontal axis and shows which functions are involved in which processes.
G
Gaps and Disconnects Patterns: A process redesign pattern that focuses on checking the handoffs between departments and functional groups in order to assure that flows across departmental lines are smooth and effective.
Gateway: Branch point in the Process flow represented as a diamond shape. A gateway controls the process flow.
Goal Hierarchy: A hierarchical tree that shows how organizational goals, pictured at the top or on the left are subdivided into more specific goals for value chains, processes, sub-processes and ultimately to
activity goals.
Group: Groups consisting of individual users, defined by Admin. A Group is represented with a rounded-corner rectangle and dashed lines. The Group is used to group different activities but does not affect the flow in the diagram.
Groovyscript: Groovy is an object-oriented programming language for the Java platform. It can be used as a scripting language to write expressions on conditions, on forms etc. Groovy uses a Java-like bracket syntax.
H
Human task: A user task that requires a human interaction to complete it.
I
Inclusive gate: XOR join, AND split; the first input to arrive will allow the Process to pass through the Gate if there are multiple outputs, all will fire (unless Conditions are defined on Transitions)
Initiator: An actor who creates the first step in a process. (by default).
Instance: Single case of a Process.
Instantiator: Creates an executable copy of a model.
Integrator (Java): An integrator is the “middleman” between the software editor and the customer. They are responsible for training the client that buys a BOS SP license. (They will have had to be previously trained by Bonitasoft).
Internal-Oriented e-Business Applications: A generic way of talking about business processes and Internet applications that use the Internet to allow companies to link with their employees or to link their internal applications to share information or data.
Iterative: Copying/repeating of a task or object in a process.
J
J2EE (Java 2 Platform, Enterprise Edition): A software programming platform from Sun for developing and running distributed enterprise applications, based largely on modular components running on an application server.
JAR files: Java Archive file (compressed). Developers use it to distribute a Java application or library. Collection of Java class files, text, images.
jBPM: A workflow engine written in Java. Market competition for BOS.
Join checker: When a multi-instantiator creates multiple parallel tasks, the join checker checks whether a number of a tasks in progress have finished or not…
Junction, Junction Bar: On a process diagram a way of showing that one flow (output) is divided and sent into multiple activities, or to show that multiple flows must all be complete before the activity immediately after the bar can occur.
K
KANO Analysis: An approach to defining customer satisfaction that divides outputs , service or product features of outputs into (1) basic requirements (2) satisfiers and (3) delighters.
Knowledge Management (KM): Key Performance Indicator. Personalized performance metrics and benchmarks that drive the financial and operational success of the company.
KPI: Key Performance Indicator. Personalized performance metrics and benchmarks that drive the financial and operational success of the company.
L
Lane: A sub division of a pool
Lean Manufacturing: An approach to designing and managing production processes that emphasizes minimal inventory and just-in-time delivery, among other things, to improve the efficiency of a manufacturing process.
Levels of Analysis: For purposes of analysis, we divide a company into three levels. (1) the Organization and its
environment, (2) the Value chains, processes and sub-processes, and (3) Activities.
Library: Jar files
Log: Studio log
Look n feel: A tool to customize the appearance of the web application.
Loop: Transitions that continue circling sequentially between gates until a particular condition is met.
M
Manager: Organizational lead of a team of Users
Measures Hierarchy: A hierarchical tree that shows how organizational measures, pictured at the top or on the left are subdivided into more specific measures for value chains, processes, sub-processes and ultimately to activity goals.
Menu Bar: Menu bar with roll down menus. Located at the top of Bonita Studio, above the Task bar.
Message flow: A Message Flow is represented with a dashed line, an open circle at the start, and an open arrowhead at the end. It tells us what messages flow across organizational boundaries (i.e., between pools). A message flow can never be used to connect activities or events within the same pool.
Middleware: Middleware is computer software that connects software components or some people and their applications.
Model: A formal set of relationships that can be manipulated to test assumptions.
P
Process Developer/ Designer: Uses Bonita Studio to design a process, including the Process Diagram, Connectors, and end user Forms. BPM component that allows a trained user to analyze and model a process, step by step, as well as assign logic to it.
Process Engine: BPM component that executes the actual flow of a modeled process, assigning manual activities to people and automated activities to applications as the process unfolds.
Process Instance: A process diagram describes a generic sequence of events. An instance describes an actual process which includes data, real actions, and specific decisions.
Process Management: Most managers or supervisors are responsible for specific processes or activities. They are responsible for organizing the process or activity and securing the resources need to execute it, and they are responsible for measuring the results of the activity and providing rewards or corrective feedback when necessary.
Process Measures or Process Output Measures: Measures of whether a process or activity is achieving its goals.
Properties: The parameters of an object which can be modified.
R
Receive Task: Waits to receives a Message when the Task is reached in the Process; same as Receive Message.
Reporting: Print compiled reports of activity in steps from User XP Admin. An exported file for KPI which shows (.rpt)
Repository: A repository can be local or remote on a server. It can be a shared workspace with others, accessed by SVN. (see collaborative modeling).
Resources: Collection of data used in Process Simulation.
REST: Representational State Transfer. An application is installed on a server and communicates with the Bonitasoft engine via http protocol.
Restore point: Create a Restore Point in a process that will allow you to restore a process to this specific previous state. In the Menu bar, go to Repository -> Manage restore point -> create restore point.
Role: The title/position/job etc of an individual user in an Actor selector, as defined in User Experience.
Rules Engine: A BPM component that manages the flow of information and activities within a process according to the formulas and rules assigned to it.
Rummler-Brache Methodology: Geary Rummler and Alan Brache defined a comprehensive approach to organizing companies around processes, managing and measuring processes and redefining processes in their 1990 book Improving Processes.
Run: Make the process work through the steps in a web interface. (See Execution)
Runtime: The stage at which the process is run. (See Execution)
S
Scorecards： Cross-functional analytic applications that define, measure, and analyze a business strategy according to Key Performance Indicators (KPIs).
Script Task： Sends a message; same as Send Message event
Send Task： Sends a message; same as Send Message event.
Sequence flow: A Sequence Flow is represented with a solid line and arrowhead and shows in which order the activities will be performed. The sequence flow may also have a symbol at its start, a small diamond indicates one of a number of conditional flows from an activity, while a diagonal slash indicates the default flow from a decision or activity with conditional flows.
Service Task: An Automatic Task that calls a Web service
SHOULD process: Also TO-BE process. A description or diagram of the process that the redesign team proposes to create.
Silo Thinking: It is a term of “derision” that suggests that each department in an organization chart is a silo, standing alone, and not interacting with any of the other departmental silos.
Simple Object Access Protocol (SOAP): An Internet protocol that is used to move XML files around the Internet.
SIPOC (Supplier, Input, Process, Output, Customer): An acronym used by Six Sigma practitioners to remind them of how to set up a high-level overview of a process.
Simulation: A technique that uses a model to make predictions about a system or process. Process simulation tools normally assign values to activities and then a number of cases to see how the business process will respond.
Six Sigma: A movement, method and set of techniques focused on improving business processes. Relies heavily on statistical techniques to measure success.
Social BPM: Social BPM is the recognition that smart knowledge workers can innovate within a structured process framework to create an outcome that is better than trying to follow a pre-defined process alone.
Software Engineering: A movement, methods, and techniques aimed at making software development more systematic.
Standard or Normal Bell-Shaped Curve: A statistical tool for describing variations from a mean. It shows that most deviation is slight and that extreme variations are few and infrequent.
Start event: Acts as a trigger for the process; indicated by a single narrow border; and can only be Catch, so is shown with an open (outline) icon.
Step: In Bonita User Experience. A task in a Process Case becomes a Step to be completed by a User
Strategic Positioning: Defining a position in which an organization can achieve dominance or at least success.
Subprocesses: Process analysis necessarily occurs on levels. A high-level process diagram shows major processes. Each major process is typically divided into sub-processes which are represented on separate process diagrams. Those processes, in turn, may be sub-divided into sub-processes.
Subprocess Task: Element that represents a subprocess in process design.
Subscription Pack: Adds support and extra features to help collaboration, accelerate processing and increase security.
Super-system Diagram: An organization diagram that represents the company as a blank box and focuses on the elements like suppliers and customers that make inputs and outputs to the company.
Supply Chain Council (SCC): International consortium of companies interested in improving organizational supply chains.
Supply Chain Management (SCM): A vague term describing any of a number of packaged or tailored applications or tools designed to help with the development or execution of supply chain systems or with managing information gained from supply chain interactions.
Supplier-Oriented e-Business Applications: A generic way of talking about business processes and Internet applications that use the Internet to allow companies to link with business partners or suppliers to coordinate their efforts.
Synchronize: Repositories on local and remote servers are synchrnised with Bonita Studio.
Synchronous Process: In a synchronous process, one activity sends a message to another and then waits for a response before proceeding.
System Administrator: The “Superuser” who gives rights to users, creates new users with passwords.
Systems Dynamics: This is a specific approach to modeling systems that emphasizes the feedback loops that tie sub- systems together and explain the dynamic changes that occur over the course of time.
Swim lane (lane): A row on a business process diagram. A way of indicating who is responsible for a given process or
activity.
T
Task: An activity; an action in the Process, specific work performed when a process is deployed and running, a Task in Bonita Studio becomes a Step in Bonita User Experience.
Task bar: Menu bar with task icons. Located at the top of Bonita Studio, below the Menu bar. Also known as the cool bar.
Team member: Organizational subordinates of a manager (All Users assigned to a manager are Team members of that Manager)
Three Levels of Organization (Performance Framework): A Rummler-Brache concept. There are 3 primary levels of business process analysis: the organizational level, the process level, and the activity or performance level (which Improving Performance called the Job Level).
Total Quality Management (TQM): A movement, an industrial discipline, and a set of techniques for improving the quality of processes. TQM emphasizes constant measures and statistical techniques to help improve and then maintain the output quality of processes.
Throwing: Events in a process are thrown. Throwing sends a message.
Transaction or Production Workflow Systems: A type of workflow system that moves documents or information from one terminal to another following a workflow model. Compare with Ad Hoc and Administrative Workflow Systems.
Transitioning to a New Process:The transition period occurs after managers and employees have been trained in the new process, when they actually start using it.
U
Unified Modeling Language (UML): An international, standard notation for modeling software systems. The UML specification supports several different types of diagrams, including the Activity Diagram, which is used to model business processes and workflow diagrams. UML was created and is maintained by the OMG.
Universal Description, Discovery and Integration (UDDI): A Web protocol, based on the WSDL language, that allows one Web system to locate others and determine what format messages to that system must take.
Use Case Diagram: One type of UML diagram. Often used by software developers to define the software requirements for a system. Use case diagrams focus on scenarios that describe how users use the application.
User: Defined in User Experience. Individuals with access to Steps, cases, etc, as defined in User Experience.
User/End user: Any individual who executes a deployed BOS process in User XP or in standalone web forms.
User Experience: Graphic interface used to manage and pilot different tasks corresponding to different processes in Studio.
User Role: Access privileges are assigned according to User Role (defaults: basic User and Admin)
V
Value Added Activity: A process or activity that adds value to a product or service. Value is judged by the customer, who can be the customer of the company, or an internal customer who receives the output of the process or activity.
Value-Added Analysis: A process redesign pattern that focuses on eliminating activities that don't add value or at least enable value-added activities.
Value Chain: A very large-scale business process that is initiated by a customer request, or by the decision of the company to enter a new line of business, and results in the delivery of a process or service to a customer
Value-Enabling Activities: Activities or processes that do not, in themselves, meet the criteria of value adding activities, but which must be performed in order to make it possible to perform value adding activities. The
activities involved in the development of most software applications are value-enabling activities.
Variable: The container for data – used to define fields in a form.
Vertical Alignment: Focuses on aligning strategic goals and measures from value chains down to activities. Sometimes includes management systems that align each manager's goals and evaluation criteria from
organizational strategies to supervisor's goals.
View form: Visual preview of the form before deployment.
View pageflow: Used to define read-only Forms
W
Web application/Web app: The Web package dedicated to a process that defines its forms and look-n-feel
Whiteboard: The space in Bonita Studio where the process is drawn graphically, as on a whiteboard. Contains Pools (Processes) and Lanes.
Web Apps: Interface used to design forms for user interaction and process launching
Widget: Tool in Form Builder (Application) used to create forms with preset fields.
Workflow: Generic term for a process or for the movement of information or material from one activity (worksite) to another.
Workflow Model: Another name for a process diagram. Often includes both a diagram and rules that define the flow of information from one activity to the next.
Workflow Reference Model: Model created by the Workflow Management Coalition to define a workflow management system and to identify the most important system interfaces. Other WfMC standards make reference to this model.
Workflow System or Engine: A software tool or program that helps analysts define a process and the rules governing process decisions, and then manages the actual distribution of information related to specific instances or cases to terminals and databases. WSFL.
Work Portal： BPM suite component that gives users a productive workspace for managing tasks, content, forms, documents, notifications, and reminders.
Workspace： Place to store BOS artifacts
X
XOR gate： the first input to arrive will allow the Process to pass through the Gate. If there are multiple outputs, only one will fire.
XML (eXtended Markup Language)： An Internet protocol defined by the W3C. A file format that includes within a file both data and rules for how the data is to be interpreted. Using XML, one can create XML languages – in effect, sets of terms that companies agree to use in a specific way in order to facilitate the exchange of data.
XML-Based Process Definition Language (XPDL)： The Workflow Management Collation (WfMC) created this standard language to describe how workflow tools can communicate information about business processes with each other over the Internet.
XML Business Process Language： A computing language in which one can describe business processes and their relationships. These languages use XML to pass messages.
XPDL: XPDL: Process Definition Language (xml) A language used to interchange business process definitions between BPM and other workflow products.
XSLT (Extensible Stylesheet Language Transformations): Extensible Stylesheet Language Transformations (XSLT) is an XML-based language used for the transformation of XML documents.
