000 03863nam a22005415i 4500
001 978-3-030-86152-0
003 DE-He213
005 20240423125520.0
007 cr nn 008mamaa
008 220103s2021 sz | s |||| 0|eng d
020 _a9783030861520
_9978-3-030-86152-0
024 7 _a10.1007/978-3-030-86152-0
_2doi
050 4 _aQA76.758
072 7 _aUMZ
_2bicssc
072 7 _aCOM051430
_2bisacsh
072 7 _aUMZ
_2thema
082 0 4 _a005.1068
_223
100 1 _aMyklebust, Thor.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
245 1 0 _aFunctional Safety and Proof of Compliance
_h[electronic resource] /
_cby Thor Myklebust, Tor Stålhane.
250 _a1st ed. 2021.
264 1 _aCham :
_bSpringer International Publishing :
_bImprint: Springer,
_c2021.
300 _aXXIV, 265 p. 73 illus., 57 illus. in color.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
505 0 _a1. 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.
520 _aThis 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. Features and Benefits • First book about how to plan and develop relevant proof of compliance documentation and information • Describes in detail what to include in relevant plans and documents • Provides manufacturers, developers, consultants and operators with numerous example plans.
650 0 _aSoftware engineering
_xManagement.
650 0 _aElectronic data processing
_xManagement.
650 0 _aIndustrial Management.
650 0 _aData protection.
650 1 4 _aSoftware Management.
650 2 4 _aIT Operations.
650 2 4 _aIndustrial Management.
650 2 4 _aSecurity Services.
700 1 _aStålhane, Tor.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
710 2 _aSpringerLink (Online service)
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783030861513
776 0 8 _iPrinted edition:
_z9783030861537
856 4 0 _uhttps://doi.org/10.1007/978-3-030-86152-0
912 _aZDB-2-SCS
912 _aZDB-2-SXCS
942 _cSPRINGER
999 _c178784
_d178784