Functional Safety and Proof of Compliance

Thor Myklebust, Tor Stålhane

$168.95 $134.76

Paperback

Not in-store but you can order this
How long will it take?

Availability Information

We source books from suppliers in Australia and overseas. For books we don't currently have in stock, the time it takes to get them from our suppliers can vary widely - from a few days to a few months - so we check each book with each supplier to determine the expected time it will take to be supplied to us.

We then advise you accordingly. If the time taken to get any book is too long for you, you can let us know and we will cancel or adjust your order, and refund as required.

To find out the anticipated arrival time for specific items prior to ordering, please contact us by phone or email:

Phone +61 2 9264 3111, or 1800 4 BOOKS (1800 4 26657) if outside Sydney:
option 1 Abbey's Bookshop (Crime, History, Science, Kids & more) • info@abbeys.com.au
option 2 Language Book Centre (ESL & Foreign Languages) • language@abbeys.com.au
option 3 Galaxy Bookshop (Sci-fi, Fantasy, Romance, Graphic Novels) • sf@galaxybooks.com.au

QTY:

English

Springer Nature Switzerland AG
04 January 2022

Business mathematics & systems; Engineering: general; Health & safety aspects of computing; Computer security; Information architecture

This book aims to facilitate and improve development work related to all documents and information required by functional safety standards.

Proof of Compliance (PoC) is important for the assessor and certification bodies when called up to confirm that the manufacturer has developed a software system according to the required safety standards. While PoC documents add functionality to the product neither for the developer nor for the customer, they do add confidence and trust to the product and ease certification, and as such are important for the product’s value. In spite of this added value, the documentation needed for PoC is often developed late in the project and in a haphazard manner.

This book aims at developers, assessors, certification bodies, and purchasers of safety instrumented systems and informs the reader about the most important PoC documents. A typical PoC documentation encompasses 50 to 200 documents, several of which are named in the safety standards (e.g., 82 documents in IEC 61508:2010 series, 101 documents in EN 5012X series and 106 work products in ISO 26262:2018 series). These documents also include further references, typically one to twenty of them, and the total number of pages developed by the manufacturer varies between 2000 and 10000 pages. The book provides guidance and examples what to include in the relevant plans and documents.

By: Thor Myklebust, Tor Stålhane
Imprint: Springer Nature Switzerland AG
Country of Publication: Switzerland
Edition: 1st ed. 2021
Dimensions: Height: 235mm, Width: 155mm,
Weight: 450g
ISBN: 9783030861513
ISBN 10: 3030861511
Pages: 265
Publication Date: 04 January 2022
Audience: Professional and scholarly , Undergraduate
Format: Paperback
Publisher's Status: Active

1. The Introduction.- 2. Agile Practices.- 3. POC in Agile Development and for SMEs.- 4. Generic Documents.- 5. Plans and Functional safety Management.- 6. Safety Analysis Methods Applied to Software.- 7. Safety and Risk Documents.- 8. Software Documents.- 9. Test, Analysis and V&V.

Thor Myklebust is a senior safety assessor, business developer and researcher at SINTEF Digital in Norway, where he is involved in mainly international and national development and research projects. He has participated in several international committees since 1988, been a member of safety IEC 65, the IEC 61508 international committee, railway CENELEC/TC 9 and NB-rail (notified bodies) since 2007. In addition, he was vice chair of NB-Rail in 2014 and chairman of NB-Rail in 2015. He is also one of the founders of SafeScrum®, a methodology for agile development of safety-critical software. Tor Stålhane is professor emeritus at the Norwegian University of Science and Technology in Trondheim. He holds a PhD in statistics and is currently doing research in software engineering and system safety analysis. He, too, is one of the founders of SafeScrum®.