Page 9 Approval of safety cases

Error: paragraph break missing

Appears as

“The Safety Case Report format in this book is based on the information expected by CAP 1801, which defines a generic assessment method for Safety Case Reports. It is recognised that it is common to additionally sample detailed evidence items from the safety case that would not be expected to be included in the SC Report.”

Should be

“The Safety Case Report format in this book is based on the information expected by CAP 1801, which defines a generic assessment method for Safety Case Reports.

It is recognised that it is common to additionally sample detailed evidence items from the safety case that would not be expected to be included in the SC Report.”

Page 14 Addressing cyber security in the safety case report

Error: 'impact' should read 'effect'

Appears as

“This book addresses how and where to include the safety case material (if it is present) that concerns the potential impact of security and cyber security threats on the safety of the services. The SC Report format in this book does not address any other aspect of security risk management.”

Should be

This book addresses how and where to include the safety case material (if it is present) that concerns the potential effect of security and cyber security threats on the safety of the services. The SC Report format in this book does not address any other aspect of security risk management.

Page 15 Addressing cyber security in the safety case report

Error: 'increase' should read 'alter'

Appears as

“c)      increase the probability of an accident arising from a hazard, by reducing the effectiveness of mitigations.”

Should be

“c)      alter the probability of an accident arising from a hazard, by reducing the effectiveness of mitigations.”

Page 55 3.3.5

Error: maintenance and support activities should be environmental events

Appears as 

“c)      inherently included in the safety analysis modelling because the maintenance  and support activities are included in the POSS specifications.”

Should be

“c)      inherently included in the safety analysis modelling because the environmental events are included in the POSS specifications.”

Page 55 3.3.6

Error: missing word

Appears as

“b)     showing that the cyber security management is adequate elsewhere, and therefore the  safety case does not address these effects on the assumption that there will none”

Should be

“b)     showing that the cyber security management is adequate elsewhere, and therefore the safety case does not address these effects on the assumption that there will be none”

Page 56 3.3.7

Error: Missing word

Appears as

“b)     that physical security management is shown to be adequate elsewhere and therefore the safety case does not address these effects on the assumption that there will none”

Should be

“b)     that physical security management is shown to be adequate elsewhere and therefore the safety case does not address these effects on the assumption that there will be none”

Page 141 Integrity & Confidence

Error: Missing text

Appears as

“Integrity: the probability that the car will maintain the set cruise control speed within +/- 2%”

Should be

“Integrity: the probability that the car will maintain the set cruise control speed within +/- 2% shall be >98%”

Page 145 Safety Requirements

Error: Missing text

Appears as

“b)     The 'safety criteria' define the acceptable safety performance for each transitional stage,  derived from the ‘risk acceptance principles’, at the boundary of the Internal Assurance Scope applicable to that transitional stage.”

Should be

“b)     The 'safety criteria' define the acceptable safety performance for each transitional stage,  derived from the ‘risk acceptance principles’, at the boundary of the Internal Assurance Scope applicable to that transitional stage or above.”

Page 15, 23, 86, 145 Safety arguments addressing localised harm

Error: Incorrect heading

Appears as

“Safety arguments addressing localised harm”

Should  be

“Safety arguments addressing local harm”

Page 145 Service

Error: Incorrect terminology

Appears as

“A service is an output from a functional system that is intended to be of use. The output may be either intangible (e.g. information, data or instructions) or tangible (e.g. a product, commodity or function). In addition to the primary services, the functional system may also have one or more functions that provide services to protect against localised harm (see Safety arguments addressing local harm on page 15).”

Should be

“A service is an output from a functional system that is intended to be of use. The output may be either intangible (e.g. information, data or instructions) or tangible (e.g. a product, commodity or function). In addition to the primary services, the functional system may also have one or more functions that provide services to protect against local harm (see Safety arguments addressing local harm on page 15).”