BIBLIO is the largest independent book marketplace in the world, with over 100 million books.

Skip to content

Formal Methods for Embedded Distributed Systems: How to master the complexity (Kluwer International Series in Engineering & Computer Scienc)

Formal Methods for Embedded Distributed Systems: How to master the complexity (Kluwer International Series in Engineering & Computer Scienc)

Formal Methods for Embedded Distributed Systems: How to master the complexity
Stock photo: cover may vary

Formal Methods for Embedded Distributed Systems: How to master the complexity (Kluwer International Series in Engineering & Computer Scienc) Hardback - 1991

by Kordon, Fabrice

Add to wish list
  • New
  • Hardback
New

Description

Springer, 1991-09-15. 2004. hardcover. New. 6.14x0.69x9.21. Buy with confidence. Excellent Customer Service & Return policy.
Ask the seller a question Add to wish list
A$172.97
Free Delivery within USA
Standard delivery: 5 to 10 days
More delivery options
Dropship order
Ships from Ergodebooks (Texas, United States)

Details

About Ergodebooks Texas, United States

Biblio member since 2005

Our goal is to provide best customer service and good condition books for the lowest possible price. We are always honest about condition of book. We list book only by ISBN # and hence exact book is guaranteed.

Terms of Sale:

We have 30 day return policy.

Browse books from Ergodebooks

Reader reviews for Formal Methods for Embedded Distributed Systems: How to master the complexity (Kluwer International Series in Engineering & Computer Scienc)

From the publisher

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.

First line

tracking-