Formal Methods and Object Technology

Descripción:

This text presents an overview of two approaches to software engineering - formal methods and object-oriented techniques. By extracting the best aspects of each, the text demonstrates how better and safer software is being developed. Three main strands of research are identified and discussed. Editor(s): Goldsack, Stephen J.; Kent, Stuart J. H. Series: Formal Approaches to Computing & Information Technology (FACIT). Num Pages: 368 pages, biography. BIC Classification: UMN; UMX; UMZ. Category: (P) Professional & Vocational; (UP) Postgraduate, Research & Scholarly. Dimension: 234 x 156 x 20. Weight in Grams: 543. . 1996. Softcover reprint of the original 1st ed. 1996. Paperback. . . . . Books ship from the US and Ireland. N° de ref. del artículo V9783540199779

Denunciar este artículo

Sinopsis:

Reseña del editor: 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.