1. Slide 1 Business Modelling: OMG - EDOC Bringing together business goals, standards, processes and technologies for the e-enabled enterprise Enterprise Distributed Object Computing

2. Slide 2 Integrating Enterprises, People & Systems - Worldwide Using Internet Technologies Enabling e

3. Slide 3 Integrating Enterprises, People & Systems - Worldwide Business Requirements Virtual Enterprises Enterprise Integration (EAI) Supply-chain automation (B2B) Customer Integration (B2B) Web deployment (B2C) Internet Marketplace (B2C) Collaboration and Integration

4. Slide 4 The dynamic reality The information system must facilitate; Rapid realization of business goals Integration of independent processes and systems Multiple and Changing business requirements business processes technologies standards enterprise boundaries partners

5. Slide 5 The e-enabled enterprise Has a competitive advantage in its capability to embrace collaboration and change

6. Slide 6 Components Workflow Repositories Metadata OpenCollaborativeEnterprise Embracing collaboration and change Model Driven Architecture Shared Data EAI We need to extract the meat from the buzzwords And figure out how these concepts fit together To e-enable the enterprise Web Services Middleware Messaging & Events

7. Slide 7 Business & Technology Coupling “Open B2B” Ad-hoc business “Community B2B” - Business Partners & Independent Divisions Integration within a managed domain Integration or production of an application Internet Computing Model ebXML Soap Events & Messaging JMS MQ-Series Synchronous Transactional RPC Corba EJB Shared Data SQL IMS-DB Collaborative Components EDOC Model (UML) Traditional EDI

8. Slide 8 The role of open systems in the enterprise Supporting open distributed computing while meeting local requirements

9. Slide 9 The Enterprise “The Enterprise” The “open domain” Independent domains collaborating via open standards No assumption of “the same thing” on both sides! Appropriate inside and outside the enterprise (EI & B2B) Requires business (process collaboration and information) and technical (middleware) standards The open domain needs a point of ownership in the enterprise Enterprise boundaries are not static!

10. Slide 10 The Internet Computing Model Collaboration of independent entities Document exchange over internet technologies Large grain interactions No required infrastructure * Long lived business processes Business transactions Business Party Business Party Portals

11. Slide 11 Requirements for the “ICM” Contract of Collaboration Shared business semantics Meta-Model (EDOC-ECA) and representation (I.E. XMI, ebXML- BPSS) Shared Repository for Contracts (MOF, UDDI, ebXML) Connectivity (middleware) which meets requirements of the contract Implementation of each contract role providing connectivity (application server) Business Partner Business Partner Repository Contracts (Metadata) Contract of collaboration can be mapped to the format of various technologies. (ebXML, Soap,.NET) Instance Data

12. Slide 12 Two levels of interoperability Instance data and interoperability Metadata (contract) interoperability Business Partner Business Partner Bridge Each can be transformed Purchasing Model.NET ebXML BPSS ebXML Biztalk Normal Form Over Soap

13. Slide 13 Drilling down – inside a role The open domain should make no assumptions about the “inside” of a role. Inside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used Until you get to system inside a managed domain Shared resources (DBMS) Common Management Frequently a legacy system Inner Role Legacy Inner Role Inner Role Domain Cust

14. Slide 14 Collaborative Business Semantics Defined: The processes, information and contracts of interaction between collaborators within a community Collaborative business semantics are a valuable long-term asset Captures information and process Requires ownership and support in the open domain Do not put this valuable asset in a (transient - one size fits all) technology specific form Use technology independent models (MDA) Map to the technology of the day (E.G. DTD)

15. Slide 15 Required support for the open domain Connectivity standards and infrastructure Providing the enterprise “bus” (Intranet) http, Soap, ebXML Common processes and lexicon What goes on the bus - the real business value! Facilitating communities of practice Meta-model standards (UML, ebXML-BPSS, EDOC...) How to represent shared processes and information Repositories Finding services, models and components for design time and runtime integration

16. Slide 16 Standards for Global Internet Computing UML4EDOCUML4EDOC SOAP WSDL XML XML-Schema.NET BPML

17. Slide 17 XML Standards XML Schema & DTD Description and packaging of data Soap Basic messaging and packaging Extensions for Soap-RPC with WSDL May be extended to support collaborative messaging

18. Slide 18 Vision EDOC (a UML Profile) Provide an architecture for open collaborative computing Simplify the development of component based distributed systems by means of a modelling framework, based on UML 1.4 Provide a platform independent, recursive collaboration based modelling approach supporting multiple technologies. Embrace Model Driven Architectures (MDA) – Provide design and infrastructure models and mapping ebXML Creating a single global electronic market Includes process specification, transport and repositories

19. Slide 19 ebXML & EDOC Transport Distribution Repository Runtime Enterprise Integration Components Information Model MDA Collaboration Process Model ebXML EDOC

