Formal Methods for Embedded Distributed Systems: How to master the complexity / Edition 1

Hardcover (Print)
Buy New
Buy New from BN.com
$170.05
Used and New from Other Sellers
Used and New from Other Sellers
from $11.00
Usually ships in 1-2 business days
(Save 93%)
Other sellers (Hardcover)
  • All (8) from $11.00   
  • New (4) from $41.63   
  • Used (4) from $11.00   

Overview

The development of any Software (Industrial) Intensive System, e.g. critical embedded software, requires both different notations, and a strong development 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! Formal Methods for Embedded Distributed Systems is dedicated to the presentation of some techniques to be used in the context of distributed and/or embedded systems. Since formal techniques rely on models, i.e. different descriptions of the system to be designed, the presented techniques are located in the first part of software development. Formal Methods for Embedded Distributed Systems makes many connections between "traditional development approaches" and the latest developments in formal techniques that are known as the best solution to significantly increase the reliability of such systems. The target audience is mainly composed of professionals (engineers, researchers and teachers), and students (graduated and postgraduated) who want to have a clear understanding of how to manage the inherent complexity of critical and/or distributed systems.

Read More Show Less

Product Details

  • ISBN-13: 9781402079962
  • Publisher: Springer US
  • Publication date: 9/15/1991
  • Edition description: 2004
  • Edition number: 1
  • Pages: 263
  • Product dimensions: 9.21 (w) x 6.14 (h) x 0.69 (d)

Table of Contents

PrefaceContributing AuthorsIntroduction; F. Kordon, M. Lemoine 1. The "Traditional" development approach2. What is covered in this book3. Organization of chaptersPart I: The BART Case Study1: The BART Case Study; V. Winter, F. Kordon, M. Lemoine 1. Introduction2. Objective3. General Background on the BART Train System4. Informal Specification for the AATC System 5. Inputs and Outputs to the Control Algorithm6. Physical Performance of the Train in Response to Commands7. Worst Case Stopping Profile8. Considerations with Acceleration and Speed Commands9. Quantitative Quality and Safety Metrics to be Demonstrated 10. Vital Station Computer (VSC) Issues11. Miscellaneous Questions and AnswersPart II: Building and Validating Conceptual Aspects2: Formal Specification and Refinement of a Safe Train Control Function; V. Winter, D. Kapur, G. Fuehrer 1. Introduction2. Technical approach and method3. Inputs taken from the BART case study 4. Applying the approach to the case study5. Results raised by this technique6. Conclusion7. Appendixes3: From UML to Z; M. Lemoine, G. Gaudière 1. Introduction 2. Technical approach and method 3. Our approach in details 4. Inputs taken from the BART case study 5. Applying the approach to the case study 6. Results raised by this technique 7. Conclusion
4: Environmental Modeling with UML; Adriaan de Groot, Jozef Hooman 1. Introduction 2. Technical approach and method 3. Applying our approach to the case study 4. Designing a Controller 5. Results raised by this technique 6. Conclusion Part III: Building and Validating Operational Aspects
5: Checking BART Test Scenarios with UML’s Object Constraint Language; M. Gogolla, P. Ziemann 1. Introduction 2. Technical approach and method 3. Inputs taken from the BART case study 4. Applying the approach to the case study 5. Results raised by this technique 6. Conclusion
6: Modeling and verifying behavioral aspects; F. Bréant, J. -M. Couvreur, F. Gilliers, F. Kordon, I. Mounier, E. Paviot-Adet, D. Poitrenaud, D. Regep, G. Sutre 1. Introduction2. Technical approach and method3. Inputs taken from the DART case study4. Applying the approach to the case study5. State space computation using DDD6. Conclusion Part IV: Methodological Aspects
7: AutoFocus - Mastering the Complexity; B. Schätz 1. Introduction2. Technical Approach and Method3. Inputs taken from the BART case study4. Applying the approach to the case study5. Results raised by this technique6. Conclusion8: Conclusions; F. Kordon, M. Lemoine 1. Are Formal Methods an appropriate answer to the Design of Distributed Systems?2. A process for the Design of Safety Critical Distributed Systems

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)