
Dependability Metrics
GI-Dagstuhl Research Seminar, Dagstuhl Castle, Germany, October 5 - November 1, 2005, Advanced Lectures
Springer (Publisher)
Published on 30. May 2008
Book
Paperback/Softback
XI, 305 pages
978-3-540-68946-1 (ISBN)
Description
With the growingubiquity of computing systems it is essentialthat we canplace reliance on the services they deliver. This is particularly obvious and important in areas like aircraft avionics, global ?nancial transaction processing, or nuclear power plant control where human lives or large ?nancial values are at stake. But also the worldwide daily nuisances of computer viruses or data corruptions caused by crashing operating systems collectively impose high costs on society, which are beginning to become economically relevant. Within computer science, the termdependability has been introduced as a general term to cover all critical quality aspects of computing systems. Foll- ing the terminology of Laprie [26, 293], a system is dependable if trust can justi?ably be placed in the service it delivers (we will de?ne dependability and related terms more precisely later in this book). In the early days of computer science, researchers thought thatprogram correctness was the key to depe- ability meaning that a programalways terminates and satis?es its postcondition if it is started in a state where its precondition holds. Today we knowthat many other factors in?uence the well-functioning of a computer system.
Examples of these factors are: - Hardware reliability: The occurrence of hardware faults, which cannot be neglected in critical systems. - Non-functional properties: The growingimportance of properties which c- not be expressed so easily as pre- and postconditions. As an example, c- sider the performance requirement that the averageresponse time should be below some value.
Examples of these factors are: - Hardware reliability: The occurrence of hardware faults, which cannot be neglected in critical systems. - Non-functional properties: The growingimportance of properties which c- not be expressed so easily as pre- and postconditions. As an example, c- sider the performance requirement that the averageresponse time should be below some value.
More details
Series
Edition
2008 ed.
Language
English
Place of publication
Berlin
Germany
Publishing group
Springer Berlin
Target group
Professional and scholarly
Research
Illustrations
XI, 305 p.
Dimensions
Height: 235 mm
Width: 155 mm
Thickness: 18 mm
Weight
493 gr
ISBN-13
978-3-540-68946-1 (9783540689461)
DOI
10.1007/978-3-540-68947-8
Schweitzer Classification
Content
to Dependability Metrics.- to Dependability Metrics.- I Foundations.- On Metrics and Measurements.- Validation of Predictions with Measurements.- Consistent Metric Usage: From Design to Deployment.- Basic and Dependent Metrics.- Goal, Question, Metric.- Quality of Service Modeling Language.- Markov Models.- II Reliability Metrics.- Hardware Reliability.- Software Reliability.- III Security Metrics.- to Security Metrics.- Cryptographic Attack Metrics.- Security Measurements and Metrics for Networks.- Industrial Approaches and Standards for Security Assessment.- Economic Security Metrics.- Human Factors.- IV Performance Metrics.- to Performance Metrics.- Performance-Related Metrics in the ISO 9126 Standard.- Analytical Performance Metrics.- Performance Metrics in Software Design Models.- Measuring Performance Metrics: Techniques and Tools.- Performance Metrics for Specific Domains.- V Overlapping Metrics.- to Overlapping Attributes.- Performability.- Reliability vs. Security: A Subjective Overview.