20. Slide 20 Standards for collaboration EDOC-ECAebXML-BPSS Business CollaborationsYes – Community ProcessYes – Multi Party Collaboration Contract of InteractionYes – Protocol with Choreography & Object Interface Yes – Binary Collaboration with Choreography and Business Transactions Content ModelYes – Document ModelUses external forms, such as XML Schema Recursive CompositionYes – Recursive Composition into Enterprise No – Only “B2B” Detail sufficient to drive communications No – Requires technology mappingYes – As ebXML transport. BPSS includes timing and security parameters. Computing Models SupportedInternet document exchange, entities, business processes, objects and events Internet document exchange

21. Slide 21 Parts of EDOC Enterprise Collaboration Architecture (PIM) Component Collaboration Architecture Business Process Specification Entities Business Events Patterns Technology Mapping (PSM – in progress) Flow Composition Model (Messaging) EJB & Corba Components ebXML.NET Others… MAPPING – Precise models are are source code

22. Slide 22 XML Corba EJB.NET Events HTTP Web Server Applications Enterprise Architecture SQL DBMS, Client/Server & Legacy Applications Client Applications EAI Applications & B2B E-Commerce Web Browser Supply Chain Enterprise Components

23. Slide 23 Parts of ebXML Business Process Specification (Like EDOC-CCA) XML Representation of business process Core Components Business Data Types & documents based on context Collaboration Protocol Profile What business partners implement what business processes using what technologies One-One agreement for doing business Transport Routing & Packaging Messaging Built on Soap Registry & Repository Finding business partners, document and process specifications

24. Slide 24 ebXML Architecture BP Specification Business Process Core Data Blocks Business Messages CPA Context ForBuilt With Implement one Partner Role Implement other Partner Roles Register Designtime CPP Transport Package Business Service Interface Internal Business App Business Service Interface Runtime

25. Slide 25 Summary of points thus far We must enable the emerging Internet Computing Model Loosely coupled roles exchanging documents based on a contract of collaboration Web need interoperability at two levels Messaging for the data Metadata for the contract of collaboration, stored in repositories This model of collaborating roles is recursive, extending into the enterprise, into managed domains and into applications Inside the enterprise we want to include resources entities, business events and business processes Supporting the open domain has some required parts and can be augmented with a “treasure chest” of tools and infrastructure Between EDOC & ebXML we are covering B2B and intra enterprise

26. Slide 26 EDOC Component Collaboration Architecture The model of collaborative work

27. Slide 27 The Marketplace Example Mechanics Are Us Buyer Acme Industries Seller GetItThere Freight Shipper Order Conformation Ship Req Shipped Physical Delivery Delivered Status Process Complete

28. Slide 28 The Seller’s Detail Order Conformation Shipped Ship Req Shipped Delivered Order ProcessingShipping Receivables Event

29. Slide 29 Parts of a CCA Specification Structure of process components and protocols Process components, ports, protocols and documents Class Diagram or CCA Notation Composition of process components How components are used to specify components Collaboration diagram or CCA Notation Choreography Ordering of flows and protocols in and between process components Activity Diagram

30. Slide 30 The Community Process Identify a “community process”, the roles and interactions Protocol

31. Slide 31 Protocols

32. Slide 32 Composition

33. Slide 33 ECA Entity Profile The model of things Data Inside a “shared domain ”

34. Slide 34 Adding Entities Entities are added to manage entity data Entity Roles are managers that provides a view of the same identity in another context The Entities have ports for managing and accessing the entities Non-entities which are owned by (aggregate into) an entity are managed by the entity

35. Slide 35 ECA Business Events The model of when… Loosely coupled integration within the enterprise and with “aligned” business partners

36. Slide 36 Business Process Business Entity Business Rules Business Events Business Actions Business Process Business Entity Business Rules Business Events Business Actions Event Based Business Processes Event Notification

37. Slide 37 App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions Point to point Event Notification Event Notifications

38. Slide 38 App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions Pub/Sub Pub/Sub Event Notification

39. Slide 39 Event Example

40. Slide 40 Vision Building and adapting systems for collaboration, reuse and change

41. Slide 41 Business Component Marketplace The business component marketplace is projected to be a 10b market in 5 years Consider the value of XML components that wrap popular legacy New application functionality built from components Components for integration and transformation XML and web services makes an excellent basis for such components Technology components, such as for repositories and DBMS Marketplace my be inside the enterprise or commercial

42. Slide 42 OMG Model Driven Architecture (MDA) High level – platform independent models Technology Models Mapping Custom Standard Standard Models produce technology specific standards artifacts

