Collecting and analyzing data for valuable decision making in a service oriented business scenario. Stefano SCAMUZZO

Transcription

1 Collecting and analyzing data for valuable decision making in a service oriented business scenario Stefano SCAMUZZO ENGINEERING Group ( Technical, Innovation & Research Division Architectures & Consulting SPAGOWORLD, Executive Board ( SPAGOBI, Ecosystem Manager (

2 Engineering Group

3 Everyone needs services

4 But what is a service? The The Core Core concept concept in in a Service Service Oriented Oriented model model is is the the concept concept of of Service Servicewhich is is subject subject to to interpretations interpretations that that make make its its meaning meaning quite quite ambiguous ambiguous Different Different points points of of view view are are possible: possible: The The Business Business Analyst Analystpoint of of view: view: a service service is is a functionality, functionality, part part of of a Business Business Process Process The The Designer Designerpoint of of view: view: a service service is is a software software module module with with a precise precise functional functional identity identity that that can can be be invoked invoked through through a well well defined defined and and documented documented public public interface interface We We prefer prefer to to talk talk in in terms terms of of processes processesand and components components The The Business Business Analyst Analystanalyzes analyzes the the processes processes so so as as to to detect detect the the functional functional components components he he needs needs to to build build the the process process The The Designer Designertranslates the the identified identified components components into into services services

5 What methodology to use? Bottom-up Leverage the existing applications and start building services as an assembly of existing components benefits: time reduction risks: the developed services have a shorter lifecycle and demand frequent maintenance and refactoring Top-down Start from business models to identify a complete plan of the services to be built, then iterate on their design and implementation benefits: tidy and complete architecture risks: huge initial investment for analysis an identification of the services plan Meet-in-the-Middle (Agile Delivery): Gradual definition of the services plan and parallel implementation of highest priority services. When the service plan has sufficiently progressed, services can be revised to make them compliant with the plan. The goal: to balance the need for a tidy design with the demands of a rapid development and time to market.

6 Synthesis of the methodology Enterprise Business Models Definition Service-Oriented Analysis Technological Architecture Definition Service Plan Definition

7 The Universal approach Universal Middleware Integration Processes Integration ESB Cooperation Connectors Orchestration Collaboration BPM IT & Business goals eform Lifecycle PDF Business Rules management SOA Application (Web Mobile) Innovation / reuse (FI mobile) Management & Intelligence Adaptable Middleware Services Design & develop. Tools IDE Governance Process & services management Business Activity monitor Core Core components components (service (service bundles) bundles) for for the the integration integration and and management management of of services; services; for for the the definition definition of of business business rules rules and and the the realization realization of of application application modules modules in in SOA SOA architectures. architectures. By By parameterizing parameterizingeach each component, component, the the solution solution gains gains a considerable considerable modularity, modularity, allowing allowing to to meet meet even even the the most most complex complex requirements. requirements.

8 Case history: a University Defining Defining the the architectural architectural framework framework to to support support new new projects projects following following a collaborative collaborative development development model model based based on on modular modular software software components components that that interact interact using using consistent, consistent, shared shared and and integrated integrated information. information. The The development development of of a service service is is split split into into phases: phases: initial initial integration integration of of the the existing existing systems systems followed followed by by a re-engineering re-engineering process process Requirements? Where is the information? New components? Reuse? Deploying components on infrastructure nodes Standards Connectors ARIS -> BPMN Application services Infrastructural services Unified Information Methodology New Platform Monitoring & Management

9 Case history: a University Explicitly expressed No No application silos silos Workflow Interoperability Document Management Scalability Unified Unified data data model model Flexibility SSO SSO & Security/Profiling Standardization Governance Iterative development - initial integration of existing applications ARIS processes modeled by the Customer Low organizational impact Performance Scalability (SLA) Availability Knowledge gain Proposed

10 Case history: a University Functional areas Processes & services Unified data model

11 Case history: a University Reusing Jar Library R Jar Library Transformation Develop new component New Requirement OSGi Bundles Implements Spagic Interface Spagic Bundles Config Publishing rules Deploy Supported by Eclipse Visual Tools Spagic Service Manager... Spagic MetaDB Registration

12 Case history: a University Analysis and Development Team G o v e r n a n APPLICATION GOVERNANCE c e PROJECT MANAGEMENT GOVERNANCE SERVICES KNOWLEDGE MANAGEMENT SECURITY GOVERNANCE Services and Contract Manager SERVICES GOVERNANCE INFRASTRUCTURE GOVERNANCE Operations Users Services/Applications

13 Governance requires BI / BAM Real time monitor for processes, services and relevant information Error management and process restart Events generated by systems monitor Support to decision making MetaDB (real time) Data Warehouse

14 Business Activity Monitoring BAM systems detect events and make them meaningful to business users Data Source(s) Console & Dashboards BUSINESS USERS Data Complex Event Processing (CEP) EVENT DETECTION Events EVENT VISUALIZATION Alarms & Notifications EVENT NOTIFICATION RT & Historical Analysis DWH STORAGE

15 Case History: BAM Web-based authenticated access Data Sources: SAP, CRM, backoffice, technical BPM System (TIBCO) Real Time Console & Dashboards REAL TIME Other SpagoBI Engines Event Manager DB (events) HISTORICAL ANALYSIS

16 Case History: BAM

17 Case History: BAM Alarms for critical situations (bottleneck, SLA) Overview and detail

18 Data as a service Structured Data Unstructured Data Sensor Data Transactional Time phased data Text, Social User feedbacks RFID, GPS QR codes VOLUME VELOCITY VARIABILITY V V V V New data types Video, voice Images Big Data

19 Data as a service

20 (Big) Data as a service Infrastructure On Site IaaS Data Management Capture Clean Load Store View and Analyze Exploration, navigation, presentation Text analysis Text mining Application Cloud SaaS ETL SERVICES BI

21 Big Data Application fields Brand Reputation Sentiment analysis Social listening Complaint Analysis Social CRM Competitive intelligence

22 Big Data Scenarios

23 Big Data approach

24 Open Data Out-of-date Inhomogeneous Multi-format Different detail levels Dispersed Growing Public and private sectors Structured Measurable quality It s the momentum

25 Open data: case history

26 Open data: case history

27 Open data: case history

28 Open data: case history

29 Open data: case history USAGE SCENARIOS in Services......t o help companies per f or m market r esear ches in Trade......t o analyse demands and emer ging t r ends in Turism......t o compar e exist ing r ange wit h available of f icial st at ist ics

30 How open source helps

31 New skills requires

32