Michel RIVEILL

Professeur d'informatique à Polytech'Nice - Sophia / Directeur du département "sciences informtiques"

Chercheur en informatique au laboratoire I3S / Responsable du projet Rainbow

Pointeurs pour l'enseignement...

! ! ! Petit préambule important ! ! !

Je remercie chaleureusement les auteurs qui m'ont transmis leurs cours. Ce travail est le leur. Si un cours vous a plus, si vous utilisez un des cours pour vous former, si vous améliorez une présentation envoyez leur un mail... proposez, vous aussi votre travail.


Toutes les références indiquées dans cette page de cours/manuels sont disponibles pour une libre consultation, mais les auteurs se réservent les droits d'auteurs et tous les autres droits :

  • Vous n'avez pas le droit de mettre en circulation cette ½uvre en entier ou en partie, même modifiée ou traduite  pour en tirer un profit commercial quelconque.
  • Mais vous avez le droit d'utiliser ce cours à toutes fins non-commerciales, en particulier si vous êtes étudiants ou enseignants.
  • Inutile de me demandé un corrigé de travaux pratiques si les sujets sont en ligne, à vous de proposer une solution.

Je ne suis pas constamment a la recherche de cours et documentation en français accessible gratuitement, plus particulièrement en systèmes et réseaux. Donc si vous en connaissez d'autres, n'hésitez pas à m'envoyer un petit mot

Vous avez écrit un cours... il peut servir à d'autres enseignants... n'hésitez pas à m'envoyer un petit mot si vous souhaitez le mettre à la suite des autres. De nombreux chapitres sont encore incomplets.

Si vous remarquez qu'un lien est rompu...  faites signe, j'essayerai d'y remédier.

5 precedents precedent Home suivant 5 suivants

Note : ce site fait partie de l'anneau ObjectWeb qui contient de la documentation et des supports de cours essentiellement en français sur les logiciels d'infrastructures

La plupart des fichiers sont en format PDF. Pour obtenir Acrobat Reader, cliquez ici 

 
Accès en ligne à des mémoires de masters, DEA, thèse et HDR en systèmes répartis


  

Langage et programmation (cours de base)

Initiation aux réseaux informatiques (cours de base)

