1. IMS 5024, Semester 2, 2002 Lecture 5 1 IMS 5024 Event-driven modelling

2. 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

3. 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

4. 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

5. IMS 5024, Semester 2, 2002 Lecture 5 5 My consultation times Monday 10 – 11.30 am Tuesday 2 – 3.30 pm

6. IMS 5024, Semester 2, 2002 Lecture 5 6 Pitfalls Not starting early Reading, more reading and then some reading. Plagiarism !!!!!

7. IMS 5024, Semester 2, 2002 Lecture 5 7 Different perspectives Process Data Behaviour / Stimulus response – how system reacts to external and internal events Difference

8. 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

9. IMS 5024, Semester 2, 2002 Lecture 5 9 Key constructs of BRD State Event Condition Signal Blob

10. 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

11. IMS 5024, Semester 2, 2002 Lecture 5 11 Business rule types Implementation rules Processing rules Policy rules

12. 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)

13. 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

14. 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

15. IMS 5024, Semester 2, 2002 Lecture 5 15 Example of candidate list of business events and signals Receive customer orderT Delete lineE Reject orderE Create new orderE Send invoiceM Generate credit noteE Receive paymentT Create outstanding itemE Create new customerE Move to good customerE Move to bad customerE

16. IMS 5024, Semester 2, 2002 Lecture 5 16 Example of a OLH Customer Temp cust Good cust Bad cust

17. IMS 5024, Semester 2, 2002 Lecture 5 17 Example of UBRD

18. IMS 5024, Semester 2, 2002 Lecture 5 18 Example of BRD

19. IMS 5024, Semester 2, 2002 Lecture 5 19 Example of EST

20. 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

21. 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

22. 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

23. 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

24. 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?)

25. 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

26. 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

27. 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

28. IMS 5024, Semester 2, 2002 Lecture 5 28 Example of an EPC

29. 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

30. IMS 5024, Semester 2, 2002 Lecture 5 30 Example of a component model

31. IMS 5024, Semester 2, 2002 Lecture 5 31 Example of Organisation model

32. IMS 5024, Semester 2, 2002 Lecture 5 32 Example of data model

33. IMS 5024, Semester 2, 2002 Lecture 5 33 Example of an Interaction model

34. IMS 5024, Semester 2, 2002 Lecture 5 34 Evaluation of Data modelling Problem orientedProduct 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

35. IMS 5024, Semester 2, 2002 Lecture 5 35 Advantages of Event driven modelling  Concentrate on the problem area  Identify business processes  Cost

36. IMS 5024, Semester 2, 2002 Lecture 5 36 Disadvantages of event driven modelling Difficult to implement Early days Cost

37. IMS 5024, Semester 2, 2002 Lecture 5 37 Process modelling view of ISD Development group Objectives Environment Object system Object system Change process Hirschheim et al see reading list

38. 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