You may have to Search all our reviewed books and magazines, click the sign up button below to create a free account.
1 In a number of recent presentations – most notably at FME’96 –oneofthe foremost scientists in the ?eld of formal methods, C.A.R. Hoare,has highlighted the fact that formal methods are not the only technique for producing reliable software. This seems to have caused some controversy,not least amongst formal methods practitioners. How can one of the founding fathers of formal methods seemingly denounce the ?eld of research after over a quarter of a century of support? This is a question that has been posed recently by some formal methods skeptics. However, Prof. Hoare has not abandoned formal methods. He is reiterating, 2 albeitmoreradically,his1987view thatmorethanonetoolandnotationwi...
Presents an authoritative register of Virginia's colonial soldiers, drawing on county court minutes, bounty land applications, records of courts martial, county militia rosters, and public records in England. Detailed information on soldiers' names, ranks, pay, places of birth, and appearance is divided into sections on different sources and different conflicts, including King George's War, the French and Indian War, and Dunmore's War. Useful for genealogists and historians. Annotation copyrighted by Book News, Inc., Portland, OR
In the early 1990s, NASA Goddard Space Flight Center started researching and developing autonomous and autonomic ground and spacecraft control systems for future NASA missions. This research started by experimenting with and developing expert systems to automate ground station software and reduce the number of people needed to control a spacecraft. This was followed by research into agent-based technology to develop autonomous ground c- trol and spacecraft. Research into this area has now evolved into using the concepts of autonomic systems to make future space missions self-managing and giving them a high degree of survivability in the harsh environments in which they operate. This book des...
This book provides a comprehensive introduction to various mathematical approaches to achieving high-quality software. An introduction to mathematics that is essential for sound software engineering is provided as well as a discussion of various mathematical methods that are used both in academia and industry. The mathematical approaches considered include: Z specification language Vienna Development Methods (VDM) Irish school of VDM (VDM) approach of Dijkstra and Hoare classical engineering approach of Parnas Cleanroom approach developed at IBM software reliability, and unified modelling language (UML). Additionally, technology transfer of the mathematical methods to industry is considered. The book explains the main features of these approaches and applies mathematical methods to solve practical problems. Written with both student and professional in mind, this book assists the reader in applying mathematical methods to solve practical problems that are relevant to software engineers.
Reports about recent developments of ADA, especially in the UK. It contains an introduction to ADA 9X and reports about the improved support for object-oriented programming and the tasking model. It also discusses high-integrity applications, safety critical software development and the mapping of ADA projects on the 2157A standard.
A brief but comprehensive introduction to the field and pragmatic guidance on the implementation of a sound quality system in the organization. It provides an enhanced knowledge of software inspections, metrics, process involvement, assessment of organization, problem solving, customer satisfaction surveys, the CMM, SPICE, and formal methods. Sample material on software inspections, metrics, and customer satisfaction can be adapted by readers to their respective organizations. In addition, readers will gain a detailed understanding of the principles of software quality management and software process improvement. Concepts can then be readily applied to assist improvement programs within organizations.
Software has long been perceived as complex, at least within Software Engineering circles. We have been living in a recognised state of crisis since the first NATO Software Engineering conference in 1968. Time and again we have been proven unable to engineer reliable software as easily/cheaply as we imagined. Cost overruns and expensive failures are the norm. The problem is fundamentally one of complexity: software is fundamentally complex because it must be precise. Problems that appear to be specified quite easily in plain language become far more complex when written in a more formal notation, such as computer code. Comparisons with other engineering disciplines are deceptive. One cannot ...