0
Always-on Distributed Spreadsheet Mashups<br />Pierpaolo Baglietto (1), Fabrizio Cosso (2), Martino Fornasa (1), Simone Ma...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
Introduction (1/2)<br />CIPI’s research activities<br />Mashups are composite applications that allow to merge different f...
Introduction (2/2)<br />About our prototype based on the Wiring paradigm…<br />It aims at combining data and services rega...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
RequirementsforMashuptools<br />Here is a list of 4 requirements that we identified for the usage of Mashup tools in the E...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
Platform architecture and operating principles (1/2)<br />Components of the platform:<br />A centralized server-sideCompos...
Platform architecture and operating principles (2/2)<br />Operating principles:<br />The exporter contribution update is p...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
Hierarchical Enterprise Spreadsheet Mashup – HESM (1/3)<br />The main concepts in HESMs are:<br />Master Organizational Un...
Hierarchical Enterprise Spreadsheet Mashup – HESM (2/3)<br />Case Study: the Car Dealers Example<br />The company is organ...
Hierarchical Enterprise Spreadsheet Mashup – HESM (3/3)<br />Case Study: the Car Dealers Example (Screenshots)<br />13<br ...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
Platform implementation (1/2)<br />The Client Plug-in must be installed on nodes running the MS Excel software<br />The Pl...
Platform implementation (2/2)<br />Sequence Diagram for an exportation involving an intermediate spreadsheet<br />16<br />...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
Discussion<br />Other Spreadsheet-based Mashup tools focus on the integration of different data sources into Spreadsheets<...
Our approach can be seen as complementary with respect to the platforms that import different data sources and convert the...
Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadshee...
Conclusion<br />We designed a spreadsheet Mashup tool which allow to:<br />Create distributed spreadsheet composition<br /...
Upcoming SlideShare
Loading in...5
×

Mashup2010

