Formal Methods and Object Technology

Stephen J. Goldsack et Stuart J.H. Kent

ISBN 10: 3540199772 / ISBN 13: 9783540199779

Published by Springer-Verlag Berlin and Heidelberg GmbH & Co. K, 1996

About this Item

Ancien livre de bibliothèque. Edition 1996. Ammareal reverse jusqu'à 15% du prix net de cet article à des organisations caritatives. ENGLISH DESCRIPTION Book Condition: Used, Very good. Former library book. Edition 1996. Ammareal gives back up to 15% of this item's net price to charity organizations. Seller Inventory # E-554-885

Bibliographic Details

Title: Formal Methods and Object Technology

Publisher: Springer-Verlag Berlin and Heidelberg GmbH & Co. K

Publication Date: 1996

Binding: Softcover

Condition: Très bon

About this title

Synopsis:

Rationale Software engineering aims to develop software by using approaches which en­ able large and complex program suites to be developed in a systematic way. However, it is well known that it is difficult to obtain the level of assurance of correctness required for safety critical software using old fashioned program­ ming techniques. The level of safety required becomes particularly high in software which is to function without a break for long periods of time, since the software cannot be restarted and errors can accumulate. Consequently programming for mission critical systems, for example, needs to address the requirements of correctness with particular care. In the search for techniques for making software cheaper and more reliable, two important but largely independent influences have been visible in recent years. These are: · Object Technology · Formal Methods First, it has become evident that objects are, and will remain an important concept in software. Experimental languages of the 1970's introduced various concepts of package, cluster, module, etc. giving concrete expression to the importance of modularity and encapsulation, the construction of software com­ ponents hiding their state representations and algorithmic mechanisms from users, exporting only those features (mainly the procedure calling mechanisms) which were needed in order to use the objects. This gives the software com­ ponents a level of abstraction, separating the view of what a module does for the system from the details of how it does them.