Ma'am Thess Exam Lesson Notes PDF

**Lesson Number:** *(Week 2)* **Lesson 1:** **Topic:** **Introduction to Business Process Design and Management** - - **Lesson Presentation:** ***The motives of entrepreneurs:*** 1. 2. - - - - -  **Business risks may include:** - - - - -...

**Lesson Number:** *(Week 2)* **Lesson 1:** **Topic:** **Introduction to Business Process Design and Management** - - **Lesson Presentation:** ***The motives of entrepreneurs:*** 1. 2. - - - - -  **Business risks may include:** - - - - - ***Business Process Design Overview*** **Structured Processes** +-----------------------------------------------------------------------+ | **Lesson Number:** *(Week 3)* **Lesson 2** | +=======================================================================+ | **Topic:** | | | | - - | +-----------------------------------------------------------------------+ | **Lesson Presentation:** | | | | 1. | | | | | | | | 2. | | | | | | | | 3. | | | | - | | | | | | | | - | | | | 4. | | | | | | | | 5. | | | | | | | | 6. | | | | - - - - | | | | | | | | - - - - - | | | | | | | | - | | | | | | | | - | | | | | | | | - | | | | | | | | - | +-----------------------------------------------------------------------+ +-----------------------------------------------------------------------+ | **Lesson Number:** *(Week 5)* **Lesson 4** | +=======================================================================+ | - - - - - | +-----------------------------------------------------------------------+ | **Lesson Presentation:** | | | | - - - - | | | | | | | | - - | | | | | | | | - | | | | | | | | - - - - - - | | | | *Adding Value for the Customer* | | ------------------------------- | | | | - - - - | | | | | | | | - Starting with a customer placing an order **(the customer need)** | | send IT-based information to the warehouse: | | | | -  | | | | | | | | - - - - - - - - | | | | *Sequence: Significance in Business Process Modelling* | | ------------------------------------------------------ | +-----------------------------------------------------------------------+ +-----------------------------------------------------------------------+ | **Lesson Number:** *(Week 6)* **Lesson 5** | +=======================================================================+ | - - - | +-----------------------------------------------------------------------+ | **Lesson Presentation:** | | | | ***Purpose and benefits*** | | | | - - - - - - - - | | | | ***Stages in Development of BPMN:*** | | | | - - - - - | | | | | | | | - - - - - | | | | ***Common BPMN symbols & Notations*** | | | | A BPMN diagram, or business process model and notation diagram, is | | used to create easy-to-read business process model flowcharts that | | can be shared across enterprises and industries. Flow objects, | | linking objects, swimlanes, and artifacts are the four primary | | classes of BPMN diagram symbols. Below is a detailed explanation of | | BPMN diagram shapes and their implications. | | | | **BPMN event types** | | | | Events represent an activity in a business process. | | | |  **Start event symbol** - Signals the first | | step of a process. | | ------------------------ ------------------------------------------ | | ------------------------------------------------------- | | **Intermediate event symbol** - Represents | | any event that occurs between a start and end event. | |  **End event symbol** - Signals the final s | | tep in a process. | | | | ***BPMN event symbols*** | | | | **Message symbol** - Triggers the process, | | facilitates intermediate processes, or finishes the process. | | ------------------------ ------------------------------------------ | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | -------------------------------- | |  **Timer symbol** - A time, date, or recurr | | ing time and date triggers the process, aids intermediates processes, | | or completes the process. | | **Escalation symbol** - A step reacts on a | | n escalation and flows to another role in the organization. This even | | t is only used within an event sub-process. An escalation occurs when | | someone at a higher level of responsibility within the organization | | becomes involved in a process. | |  **Conditional symbol** - A process begins | | or continues when a business condition or business rule is met. | | **Link symbol** - A sub-process that is pa | | rt of a larger process. | |  **Error symbol** - A caught error at the s | | tart, middle, or end of a process. An event sub-process with an error | | trigger will always interrupt its containing process. | | **Cancel symbol** - Reacts on a transactio | | n that was cancelled within a sub-process. In an end event, the cance | | l symbol represents the triggered cancellation of a process. | |  **Compensation symbol** - A refund that's | | triggered when operations partially fail. | | **Signal symbol** - A signal that communic | | ates across different processes. A signal symbol can begin a process, | | facilitate it, or complete it. | |  **Multiple symbols** - Multiple triggers i | | nitiating a process. | | **Parallel multiple symbol** - A process i | | nstance that doesn\'t start, continue, or end until all possible even | | ts have occurred. | |  **Terminate symbol** - Triggers the immedi | | ate termination of a process step. All related instances are terminat | | ed at the same time. | | | | ***BPMN activity symbols*** | | | | **Task symbol** - The most basic level of | | an activity and cannot be broken down further. For example, a morning | | routine process might involve the task of turning on your computer. | | ------------------------ ------------------------------------------ | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | ---------------------------- | |  **Sub-process symbol** - Is a group of tas | | ks that fit together particularly well. There are two different views | | of the sub-process. One is the collapsed view, which has an expandab | | le plus sign to show more details. The other view is an expanded sub- | | process view, which is large enough to house all the tasks that fully | | describe the sub-process. | | **Transaction symbol** - Is a specialized | | sub-process that involves payment. | |  **Call symbol** - Is a global sub-process | | that is reused at various points in the business flow. | | | | ***BPMN gateway symbols*** | | | | **Exclusive symbol** - Evaluates the state | | of the business process and, based on the condition, breaks the flow | | into one or more mutually exclusive paths. For example, one report w | | ill be written if a supervisor grants approval; no report will be gen | | erated if the supervisor withholds approval. | | ------------------------ ------------------------------------------ | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | --------------------------------------------------------------------- | | ---------------- | |  **Event-based symbol **- An event-based ga | | teway is similar to an exclusive gateway---both involve one path in t | | he flow. In the case of an event-based gateway, however, you are eval | | uating which event has occurred, not which condition is being met. Fo | | r example, you might wait to send an email until the CEO has arrived | | at the office. If the CEO doesn't arrive, the email will remain unsen | | t. | | **Parallel symbol **- Differs from other g | | ateways because it's not dependent on conditions or events. Instead, | | parallel gateways are used to represent two concurrent tasks in a bus | | iness flow. An example is a marketing department generating new sales | | leads and contacting existing leads at the same time. | |  **Inclusive symbol **- Breaks the process | | flow into one or more flows. For example, an inclusive gateway could | | involve business actions taken based on survey results. One process m | | ay be triggered if the consumer is satisfied with Product A. Another | | flow is triggered when the consumer indicates that they are satisfied | | with product B, and a third process is triggered if they aren\'t sat | | isfied with A. | | **Exclusive event-based symbol **- Starts | | a new process instance with each occurrence of a subsequent event. | |  **Complex symbol **- These gateways are on | | ly used for the most complex flows in a business process. An ideal us | | e case for the complex gateway is when you need multiple gateways to | | describe the business flow. | | **Parallel event-based symbol **- As the n | | ame suggests, this gateway is similar to a parallel gateway. It allow | | s for multiple processes to happen at the same time, but unlike the p | | arallel gateway, processes are event-dependent. | | | | ***3 types of Connecting objects in a BPMN diagram*** | | | |  **Sequence flow symbol** - Connects flow o | | bjects in proper sequential order. | | ------------------------ ------------------------------------------ | | ---------------------------------------------- | | **Message flow symbol **- Represents messa | | ges from one process participant to another. | |  **Association symbol **- Shows relationshi | | ps between artifacts and flow objects. | | | | ***Swimlanes in a BPMN diagram*** | | | | In a BPMN diagram, swimlanes are used to arrange different components | | of a process. Swimlanes divide items into lanes visually, with each | | step of the process assigned to its own lane. These components can be | | placed vertically or horizontally. Swimlanes can expose delays, | | inefficiencies, and the people responsible for each step in a | | process, in addition to organizing operations into discrete | | categories. | | | |   | | | |  **Data input symbol** - Represents data re | | quirements that tasks in the business process depend on. | | ------------------------ ------------------------------------------ | | --------------------------------------------------------------------- | | ------ | | **Data output symbol **- Demonstrates info | | rmation produced as the result of a business process. | |  **Data collection symbol **- Signifies inf | | ormation collected within a business process. | | **Data storage symbol **- Represents the a | | bility to store or access data that's associated with a business proc | | ess. | +-----------------------------------------------------------------------+ +-----------------------------------------------------------------------+ | **Lesson Number:** *(Week 7 & 8)* **Lesson 6** | +=======================================================================+ | **Topic:** **Modeling Business processes (Part 2)** | | | | - - - - - - - | +-----------------------------------------------------------------------+ | **Lesson Presentation:** | | | | We briefly discussed various business process modelling strategies in | | one of our previous BPM posts. As promised, here\'s a more in-depth | | look at several BPM strategies and how to properly apply them. | | | | Business process modelling is primarily used to map a workflow in | | order to comprehend, analyse, and improve that workflow or process. | | The use of a diagram aids in visualizing the process and making | | better judgements. | | | | ***Different techniques/ diagrams of BPM:*** | | | | Let's start with the latest: | | | | 1\. **Business Process Modelling Notation (BPMN)** | | | | - - | | | | BPMN consists of the following basic building blocks: | | | | - - - - | | | | The most significant benefit of BPMN is that it is a well-defined | | standard. Because so many business analysts are familiar with it, | | collaboration becomes easier. Furthermore, most modelling tools | | accept BPMN, making it much easier to share and update even between | | different programs. All of these factors combine to make BPMN the | | most widely used business process modelling technique today. | | | |  | | | | 2.** UML Diagrams** | | | | 3\. **Flowchart Technique** | | | | 4. **Data Flow Diagrams -- Yourdon's Technique** | | | | 6. **Role Interaction Diagrams -- RID** | | | |  | +-----------------------------------------------------------------------+