eBusiness – Past and Future

1. eBusiness – Past and Future Anders Bonde, Senior IT Architect

2. Anders Bonde • 1982 Master of Science (Math. & Physics) • 1982-85 Teacher (“Gymnasium”, University etc) • 1985-92 IBM Denmark • Co-Author of IBM Redbook (1990) • “Object-oriented design - A preliminary approach”. • 1992-2004 The Danish Object Company • Involved in approx. 100 projects (1992-2004) • My role: Mentor, teacher, architect, designer, project manager and programmer • 2004-2006 (July) Mærsk Data (now IBM) • Manager IBM APMM eCommerce • 50 people in DK & 20 people in India • My people: Project mgrs, architects, developers, integrators and testers • 2006 (aug)-now IBM Global Business Solutions • Business Manager / Senior IT Architect • APM, Arla, Jyske Bank, Skat etc

3. Agenda • The Past: 4 eBusiness Case-stories • Jyske Netbank Erhverv • CRMDirect • Maerskline.com • Stockholm Congestion Tax System • The Future: Patterns & Reference Architecture • IBM Patterns for eBusiness • IBM eBusiness Reference Architecture • SOA – Service Oriented Architecture

4. Warning: I talk ‘Technish’ • eBusiness/eCommerce is not ONLY about technology • But it is ALSO about technology • “As simple as possible, but not simpler” (*) • And I will talk about technology • But I also understand the (e)Business! You are welcome to challenge me! (*) Einstein about Physics

5. Requirements - it’s not easy :o) You know this?

6. The traditional IT development process Business IT This is what I’ll get This is what I want Disjoint, Slow Requirement Analysis breakdown requirements • round • hollow • air inside • elongated. Length> height Design to requirements • round • with a hole • air inside • width > height

7. The Past: “Real life” eBusiness Case-stories Anders Bonde

8. Jyske NetbankErhverv Anagrammer

9. Jyske Netbank Erhverv • Officebank system for enterprise customers. • State-of-the-art • 100% Java (signed applet runs in browsers, also “offline”) • Main features • Payment-system (!!!) (incl. Euro support) • Integration with leading ERP systems • Advanced reporting facilities. • “FIT” Client technology • “Look-and-feel” of client/server, • Maintained like a mainframe application. Anagrammer

10. Jyske Netbank Erhverv • New customer: Danish Government • Unique Selling Points: • Ease-of-use • Performance • Price! • Handle all payments for next 5 years • 30 million transactions per year! • 1000 billion DKK (125 billion EUR) per year • 2000 Public Departments • 10000++ users Anagrammer

11. Anagrammer

12. Anagrammer

13. Java object COBOL DB2 Jyske Netbank Erhverv Arkitektur ”http” (CBT) Internet Server (S/390) JNE Appl. JDBC C / CGI Local Database (Access) BackOffice programmer SQL Database Server (S/390) Application Server (S/390) Anagrammer

14. Anagrammer

15. What is CRMDirect • Internet-based CRM concept • Customer Relationship Management • Everything ”In a box” • CRM, Hosting, Security, Backup etc • Optional: Partner data • Integrated with intelligent data • Market- & Credit information • Købmandsstandens OplysningsBureau, DK • CreditInform, Norway • Or your data ...

16. Anagrammer

17. CRM Vision • ”As simple as possible, but not simpler” • CRM functionality = Pragmatic • ”Best-of-breed” • Technology = No compromises! • THE CRM solution for The Mobile Organisation

18. Client Appl. Java object EJB Server Appl. ERP DB2 Architecture II WAP https/ XML Internet Server (WebSphere) “ServLet’s” IP SQL Application Server Database Server

19. Anders Bonde

20. A Container is not just a container :o)

21. Rebranding – Feb 12, 2006

22. Stockholm Congestion Tax System

23. The Stockholm Project A local government project to reduce congestion, based on three initiatives. 2 – Test congestion taxation 3 – Provide more parking 1 – Improve public transport

24. Congestion Tax Objectives • Reduce traffic by 10-15% • Increase average speed • Reduce pollution • Improve environment • Improve public transportation

25. User channels: Internet, Pressbyrån, 7-Eleven, Call Centre • Variable tax scheme • Continues flow • Alternative ways of identification Technology: Q-free Roadside Transponder IBM Data Centre IBM OCR Payment channels Congestion Tax Solution Overview

26. Challenges • Negative public opinion • Demanding SLA • High visibility • Integrity problems • 24 hours cycle • Volume uncertainty • Passages • Images stored • Payments • Call center calls • OBU distribution

27. Stockholm Congestion Tax Results • Uninterrupted operation every day • Traffic reduced by 25% • Public transportation passengers increased by 40,000 per day • Congestion during peak hours dramatically reduced • No major re-routed traffic problems • Average speed of buses increased

28. 99,99% vehicle identification

29. The future: Patterns and Reference Architectures Anders Bonde

38. e-business Reference Architecture V2.3 An Introduction |

