Louis Perrochon

Learn More
This paper focuses on the problem of accessing interactive information servers ("interactive sessions" in W3-terminology, e.g. an existing library information system) directly with a W3-browser instead of opening an additional viewer (e.g. a terminal emulation program). IDLE is a language designed to describe the user interface of interactive information(More)
Distributed systems' runtime behavior can be difficult to understand. Concurrent, distributed activity make notions of global state difficult to grasp. We focus on the runtime structure of a system, its execution architecture, and propose representing its evolution as a partially ordered set of predefined architectural event types. This representation(More)
CHAIMS supports an innovative paradigm in software engineering: Composition. The CHAIMS programming language focuses solely on integrating so-called megamodules into new applications. In doing this, CHAIMS exploits existing or emerging standards for interoperation like CORBA, ActiveX, JavaBeans or DCE. This approach reduces software development and(More)
Event Mining discovers information in a stream of data, or events, and delivers knowledge in real-time. Our event processing engine consists of a network of event processing agents (EPAs) running in parallel that interact using a dedicated event processing infrastructure. EPAs can be conngured at run-time using a formal pattern language. The underlying(More)
This paper is based on the notion of data quality. It includes correctness, completeness and minimality for which a notational framework is shown. In long living databases the maintenance of data quality is a rst order issue. This paper shows that even well designed and implemented information systems cannot guarantee correct data in any circumstances. It(More)
Have you ever put a software system together without working out the full architecture before hand? If yes, did you feel guilty for not following good software practice? We think that not doing a design up-front may be the right thing to do in the face of rapid technology change. Today's software systems evolve too quickly, include too much legacy code, and(More)