Patterns & Techniques for Separating Business Logic in New SOA System Development. Iyad Jabri Intelliun Corporation CEO

Transcription

1 Patterns & Techniques for Separating Business Logic in New SOA System Development Iyad Jabri Intelliun Corporation CEO Building a Service Oriented Architecture with BPM & MDA October 16-19, 2006 Burlingame, CA

2 Agenda Object-Oriented Development SOA Development SOA with Model-Driven Development SOA Patterns & Techniques Summary Q&A

3 Object-Oriented Development Non-functional Requirements Functional Requirements Analysis Abstract Design Architecture Implementation Detailed Design

4 Object-Oriented Development Common Scenario Non-functional Requirements Functional Requirements Analysis Textual Document Flowcharts Glossary of Terms Actors Use Cases Interactions Analysis Class Diagram J2EE EJB Servlets/JSP SQL JUnit Architecture Abstract Design Class Diagrams Activity Diagrams Package Diagrams Implementation Detailed Design Java Interfaces SessionBeans & EntityBeans Servlets and JSP s SQL Schema JUnit Tests

5 Object-Oriented Development Example Problem Statement: A practice management system is needed to schedule and track patient visits to a doctor s office. The patient should be able to schedule an appointment, check-in at the doctor s office then check-out and pay the visit fee. A nurse needs to capture the patient vitals and record his/her chief complaint. The doctor needs to view the patient s vitals and medical history, examine the patient and record the diagnosis and prescribed treatment.

6 Object-Oriented Development Use Case Analysis Business Use-Case: Manage Patient Visits A patient calls the doctor office and asks for an appointment The office manager reviews the doctor s calendar and schedules an appointment for the patient The patient visits the doctor s office, signs in with the office manager, then fills in a patient intake form The office manager enters patient intake form into the system and queues the patient for the nurse The nurse picks the next patient in the queue and captures his/her vitals and records the chief complaint. The doctor visits with the patient, reviews the patient record then establishes the diagnosis and treatment. The patient checks out with the office manager and pays the visit fee

7 Object-Oriented Development Use Case Model View Doctor s Calendar Schedule Appointment Record Patient Vitals and Chief Complaint Nurse Check-in Patient View Patient Record Office Manager Manage Patients (CRUD) Generate Visit Invoice Record Diagnosis & Treatment Doctor Apply Patient Payment

8 Object-Oriented Development Analysis Class Diagram -owner Doctor Appointment * 1 Calendar -calendar 1 -calendar -appointments 1 * -doctor Ledger 1 -ledger 1 -ledger * -transactions -patient 0,1 Patient 1 -owner Invoice -patient 1 -visit 0,1 * -visits Visit 1 -visit * -details * -visits Transaction VisitDetail Payment

9 Object-Oriented Development Abstract-Design Class Diagram

10 Object-Oriented Development Abstract-Design Class Diagram Create a Visit Add Visit to Patient s visits Invoke Visit s queue() Update status Create an Invoice Derive Invoice details based on Visit Add Invoice to Ledger Create a Payment Add Payment to Ledger

11 Object-Oriented Development Requirement Change 1 Calendar -calendar Different doctors setup their practices differently: -calendar +schedule() 1 Collect payment on patient check-in -owner Doctor -doctor Create a Visit Add Visit to Patient s visits Invoke Visit s queue() Appointment +checkin() * -appointments «singleton» Practice listqueuedvisits() 1 -doctors * * Ledger 1 +add() -ledger 1 -ledger * -transactions -patient 0,1 * -patients Patient -patient 1 1 -owner Invoice -visit 0,1 * Visit +queue() +update() +checkout() 1 * -visits -visit -details * -visits Update status Create an Invoice Derive Invoice details based on Visit Add Invoice to Ledger Create a Payment Add Payment to Ledger Transaction VisitDetail Payment checkin() and checkout() has Process Logic

12 SOA Development Principals Agility Business Driven Approach Service Orientation Service Encapsulation, Autonomy and Reuse Service Composition Service Configurability Service Loose Coupling

