IAB203-2020S1 Assessment Assignment-1 PDF

Preview

Summary

assignment1...

Description

IAB203 Business Process Modelling semester 1, 2020 Assignment 1

This aim of the first assignment is to get familiar with process modelling, BPMN, process modelling tools and modelling in groups, and to model a complex business process.

1

Key Info

Group size 3 students Deadline 12 April, 23:59 (end of week 7) Page limit at most 10 pages Weight 20% Submit one PDF on Blackboard Questions Ryan Dunn, [email protected] Form groups of 3 students and register in a group on Blackboard. If you can’t manage to form a group of 3 students, use the Blackboard forum to find other group members.

2

The Assignment 1. Choose one business process from the list in Appendix A. 2. Describe the context of the process: the type of process (e.g. order-to-cash, procure-topay, issue-to-resolution), the customer, actors and business objects involved, outcomes of the process and the value delivered to the customer. 3. Describe the process textually. That is, write a text that explains the process as if it were a modelling exercise from the tutorials. It is not important whether the “real” process would be executed exactly as you describe, just imagine parts where necessary. 4. Model the process in BPMN 2.0. • Adjust the scope and abstraction level of the process such that it contains around 30 40 BPMN activities/gateways/events in total. • The model should be syntactically and behaviourally correct. • Model the process from the perspective of the organisation.

1

• Include the data perspective and the resource perspective. Include at least 2 swimlanes within the organisation and model external parties as black boxes. • Make sure that the model and the textual description match as much as possible, using the elements covered in week 1-4. If an aspect of the process cannot be modelled using these constructs, then model something close and document the omission as a modelling decision. • We recommend to use a modelling tool such as Signavio, Microsoft Visio or Omnigraffle to draw the model, but it’s up to you. 5. Keep track of design decisions and assumptions. 6. Submit a report in one PDF on one PDF on Blackboard before 12 April, 23:59 (end of week 7), according to Section 3.

3

Report

The structure of the report is up to you, however make sure it contains: • Brief explaination of the context of the process. One sentence each for most of the context items should do. • The textual description of your chosen process. • The BPMN model of your chosen process (make sure that we can read it). • An explanation of each modelling decision made. The report should consist of at most 10 pages (including everything).

A

List of processes • Bidding for an item on eBay • Booking a flight on Expedia • Booking a hotel room on Booking.com • Applying for a loan on Nimble • Applying for a birth certificate at the Brisbane City Council • Applying for a passport at Australia Post • Lodging a health insurance claim

B

Marking, Feedback, Rules & Questions

After hand-in, we will mark your assignment and send you feedback as soon as possible, using the marking criteria shown in Section B.3. In case you have any further questions or feedback for us, please contact the unit coordinator during the support sessions or via [email protected]. For more rules and regulations, and ways to ask us questions, see the study guide on Blackboard. 2

B.1

Frequently Asked Questions

1. When modelling the selected business process, whose perspective should we be looking at, i.e. the organisation or customer? Do we have to describe and model all perspectives? Take the perspective of the organisation and model other parties as black boxes. 2. Should the models be generic and not design-specific? E.g. Are we to include specific functions such as ”Click X button” or should it be described in general terms such as ”Select option to X”? You have to design a conceptual process model, not a model that details how to interact with a webpage. Thus, ”Click X button” is too specific and not interesting from a process perspective. A better label for an activity would be “assess application”. 3. What content are we expected to know up to for the first assignment? You may need the concepts you’ve learned in lectures 1-7. 4. Our team is modelling the [insert scenario here]. Can you please take a look and provide constructive feedback on whether or not we are on the correct path? The teaching team is available to answer general questions about the assignment during the support sessions, but cannot pre-mark your assignment, read report drafts nor review detailed models in detail prior to the submission of the assignment. 5. How can we make sure that our model is behaviourally correct? A block-structured model is guaranteed to be behaviourally correct if you make sure that all gateways come in pairs of the same type. For instance, an OR-split should always correspond to an OR-join. If you cannot make your model fully block-structured, try to identify the areas where it is not block-structured and carefully reason about these parts using the definitions from the lecture. 6. Can we connect two XOR/OR-splits directly? To take its decision, a XOR-split or an OR-split needs the data of its conditions to be available. If this data is available, the XOR- or OR-split can take its decision. If this data is not available, an activity is necessary to obtain it. For instance: the number of registrations is readily available in an SAP-system, but not in a paper-based process. Thus, the SAP system can use an XOR-split that decides based on the number of registrations, while the paper-based process first needs an activity, e.g. “count registrations”.

B.2

Frequent Mistakes & Hints

1. Missing labels on (X)OR-split conditions, message flows, start/end events 2. Two actions in one task (e.g. Ship goods and invoice customer); decompose into 2 tasks instead 3. Too low level tasks such as click X button or continue to X page on website; model at conceptual level (e.g. Fill out form) 4. Sequence flows crossing pools’ boundaries 3

5. Missing sequence flows: each element should be on a sequence-flow path from a start event to an end event within the same pool 6. Remember: we will check that your model is syntactically correct (both structurally and behaviourally), that it is semantically correct (it does model exactly the process description that you have provided in the report). We do not check whether the process matches what would be executed in real life (within reason). 7. Modelling without knowing: We recommend to only use the following BPMN elements for Assignment 1: activities, start and end events, message events, gateways, data objects and data stores, pools and lanes, text annotations, start message event, message flows (all elements presented until week 4). You are allowed to use advanced BPMN elements which we haven’t explained yet, however if you use them improperly, it might cost you points. Our advice: don’t venture yourself into new stuff. Assignment 1 is not about modelling a complex scenario, but about creating good quality BPMN models.

B.3

Marking Criteria

This is a draft of the marking criteria we will use to mark the first assignment, to give an idea what we’re looking for. The points sum to 100 and count for 20% towards the unit score. Penalties apply for reports that exceed the page limit. Misconduct will be reported to the SEF student misconduct committee. Misconduct includes handing in work that is not your own, re-using parts from someone else, and including text without citation.

4

Deliverable

Unacceptable 0−

1 5

Needs work

Acceptable

Good

Excellent

1 5

2 5

3 5

4 5

−

2 5

−

3 5

−

4 5

Max points

−1

Presentation format of report (structure, layout, grammar & spelling, consistency, readability of model, . . . )

0 criteria met

1 criterion met

2 criteria met

3 criteria met

4-5 criteria met

Context type of process, customers, actors, objects, outcomes, value

many missing

some missing or incorrect

all present and correct

well explained

very well explained

10

Description textual description of the process should be sensible, right amount of complexity, right level of abstraction

no explanation

limited explanation

reasonable explanation

good and sensible explanation

excellently described

15

Assumptions & modelling decision

missing

many assumptions missing

with some gaps, assumptions lead to model

assumptions naturally lead to model

assumptions naturally lead to model & well motivated

15

Control-flow syntactially correct, behaviourally correct, semantically correct w.r.t. description (after assumptions), right amount of complexity, right level of abstraction

badly aligned, too many mistakes

poorly aligned/many mistakes/too simple

acceptably aligned, some mistakes

well-aligned, minor mistakes/too complex

perfectly aligned, correct

30

Resources at least 2 swimlanes, black boxes for other parties, alignment with description

badly aligned

poorly aligned, major differences

acceptably aligned, some differences

well-aligned, minor differences

perfectly aligned

10

Data appropriate data perspective, alignment with description

missing

badly aligned

poorly aligned, major differences

well-aligned, minor differences

perfectly aligned

10

10

5...