## 3 Proposed Business Object Oriented Process Modelling (BOOPM) Framework
A context diagram is a useful tool for confirming the overall scope of the business function and the system integration requirements for process analysis. Business use case diagrams can be used to establish the context to confirm the functional scope of each business process. _Step 2: Business Process Discovery_  
In this step, the target business process to be improved is identified. It involves defining and establishing the boundary and interfaces, as well as dependencies with other processes. A process model is developed to provide a visual picture of the process with a break-down of sub-processes. Typically, a business process consists of a number of events and activities with each task defined as a single unit of work when the activity involved is simple. In addition, decision points that affect how the process gets executed are included in the process model. A process also involves a number of actors, physical and non-physical objects. Finally, one or more outcomes of the process on execution are included in the process model. Among some of the standards used for modelling business processes, our proposed modelling framework adopts business process modelling notation (BPMN) for pictorially depicting the details of a business process flow and execution. The key elements of such a workflow modelling diagram using BPMN are objects and connections between objects that form sequence flows. Objects could be events, tasks, or gateways. Where events are used to depict the beginning or ending of a process, tasks are used to represent activities that need to be executed, and finally, gateways are used to control the sequence flows [43; 57; 58]. The main BPMN elements fall under the following four categories:  
1. flow objects, which include events, tasks and gateways (basic elements of a BPM diagram);
2. connecting objects, which are mainly different types of arcs that connect various flow objects;
3. swim lanes, which groups roles or organisational departments that are related; and
4. artefacts, which provide information related to diagrams. The purpose of this workflow diagram using BPMN is to form an \"as-is\" process model that provides a common understanding and communication among the stakeholders. In particular, it assists the business analysts, systems engineers and process engineers to collectively consider the structural data objects and their dependencies to review the different process components and reengineer them for process innovation to achieve business improvements. _Step 3: Business Process Analysis_  
The primary aim of this step is to review and propose changes in the functional scope of the business process and to recommend changes. The behavioural and structural analysis of the business process is conducted in this step to review the interfaces, data dependencies and boundaries of the \"as-is\" process model [59; 60]. The stakeholder requirements are analysed using object-oriented analysis techniques and this is facilitated by developing system use cases, object diagrams and value indicators for the As-Is process model. These diagrams, including class diagrams showing classes and their associations, are used to illustrate the current situation of the process within an enterprise system. The purpose of a system use case diagram is to support the automation of business use cases. Process value analysis of the \"as-is\" BPMN diagram should indicate if the outcomes have actually delivered any value to the actors involved in the process. The actors in the use case diagrams should include all the internal and external stakeholders including customers and suppliers of the business process. A Value-Added Analysis is performed on how the outputs of each activity are consumed by the actors in meeting the stakeholder's requirements and expectations. Those activities that satisfy the business requirements are important for the internal operations and are classified as business value-added activities.