IMS 5024

IMS 5024, Semester 2, 2002 Lecture 5

1

IMS 5024

Event-driven modelling

IMS 5024, Semester 2, 2002 Lecture 5

2

Content

• Individual assignment• Pitfall revisited• Group assignment• BSD• SAP R/3• Place in ISD• Evaluation of event driven modelling• Reading list for next week

IMS 5024, Semester 2, 2002 Lecture 5

3

Individual assignment

Date due: 29 August 2002 – Difference between social and

technical–Show understanding of the

subject matter–Questions e-mail Bahar directly

IMS 5024, Semester 2, 2002 Lecture 5

4

Teaching Assistant

• Bahar Jamshidi

• E-mail: bahar.jamshidi@infotech.monash.edu.au

• Queries about marks• Other queries• Thursday 6 – 7 PM

IMS 5024, Semester 2, 2002 Lecture 5

5

My consultation times

• Monday 10 – 11.30 am

• Tuesday 2 – 3.30 pm

IMS 5024, Semester 2, 2002 Lecture 5

6

Pitfalls

• Not starting early

• Reading, more reading and then some reading.

• Plagiarism !!!!!

IMS 5024, Semester 2, 2002 Lecture 5

7

Different perspectives

• Process

• Data

• Behaviour / Stimulus response – how system reacts to external and internal events

• Difference

IMS 5024, Semester 2, 2002 Lecture 5

8

Techniques

• State transition diagrams

• Business rules diagram (BRD)

• Event-driven process chain methodology

• Petri nets

• Finite state machines

IMS 5024, Semester 2, 2002 Lecture 5

9

Key constructs of BRD

State Event Condition

Signal Blob

IMS 5024, Semester 2, 2002 Lecture 5

10

Definition of a business rule

• An explicit state change context in an organisation which describes the states, conditions and signals associated with events that either change the state of a human activity system so that subsequently it will respond differently to external stimuli or reinforce the constraints which govern a human activity system

IMS 5024, Semester 2, 2002 Lecture 5

11

Business rule types

Implementation rules

Processing rules

Policy rules

IMS 5024, Semester 2, 2002 Lecture 5

12

Steps in creating BRD

• Identify candidate business (policy) rules• Identify candidate events and signals• Identify candidate objects in problem situation• Construct object life histories (OLH) for each

object identified• Construct user business rule diagrams (UBRD)• Construct business rules diagram• Construct event specification table (EST)

IMS 5024, Semester 2, 2002 Lecture 5

13

Example of candidate business rules (Policy rules) (1)

• Orders sent by mail or telephone• Omissions on order line leads to deletion• Credit balance >= order value to accept order else

reject• Stock qty >= order qty to accept order otherwise

reject• One invoice for one order• Sum of payments = order value – sum of credit notes• One order may have many credit notes

IMS 5024, Semester 2, 2002 Lecture 5

14

Example of candidate business rules (Policy rules) (2)

• Many payments per invoice possible• Overdue invoices occur 30 days after statement• If product not carried reject item• If unobtainable multiples reject item• New order created for outstanding items• Only good customers may obtain credit orders• Credit balance reduced for all items on an order

including outstanding items

IMS 5024, Semester 2, 2002 Lecture 5

15

Example of candidate list of business events and signals

Receive customer order TDelete line EReject order ECreate new order ESend invoice MGenerate credit note EReceive payment TCreate outstanding item ECreate new customer EMove to good customer EMove to bad customer E

IMS 5024, Semester 2, 2002 Lecture 5

16

Example of a OLH

Customer Tempcust

Goodcust

Badcust

IMS 5024, Semester 2, 2002 Lecture 5

17

Example of UBRD

IMS 5024, Semester 2, 2002 Lecture 5

18

Example of BRD

IMS 5024, Semester 2, 2002 Lecture 5

19

Example of EST

IMS 5024, Semester 2, 2002 Lecture 5

20

SAP R/3

• Why?Blend business processes and technology

• Best practice processes – then focus on unique aspects

• Blueprint used as reference model

• Business process takes center stage

IMS 5024, Semester 2, 2002 Lecture 5

21

Blueprint

• Help organisations to define needs, develop solutions and optimize their processes

• Do not need to start from scratch• Customisation possible• Include functions, process, information

flow and organisation views• Business processes are shown in the Event-

driven process chains

IMS 5024, Semester 2, 2002 Lecture 5

22

Modelling approach

• Define / redefine the organisations goals

• Create a model to reflect the goals

• Develop unique applications

• Implement the applications

IMS 5024, Semester 2, 2002 Lecture 5

23

SAP approach

• Map company processes to the blue print (reflect “best practice”)

• Define target situation

• Focus on unique aspects

• Customize and configure

IMS 5024, Semester 2, 2002 Lecture 5

24

Key elements of SAP blueprint

• Events (when should something be done?)

• Tasks or functions (what should be done?)

• Organisation (who should do what?)

• Communication (What information is required to the right task?)

IMS 5024, Semester 2, 2002 Lecture 5

25

Event-driven process chain (EPC) methodology (1)

• Event e.g.. Goods arrived

• Task / function e.g.. Verify goods

• Organisation e.g. Good receiving dept

• Information e.g. Delivery note

IMS 5024, Semester 2, 2002 Lecture 5

26

Event-driven process chain (EPC) methodology (2)

• Process path

• Logical operator

• Control flow

• Information/material flow

• Resource/organisation unit assignment

Xor

IMS 5024, Semester 2, 2002 Lecture 5

27

Legend

• EPC is the central view

• Event always trigger a task

• Start and end with an event

• Organisational units are added

• Navigation between process models by start and final event

IMS 5024, Semester 2, 2002 Lecture 5

28

Example of an EPC

IMS 5024, Semester 2, 2002 Lecture 5

29

Other views

• Component model – describe what is done

• Organisation model – Who does what and who is responsible

• Data model – what is needed to do something

• Interaction model – what information must be exchanged between different units

IMS 5024, Semester 2, 2002 Lecture 5

30

Example of a component model

IMS 5024, Semester 2, 2002 Lecture 5

31

Example of Organisation model

IMS 5024, Semester 2, 2002 Lecture 5

32

Example of data model

IMS 5024, Semester 2, 2002 Lecture 5

33

Example of an Interaction model

IMS 5024, Semester 2, 2002 Lecture 5

34

Evaluation of Data modelling

Problem oriented Product oriented

Concep-tual

Structured analysis

Entity relationship modelling

Logical construction of systems

Modern structured analysis

Object oriented analysis

Structured design

Object oriented design

Formal PSL/PSA

JSD

VDM

Levels of abstraction

Stepwise refinement

Proof of correctness

Data abstraction

JSP

Object oriented programming

IMS 5024, Semester 2, 2002 Lecture 5

35

Advantages of Event driven modelling

Concentrate on the problem area Identify business processes Cost

IMS 5024, Semester 2, 2002 Lecture 5

36

Disadvantages of event driven modelling

• Difficult to implement

• Early days

• Cost

IMS 5024, Semester 2, 2002 Lecture 5

37

Process modelling view of ISD

Development group

Objectives

Environment

Object system

ObjectsystemChange

process

Hirschheim et al see reading list

IMS 5024, Semester 2, 2002 Lecture 5

38

Reading for next week

• Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., Lorensen, W. (1991) Object oriented modeling and design. Prentice Hall, Inc. USA. Chapter 1,2,3,4