Task 1: Investigate, define and describe the process in plain English. Before modelling a process, one needs understand the process, have the definition of the process (as the basis for modelling), specify the scope of the model, and make necessary assumptions for modelling the process. You firstly need to explore AbeBooks website to find and sort out the steps of buying a book (new or used) and then selling the used book using the buyback service. As you are working on a process model (instead of a single instance/case of the process), you need to consider all possible cases/scenarios when buying a book and then selling it with buyback service. Use a top-down approach when identifying and organising the tasks. That is, identify the top-level process tasks first, i.e. the major tasks involved in the process, and some of the tasks may be subprocesses at the top-level (with details hidden away from the top-level). Then think about the ordering of the tasks/subprocesses in the top-level process, especially where the flow should be split/joined. Following this approach, the top level process will provide a meaningful overview of the overall process and, at the same time, will not become overly complicated. After the tasks/subprocesses and the control flow of the top level process have been defined, you can figure out the details of each subprocess in the same way. Remember that you are required to work on the process from the customer (buyer & seller) perspective, so the tasks in your process are those to be carried out by a customer. For the top level process and any of its subprocesses, aim for 10 or fewer tasks/subprocesses (definitely no more than 15 tasks/subprocesses at each level). Limit your process hierarchy to two levels. That is, model the top level process and its subprocesses, and don’t go into the details of subprocesses of a subprocess. When describing the process in plain English, present the top level process first and indicate which tasks are subprocesses in the description, and then describe in detail your selected subprocess to be modelled using BPMN (see below Task 2.2). The process description must clearly state the scope of your process and the assumptions you have made about the process. The English description of the process will become the basis for the modelling in the following tasks. It is very likely that during the modelling, you will need to investigate further to clarify doubts and subsequently revise the description. Try to restrict the length of the process description to one A4 page, and use lists/dot points when necessary. Task 2: Model the process using BPMN 2.0 Task 2.1. Use BPMN 2.0 to model the top-level process, without details of subprocesses. Task 2.2. Select one subprocess from your top-level model created in Task 2.1, and model the selected subprocesses using BPMN 2.0. You must select a subprocess of reasonable complexity: the subprocess must comprise 5 to 10 tasks, and the control flow must contain splits/joins gateways. You are encouraged to use a BPMN 2.0 compliant editor (e.g.Yaoqiang - available on the Internet) to draw the BPMN models. Task 3: Identify and list all the workflow patterns that occur in your models. Task 4: Reflection a) Reflective comments on your modelling experience, for example the difficulties you have encountered and alternative ways in which you might have built the models. b) Your thoughts on the process from the perspective of AbeBooks, i.e. how would it be different from the process from a customer’s perspective?