43. Slide 43 Automated MDA Profile (E.G. EDOC) Framework & Infrastructure (E.G. XML) InfrastructureMapping Mapping is tuned to the infrastructure Tools Produce & Integrate EnterpriseComponents UMLDesign

44. Slide 44 Technology Independence Business Logic Component ebXml Business Logic Component BizTalk Business Logic Component RosetaNet Business Logic Component Ejb Adapters EJB Business Logic Component ebXml BizTalk Rosetanet Adapters CICS EJB MQ Corba

45. Slide 45 Iterative Development Build Release Build Deploy Business Model Design Infrastructure Development Automation

46. Slide 46 High level tooling & infrastructure MUST BE SIMPLE! We must be able to create better applications faster We must separate the technology and business concerns, enable the user Tooling + Infrastructure Executable models are source code Tooling must be technology aware Infrastructure must support tooling, not manual techniques Model based component architectures

47. Slide 47 High level tooling & infrastructure MUST BE SIMPLE! We must be able to create better applications faster We must separate the technology and business concerns, enable the user Tooling + Infrastructure Executable models are source code aTooling must be technology aware Infrastructure must support tooling Model based component architectures Executable Models

48. Slide 48 Net effect Using these open standards and automated techniques we can; Achieve the strategic advantage of an open and flexible enterpise Produce and/or integrate these systems FASTER and CHEAPER than could be done with legacy techniques Provide a lasting asset that will outlive the technology of the day

49. Slide 49 Typical Requirement B2B Buyer Web Service Seller Buyer Web Page HTML Seller

50. Slide 50 B2B Buyer Multi-tier implementation Buyer Web Page HTML Buyer Proxy Web Service Seller Could have multiple implementations using different technologies Could have multiple implementations using different technologies

51. Slide 51 Legacy Seller Applications Event Cloud B2B Buyer Multi-tier implementation Buyer Web Page HTML Buyer Proxy Web Service Seller Event Implementing seller using events

52. Slide 52 Model Driven Architecture Automating Design To execution

53. Slide 53 MDA Overview Use high level UML models made precise with profiles With technology specific mappings To produce substantial parts of the executable system

54. Slide 54 Models and mapping Specification Implementation Solution Provisioning BXS map Platform-specific artifacts (IDL/DTD) Platform Independent Model Versioned repository Business Model UML/CORBA UML/EJB XML OAG SOAP ebXml RosettaNet Legacy Management Over Time

55. Slide 55 Model to Deployed Artifacts Map source Automated platform-specific process object module application runtime compile package assemble deploy Supplier-Specific artifacts overrides Process control parameters Configure map Select Tools Locate Resources Platform-specific Process steps artifacts

56. Slide 56 Generated Artifacts Implementation Artifacts (EJB Examples) Java Source Class Objects Stubs, Skeletons, Helpers, Holders, Interfaces Jars,Wars,Ears BeanInfo,Editors.. Business Object Implementation Logic Homes, Managers, Primary Keys SQL Descriptors Documentation M0/M1 XMI/DTD Serialization, Persistence Management Artifact generation involves multiple tools EJB Container provider;Deployment tools;Packagers; java development tools(IDE);persistence provider;… Typical 10-20 per PIM Classifier 0-20% manual override

57. Slide 57 PIM Reverse Engineering model navigation process disposition algorithms Production rule engine Native artifacts Native meta-model is platform-specific XML DTD/Schema; java introspection; SQL tables; legacy model; etc. Map navigates the native meta-model, populates PIM Limited semantic recovery Information and middleware models work best

58. Slide 58 MDA and Components Specification Implementation Solution Provisioning BXS Platform Independent Model Business Model Direct Execution Components

59. Summary of MDA benefits Isolates domain specifications from platform details Reduces complexity Preserves domain model semantics Increases stability and lifetime Generates to platform/legacy of choice Decreased development time fast iterative development separation between the engineering and business requirements Increased quality. Builds on industry directions DomainSpecifications MDA Users

60. Slide 60 Goal Understand human mind. Difficulty Minds are unobservable Minds differ human from other animals. It is not comfortable to make research on it. Benefits Help us understand ourselves more Help to write software requirement specifications.

61. Slide 61 What is mind? Cognitive Science hopes to explain mind in terms of low- level neural events. Measure electrical and chemical changes in the brain as it performs various tasks Explain mind in terms of such things as synaptic dynamics and brain modularity Authors attack this approach as ridiculous as predicting the weather based on the known behavior of gas molecules. My different thoughts

62. Slide 62 What is mind?- 2 Social-psychological science tries to explain mind in terms of social interactions. Minds come from evaluating, comparing, and imitating one another, from experience and emulating the success behaviors of others. My different thought. How to explain inventions, such as integral, relativity theory. Wolfram secludes himself for 10 years to write the book

