UNISYS BUSINESS BLUEPRINTS.

Transcription

1 UNISYS BUSINESS BLUEPRINTS. Model-driven Architecture and Enterprise Integration A Western Australia Case Study David M Bridgeland Chief Technology Officer Global Transformation Team Unisys September 2003 Systems Integration. Outsourcing. Infrastructure. Server Technology. Consulting.

2 Breaking the rules? Unisys Business Blueprints Case Study: Western Australia Department of Justice Model-driven architecture MDA and enterprise integration 2

3 Background: a history of requirements melt Freeze the requirements, then build it Iterative processes Rational Unified Process Multi-year construction plans Long gap between requirement freezing and delivered system Slow feedback to system stakeholders Little responsiveness to changing conditions High failure rate Expensive mistakes Iterations (or versions) every months Requirements frozen until the next iteration Adapts to slowly changing requirements 4 6 week iterations Multiple iterations through elaboration and construction Requirements gradually frozen through construction Even more flexibility But complexity scares off some Extreme Programming 2 week iterations Requirements frozen for eight days Adapts well to changing requirements But does not scale to larger efforts 3

4 Our clients face agility challenges Hard to get new products and services out the door quickly Organizational silos, redundant processes, and changing business process is extremely difficult and costly Continued challenges integrating existing with emerging technology applications Governance between IT and business is confusing and complicated. Gap exists between business requirements and technology delivery 60-80% of functionality is redundant and in silos Difficulty in seeing, much less getting, value out of IT investments 70% of IT spending on maintenance and redevelopment 4

5 Introducing Business Blueprints Business Blueprints are a set of Tools, methods and libraries of Organizational patterns, business processes components and technology implementation options That allow a client to build or modify business processes quickly and predictably Bringing the concept of blueprinting to the arena of high-volume, mission-critical systems Expressed in industry standard formats (BPEL, UML) Traceability between business and technology models is the critical value 5

6 Blueprint: all of the intellectual property of an application Business Architecture Vision and Operations Model Characterization of organizational domain including objectives, structure, organizational measures, and competitive framework Business Process Model and Patterns Characterization of the operational requirements and key business processes Functional and Application Model Key functions implemented as a set architectural models (UML) representing core services Infrastructure Model Services Based Technical Architecture Characterization of the deployment services and technologies to realize the objectives. Key functional services (web services) that are provided to all applications in the organization (Security, Network, Application Server, Data Services, Integration Services, Administration) 6

7 UML is not enough BPEL, etc. The UML is a standard language for writing software blueprints. Grady Booch et al, But UML is missing some things: Alignment Chasm UML Business processes Business process simulation Goals Strategies Trends Business interaction Organizational context Organization structure Locations 7

8 Traceability of models is key A business process changes: what use cases are affected? A use case changes: what classes are affected? A class changes: what components are affected? Traceability of Models is the Key!! A component changes: what server clusters are affected? Or backwards, for reverse traceability 8

9 What s unique about Blueprints? Representing the intellectual property as a set of models (UML + others) Combining the intellectual property with the application Maintaining the models with the app Traceability Reverse traceability 9

10 Blueprints in action Unisys has Business Blueprints currently in development, supporting mission-critical applications for: Justice and Public Safety Health and Human Services Integrated Registry Tax and Revenue Life Insurance and Pension Property and Casualty Enterprise Payments Banking and Mortgage Airline Core Systems Safe Commerce 10

11 Western Australia Dept of Justice Blueprint Initiatives Client: Western Australia Department of Justice Responsibility: Criminal and civil justice in the state of Western Australia (1 million square miles, 2 million people) Challenge: Replace 14 legacy systems that manage court administration: Case management for civil and criminal jurisdictions Scheduling cases with judges and courtrooms Managing change in the schedules Tracking case outcomes Tracking financials, including fines and enforcement Current status: Civil court management deployed Legacy civil court management systems retired Criminal court management system in progress US $5 million 11

12 Many courts at three different levels Supreme Court Every court is run differently District Courts Magistrate Courts Variety in business processes Variety in business processes Different business processes also reflect differences in local legal cultures Goal: run the courts on the same application 12

13 Why Blueprints? Adapt to to changes in in legislation Adapt to to changes in in demand by by the the public Adapt to to changes in in technology Adapt to to changes in in business processes 13

14 Blueprints enabled an MDA approach UML models.net code More than 80% of the code is automatically generated from the models The maintenance is done on the models, rather than the code This model-driven architecture (MDA) approach directly supports agility and flexibility 14

15 ICMS architecture ICMS Design ICMS Design ICMS presentation ICMS Server Framework.Net Server.Net Server MDA generation Low bandwidth connection ICMS business logic logic ICMS Client Framework.Net Client.Net Client Designed (in UML) Auto-generated (VB.Net) Developed (in VB.Net) Supplied (by Microsoft) 15

16 The architecture supported local variety and complexity The UML differed from level to level At a single level, the UML differed from court to court The system was tailored for each court The impact of the differences could be minimized District Courts Magistrate Courts Supreme Court Variety in business processes Variety in business processes 16

17 Late requirements changes emerged When implementation was completing, the client discovered key functionality was missing. Examples were: Multi Jurisdictional Security Enhanced Wizards for Document Lodgment Enhancements to Case Management Workflow Most new requirements led to UML model changes New.Net code was generated; little hand generated code was written Coding would take around 4 times longer without MDA, other activities (i.e. analysis etc) remain unchanged With Blueprints (actuals) Without Blueprints (estd) $1 million $3 million 26 weeks 77 weeks 17

18 MDA is real today Benefits: See early versions of the production system Quickly see the results of changes Flexibility for future changes A consistent look and feel across your application A consistent architecture style The ability to make application-wide performance improvements Achieve the benefits of vendor products without vendor lock-in Support multiple platforms Consistent integration among multiple systems UML models that always match your application An application architecture that is no more complex than it needs to be All of these benefits are achievable with other approaches; only MDA bring them together seamlessly. 18

19 Enterprise application integration can be expensive The technology is well understood, but Much development and configuration time Intellectual property reconstruction Business workflows Use cases Application logic Constraints Organizational relationships Organizational structure Strategies Goals Trends Over and over again: For each of the integrated apps For each integration Eligibility Determination 1985 Welfare Management System County Assistance Electronic Case Folder Inbound Imaging Outbound Record Archival Fair Hearings System 1997 The cost is systems archaeology 19

20 As MDA becomes widespread, EAI becomes easier Up-to-date complete UML for applications Archaeology is unnecessary Semantics that should be the same, actually are Semantics that are different can be mapped UML can drive the EAI configuration MDA Penetration Starts 10% 30% 60% COTS Support A few Some Most Legacy Tooling Starts 10% 25% MDA-driven EAI Starts Common 20