1 / 86

SOA Part1 Lecture 5

SOA Part1 Lecture 5. Dr. Withalm 18-Sep-14. Lectures at the University of Bratislava/Autumn 2011. 19.09.2011 Lecture 1 The long Way from OO to SOA & WEB- Services 26.09.2011 Lecture 2 Semantic WEB & SOA-Technological Basis

yovela
Download Presentation

SOA Part1 Lecture 5

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOA Part1 Lecture 5 Dr. Withalm 18-Sep-14

  2. Lectures at the University of Bratislava/Autumn 2011 19.09.2011 Lecture 1 The long Way from OO to SOA & WEB- Services 26.09.2011 Lecture 2 Semantic WEB & SOA-Technological Basis 10.10.2011 Lecture 3 SOA-Basing on J2EE & SOA-Focus on Business Processes 17.10.2011 Lecture 4 B2B Frameworks and related Standards 14.11.2011 Lecture 5 WEB 2.0 & GRID & Cloud Computing Dr.Withalm

  3. Summary of lecture 4/1 • Both new business processes and new technologies • Are drivers of architecture change • Service bus facilitates • The co-operation of different applications • Which are themselves aggregated by services • In SOA you are only concerned with three parties • Service Provider, Service Requestor, Service Broker • Reuse is in the spotlight of SOA • Services are aggregated by other services • Orchestration & Choreography • Business components contain business services • Business processes are aggregated by different business services • Each business component has service interfaces • Technical service interface • Business service interface • Data entity • Service integration adapter Dr.Withalm

  4. Summary of lecture 4/2 • Servlets are influenced by applets and CGI • Are provided by a class library • Are executed on the Web Server • Portlets provide a user interface • Which allows an end user to interact directly with the service • JSR 168 standard is available • Some obstacles should be taken into account • IT management of SOA is challenging • Many service level agreements must be concluded • Disputes between enterprises may arise • If services are highly profitable • Danger of system chaos exists • Millions of networked services are hardly comprehensible • Implications of SOA • i.e. different kinds of SW developers Dr.Withalm

  5. Today’s Agenda • Brief introduction of ARIS • Connection SOA with ARIS • Event Control – Event Driven Process Chain (EPC) • Function Allocation Diagram • Information Flow Diagram • Event Diagram • Function Organization Data • EPC/PCD Dr.Withalm

  6. ARIS(ARchitecture of integrated Information Systems)/1 • Main focus is modeling of business processes and their implementation on information systems • This architecture concept enables methods to be evaluated and organized • By concentrating on their focal points • And it also serves as an orientation Framework for complex development projects • Because in its structuring elements • It contains an implicit procedural model • For the development of integrated information systems Dr.Withalm

  7. ARIS(ARchitecture of integrated Information Systems)/2 • An architecure of this kind naturally leads toward standardization in the use of methods • As a result existing and new modeling methods were merged • To create a holistic method for modeling business processes • On the basis of this architecture • This ARIS architecture was then used as the basis for the development of the • ARIS toolset – a family of tools developed by IDS Scheer • i.e. ARIS Simulation, ARIS Web Publisher, ARIS Lotus Notes Connectivity • ARIS toolset supports consultants and companies in • Creating, analyzing, and evaluating company processes • For purposes of Business Process Reengineering Dr.Withalm

  8. ARIS(ARchitecture of integrated Information Systems)/3 • Following issues are tackled (more than 2000 pages!!): • Structure and structuring elements • Allocation of the individual modeling methods to the the structuring elements of the ARIS architecture. • Implementation of UML in ARIS • Implementation of OMT in ARIS • Knowledge Management methods • ARIS solutions for specific business management problems • ARIS BSC (Balanced Score Card) method • eBusiness Scenario Diagram and CBusinessMaps Dr.Withalm

  9. ARIS(ARchitecture of integrated Information Systems)/4 Dr.Withalm

  10. ARIS(ARchitecture of integrated Information Systems)/5 Dr.Withalm

  11. ARIS Analytical Views of the Process Model Dr.Withalm

  12. Process Model Views Dr.Withalm

  13. Example of a Process Chain Diagram Dr.Withalm

  14. Descriptive Levels of an Information System Dr.Withalm

  15. ARIS Concept Dr.Withalm

  16. Example of a Process Chain Diagram Dr.Withalm

  17. Representation of a Function • A function is a technical task or activity performed on an object in support of one or more company objectives • Elementary functions are functions which cannot be reduced any further for the purpose of business process analysis. • Example: Dr.Withalm

  18. Function Tree (Extract) Dr.Withalm

  19. Object –oriented Function Tree Dr.Withalm

  20. Process – oriented Function Tree Dr.Withalm

  21. Execution - Oriented Function Tree Dr.Withalm

  22. Mapping of an ARIS function onto a SOA service/1(Architecture of Integrated Information systems) Dr.Withalm

  23. Mapping of an ARIS function onto a SOA service/2 • The ARIS function which denotes a business service • Is directly mapped onto a SOA service • I/O data are mapped to the respective I/O data of the service • The operating entity is the SOA service provider • Activating and resulting events are elements of the service of the service consumer • In which the service is employed Dr.Withalm

  24. Event Control-Event-Driven Process Chain (EPC) /1 • Events such as Customer order received or Invoice produced define the point • at which a change in the state of information objects (data) occurs. • They are described in the data view of the ARIS architecture. • The procedural sequence of functions in the sense of business processes • is represented in process chains. • This means that the start and end events can be specified for each function. • Events are not only trigger functions, but they are results of functions. Dr.Withalm

  25. Event Control-Event-Driven Process Chain (EPC)/2 • By an event we understand the fact • that an information object (data) has taken on a business-relevant state • which is controlling or influencing the further procedure of the business process. • Unlike a function, which is a time-consuming occurrence, • an event is related to one point in time. Dr.Withalm

  26. Event Control-Event-Driven Process Chain (EPC)/3 • The change in state of an information object • may refer to the first occurrence of this information object • e.g., Customer order received • or to a change in state in the sense of a change in status • that is recorded in an attribute occurrence • e.g., Offer is refused. Dr.Withalm

  27. Event Control-Event-Driven Process Chain (EPC) /4 • Since information objects and attributes are described in the ARIS data view, • the event-driven representation of process chains is a link • between the data view and the function view. • Hence it is assigned to the ARIS control view. • Events are graphically represented as hexagons. • The description should not only contain the information object itself (Order), • but also its status change (received). Dr.Withalm

  28. Event Control-Event-Driven Process Chain (EPC)/5 Events (Graphical Representation): Dr.Withalm

  29. Event Control-Event-Driven Process Chain (EPC) /6 • Events trigger functions and are the results of functions. • By arranging this event-to-function change in a sequence, • so-called event-driven process chains (EPCs) are created. • An event-driven process chain (EPC) shows • The chronological-logical procedure of a business process. Dr.Withalm

  30. Event Control-Event-Driven Process Chain (EPC)/7 Example of EPC: Dr.Withalm

  31. Event Control-Event-Driven Process Chain (EPC)/8 • An example of an EPC is shown in above figure. • Since events determine which state or condition will trigger a function • and which state will define the end of a function, • the starting and end nodes of such an EPC are always events. • Several functions can originate simultaneously from one event and conversely • a function can have several events as its result. Dr.Withalm

  32. Event Control-Event-Driven Process Chain (EPC) /9 • A link in the form of a circle is used to represent • branches and processing loops in an EPC. • These connections, however, not only serve as graphic operators, • but define the logical links • between the objects they connect. Dr.Withalm

  33. Event Control-Event-Driven Process Chain (EPC) /10 Dr.Withalm

  34. Event Control-Event-Driven Process Chain (EPC)/11 • In the first example of above Figure • the starting events are linked by an AND operator. • This means that the procedure Release operation • is only started if a routing is available • and the necessary resources have been verified. • Therefore, both events must have occurred before the procedure can begin. Dr.Withalm

  35. Event Control-Event-Driven Process Chain (EPC) /12 • The second example shows an exclusive OR operator • The Check supplier offer function may either result • in acceptance or rejection of the quote. • Both results, however, cannot occur at the same time. Dr.Withalm

  36. Event Control-Event-Driven Process Chain (EPC) /13 • Besides these two cases and the "Inclusive OR" operator, • more complex relationships are conceivable. • In this case, a general rule can be represented in an EPC • which will be described later in more detail in the form of a rule diagram. Dr.Withalm

  37. Event Control-Event-Driven Process Chain (EPC) /14 • Therefore, we can distinguish between two different types of operators: • Event operators • Function operators Dr.Withalm

  38. Event Control-Event-Driven Process Chain (EPC)/15 overview of all possible event operators: Dr.Withalm

  39. Event Control-Event-Driven Process Chain (EPC)/16 overview of all possible function operators: Dr.Withalm

  40. Event Control-Event-Driven Process Chain (EPC) /17 • In this context, special attention must be paid to the restrictions • which exist for function operators. • Due to the fact that events cannot make decisions • Only functions can do this • a triggering event must not be linked using an OR or XOR operator ! • Below, possible operators are explained using examples. Dr.Withalm

  41. Event Control-Event-Driven Process Chain (EPC) /18 Operator for Triggering Events /1AND Operator The function can be started only after all events have occurred. Dr.Withalm

  42. Event Control-Event-Driven Process Chain (EPC) /19 Operator for Triggering Events /2OR Operator • The function will be carried out • after at least one of the events has occurred. Dr.Withalm

  43. Event Control-Event-Driven Process Chain (EPC) /20 Operator for Triggering Events /3XOR operator • The function is started after exactly one and only one event has occurred. Dr.Withalm

  44. Event Control-Event-Driven Process Chain (EPC) /21 Operator for Created Events /1AND Operator • The function results in all events occurring. Dr.Withalm

  45. Event Control-Event-Driven Process Chain (EPC) /22 Operator for Created Events /2OR Operator • Executing the function results in at least one of the events occurring. Dr.Withalm

  46. Event Control-Event-Driven Process Chain (EPC) /23 Operator for Created Events /3XOR Operator • Executing the function results in one event at the most occurring. Dr.Withalm

  47. Event Control-Event-Driven Process Chain (EPC) /24Linking of functions with created events /1AND Operator of Functions with Created Events • The event occurs only after all functions have been carried out. Dr.Withalm

  48. Event Control-Event-Driven Process Chain (EPC) /25Linking of functions with created events /2OR Operator of Functions with Created Events • The event occurs after at least one of the functions has been carried out. Dr.Withalm

  49. Event Control-Event-Driven Process Chain (EPC) /26Linking of functions with created events /3XOR Operator of Functions with Created Events • The event occurs when exactly one of the functions • has been carried out. Dr.Withalm

  50. Event Control-Event-Driven Process Chain (EPC) /27Linking of functions with triggering events /1AND Operator of Functions with Triggering Events • The event triggers all functions. Dr.Withalm

More Related