512

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
512
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Mashup2010"

  1. 1. Always-on Distributed Spreadsheet Mashups<br />Pierpaolo Baglietto (1), Fabrizio Cosso (2), Martino Fornasa (1), Simone Mangiante (1), Massimo Maresca (1), Andrea Parodi (2), Michele Stecca (1) <br /> <br />(1) Computer Platform Research Center (CIPI) - University of Padova, University of Genova, Italy<br />(2) M3S S.r.l. - Genova, Italy<br />Mashups’10Ayia Napa, Cyprus, Dec. 1st 2010<br />m.stecca@cipi.unige.it<br />
  2. 2. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />Platform implementation<br />Discussion<br />Conclusion<br />2<br />Agenda<br />2<br />
  3. 3. Introduction (1/2)<br />CIPI’s research activities<br />Mashups are composite applications that allow to merge different functionalities, data sources, user interfaces, etc. <br />Mashups are usually defined as lightweight tools. According to the classification provided by Fischer et al. (2009), it is possible to identify some paradigms aiming at supporting the easy creation of composite services:<br />Wiring paradigm (e.g., JackBe Presto, Yahoo Pipes!, etc.)<br />Spreadsheet-based frameworks (e.g. SpreadATOR, IBM A1, etc.)<br />Programming by demonstration (e.g., Dapper)<br />Automatic creation of Mashups (e.g., MaxMash)<br />In this paper we propose to improve the current generation of Spreadsheet-based Mashup tool by adding two new features:<br />The Distributed Spreadsheet Composition functionality, and<br />The Always-on functionality (i.e., the Spreadsheet Mashup is updated even if one or more components are offline) <br />3<br />3<br />
  4. 4. Introduction (2/2)<br />About our prototype based on the Wiring paradigm…<br />It aims at combining data and services regardless the specific technologies used for their implementation (e.g., RSS Feed, Rest WS, SOAP WS, etc.)<br />We re-use the Service Creation Environment developed during the FP6 project called OPUCE (Open Platform for User-Centric Creation and Execution)<br />We developed a platform for the execution of Event Driven Mashups (i.e., each basic block may generate one or more events during its execution)<br />We implemented different versions of the execution platform based on different technologies (Web Services, Java Message Service – JMS, and Plain JAVA code over Virtualized environments)<br />4<br />4<br />
  5. 5. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />The Car Dealers case study<br />Platform implementation<br />Discussion<br />Conclusion<br />5<br />Agenda<br />5<br />
  6. 6. RequirementsforMashuptools<br />Here is a list of 4 requirements that we identified for the usage of Mashup tools in the Enterprises<br />Support of lightweight creation of Situational Applications Spreadsheets are well known tools;<br />Support of reuse of already existing data Spreadsheets are widely used to store enterprise data;<br />Compliance with the distributed and hierarchical structure of enterprises  different units of the same company may be geographically distributed;<br />Support of automatic updates and Always-on distributed Composite Spreadsheets synchronize the linked spreadsheets automatically even when one or more components of the distributed spreadsheet are offline. <br />6<br />6<br />
  7. 7. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />Platform implementation<br />Discussion<br />Conclusion<br />7<br />Agenda<br />7<br />
  8. 8. Platform architecture and operating principles (1/2)<br />Components of the platform:<br />A centralized server-sideComposition Platform supports the execution of spreadsheet data exportation and importation, manages user accounts, and synchronizes data across dependent spreadsheet;<br />AClient Plug-inintegrated in the end-user spreadsheet application. It interacts with the composition platform by means of messages exchange and allows the user to import/export data through a graphical UI.<br />Spreadsheet types: <br />Importer: it imports data from other Spreadsheets;<br />Exporter: it exports data toother Spreadsheets;<br />Intermediate: it is both an importer and an exporter at the same time, and at least one exported cell is a function of an imported cell (via direct inclusion or formulas).<br />8<br />8<br />
  9. 9. Platform architecture and operating principles (2/2)<br />Operating principles:<br />The exporter contribution update is periodically performed by each exporter Plug-in towards the platform;<br />The importer spreadsheet update is periodically performed by the importer Plug-in. The Plug-in periodically polls the platform for new contributions or updates;<br />The data propagation function works as follows:<br />When a client Plug-in realizes that the spreadsheet is intermediate it uploads the entire spreadsheet on the platform. Every time an intermediate spreadsheet is updated the Plug-in performs a new upload.<br />When an intermediate spreadsheet is offline, the platform runs a local spreadsheet engine in order to recalculate the exported ranges based on fresh import ranges.<br />9<br />9<br />
  10. 10. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />Platform implementation<br />Discussion<br />Conclusion<br />10<br />Agenda<br />10<br />
  11. 11. Hierarchical Enterprise Spreadsheet Mashup – HESM (1/3)<br />The main concepts in HESMs are:<br />Master Organizational Unit (MOU)<br />Contributing Organizational Units (COU)<br />Space<br />Master Spreadsheet<br />Chain of spaces<br />11<br />11<br />
  12. 12. Hierarchical Enterprise Spreadsheet Mashup – HESM (2/3)<br />Case Study: the Car Dealers Example<br />The company is organized in an hierarchical way:<br />Car Dealers – CDs interact with costumers<br />A set of CDs located in a certain area are managed by the same Area Sales Manager - ASM<br />A set of ASMs located in a certain region are managed by the same Regional Sales Manager – RSM<br />There are different relationships among actors:<br />CDs keep track of their sales in their own spreadsheets<br />CDs are the COUs of the spreadsheet owned by the related ASM (i.e., the MOU of this relationship)<br />ASMs keep track of the regional sales in their own spreadsheets<br />ASMs are the COUs of the spreadsheet owned by the related RMS (i.e., the MOU of this relationship)<br />12<br />12<br />
  13. 13. Hierarchical Enterprise Spreadsheet Mashup – HESM (3/3)<br />Case Study: the Car Dealers Example (Screenshots)<br />13<br />13<br />
  14. 14. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />Platform implementation<br />Discussion<br />Conclusion<br />14<br />Agenda<br />14<br />
  15. 15. Platform implementation (1/2)<br />The Client Plug-in must be installed on nodes running the MS Excel software<br />The Plug-in and the Composition Platform communicates by means of SOAP-based APIs<br />The DB stores the importations, exportations, and the dependencies among spreadsheets<br />The Excel Server component runs the intermediate spreadsheets when needed (i.e., an update in the exporting file occurred)<br />The importing spreadsheets poll the Composition Server to retrieve updated data<br />15<br />15<br />
  16. 16. Platform implementation (2/2)<br />Sequence Diagram for an exportation involving an intermediate spreadsheet<br />16<br />16<br />
  17. 17. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />Platform implementation<br />Discussion<br />Conclusion<br />17<br />Agenda<br />17<br />
  18. 18. Discussion<br />Other Spreadsheet-based Mashup tools focus on the integration of different data sources into Spreadsheets<br /><ul><li>On the contrary we focus on the distributed and always-on composition of spreadsheets
  19. 19. Our approach can be seen as complementary with respect to the platforms that import different data sources and convert them to spreadsheet cells</li></ul>The proposed solution aims at modeling the hierarchical structure of enterprises as shown in the Car Dealer case study<br />The proposed solution may take advantage of the emerging Cloud Computing paradigm in two different ways:<br />In a Infrastructure as a Service – IaaS scenario, the Composition Platform might run on a Virtual Machine deployed “in-the-cloud” (e.g., it might be an Amazon Machine Image – AMI deployed on the Amazon EC2 Cloud)<br />In a Software as a Service – SaaS scenario, the Composition Platform might rely on the Google Spreadsheet APIs which allow to manipulate spreadsheets stored “in-the-cloud”<br />18<br />18<br />
  20. 20. Introduction<br />Requirements<br />Platform architecture and operating principles<br />Hierarchical Enterprise Spreadsheet Mashup<br />Platform implementation<br />Discussion<br />Conclusion<br />19<br />Agenda<br />19<br />
  21. 21. Conclusion<br />We designed a spreadsheet Mashup tool which allow to:<br />Create distributed spreadsheet composition<br />Update the spreadsheet composition automatically even if one or more components are offline (Always-on feature)<br />Reflect the hierarchical structure of enterprises where actors working at different levels contribute to the creation of aggregated information<br />We implemented a prototype of the system presenting the following features:<br />The client Plug-in is implemented to run on the Microsoft Office system<br />The Client/Server communication architecture is based on SOAP messages exchange<br />It manages the automatic update of complex spreadsheet composition through the execution of intermediate spreadsheets<br />Future works<br />Security<br />Versioning<br />Spreadsheet Mashups “in-the-cloud”<br />20<br />20<br />
  22. 22. Thank you for your attention<br />21<br />21<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×