13 The Architecture in SOA Service Definitions Business Processes (Composition and Orchestration) Complexity of Change Administrator System Integrator Developer Components (Service Implementations) Rules (Simple Rules) Rules Business Processes Components

14 SOA Development Non-functional Requirements Functional Requirements Analysis Architecture Service Definitions (including metadata and operations) Business Processes Rules Component Specs Buy or Implement Components Abstract Design

15 SOA Development Abstract Design

16 SOA Development Abstract Design Service Composition & Orchestration Service Implementation

17 SOA Development Implementation (Today) Service Implementation Traditional server-side development Service Composition & Orchestration Business process and workflow modeling XML manipulations and transformations User interface development (e.g. web development) Human interaction and usage flow Graphics design and GUI components Usability Logic (bridging the gab between coarse grain Web services and usability needs) Mixed Development/Mixed Skills

18 SOA Development Implementation with MDD? Service Implementation Traditional server-side development Service Composition & Orchestration Business process and workflow modeling XML manipulations and transformations User interface development (e.g. web development) Human interaction and usage flow Graphics design and GUI components Usability Logic (bridging the gab between usability needs and coarse grain Web services) Mixed Development/Mixed Skills

19 SOA Development Implementation with MDD?

20 SOA Development Implementation with MDD? public void addcpts( String[] codes ) { for( String code : codes ) { VisitDetail detail = new( VisitDetail ); detail.cptcode = code; this.details.add( detail ); } } * +notes 1 -visit Visit +addcpts() +addattachment() +addnote() #listdiagnosis() 1 -visit -visit 1 * +attachments public void addnote( String subject, Text details ) { Note note = new( Note ); note.subject = subject; note.details = details; note.author = User.current().id; note.timestamp = Timestamp.now(); this.notes.add( note ); } Note * +details Attachment +subject +details +author +timestamp +delete() VisitDetail +cptcode +diagnosis +delete() +subject +content +author +timestamp +delete() public String listdiagnosis() { return details->diagnosis.distinct().sorted(); }

21 SOA Development SOA and Model-Driven Development (MDD) MDD MDD

22 SOA Development SOA and Model-Driven Development (MDD) Interface Layer Resource Layer Application Logic Layer Services Bus Service Implementation Service Composition & Orchestration Interface Layer Resource Layer Application Logic Layer

23 Separating Logic in SOA/BPM/MDD The Problem Complexity of Change Administrator System Integrator Developer Rules Business Processes Components Push the Logic

24 Separating Logic in SOA/BPM/MDD Patterns & Techniques Business Processes Logic Flow Business Process Minimize business specific flows in the Service implementations Loose Service Coupling Minimize invoking one service from the implementation of another Usability Features Minimize service operations that are geared toward fine grain end-user usability features

25 Separating Logic in SOA/BPM/MDD Patterns & Techniques Business Processes Workflow User Tasks Management Extract all task assignment and task list management requirements from Service implementations Notification s, paging, etc. should be kept in the workflow Escalation Giving task control to another resource when a certain condition occurs (e.g. after a set time) belong in the workflow Call for Action (e.g. Approvals) Call to review, approve, decline, etc. should be separated from the service implementation and managed in the workflow

26 Separating Logic in SOA/BPM/MDD Patterns & Techniques Rules Parameter Rules Limit Values For example if a credit score must be greater than 600, or a student GPA higher than 3.0 Breakpoint Values For example different number of signatures (approvals) required for loans between $0-$4,999; $5,000-$9,999; $10,000-$99,999; and $100,000 and above Units and Scales Measurements, currency, etc. Algorithms and strategies For example encryption, search, domain-specific algorithms, etc.

27 Separating Logic in SOA/BPM/MDD Patterns & Techniques Rules Complex Rules Decision Rules using a Rule Engine Complex rules can be represented as services

28 Summary SOA brings new ingredients to component architecture that better its chances of success MDD offers a unified approach to SOA It s important to extract and separate rules and processes from service implementations to maximize reuse and agility It s important to maintain separation between interface and application logic

29 Questions & Answers Q&A