Réseaux informatiques (cours d'approfondissement)

Réseaux de télécommunication

  • Polycopiés
  • Transparents
  • Exercices
  • Travaux pratiques
  • Autres cours sur le sujet

 

Systèmes d'exploitation (cours de base)

Systèmes répartis (cours d'approfondissement)

Internet (Cours à la mode)

Construction des applications répartie (cours d'approfondissement)

  • Polycopiés
  • Transparents
    • Modèle à espace de tuples (version provisoire), Daniel HAGIMONT, CR INRIA
    • Modèle à objets dupliqués, Daniel HAGIMONT, CR INRIA
    • Modèle à objets actif
    • Architectures réparties
    • Modèles de composants
    • COM+
    • Composants CORBA
    • J2EE et EJB
    • .Net
    • Modèle Driven Architecture
      • MDA from hyde to hope, and reality, Jean Bezivin, Université de Nantes
      • System Level Design For Real Time Applications, A. Ferrari/A. Sangiovann, PARADES PARADES EEIG
        ABSTRACT :
        Embedded System Design (ESD or just ES) is about the implementation of a set of functionalities satisfying a number of constraints ranging from performance to cost, emissions, power consumption and weight. In recent years, the functionalities to be implemented in embedded system have grown in number and complexity so much so that the development time is increasingly difficult to predict and to keep in check. The complexity increase coupled with the constantly evolving specifications has forced designers to look at implementations that are intrinsically flexible, i.e. software-based. This corresponds to increasing problems in verifying design correctness, a critical aspect of ESD since several application domains, such as transportation and environment monitoring, are characterized by safety considerations that are certainly not interesting for the traditional PC-like software applications. In addition to this aspect, little attention has been traditionally paid to hard constraints on reaction speed (Real Time), memory footprint and power consumption of software. This is of course crucial for embedded systems. These considerations point to the fact that embedded software (ESW) is really an implementation choice of a functionality that can be indifferently implemented as a hardware component and that we cannot abstract away time characteristics of software as we do in the traditional software domain.

        ESW today is written using low level programming languages such as C or even Assembler to cope with the tight constraints on performance and cost typical of most embedded systems. In most embedded software, operating systems were application dependent and developed in house. Once more performance and memory requirements forced this approach. With the increased complexity of ES application, this rather primitive approach has become the bottleneck and most system companies have decided to enhance their software design methodology to increase productivity and product quality.

        To change radically ESD we advocate that is mandatory to derive embedded software from higher level of abstraction system models and link ESW to the programmable platforms that support it thus providing the much needed means to verify whether the constraints posed on ES are met.

      • Object to Model Paradigm Change with the MDA initiative, Jean Bezivin, Université de Nantes
        ABSTRACT :
        This presentation covers the new software development framework recently proposed by the Object Management Group. The Model- Driven Architecture departs from traditional code-centric approaches to explore new practical ways to separate platform-independent business models from platform-specific design and implementation models. The initial definition of UML has been instrumental in the move from the Object Management Architecture to the Model Driven Architecture. However the UML meta-model is only part of this rapidly evolving organization. We shall mainly concentrate in this talk on the regular organization of models, meta- models, and operation on them. An attempt will be made to separate the precise notions that may already be practically used for development from the open questions that still need more research work.
      • UML and Real-Time, François Terrier,
        ABSTRACT :
        Engineers are more and more faced to the hard problem of developing more sophisticated real-time systems while time to market and cost constraints are constantly increasing. The necessity of adopting object oriented modeling in the real-time domain appears to be essential in order to face the rapidly changing market conditions. Main obstacles are the lack of standards and no good ad equation with real-time domain issues. With the standardization of UML 1.3 and 1.4, the first main drawback is coming down. Current work performed at the OMG on UML standard evolutions to better integrate real-time issues shows both that there is a strong interest on the subject and that current proposals are neither completely satisfying, nor completely compatible. In particular, some available methods (namely ARTiSAN, RT-UML/Rhapsody, TAU UML/SDL and UML-RT/Rose-RT, SyncChart-Esterel) provide a good support for parallelism modeling of an application. Nevertheless, they are often poor to express quantitative real-time features (such as deadlines, periods, priorities.) and are always based on proprietary solutions not obviously fully compliant with the UML standard. So It remains two important challenges: first to define how to support high level real time specification concepts in UML; and, second, to unify them within these proposed by existing tools. In addition, each approach uses different and specific underlying execution model. This leads to tool dependent solutions sometimes not so "standard". In order to manage this variability of the implementation models and choices, the community pay more and more attention on the definition of a model based development methodology. New challenge addressed by the OMG, the MDA approach gives rise to a strong interest in the domain of the embedded systems in order to increase independency among functional models, execution paradigms and hardware architectures.
      • Advanced modeling technics: contract, aspect and pattern, Jean-Marc Jézéquel, PR Université de Rennes,
        ABSTRACT :
        Separation of concerns is a basic engineering principle that is often applied in object-oriented analysis and design by dissociating functional aspects (PIM level business objects) from non-functional ones (such as persistency, fault-tolerance and so on) and their platform specific implementations. The Unified Modeling Language (UML) gives the designer a rich, but somehow disorganized, set of views on her model as well as many features, such as design pattern occurrences, stereotypes or tag values to add non-functional annotations to a model. In this tutorial, we show how to organize all of these features around the central notions of (1) quality of service contracts (for specifying non-functional properties a la QML on PIMs) and (2) aspects for describing how they can be implemented (PSM). based on our experience in the IST QCCS project, we propose to model contracts in UML with a small set of stereotypes, and to represent aspects a bit like design pattern occurrences, that is using parameterized collaborations equipped with transformation rules expressed with an object-oriented extension of OCL2 working at the M2 level. The second part of this tutorial will present our transformation based approach as implemented in the UMLAUT framework to build design level aspect weavers, based on a meta-level interpreter, that takes a PIM as entry point, processes the various aspect applications as specified by the designers, and outputs another (detailed design, or PSM level) UML model that can serve as a basis for code generation.
      • Component based engeneering in MDA, Philippe Merle, CR INRIA Futur
      • MDA experiment in telecom industry, Bertrand Nicolas,
        ABSTRACT :
        Technology evolutions go faster and faster. The stablest features are business models. So France Telecom developed a method, called MetYs, for designing its telecom services and its information systems. This method splits functional and technical features. MetYs gathers several processes: business process analysis, domain analysis, system analysis, global architecture, domain architecture, system architecture, design, . According to MDA principles, the functional models are transformed into design models by using rules elaborated during architecture processes. The presentation introduces MetYs processes, and shows an example of its use for telecom services modelling. In that case, the MDA principles are applied to transform PIM services analysis models to PSM models used for services simulation.
    • OSGi (La plateforme dynamique de services OSGI), Didier Donzes, MC UJF
  • Etude de cas
  • Exercices
  • Travaux pratiques
  • Autres cours sur le sujet

    •  

    Intégration des systèmes

    Informatique mobile et embarquée

     

    Ressources complémentaires

     

    Michel RIVEILL

    Laboratoire I3S - Bât. ESSI
    930 Route des Colles
    06903 Sophia Antipolis CEDEX

    email : riveill at unice.fr

    Généralité

    Projet Rainbow

    Ressources en lignes

    Les rubriques des cours :

     

    Rechercher sur ce site avec Google: 

     

    dernière mise à jour
    le 07 avril 2006

     

     

    Réservation d'Hôtel à Prix Réduits - HotelClub