Business Process Model - Revision history

User at 12:28, 5 January 2023

2023-01-05T12:28:21Z

User at 21:02, 20 September 2022

2022-09-20T21:02:44Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T14:17:58Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 16:44, 5 November 2019

2019-11-05T16:44:14Z

User at 16:43, 5 November 2019

2019-11-05T16:43:35Z

User: Business Process Model (BPM) refers to a structural representation, description or diagram, which defines a specified flow of activities in a particular business or organizational unit.

2018-12-10T17:53:51Z

Business Process Model (BPM) refers to a structural representation, description or diagram, which defines a specified flow of activities in a particular business or organizational unit.

User: Created page with "'''Content Coming Soon'''"

2018-12-07T01:50:38Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

@@ Line 1: / Line 1: @@
 The term '''Business Process Model (BPM)''' is the noun form of [[Business Process Modeling]], and refers to a structural representation, description, or diagram, which defines a specified flow of activities in a particular business or organizational unit. It is a representation - usually computer-generated and diagrammatic, but can be a low-tech whiteboard or flipchart and marker pens and sticky notes - of a process within a business. Two models are usually produced: an 'as is' and a 'to be'. The process(es) featured in a Business Process Model can be very simple or highly complex, and will typically involve different departments working (hopefully) together while the provision or creation of a product or service flows through different stages and decision points in an organization on its way to the customer. A Business Process Model for a large process can be comprised of other smaller modeled processes which contribute to the whole. In theory, an entire huge business can be modeled, although for the modeling to be useful and meaningful to people it is normally built in sections, each representing a self-contained process alongside potential scores, hundreds or even thousands of others, all inter-relating, smoothly, efficiently and enjoyably. (The 'enjoyable' part is not a technical necessity, but is actually important for any model to translate from theory into sustainable practice).<ref>What is a Business Process Model? [http://www.businessballs.com/business-process-modelling.htm]</ref>
-'''Elements of a Business Process Model'''<ref>Elements of a Business Process Model [http://www.bridging-the-gap.com/how-to-analyze-a-business-process/]</ref><br />
+== Elements of a Business Process Model ==
-A Business Process Model contains the following elements:
-*Statement of Scope – It’s very easy for one process to turn into several. Naming your process with a clear name in the Verb Noun syntax and writing a starts with / ends when statement will help you clearly identify the scope of the process.
+A Business Process Model contains the following elements:<ref>[http://www.bridging-the-gap.com/how-to-analyze-a-business-process/ Elements of a Business Process Model
 *Desired Outcome – It’s easy for a process to get ingrained in “how we do it here” but lose its value over time.  As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
 *Process Flow or Activity Descriptions – This is the meat of the process model. It’s essentially a list of the steps completed by people in certain roles. This is the primary or most common path through the business process.
@@ Line 15: / Line 27: @@
 ===See Also===
-[[Business Process]]<br />
 ===References===
 <references />

@@ Line 1: / Line 1: @@
-The term [[Business]] [[Process]] [[Model]] (BPM) is the noun form of [[Business_Process_Modeling|Business Process Modeling]], and refers to a structural representation, description or diagram, which defines a specified flow of activities in a particular business or organizational unit. It is a representation - usually [[computer]]-generated and diagrammatic, but can be a low-tech whiteboard or flipchart and marker pens and sticky notes - of a process within a business. Two models are usually produced: an 'as is' and a 'to be'. The process(es) featured in a Business [[Process Model]] can be very simple or highly complex, and will typically involve different departments working (hopefully) together while the provision or creation of a [[product]] or [[service]] flows through different stages and decision-points in an organisation on its way to the [[customer]]. A [[Business Process]] Model for a large process can be comprised of other smaller modeled processes which contribute to the whole. In theory an entire huge business can be modeled, although for the modelling to be useful and meaningful to people it is normally built in sections, each representing a self-contained process alongside potentially scores, hundreds or even thousands of others, all inter-relating, smoothly, efficiently and enjoyably. (The 'enjoyable' part is not a technical necessity, but is actually important for any model to translate from theory into sustainable practice).<ref>What is a Business Process Model? [http://www.businessballs.com/business-process-modelling.htm Business Balls]</ref>
+The term '''Business Process Model (BPM)''' is the noun form of [[Business Process Modeling]], and refers to a structural representation, description, or diagram, which defines a specified flow of activities in a particular business or organizational unit. It is a representation - usually computer-generated and diagrammatic, but can be a low-tech whiteboard or flipchart and marker pens and sticky notes - of a process within a business. Two models are usually produced: an 'as is' and a 'to be'. The process(es) featured in a Business Process Model can be very simple or highly complex, and will typically involve different departments working (hopefully) together while the provision or creation of a product or service flows through different stages and decision points in an organization on its way to the customer. A Business Process Model for a large process can be comprised of other smaller modeled processes which contribute to the whole. In theory, an entire huge business can be modeled, although for the modeling to be useful and meaningful to people it is normally built in sections, each representing a self-contained process alongside potential scores, hundreds or even thousands of others, all inter-relating, smoothly, efficiently and enjoyably. (The 'enjoyable' part is not a technical necessity, but is actually important for any model to translate from theory into sustainable practice).<ref>What is a Business Process Model? [http://www.businessballs.com/business-process-modelling.htm]</ref>
-'''Elements of a Business Process Model'''<ref>Elements of a Business Process Model [http://www.bridging-the-gap.com/how-to-analyze-a-business-process/ Bridging the Gap]</ref><br />
+'''Elements of a Business Process Model'''<ref>Elements of a Business Process Model [http://www.bridging-the-gap.com/how-to-analyze-a-business-process/]</ref><br />
 A Business Process Model contains the following elements:
-*Statement of Scope – It’s very easy for one process to turn into several. Naming your process with a clear name in the [Verb] [Noun] syntax and writing a starts with / ends when statement will help you clearly identify the scope of the process.
+*Statement of Scope – It’s very easy for one process to turn into several. Naming your process with a clear name in the Verb Noun syntax and writing a starts with / ends when statement will help you clearly identify the scope of the process.
-*Desired [[Outcome]] – It’s easy for a process to get ingrained in “how we do it here” but lose its [[value]] over time.  As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
+*Desired Outcome – It’s easy for a process to get ingrained in “how we do it here” but lose its value over time.  As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
 *Process Flow or Activity Descriptions – This is the meat of the process model. It’s essentially a list of the steps completed by people in certain roles. This is the primary or most common path through the business process.
-*Exceptions – In addition to the primary path, you want to include variations. What happens if information on a form is illegible, a required piece of information is not provided, or a special condition is met?
+*Exceptions – In addition to the primary path, you want to include variations. What happens if the information on a form is illegible, a required piece of information is not provided, or a special condition is met?
 *Business Rules – Your process flow will presume a certain set of rules are followed or enforce those rules. As processes get more complex, it often makes sense to break the business rules out separately so they can be more easily managed as they change.
-*Entry Criteria and Inputs – Entry Criteria identify what needs to be true in order for the process to start. Inputs identify any tangible work items someone executing the business process needs to have present-at-hand.
+*Entry Criteria and Inputs – Entry Criteria identify what needs to be true in order for the process to start. Inputs identify any tangible work items someone executing the business process needs to have present at hand.
 *Exit Criteria and Outputs – Exit Criteria identify what needs to be true when the process ends. Outputs identify tangible work items generated through the course of the business process.
-*[[Workflow]] Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.
+*Workflow Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.
 ===See Also===
-[[Business_Process|Business Process]]<br />
+[[Business Process]]<br />
-[[Business_Process_Execution_Language_(BPEL)|Business Process Execution Language (BPEL)]]<br />
+[[Business Process Execution Language (BPEL)]]<br />
-[[Business_Process_Analytics|Business Process Analytics]]<br />
+[[Business Process Analytics]]<br />
-[[Business_Process_Architecture|Business Process Architecture]]<br />
+[[Business Process Architecture]]<br />
-[[Business_Process_Engine_(BPE)|Business Process Engine (BPE)]]<br />
+[[Business Process Engine (BPE)]]<br />
-[[Business_Process_Improvement_(BPI)|Business Process Improvement (BPI)]]<br />
+[[Business Process Improvement (BPI)]]<br />
-[[Business_Process_Automation|Business Process Automation]]<br />
+[[Business Process Automation]]<br />
-[[Business_Process_as_a_Service_(BPaaS)|Business Process as a Service (BPaaS)]]<br />
+[[Business Process as a Service (BPaaS)]]<br />
-[[Business_Process_Change_Cycle|Business Process Change Cycle]]<br />
+[[Business Process Change Cycle]]<br />
-[[Business_Process_Management_(BPM)|Business Process Management (BPM)]]<br />
+[[Business Process Management (BPM)]]<br />
-[[Business_Process_Integration|Business Process Integration]]<br />
+[[Business Process Integration]]<br />
-[[Business_Process_Reengineering_(BPR)|Business Process Reengineering]]<br />
+[Business Process Reengineering (BPR)]]<br />
-[[Business_Process_Mapping|Business Process Mapping]]<br />
+[[Business Process Mapping]]<br />
-[[Business_Process_Modeling|Business Process Modeling]]<br />
+[[Business Process Modeling]]<br />
 ===References===
 <references />

@@ Line 1: / Line 1: @@
-The term Business Process Model (BPM) is the noun form of [[Business_Process_Modeling|Business Process Modeling]], and refers to a structural representation, description or diagram, which defines a specified flow of activities in a particular business or organizational unit. It is a representation - usually computer-generated and diagrammatic, but can be a low-tech whiteboard or flipchart and marker pens and sticky notes - of a process within a business. Two models are usually produced: an 'as is' and a 'to be'. The process(es) featured in a Business Process Model can be very simple or highly complex, and will typically involve different departments working (hopefully) together while the provision or creation of a product or service flows through different stages and decision-points in an organisation on its way to the customer. A Business Process Model for a large process can be comprised of other smaller modeled processes which contribute to the whole. In theory an entire huge business can be modeled, although for the modelling to be useful and meaningful to people it is normally built in sections, each representing a self-contained process alongside potentially scores, hundreds or even thousands of others, all inter-relating, smoothly, efficiently and enjoyably. (The 'enjoyable' part is not a technical necessity, but is actually important for any model to translate from theory into sustainable practice).<ref>What is a Business Process Model? [http://www.businessballs.com/business-process-modelling.htm Business Balls]</ref>
+The term [[Business]] [[Process]] [[Model]] (BPM) is the noun form of [[Business_Process_Modeling|Business Process Modeling]], and refers to a structural representation, description or diagram, which defines a specified flow of activities in a particular business or organizational unit. It is a representation - usually [[computer]]-generated and diagrammatic, but can be a low-tech whiteboard or flipchart and marker pens and sticky notes - of a process within a business. Two models are usually produced: an 'as is' and a 'to be'. The process(es) featured in a Business [[Process Model]] can be very simple or highly complex, and will typically involve different departments working (hopefully) together while the provision or creation of a [[product]] or [[service]] flows through different stages and decision-points in an organisation on its way to the [[customer]]. A [[Business Process]] Model for a large process can be comprised of other smaller modeled processes which contribute to the whole. In theory an entire huge business can be modeled, although for the modelling to be useful and meaningful to people it is normally built in sections, each representing a self-contained process alongside potentially scores, hundreds or even thousands of others, all inter-relating, smoothly, efficiently and enjoyably. (The 'enjoyable' part is not a technical necessity, but is actually important for any model to translate from theory into sustainable practice).<ref>What is a Business Process Model? [http://www.businessballs.com/business-process-modelling.htm Business Balls]</ref>
@@ Line 5: / Line 5: @@
 A Business Process Model contains the following elements:
 *Statement of Scope – It’s very easy for one process to turn into several. Naming your process with a clear name in the [Verb] [Noun] syntax and writing a starts with / ends when statement will help you clearly identify the scope of the process.
-*Desired Outcome – It’s easy for a process to get ingrained in “how we do it here” but lose its value over time.  As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
+*Desired [[Outcome]] – It’s easy for a process to get ingrained in “how we do it here” but lose its [[value]] over time.  As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
 *Process Flow or Activity Descriptions – This is the meat of the process model. It’s essentially a list of the steps completed by people in certain roles. This is the primary or most common path through the business process.
 *Exceptions – In addition to the primary path, you want to include variations. What happens if information on a form is illegible, a required piece of information is not provided, or a special condition is met?
@@ Line 11: / Line 11: @@
 *Entry Criteria and Inputs – Entry Criteria identify what needs to be true in order for the process to start. Inputs identify any tangible work items someone executing the business process needs to have present-at-hand.
 *Exit Criteria and Outputs – Exit Criteria identify what needs to be true when the process ends. Outputs identify tangible work items generated through the course of the business process.
-*Workflow Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.
+*[[Workflow]] Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.

@@ Line 13: / Line 13: @@
 *Workflow Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.
-'''See Also'''<br />
 [[Business_Process|Business Process]]<br />
 [[Business_Process_Execution_Language_(BPEL)|Business Process Execution Language (BPEL)]]<br />

@@ Line 13: / Line 13: @@
 *Workflow Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.
+'''See Also'''<br />
 [[Business_Process|Business Process]]<br />
 [[Business_Process_Execution_Language_(BPEL)|Business Process Execution Language (BPEL)]]<br />

← Older revision		Revision as of 17:53, 10 December 2018
Line 1:		Line 1:
−	'''~~Content Coming Soon~~'''	+	The term Business Process Model (BPM) is the noun form of [[Business_Process_Modeling\|Business Process Modeling]], and refers to a structural representation, description or diagram, which defines a specified flow of activities in a particular business or organizational unit. It is a representation - usually computer-generated and diagrammatic, but can be a low-tech whiteboard or flipchart and marker pens and sticky notes - of a process within a business. Two models are usually produced: an 'as is' and a 'to be'. The process(es) featured in a Business Process Model can be very simple or highly complex, and will typically involve different departments working (hopefully) together while the provision or creation of a product or service flows through different stages and decision-points in an organisation on its way to the customer. A Business Process Model for a large process can be comprised of other smaller modeled processes which contribute to the whole. In theory an entire huge business can be modeled, although for the modelling to be useful and meaningful to people it is normally built in sections, each representing a self-contained process alongside potentially scores, hundreds or even thousands of others, all inter-relating, smoothly, efficiently and enjoyably. (The 'enjoyable' part is not a technical necessity, but is actually important for any model to translate from theory into sustainable practice).<ref>What is a Business Process Model? [http://www.businessballs.com/business-process-modelling.htm Business Balls]</ref>
		+
		+
		+	'''Elements of a Business Process Model'''<ref>Elements of a Business Process Model [http://www.bridging-the-gap.com/how-to-analyze-a-business-process/ Bridging the Gap]</ref><br />
		+	A Business Process Model contains the following elements:
		+	*Statement of Scope – It’s very easy for one process to turn into several. Naming your process with a clear name in the [Verb] [Noun] syntax and writing a starts with / ends when statement will help you clearly identify the scope of the process.
		+	*Desired Outcome – It’s easy for a process to get ingrained in “how we do it here” but lose its value over time. As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
		+	*Process Flow or Activity Descriptions – This is the meat of the process model. It’s essentially a list of the steps completed by people in certain roles. This is the primary or most common path through the business process.
		+	*Exceptions – In addition to the primary path, you want to include variations. What happens if information on a form is illegible, a required piece of information is not provided, or a special condition is met?
		+	*Business Rules – Your process flow will presume a certain set of rules are followed or enforce those rules. As processes get more complex, it often makes sense to break the business rules out separately so they can be more easily managed as they change.
		+	*Entry Criteria and Inputs – Entry Criteria identify what needs to be true in order for the process to start. Inputs identify any tangible work items someone executing the business process needs to have present-at-hand.
		+	*Exit Criteria and Outputs – Exit Criteria identify what needs to be true when the process ends. Outputs identify tangible work items generated through the course of the business process.
		+	*Workflow Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.
		+
		+
		+	[[Business_Process\|Business Process]]<br />
		+	[[Business_Process_Execution_Language_(BPEL)\|Business Process Execution Language (BPEL)]]<br />
		+	[[Business_Process_Analytics\|Business Process Analytics]]<br />
		+	[[Business_Process_Architecture\|Business Process Architecture]]<br />
		+	[[Business_Process_Engine_(BPE)\|Business Process Engine (BPE)]]<br />
		+	[[Business_Process_Improvement_(BPI)\|Business Process Improvement (BPI)]]<br />
		+	[[Business_Process_Automation\|Business Process Automation]]<br />
		+	[[Business_Process_as_a_Service_(BPaaS)\|Business Process as a Service (BPaaS)]]<br />
		+	[[Business_Process_Change_Cycle\|Business Process Change Cycle]]<br />
		+	[[Business_Process_Management_(BPM)\|Business Process Management (BPM)]]<br />
		+	[[Business_Process_Integration\|Business Process Integration]]<br />
		+	[[Business_Process_Reengineering_(BPR)\|Business Process Reengineering]]<br />
		+	[[Business_Process_Mapping\|Business Process Mapping]]<br />
		+	[[Business_Process_Modeling\|Business Process Modeling]]<br />
		+
		+
		+	===References===
		+	<references />