39. Business View IntegrationView User / Information View Functional View Data View Content Management View Operational View Security View Systems Management View What is ESS e-business Reference Architecture? • The Enterprise Solution Structure has reviewed and approved several reference architectures. The e-business reference architecture (ebRA) is its latest addition. • ebRA is a very prescriptive reference architecture that addresses the e-business solutions architecture space. • ebRA is based on the Architecture Blueprint which identifies 9 views that any architecture should satisfy. • ebRA is designed to be adaptive such that it meets current and future needs of a diverse user population and adapts to changing requirements

40. Across all Industries Customer Self Service Customer Loyalty eCRM Sell and Support Solutions E-Marketplaces Supply Chain Management E-Procurement Buy and Supply Solutions Industry Solutions Employee Self Service Enterprise Portals Knowledge Management Enterprise Solutions First of a kind solutions Technology Refresh Web enabling legacy systems Custom SI Solutions Provides a strong and reliable foundation For any e-business solution What is it? Financial Services Solutions Wealth management Online Brokerage Claims Processing …… Industrial Sector Solutions Automotive solutions Manufacturing solutions Petrochemical solutions …… e-business End-to-End Architecture Distribution Sector Solutions Retail solutions CPG solutions Online Gaming …… Telco and Media Solutions Digital Asset Management Online booking …… Public Sector Solutions E-government Federal government solutions State government solutions ……

41. Work Product Traceability Diagram

42. The Business Environment contains the Business Context Diagram which documents the identity of the enterprise and its interactions with other entities in its environment • The e-business reference architecture provides the ability: • For customers to perform their own transactions via the Internet • For enterprise employees to interact via the enterprise’s Intranet • To conduct business amongst companies via an extranet or the public Internet

43. The System Context highlights important characteristics of the system events and data the system receives and generates External Entities • ebRA identifies and describes the following with their connectivity considerations: • Pervasive Computing Device • Browser-based Internet Client • Browser-based Intranet Client • Legacy Systems and Databases • Web Services Directories • External Entities • Also included is a table that identifies the flows between the system the items above. The table identifies: • Entities involved with the flow • Definitions of inputs and outputs • Volume Information • Access Times Customized Pervasive Requests for (Business XML documents Computing information made delivered to Partners, over wireless Devices external systems Vendors, ASPs) protocols over HTTP or HTTPS XML documents Customized returned from presentation partner site/ delivered to client application over over wireless HTTP or HTTPS protocols Request for informational Request for information and business data made about location and Browser-based over HTTP or HTTPS binding details of e-business services over TCP/IP Internet Client Web Services HTML and XML Application Directories documents, audio, video, Information about location and image files delivered and binding details of over HTTP or HTTPS services returned from Directory over TCP/IP Request for data or Request for Requested data transactions over information or transaction TCP/IP made over results returned HTTP or HTTPS over TCP/IP Information delivered to a full Legacy Systems Browser-based function client and Databases Intranet Client desktop over HTTP or HTTPS

44. The Use Case Model describes the functional characteristics of the system • Actors include the primary actors from the User Profiles, including: User, Registered User and Mobile User • Use Case Model • Use Cases include (some from mobile devices): • Logon • Change Password • Register User • Enterprise Systems Inquiry • Browse Enterprise Systems • External Enterprise System Inquiry • Update Enterprise System • Create User Profile • Create Content • Request External Web Service

45. Overview Diagrams, Architecture Layers and Services are described for: Enterprise View IT System View Services View The Architecture Overview Diagram represents governing ideas and candidate building blocks

46. Availability Backup & Recovery Capacity Estimates & Planning Configuration Management Disaster Recovery Extensibility / Flexibility Failure Management Performance Reliability Scalability Security Service Level Agreements Standards Systems Management Environment Quality of Service under load Non-Functional Requirements identify considerations affecting Quality of Service and Constraints for the system

47. The Security & Privacy Policies provide high level statements of the management’s goals, objectives & beliefs in the security & privacy area. • This work product prescribes management’s direction to guide an organization in meeting the security & privacy objectives. These are used in the creation of the architecture as well as in the implementation of any specific solution or application. • The following policies are described in great detail in this work product: • Internet Privacy Policy • Security Policy • Domain Name Service Policy • Extranet Firewall Policy • Internet Firewall Policy • Remote Access Policy • Cryptography Policy • Key Management Policy • PC and LAN Security Policy • System Access Policy • Access Control Administration Policy • Content Policy • Anti-virus Policy • The scope of these policies are enterprise wide. In addition to the definition of policies, this work product identifies the roles and responsibilities of individuals and organizations responsible for the implementation of these directives.

48. Security & Privacy Requirements • This document addresses risks related to protecting business information wherever it resides and categorizes them into the following • Authentication / identification • Administration / Configuration • Assurance / Monitoring • Access Control • Security Policy Administration • Privacy / Confidentiality • Integrity • Accountability / Non-repudiation • Security Management • The Security & Privacy Requirements captures the process & technology needs specific to the business & IT strategies from a security and privacy perspective.

49. SOA – Service Oriented Architecture Anders Bonde

50. What is …..? … a service? A repeatable business task – e.g., print an invoice; create new booking … service orientation? A way of integrating your business as linked servicesand the outcomes that they bring … service oriented architecture (SOA)? An IT architectural style that supports service orientation … a composite application? • A set of related & integrated services that support a business process built on an SOA