Based on the experiences of nine partners from fields as diverse as oil and gas production, transportation, aerospace, nuclear power, and defense, this work presents an in-depth examination of the issues involved in assuring consistent functionality of safety software through rigorous testing. This handbook presents clear guidelines on leading practices of testing safety-related software, including the latest IEEE and IEC standards.
"Sinopsis" puede pertenecer a otra edición de este libro.
As software is very complex, we can only test a limited range of the possible states of the software in a reasonable time frame. In 1972, Dijkstra [1] claimed that 'program testing can be used to show the pres ence of bugs, but never their absence' to persuade us that a testing approach alone is not acceptable. This frequently quoted statement represented our knowledge about software testing at that time, and after over 25 years intensive practice, experiment and research, although software testing has been developed into a validation and ver ification technique indispensable to software engineering discipline, Dijkstra's state ment is still valid. To gain confidence in the safety of software based systems we must therefore assess both the product and the process of its development. Testing is one of the main ways of assessing the product, but it must be seen, together with process assessment, in the context of an overall safety case. This book provides guidance on how to make best use of the limited resources available for testing and to maximise the contribution that testing of the product makes to the safety case. 1.1 Context The safety assurance of software based systems is a complex task as most fail ures stem from design errors committed by humans. To provide safety assur on the integrity of the system and put ance, evidence needs to be gathered forward as an argued case (the safety case) that the system is adequately safe.
"Sobre este título" puede pertenecer a otra edición de este libro.
Librería: HPB-Red, Dallas, TX, Estados Unidos de America
paperback. Condición: Good. Connecting readers with great books since 1972! Used textbooks may not include companion materials such as access codes, etc. May have some wear or writing/highlighting. We ship orders daily and Customer Service is our top priority! Nº de ref. del artículo: S_361967350
Cantidad disponible: 1 disponibles
Librería: DFTP Holdings, DAYTON, OH, Estados Unidos de America
Paperback. Condición: Good. Used Texts May Have Used Book Stickers on the Cover. Used texts may NOT contain supplemental materials such as CD's, info-trac, access codes, etc. Satisfaction Guaranteed! Nº de ref. del artículo: 2018997
Cantidad disponible: 1 disponibles
Librería: BuchWeltWeit Ludwig Meier e.K., Bergisch Gladbach, Alemania
Taschenbuch. Condición: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware -As software is very complex, we can only test a limited range of the possible states of the software in a reasonable time frame. In 1972, Dijkstra [1] claimed that 'program testing can be used to show the pres ence of bugs, but never their absence' to persuade us that a testing approach alone is not acceptable. This frequently quoted statement represented our knowledge about software testing at that time, and after over 25 years intensive practice, experiment and research, although software testing has been developed into a validation and ver ification technique indispensable to software engineering discipline, Dijkstra's state ment is still valid. To gain confidence in the safety of software based systems we must therefore assess both the product and the process of its development. Testing is one of the main ways of assessing the product, but it must be seen, together with process assessment, in the context of an overall safety case. This book provides guidance on how to make best use of the limited resources available for testing and to maximise the contribution that testing of the product makes to the safety case. 1.1 Context The safety assurance of software based systems is a complex task as most fail ures stem from design errors committed by humans. To provide safety assur on the integrity of the system and put ance, evidence needs to be gathered forward as an argued case (the safety case) that the system is adequately safe. 240 pp. Englisch. Nº de ref. del artículo: 9781852330347
Cantidad disponible: 2 disponibles
Librería: Books Puddle, Woodside, NY, Estados Unidos de America
Condición: New. pp. 226. Nº de ref. del artículo: 263041978
Cantidad disponible: 4 disponibles
Librería: moluna, Greven, Alemania
Condición: New. Dieser Artikel ist ein Print on Demand Artikel und wird nach Ihrer Bestellung fuer Sie gedruckt. Covers most up-to-date standards including the relevant IEEE and IEC standards Presents clear structured guidelines on leading test practices Shows how proper testing can result in acceptable safety integrity levels Based on the experiences of nine partners. Nº de ref. del artículo: 4289322
Cantidad disponible: Más de 20 disponibles
Librería: Majestic Books, Hounslow, Reino Unido
Condición: New. Print on Demand pp. 226. Nº de ref. del artículo: 5887333
Cantidad disponible: 4 disponibles
Librería: Biblios, Frankfurt am main, HESSE, Alemania
Condición: New. PRINT ON DEMAND pp. 226. Nº de ref. del artículo: 183041968
Cantidad disponible: 4 disponibles
Librería: AHA-BUCH GmbH, Einbeck, Alemania
Taschenbuch. Condición: Neu. Druck auf Anfrage Neuware - Printed after ordering - As software is very complex, we can only test a limited range of the possible states of the software in a reasonable time frame. In 1972, Dijkstra [1] claimed that 'program testing can be used to show the pres ence of bugs, but never their absence' to persuade us that a testing approach alone is not acceptable. This frequently quoted statement represented our knowledge about software testing at that time, and after over 25 years intensive practice, experiment and research, although software testing has been developed into a validation and ver ification technique indispensable to software engineering discipline, Dijkstra's state ment is still valid. To gain confidence in the safety of software based systems we must therefore assess both the product and the process of its development. Testing is one of the main ways of assessing the product, but it must be seen, together with process assessment, in the context of an overall safety case. This book provides guidance on how to make best use of the limited resources available for testing and to maximise the contribution that testing of the product makes to the safety case. 1.1 Context The safety assurance of software based systems is a complex task as most fail ures stem from design errors committed by humans. To provide safety assur on the integrity of the system and put ance, evidence needs to be gathered forward as an argued case (the safety case) that the system is adequately safe. Nº de ref. del artículo: 9781852330347
Cantidad disponible: 1 disponibles
Librería: Revaluation Books, Exeter, Reino Unido
Paperback. Condición: Brand New. 235 pages. 9.25x6.00x0.50 inches. In Stock. Nº de ref. del artículo: zk1852330341
Cantidad disponible: 1 disponibles
Librería: buchversandmimpf2000, Emtmannsberg, BAYE, Alemania
Taschenbuch. Condición: Neu. This item is printed on demand - Print on Demand Titel. Neuware -As software is very complex, we can only test a limited range of the possible states of the software in a reasonable time frame. In 1972, Dijkstra [1] claimed that 'program testing can be used to show the pres ence of bugs, but never their absence' to persuade us that a testing approach alone is not acceptable. This frequently quoted statement represented our knowledge about software testing at that time, and after over 25 years intensive practice, experiment and research, although software testing has been developed into a validation and ver ification technique indispensable to software engineering discipline, Dijkstra's state ment is still valid. To gain confidence in the safety of software based systems we must therefore assess both the product and the process of its development. Testing is one of the main ways of assessing the product, but it must be seen, together with process assessment, in the context of an overall safety case. This book provides guidance on how to make best use of the limited resources available for testing and to maximise the contribution that testing of the product makes to the safety case. 1.1 Context The safety assurance of software based systems is a complex task as most fail ures stem from design errors committed by humans. To provide safety assur on the integrity of the system and put ance, evidence needs to be gathered forward as an argued case (the safety case) that the system is adequately safe.Springer-Verlag KG, Sachsenplatz 4-6, 1201 Wien 240 pp. Englisch. Nº de ref. del artículo: 9781852330347
Cantidad disponible: 1 disponibles