1 / 85

MITA UML Training

MITA UML Training. Leveraging best-practices, industry standards, and architecture principles to improve business performance, efficiency, and to reduce cost. 8:30 – 10:00 UML fundamentals What is a model? UML Notation UML Diagrams Model reports + UML vs. BPMN 10:15 – 12:00

chambray
Télécharger la présentation

MITA UML Training

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. MITA UML Training Leveraging best-practices, industry standards, and architecture principles to improve business performance, efficiency, and to reduce cost

  2. 8:30 – 10:00 UML fundamentals What is a model? UML Notation UML Diagrams Model reports + UML vs. BPMN 10:15 – 12:00 From MITA documents to Model MITA process  UML model Model driven architecture and design Mapping MITA concepts to UML Extending UML with Profiles UML Project Deliverables 13:00 – 14:30 Tooling Overview IBM Rational Software Architect/Modeler Websphere Business Modeler Rational Tools Summary Free tools (hyperModel, HL7 MIF, HL7 UML Profile) + 14:45 – 16:00 SOA Revisited Capability-based architecture SOA Principles SOA support for business process model SOA Governance MITA UML Training – Day 1Overview and Deliverables

  3. UML Fundamentals

  4. What is modeling? • Capture the intricacies of real-world situations, to describe the characteristics of real-world objects, their relationships, and the way objects communicate • abstractions and concepts • essential characteristics of real-world objects • An abstraction is a mental process of taking a thing, material (mobile phone) or immaterial (electromagnetic wave), real (person) or abstract (his emotional state), pruning all details that are not relevant for a particular purpose, naming it, giving it a short description to be able to manipulate and work with the abstraction (as a result) issued from this complexity reduction process

  5. Language to express abstractions of reality in a coherent way Standardized language instead of ad-hoc language Graphical language used to design software and web services Related model elements and views Standardized to improve communication Unified Modeling Language (UML) Models

  6. Activity Diagrams Describe workflows Processes Conditions Failures Information flow Process flow Timing TriggerEvent Control flow[condition] Decision Failures Actions Reused Process Object flow[condition] Result Activity Diagrams

  7. Identifies the various ways in which a user interacts with a system or other users Actors, use cases, associations, inclusion Enroll Provider Information relies on Add Update Inquire System Actor Actor Business Use case Infrastructure Use case Use Case Diagram

  8. State is changed when a condition is met Allowed states for a specific business object Useful analysis device to define the behavior of business objects controlled by services Transitions are triggers for other processes or operations Initial state Transition [condition] Object’s state Final state(no further changes are possible) State Transitions with State Machine Diagrams

  9. Invalid request New providerapplication Validrequest Approved request State Transition Diagram: Provider’s Application

  10. Sequence Diagram User role : Actor Type Message/Request System : Business Process System : Service type Return Asynchronous Notification

  11. Sequence of messages Options and alternate flows Two equivalent views View of system behavior Collaboration Diagram

  12. To view information and operations Represents types of information and associations between classes of business objects Edges do not represent data or control flowing Arrows show the direction of navigation This is used to generate XML from a model Class Diagrams - Messages Class of business object Property/Attribute Composition Association (direction) Cardinality/Multiplicity

  13. Interfaces show how the capabilities of a systems are expressed formally Operation Parameter/messages Return types/response Component Diagrams: Behavior/Process Interface Operation (parameter: parameter type…):Response type Stereotype Operation (parameter: parameter type…

  14. service operation UML  WSDL

  15. Model Report Model Report, Presentation UML Model WSDL, XSD

  16. WSDL and BPEL • UML can be used to design web services • UML-to-WSDL • UML Profiles may be used to extend the language to support BPMN • UML can be extended • Where does BPEL fit in? • BPEL allows you to write programs that use web services, and to write programs that are web services • Modelling applications with BPMN • workflow • service orchestration • Transforming BPMN into BPEL • flow • data • services • There are some known issues BPMN mapping BPMN to BPEL(1) • UML can be extended with profiles to map and generate BPEL • BPEL4WS

  17. Representing Business Processes in UML • UML 2 Activity diagram includes all the elements needed to model business processes with two exceptions: • Goals • Measures • UML profiles are used to extend the language using profiles • <<stereotypes>> • Actions, Control, Faults

  18. From MITA documents to Model

  19. MITA in the context of SOA Information Architecture Business Architecture Technical Architecture

  20. Purpose of the MITA Information Architecture • Align information requirements with Medicaid enterprise vision and direction • Improve system effectiveness • Facilitate growth and innovation • Lower overall life-cycle costs • Enable interoperability and data sharing

  21. MITA Information Architecture Neutrality Technology-, organization-, and location-neutral States have the flexibility for their specific implementation Mechanisms to extend MITA to accommodate individual State needs MITA can be extended to support other programs, e.g., behavioral health and waiver programs

  22. Style Guide • Organizes the Development of the MITA Information Architecture (IA) • Enforces MITA IA Development Methodology for consistency • Enables MITA IA Project Management • MITA Governance Platform • MITA Glossary • Automates the development of future MITA framework extensions

  23. MITA Technical Architecture • Can capture Technical Capabilities • Security • Tolerance • Can be used to generate code in a number of languages, including C#, java, and XML

  24. Approach for Service Design • Analyze business process • Identify system boundaries • Define business triggers for each operation • Identify systems and refine integration use cases for specific interactions • Refine HL7 information models • Message payloads • Terminology • Generate computable Service Descriptions (WSDL, XSD)

  25. UML Project Objectives • Applying the MITA business processes • Maturity level 3 • Using Standards (HL7, UML) for information modeling • Model-driven architecture • Manage the model and generate both documents and implementation artifacts from the single model • Developing implementable specifications • WSDL • XSD • Common information and terminology • HL7 Version 3 (www.hl7.org) • Reference Information Model

  26. Using MITA for interoperability • To fulfill the business process several systems must interact • Invoke behavior • Request/response • Query/response • Exchange information • Using a common specification • Semantic interoperability • Common terminology • Common structure • The following slides are views of a single UML model • Class diagrams (information, interactions, structure) • Sequence diagrams (behavior, service use scenarios)

  27. Narrative business process PM Enroll Provider Tier 3: Enroll Provider Item Details Links Description Trigger Event Result Business Process Steps Shared Data Predecessor Successor Constraints Failures Performance Measures Word/PDF document Evolution of MITA from doc …

  28. Narrative business process PM Enroll Provider Tier 3: Enroll Provider Item Details Links Description Trigger Event Result Business Process Steps Shared Data Predecessor Successor Constraints Failures Performance Measures Word/PDF document … to a complete model

  29. Toolboxcustomized ProviderManagement ProviderEnrollment Business Process Model browser Tools Glossary … using UML tools

  30. Model (Project Explorer)  Diagram

  31. How to… • Use the narrative to populate UML business process • Business Process • Details • Dependencies • Import HL7 Version 3.0 information models • shared data/information detail • terminology • Use UML to document the system interfaces • Common interfaces for interoperability • Services based on MITA • By implementing these services the state is aligned with MITA

  32. MITA Business Process Enroll Provider

  33. Tier 3 Business Process Hierarchy

  34. Dependencies

  35. Narrative PM Enroll Provider Tier 3: Enroll Provider Item Details Links Description Trigger Event Result Business Process Steps Shared Data Predecessor Successor Constraints Failures Performance Measures Evolution … Refinement

  36. Business Process

  37. Inquire Provider CheckRules Validation ReceiveRequest Add Provider

  38. Sample Scenario

  39. HL7 Standard Message Structure • Imported from HL7 approved standards

  40. Re-usable Allows us to avoid platform compatibility issues HL7 Data Types Address Identifier

  41. Code Sets HL7 Terminology Validation of messages

  42. Value Sets/Vocabulary Coded concept Value Set Value Set

  43. Service Interfaces - Enroll

  44. Service Interfaces – Provider Registry

  45. Interactions

  46. Web Service Description

  47. WSDL

  48. Benefits… revisited • Common specification • Maximize the reuse of business process and services (Enterprise Business Capability in the context of Service Oriented Architecture) • Interoperability between components developed by different projects or vendors • “plug-and-play” interoperability • TAC Enroll Provider demonstration

  49. Summary of Project Artifacts • Business Process (Activity diagram) • MITA “to be” • Minnesota specific business rules • Business Triggers, system boundaries • Information Model (Class Diagram • HL7-based, standardized vocabulary • Interactions ( Sequence Diagram) • Operations expose business capabilities • Service Specifications • Ports, interfaces, business rules • Used documentation and runtime artifacts • WSDL • XSD

More Related