Inria LORIA SCORE Team presentation
Download as PPTX, PDF0 likes1,020 views
The document summarizes the objectives and work of the Score Team, a group of researchers studying collaborative information systems at scale. The team's objectives are to support large-scale collaboration between organizations through service-based applications that can be trusted. Key areas of research include optimistic replication, trustworthy service composition, and scaling systems to thousands of services. The team has developed algorithms for replication and collaborative systems and is conducting experiments on cloud infrastructure with real users.
Inria LORIA SCORE Team presentation
- 1. Score Team • Web Scale Trustworthy Collaborative Information Systems Score Team – Francois Charoy March 20, 2013
- 2. Presentation • Composition of the Team (March 2013) • 10 Permanent Researchers (Professor, Associate Professor, Researcher) • 5 PhD Students • 5 Post-Doc • 5 Master Students • Web Site : score.loria.fr Team Score 3/22/2013 - 2
- 3. Objectives • Support large scale collaboration – between people, services and organisations • Help to build service based application – that can be trusted – efficiently Team Score 3/22/2013 - 3
- 4. Scientific Questions • Effective Optimistic replication • Trustworthy Service Composition • Relation to scale – Group to Community – Cloud – Thousands of services Team Score 3/22/2013 - 4
- 5. Where We Stand Design time Business Layer RunTime IT Layer Infrastructure Layer Team Score 3/22/2013 - 5
- 6. Previous Results • Algorithms for optimistic • Software/Platform replication – Bonita, • Collaborative systems – Libresource, – Qualipso Factory, • BPM models – DSMW, Etc. • Service composition Verification Team Score 3/22/2013 - 6
- 7. The project Collaborative data management Data centric service composition Trustworthy collaborative systems Team Score 3/22/2013 - 7
- 8. Collaborative Data Management • Collaboration, distributed in time, space and organisations Business Layer • Collaborate without a Collaborative Editing central authority IT Layer Optimistic replication Team Score 3/22/2013 - 8
- 9. Optimistic Replication • Investigate and evaluate new algorithms – Operational Transformation – CRDT • Support for decentralized « Real Time » Collaborative Systems • Understand their behaviour Team Score 3/22/2013 - 9
- 10. Experiment algorithms • How do they behave – With real users, – With a lot of users – With different scenarios – With different deployment Team Score 3/22/2013 - 10
- 11. First Results • Executing the same input with different algorithms • But we need more input • On going work – In the Cloud – With real users Team Score 3/22/2013 - 11
- 12. Concurrent editing generate conflicts • How to detect conflicts • How to solve conflicts • How to avoid conflicts • How to respect privacy • How to enforce privacy rules Team Score 3/22/2013 - 12
- 13. Collaborative editing conflicts Several people correcting the same document Team Score 3/22/2013 - 13
- 14. Optimistic data sharing control • Sharing contract • Trust representation • Audit log • Updated trust value based on audit • Authenticators for securing logs Team Score 3/22/2013 - 14
- 15. Coordination in dynamic situation Business Layer Design time Dynamic Process RunTime Management IT Layer Governance Aware Optimistic Replication Team Score 3/22/2013 - 15
- 16. Coordination in dynamic situation Application to crisis management • Issues – Changing goals – No central authority – Privacy/governance issues Team Score 3/22/2013 - 16
- 17. A Replicated Activity Model • Design time = Execution time • Temporal dependencies • P2P Sharing Team Score 3/22/2013 17
- 18. Data Centric Service Composition • Development of applications at the scale of the web • How to develop services that are – Efficient, Safe, Secure, Flexible, Adaptative • How to ensure/enforce some properties on service composition – Transactional properties, Security properties, Privacy/Quality of service Team Score 3/22/2013 - 18
- 19. Our landscape evolves quickly • The web as a platform – To collaborate – To produce and share data – To produce and deliver services • Elastic Computing – P2P – Cloud Infrastructure
- 20. The scale is changing • Regarding data production – Wikipedia – Climate Change Report • Regarding coordination – Crisis Management • For both – OSS development
- 21. Open services are here
- 22. Heterogeneity is back again
- 23. New ecosystems have appeared • Smartphone and tablet apps • They are based on services (REST API)
- 24. Our landscape evolves quickly • The Web as a Platform – To collaborate – To share data – To deliver services • Elastic Computing – P2P – Cloud Infrastructure Team Score 3/22/2013 - 24
- 25. Engineering Service Composition • Designing the composition (What, How) • Defining the contracts Business Layer • Verifying the contracts Modeling/Specifying/Checking • Deploying/executing • Monitoring/Auditing IT Layer Deployment/Execution • Responding to contract violation Team Score 3/22/2013 - 25
- 26. Declarative Service Composition Composition Design Composition Composition Closing the loop Implementation Monitoring is a challenge & Validation Composition Execution Team Score 3/22/2013 - 26
- 27. Model driven service engineering Team Score 3/22/2013 - 27
- 28. Advanced BPM • Collaborative Business Process • Large Scale Business Process • Orchestration of Open Services Team Score 3/22/2013 - 28
- 29. Trustworthy Collaborative Systems • Collaborative system : composition of collaborative systems • Define the confidence attributes – Trust and/or Control – Certification • Confidence is a relation – Service/Service – User/User – User/Service Team Score 3/22/2013 - 29
- 30. An approach grounded on contract • Confidence contracts in collaborative environments – Between participants – Between services – Between users and the environment • Validation of contracts and of their composition • A posteriori contracts verification Team Score 3/22/2013 - 30
- 31. Example : Trust and Data Sharing • Can we build application based on data services in the Cloud ? Team Score 3/22/2013 31
- 32. Scientific challenges • Identify confidence attributes for services • Monitor, control, validation of contracts • Matching between confidence and applications Optimistic approach for safety and security in a large scale setting Team Score 3/22/2013 - 32
- 33. Thank you ! www.inria.fr
Editor's Notes
- #17: Processes are defined on the goThe outcome (“desired end state”) becomes clear during the processGoals may change dynamicallyCoordination is collaboratively decided