Simulating Enterprise Architecture Models


Published on

This presentation provides an overview of a simulation language and an accompant

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Simulating Enterprise Architecture Models

  1. 1. Simulating Enterprise Architecture Models Balbir S. Barn, Tony Clark (Middlesex University) and Samia Oussena University of West London) ISEC 2012, Kanpur, February 2012
  2. 2. Agenda <ul><li>Problems with Enterprise Architecture (EA) </li></ul><ul><li>EA overview and related work </li></ul><ul><li>Concepts for a light-weight method for EA </li></ul><ul><li>The EA method </li></ul><ul><li>Case study </li></ul><ul><li>Conclusions </li></ul>
  3. 3. EA overview (definitions and use cases) <ul><li>“ it is a coherent whole of principles, methods, and models that are used in the design and realization of an enterprise’s organizational structure, business processes, information systems and infrastructure” (Lankhorst et al) </li></ul><ul><li>The uses of EA include: </li></ul><ul><ul><li>alignment between business functions and IT systems </li></ul></ul><ul><ul><li>business change describing the current state of a business (as-is) and a desired state of a business (to-be) </li></ul></ul><ul><ul><li>Ensuring quality (e.g. security, performance) </li></ul></ul><ul><ul><li>Acquisition and merger planning </li></ul></ul><ul><ul><li>Regulatory compliance </li></ul></ul>
  4. 4. EA overview (2) <ul><li>Origins in Zachman’s Framework (1999) </li></ul><ul><li>Today often described by large fulsome frameworks such as: TOGAF, DODAF, FEAF </li></ul><ul><li>Accompanying methods are proprietary (e.g. ORACLE, IBM) </li></ul><ul><li>Some emerging DSLs for EA </li></ul><ul><ul><li>Notably Archimate (ref): concepts and supporting notation </li></ul></ul>
  5. 5. A missing piece <ul><li>How does an EA change to meet a new business requirement? </li></ul><ul><ul><li>What impact on what systems? </li></ul></ul><ul><ul><li>Support for an equivalence analysis needed </li></ul></ul><ul><li>The current methods and frameworks use layered architectures and do not readily support this type of analysis </li></ul><ul><li>Existing emphasis on SOA as an architectural style </li></ul>Simulation: Try it and see. A means for meaningful human intervention
  6. 6. Combining SOA with Event driven architecture <ul><li>Service Oriented Architecture (SOA) </li></ul><ul><ul><li>Publication of functionality as interfaces </li></ul></ul><ul><ul><li>Interface usage via components (asynchronous/synchronous) </li></ul></ul><ul><li>Event driven architecture (EDA) </li></ul><ul><ul><li>Components are event generators and consumers (reduced coupling) </li></ul></ul><ul><ul><li>Scope for Complex Event Processing (business processes triggered by multiple, possibly temporally related events. </li></ul></ul><ul><li>Combining both approaches provides greater expressivity for dealing with a complex domain such as EA </li></ul><ul><li>This paper addresses the method requirements for this combined approach </li></ul>
  7. 7. Key features of the language
  8. 8. Method Overview <ul><li>Existing methods are: </li></ul><ul><ul><li>Large, cumbersome, lacking in agility and precision. </li></ul></ul><ul><li>The LEAP Method: </li></ul><ul><ul><li>Has two streams for “as is” / “to be” modelling </li></ul></ul><ul><ul><li>Utilises existing, best of breed modelling techniques </li></ul></ul>Step 4: Model Requirements Define Logical EA Collate Physical Architecture Define Physical EA Define Conformance and Simulate Configure Physical Architecture To be Analysis As Is Analysis New DSL Technology incorporating: Integrated model for services, events and simulation Utilize established techniques such as CRC, Use Case Models, Use Case Maps, UML … Business use case model; Information model; Business process model; Context Diagram Current components Candidate Physical EA Candidate Logical Components Simulation Logical EA (Components, Interfaces, Events) Refined Logical EA Simulation Physical EA Scope phase Simulate phase Candidate Physical EA Step 1: Step 2: Step 3: Step 5: Step 6:
  9. 9. Case study <ul><li>UK Gov requirements on HE Institutions </li></ul><ul><li>Provision of key information to help students make decisions on choice of university to study </li></ul>
  10. 10. Step 1: Model Requirements <ul><li>Use existing techniques such as those from Catalysis [ref], RUP and Ould [ref] to produce models such as: </li></ul><ul><ul><li>Context models </li></ul></ul><ul><ul><li>Information Models </li></ul></ul><ul><ul><li>Component Specifications </li></ul></ul>
  11. 11. Step 2: Define Logical Enterprise Architecture (L-EA) <ul><li>A key feature of our approach is to simulate both a logical and physical EA in terms of components, operations and events. </li></ul><ul><li>Simulation language implemented as Java interpreter </li></ul><ul><li>Components monitor events raised by registered components </li></ul><ul><li>Components maintain private state (terms – named records) </li></ul><ul><li>Invariants are boolean expressions defined over the state </li></ul><ul><li>Operations implement business processes </li></ul><ul><li>Rules: a collection of patterns that match terms and events. When all the patterns are matched the rules fire. </li></ul><ul><li>The body of the rule is an action that modifies state or invokes operations </li></ul>
  12. 12. Step 2 cont’d: The University component State Rules Invariants
  13. 13. Using Simulation <ul><li>Our LEAP language that supports the method also include features for generating a GUI on a web browser </li></ul><ul><li>The Control section is used to step through the simulation by sending tick messages to the clock </li></ul>
  14. 14. Using Simulation
  15. 15. Step 3, 4: Collating and Configuring Physical EA <ul><li>Use of existing system overviews to identify organisational systems </li></ul><ul><li>Configuring a Physical EA involves taking an appropriate slice of the EA to that includes just those systems that are likely to be required by the “to be” requirements </li></ul><ul><ul><li>Techniques such as Use Case Maps can be used. </li></ul></ul>
  16. 16. Step 5: Define Physical EA <ul><li>Identified slices of the required components are expressed in LEAP </li></ul>
  17. 17. Step 6: Conformance <ul><li>Our EA design method produces: </li></ul><ul><ul><li>A context, logical and physical EA using the LEAP language </li></ul></ul><ul><li>A single unifying language provides the means to establish conformance between logical and physical models </li></ul><ul><li>The language can be used to support techniques such as: </li></ul><ul><ul><li>Inspection based approaches </li></ul></ul><ul><ul><li>Mappings between physical and logical models </li></ul></ul><ul><ul><li>Simulation </li></ul></ul><ul><ul><li>Model checking and theorem proving </li></ul></ul>
  18. 18. Conclusion <ul><li>Enterprise Architecture remains a confusing and constantly evolving collection of expansive methods and frameworks that are document based </li></ul><ul><li>This paper has presented an effort to address the core use case “managing change and impact assessment” </li></ul><ul><li>Our effort includes: </li></ul><ul><ul><li>A Lightweight method utilising existing techniques </li></ul></ul><ul><ul><li>An accompanying language that supports precise specifications of “as is” and “to be” models </li></ul></ul><ul><ul><li>A simulation environment for supporting meaningful human intervention </li></ul></ul>
  19. 20. Research areas in MDSE@mdx Model driven software engineering User Modelling Enterprise Architecture Complex Events and Big Data Tool Modelling Modelling for Theory Building Methodology Events Foundations Tools and Technologies: DSL Building Tools: XModeller
  20. 21. World Skills 2011: UK Prime Minister David Cameron <ul><li>Product Design Engineering students </li></ul><ul><li>UK Skills Gold Winners </li></ul><ul><li>Euroskills Bronze Winners </li></ul><ul><li>Balbir/WorldSkills London 2011.m4v </li></ul>