Monitoring Scheduling for Home Gateways

International audienceIn simple and monolithic systems such as our current home gateways, monitoring is often overlooked: the home user can only reboot the gateway when there is a problem. In next-generation home gateways, more services will be available (pay-per-view TV, games. . . ) and different actors will provide them. When one service fails, it will be impossible to reboot the gateway without disturbing the other services. We propose a management framework that monitors remote gateways. The framework tests response times for various management activities on the gateway, and provides reference time/performance ratios. The values can be used to establish a management schedule that balances the rate at which queries can be performed with the resulting load that the query will induce locally on the gateway. This allows the manager to tune the ratio between the reactivity of monitoring and its intrusiveness on performance

ROCS: a Remotely Provisioned OSGi Framework for Ambient Systems

International audienceOne of the challenges of ambient systems lies in providing all the available services of the environment to the ambient devices, even if they do not physically host those services. Although this challenge has come to find a solution through cloud computing, there are still few devices and operating systems that enable applications execution by only uploading the required components into the runtime environment. The ROCS (Remote OSGi Caching Service) framework is a novel proposal which relies on a heavy-weighted standard Java/OSGi stack. It is distributed between class servers and ambient devices to provide full functionalities to resource-constrained environments. The ROCS framework provides improvements in two areas. First, it defines a minimal bootstrap environment that runs a standard Java/OSGi stack. Secondly, it provides an architecture for loading any necessary missing class from remote servers into memory at runtime. Our first results show similar performances when classes are either remotely downloaded into the main memory from a local network or from a flash drive. These results suggest a way to design minimalistic middleware that dynamically obtain their applications from the network as a first step towards cloud-aware operating systems

Liability in Software Engineering: Overview of the LISE Approach and Illustration on a Case Study

© ACM – 2010. This is the authors' pre-version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in the Proceedings of the 32nd ACM/IEEE international Conference on Software Engineering (ICSE'10) - Volume 1 – 978-1-60558-719-6/10/05 – (May 2-8 – 2010) http://doi.acm.org/10.1145/1806799.1806823LISE is a multidisciplinary project involving lawyers and computer scientists with the aim to put forward a set of methods and tools to (1) define software liability in a precise and unambiguous way and (2) establish such liability in case of incident. This report provides an overview of the overall approach taken in the project based on a case study. The case study illustrates a situation where, in order to reduce legal uncertainties, the parties to a contract wish to include in the agreement specific clauses to define as precisely as possible the share of liabilities between them for the main types of failures of the system

Liability in Software Engineering: Overview of the LISE Approach and Illustration on a Case Study

© ACM – 2010. This is the authors' pre-version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in the Proceedings of the 32nd ACM/IEEE international Conference on Software Engineering (ICSE'10) - Volume 1 – 978-1-60558-719-6/10/05 – (May 2-8 – 2010) http://doi.acm.org/10.1145/1806799.1806823LISE is a multidisciplinary project involving lawyers and computer scientists with the aim to put forward a set of methods and tools to (1) define software liability in a precise and unambiguous way and (2) establish such liability in case of incident. This report provides an overview of the overall approach taken in the project based on a case study. The case study illustrates a situation where, in order to reduce legal uncertainties, the parties to a contract wish to include in the agreement specific clauses to define as precisely as possible the share of liabilities between them for the main types of failures of the system

Liability in Software Engineering Overview of the LISE Approach and Illustration on a Case Study

© ACM, 2010. This is the authors' version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in the Proceedings of the 32nd ACM/IEEE international Conference on Software Engineering (ICSE'10) - Volume 1, 978-1-60558-719-6/10/05, (May 2-8, 2010) http://doi.acm.org/10.1145/1806799.1806823International audienceLISE is a multidisciplinary project involving lawyers and computer scientists with the aim to put forward a set of methods and tools to (1) dene software liability in a precise and unambiguous way and (2) establish such liability in case of incident. This paper provides an overview of the overall approach taken in the project based on a case study. The case study illustrates a situation where, in order to reduce legal uncertainties, the parties to a contract wish to include in the agreement specic clauses to dene as precisely as possible the share of liabilities between them for the main types of failures of the system