1 / 29

A Method for Service Identification from Business Process Models in a SOA Approach

A Method for Service Identification from Business Process Models in a SOA Approach. Leonardo Azevedo 1,2 , Flávia Santoro 1,2 , Fernanda Baião 1,2 , Jairo Souza 1 , Kate Revoredo 1 , Vinícios Pereira 1 , Isolda Herlain 3 1 NP2Tec – Research and Practice Group in Information Technology

ulla
Télécharger la présentation

A Method for Service Identification from Business Process Models in a SOA Approach

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. A Method for Service Identification from Business Process Models in a SOA Approach Leonardo Azevedo1,2, Flávia Santoro1,2, Fernanda Baião1,2, Jairo Souza1, Kate Revoredo1, Vinícios Pereira1, Isolda Herlain3 1NP2Tec – Research and Practice Group in Information Technology 2Departament of Applied Informatics, Federal University of the State of Rio de Janeiro 3Petrobras – Petróleo Brasileiro S/A

  2. Overview • Motivation • Related work • Goal of the proposal • BPM • Candidate services • Our proposal • Conclusion/Future work

  3. Motivation • SOA – Service Oriented Architecture • More flexible • Supports platform- and protocol-independent services in a distributed environment • Service • a piece of self-contained business functionality • exposed interfaces • invoked through messages • Concentrate on the businessvalue of an interface • Bridge the business/IT gap

  4. Motivation: Service life-cycle • Life-cycle model of traditional software engineering may not be directly applied in a SOA approach • New architectural roles and development tasks • Examples of challenges • Services and business requirements alignment • Security constraints • Service versioning to accommodatebusiness changes • The need for service development approach is well recognized • Consensus: services must be aligned to business processes

  5. Related work • Some proposals for service identification from business process models: • [Arsanjani, 2004; Erl 2005; Papazoglou and Heuvel, 2006; Marks and Bell 2006; McBride, 2007; Gu and Lago, 2007; Josuttis, 2007; Klose et al, 2007; Fareghzadeh, 2008; Jamshidi et al. 2008] • However, proposals • Do not present a step-by-step approach • Or present principles or guidelines that are very difficult to follow • Or suggest business process modeled in a detailed level that is difficult to accomplish

  6. Our premisse • There has to be an integrated view of the organizational business processes • There is a common process repository • Processes are linked to each other through interfaces • Processes share global elements • clusters (input/output data), business rules, business requirements

  7. Our goal • Candidate service identification from business process models. • Candidate service • Service abstraction (not implemented) which, during the design phase of a service life-cycle model, could be chosen to be implemented as a physical service or as an application function. [Erl 2005]

  8. Business Modeling • Integrates several views about business domain • Process of work (how?) • Concepts of domain (What?) • ... Quality Questions 5W1H • Set of models The most important elements for our work Who? Where? Localization When? How? Role Event Department Why? Process Activity What? Goal Product System Business rule External factors External data Objective

  9. Business rules • “Statements about constraints that organization's business process must satisfy” [Guide Business Rule Project 2008]. Define dependencies among activities. Make business process flow explicit. • Define specific rules that apply to a process activity Activity details

  10. Business requirement • A business requirement specifies a function executed by system or by a user using a system. • Usually, they are identified during process analysis in order to improve the process. System where the requirement is implemented. Business requirement

  11. Types of candidate services Candidate business service Candidate data service Business rule operations. Eventualy can read/write data directly from/to databases. CRUD operations Database Candidate utility service • Service whose operations can be used in different contexts, adjusting some of its parameters.

  12. Services Identification Method

  13. 1. Selection of activities TO-BE models of demand Automatic Sys Automatable Selection of activities Partially Supported by systems

  14. 2. Identification and Classification of Candidate Services • Scenario: evaluate several possible solutions • Proposal: use heuristics methods (successive analysis to produce a solution) • Syntactic and semantic analysis of the process model Automatic Sys Identification and classification of candidate services Automatable Partially Supported by systems

  15. Service identification • Services can be identified from: • Process flows • Workflow pattern • Recurrent flows of activities existing in different processes • Activities: • Input and output data • Business rule • Business requirement X

  16. Heuristics for candidate service identification • Heuristic 1 (Business Rule) • Heuristic 2 (Business Requirement) • Heuristic 3 (Cluster) • Heuristics for service identification from workflow patterns • Heuristic 4 (Sequence of Activities) • Heuristic 5 (AND) • Heuristic 6 (XOR) • Heuristic 7 (OR) • Heuristic 8 (Loop) • Heuristic 9 (Process Interface) • Heuristic 10 (Multi-Instance Activity) (Van der Aalst et al., 2003)

  17. Heuristic 1 (Business Rule) A candidate service must be identified from a business rule. Stocks of non-automatic tanks Get tank stocks of measurement node Production calculus of Estreito measu…

  18. Heuristic 2 (Business Requirement) A candidate service must be identified from a business requirement. Stocks of non-automatic tanks Get tank stocks of measurement node Production calculus of Estreito measu…

  19. Heuristic 5 (AND) A service candidate must be identified from an AND-pattern. AND-pattern is a structure started in a point in the workflow where a single flow is divided into multiple streams, which can run in parallel, and finalized at a point in the workflow where multiple parallel streams converge into a single flow, synchronizing them, or where branches end in final event

  20. Heuristic 4 (AND) A service candidate must be identified from an AND-pattern.

  21. 3. Consolidation of Candidate Services Principles for high-quality service implementation, organization’s quality criteria Consolidation Candidate utility service

  22. Experimental tests • The method was experimented at Petrobras • The largest Oil Company from Brazil • Business process: Diagnose daily oil production • Important process within the Exploration and Production (E&P) - Upstream area • Process aims at maximizing company results • Real time physical sensor information was used • Part of digital fields project • TO-BE process • 19 activities, control flows, 90 business rules and 37 business requirements

  23. Experimental tests • Step 1) Activity selection • 19 activities were selected • Step 2) Candidate service identification and classification • 147 candidate services • Business rule and business requirement heuristics produced 57% and 30%, respectively

  24. Experimental tests • Step 3) Consolidation of Candidate Services • Service Reuse Degree, Link Candidate Service and System, Link Candidate Service and Demand Requirements, • Link Candidate Service and Activities, • Identify Candidate Services Dependencies, • Candidate Utility Service Identification • No service of this type was identified

  25. Expert feedback • Expert evaluation of resulting candidate services • Consolidated information helped them in service implementation • Identification of reuse and which services to orchestrate • Alignment of service x business needs

  26. Conclusion • Several challenges in SOA • Service modeling, design, monitoring and management • Our proposal • Top-down approach: Services identification from business process models • Set of heuristics • Semantic and syntactic analysis of process elements • Systematic approach • Input: Business process model (TO-BE) • Output: candidate services (classified, described, and consolidated)

  27. Conclusion • This information helps service designer to better design and plan service implementation • Explicit link between business process constructs and service descriptions can be made • Tracking changes from business models that impact IT, • Easier to find which services must be changed for time-to-market.

  28. Ongoing and future work • Ongoing • Development of supporting tool • ARIS (IDS-Scheer tool) • Study of heuristics and tool support for next phases (analysis, design, implementation, deployment and maintenance) • New criteria (performance, service composition, granularity in terms of hardware, bandwidth etc) • Future work • Experimental tests in other domains

  29. A Method for Service Identification from Business Process Models in a SOA Approach ? Thank you! Questions Leonardo Azevedo1,2, Flávia Santoro1,2, Fernanda Baião1,2, Jairo Souza1, Kate Revoredo1, Vinícios Pereira1, Isolda Herlain3 1NP2Tec – Research and Practice Group in Information Technology 2Departament of Applied Informatics, Federal University of the State of Rio de Janeiro 3Petrobras – Petróleo Brasileiro S/A

More Related