Formal Methods for Embedded Distributed Systems

How to master the complexity

  • Fabrice Kordon
  • Michel Lemoine

Table of contents

  1. Front Matter
    Pages i-xx
  2. The BART Case Study

    1. V. Winter, F. Kordon, M. Lemoine
      Pages 3-22
  3. Building and Validating Conceptual Aspects

    1. V. Winter, D. Kapur, G. Fuehrer
      Pages 25-64
    2. M. Lemoine, G. Gaudiére
      Pages 65-88
    3. Adriaan De Groot, Jozef Hooman
      Pages 89-129
  4. Building and Validating Operational Aspects

    1. F. Bréant, J.-M. Couvreur, F. Gilliers, F. Kordon, I. Mounier, E. Paviot-Adet et al.
      Pages 171-211
  5. Methodological Aspects

    1. F. Kordon, M. Lemoine
      Pages 259-263

About this book

Introduction

The development of any Software (Industrial) Intensive System, e.g. critical embedded software, requires both different notations, and a strong devel- ment process. Different notations are mandatory because different aspects of the Software System have to be tackled. A strong development process is mandatory as well because without a strong organization we cannot warrantee the system will meet its requirements. Unfortunately, much more is needed! The different notations that can be used must all possess at least one property: formality. The development process must also have important properties: a exha- tive coverage of the development phases, and a set of well integrated support tools. In Computer Science it is now widely accepted that only formal notations can guarantee a perfect de?ned meaning. This becomes a more and more important issue since software systems tend to be distributed in large systems (for instance in safe public transportation systems), and in small ones (for instance numerous processors in luxury cars). Distribution increases the complexity of embedded software while safety criteria get harder to be met. On the other hand, during the past decade Software Engineering techniques have been improved a lot, and are now currently used to conduct systematic and rigorous development of large software systems. UML has become the de facto standard notation for documenting Software Engineering projects. UML is supported by many CASE tools that offer graphical means for the UML notation.

Keywords

Computer Unified Modeling Language (UML) algorithms complexity distributed systems embedded systems formal method formal specification modeling organization

Editors and affiliations

  • Fabrice Kordon
    • 1
  • Michel Lemoine
    • 2
  1. 1.Université P. & M. CurieFrance
  2. 2.ONERA Centre de ToulouseFrance

Bibliographic information

  • DOI https://doi.org/10.1007/b116264
  • Copyright Information Springer Science + Business Media, Inc. 2004
  • Publisher Name Springer, Boston, MA
  • eBook Packages Springer Book Archive
  • Print ISBN 978-1-4020-7996-2
  • Online ISBN 978-1-4020-7997-9
  • About this book
Industry Sectors
Electronics
Telecommunications
Biotechnology