63. Slide 63 Assertions Minds are social Human intelligence results from social interaction Culture and cognition are inseparable consequences of human sociality. Culture emerges as individuals become more similar through mutual social learning. What is the relation between society and culture? Particle swarms are a useful computational intelligence(soft computing) methodology.

64. Slide 64 Social learning Theory: Bandura Arisen out of reinforcement theories of behaviorism Human is different from other animals. Human can learn skills and behaviors by observations Remnant of reinforcement theory: people are more likely to imitate models whose behavior is rewarded Why do so many criminals do the same crimes shortly after they are released from prisons?

65. Slide 65 Social learning theory: more Two advantages: Information Punishments are more impressive than rewards Motivation Sources Own experience Other ’ s experiences (vicarious experience)

66. Slide 66 Formation of culture Spread of influence When the influence reaches enough people, a culture is born

67. Slide 67 What is culture? Kroeber, A.L., & Kluckhohn, C. (1952). Culture: A critical review of concepts and definitions 161 variation of culture definition was listed. " Culture consists of patterns, explicit and implicit, of and for behavior acquired and transmitted by symbols, constituting the distinctive achievements of human groups, including their embodiments in artifacts; the essential core of culture consists of traditional (i.e. historically derived and selected) ideas and especially their attached values; culture systems may, on the one hand, be considered as products of action, and on the other as conditioning elements of further action."

68. Slide 68 Culture ’ s influence on individuals Individuals ’ reasoning depends on their culture Explanations on the different history of science in China and The West. Different reasoning styles:

69. Slide 69 Reasoning styles in China and the west ChinaWest Principle of Change: Reality is a dynamical, constantly-changing process. The concepts that reflect reality must be subjective, active, flexible. Law of Identity Everything is what it is. Thus it is a necessary fact that A equals A, no matter what A is Principle of Contradiction Reality is full of contradictions and never clear- cut or precise. Opposites coexist in harmony with one another, opposed but connected Law of Noncontradiction No statement can be both true and false. Principle of Relationship To know something completely, it is necessary to know its relations, what it affects and what affects it. Law of the Excluded Middle Every statement is either true or false. There is no middle term.

70. Slide 70 Human behavior 1: Group Polarization Risky shift Phenomenon Old belief: Groups make more conservative choices that individuals. Experiment result: Group decisions are more extreme than individual decisions. The individuals really changed their views after group discussions. Caution Shift phenomenon was found later. Group Polarization: Groups tend to exaggerate the opinions of the individuals. Question: Do we need to change the jury system?

71. Slide 71 Explanation of Group Polarization Persuasive argument Individuals change their views because they are exposed to a greater number of arguments in favor of one position Normative argument In order to get other members ’ recognition or approval, individuals tend to shift their view towards the extreme. Particle swarm theoretical argument Social learning and influence tends to make individuals to try more extreme positions to get optimized results.

72. Slide 72 Human behavior 2: Self-Esteem People tend to seek behaviors and situations that help them value themselves positively and to avoid those that make them feel bad about who they are. High self-esteem helps the individual deal with stress and other negative emotions and improves their confidence and persistence to achieve their goals Low self-esteem makes the individual depressed and less confident and easy to give up their efforts.

73. Slide 73 Explanation of self-esteem Self-esteem is a measure of how well the individuals are accepted by their social group. Self-esteem can facilitate the maintenance of social groups People do not have the need to maintain self-esteem itself; instead, they have the need to be included in the social group

74. Slide 74 Human behavior 3: Self-attribution and social illusion Common belief: people have direct, immediate knowledge of our thoughts and feelings People make attributions about themselves on the basis of the same kind of information they used to interpret the action of others (Daryl Bem) Schachter and Singer ’ s “ misattribution ” paradigm. What would happen if the subjects know the effect of those drugs? Nisbett and Wilson ’ s self-report experiment People are sometimes unable to report their own mental process because they are not aware of how they think.

75. Slide 75 Computer intelligence Particle swarm computing. Imitating human society. Every particle can be considered as a person and particles interact with each other. According to the social learning theory each particle is constantly watching the particles around it to see how they are doing and adjust its behavior accordingly. (people can learn by observation) Each particle also has a memory of its behavior history. (people can learn from their own experiences)

76. Slide 76 Soft computing: Research Areas Evolutionary algorithms and genetic programming Neural science and neural network systems Fuzzy set theory and fuzzy systems Chaos theory and chaotic systems

77. Slide 77 Soft computing: attributes Hard computing requires programs to be written; soft computing can evolve its own programs Hard computing uses two-valued logic; soft computing can use multivalued or fuzzy logic Hard computing is deterministic; soft computing incorporates stochasticity Hard computing requires exact input data; soft computing can deal with ambiguous and noisy data Hard computing is strictly sequential; soft computing allows parallel computations Hard computing produces precise answers; soft computing can yield approximate answers