Cart (0)
- No items in cart.
Total
$0
There is a technical issue about last added item. You can click "Report to us" button to let us know and we resolve the issue and return back to you or you can continue without last item via click to continue button.
Not a subscriber? Register for a trial account.
Already a subscriber? 
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
| Email * | |
| Password * | |
| Confirm * | |
| First Name * | |
| Last Name * | |
| Title | |
| Company Name * | |
| Company Size * | |
| Industry * | |
| Address * | |
| Address 2 | |
| City * | |
| State * |
Zip *
|
| Country * | |
| Phone * | |
| How did you hear about MADCAD.com? * |
|
Reset password
Enter your personal account email address to request
a password reset:
a password reset:
Reset password
Enter your account email address to request
a password reset:
a password reset:
Security check
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
Report To Us
Contact us for a custom quote
⨯To continue with accurate pricing,
please select your company type below:
⨯We need your input!
Are you a code official in a jurisdiction with less than 300,000 population?
⨯ We need your input!
⨯We need your input!
Are you an existing Madcad user?
If so, please login to continue with the free items in your cart.
⨯We need your input!
This bundle includes subscribed items.
Download File
eLibrary >
IEEE Standard for Functional Safety Data Format for Interoperability within the Dependability Lifecycle (Approved Draft) >
This document is reproduced and distributed under license from The Institute of Electrical and Electronics Engineers, Incorporated (IEEE), 445 Hoes Lane, Piscataway, New Jersey 08854 and is protected by United States and international copyright laws and treaties. No part of this publication may be reproduced, in any form and in any medium, without the prior written consent of the IEEE.
If you have any questions, please contact MADCAD.com at support@madcad.com or
call at 1.800.798.9296.
Expand All
TOC Search:
IEEE Standard for Functional Safety Data Format for Interoperability within the Dependability Lifecycle (Approved Draft), 2023
- Front cover
- Title page
- Important Notices and Disclaimers Concerning IEEE Standards Documents
- Participants
- Introduction
- Contents [Go to Page]
- List of Figures
- List of Tables
- 1. Overview [Go to Page]
- 1.1 Scope
- 1.2 Purpose
- 1.3 Word usage
- 2. Normative references
- 3. Definitions, acronyms, and abbreviations [Go to Page]
- 3.1 Definitions
- 3.2 Acronyms and abbreviations
- 4. Dependability management [Go to Page]
- 4.1 Objectives
- 4.2 Requirements and recommendations [Go to Page]
- 4.2.1 Dependability management process
- 4.2.2 Product impact analysis—ME, DB [Go to Page]
- 4.2.2.1 Product impact analysis—ME
- 4.2.2.2 Product impact analysis—DB
- 4.2.3 Development interface agreement (DIA)—DL
- 4.2.4 Software tools—ME, DB [Go to Page]
- 4.2.4.1 Software tools—DB
- 4.2.4.2 Software tools—ME
- 4.2.5 Monitoring of parameters for prognostics—DB
- 4.2.6 Tailoring of dependability activities—ME, DL, DB [Go to Page]
- 4.2.6.1 Tailoring of dependability activities—ME
- 4.2.6.2 Tailoring of dependability activities—DL
- 4.2.6.3 Tailoring of dependability activities—DB
- 4.2.7 Dependability case—DB
- 4.2.8 Confirmation reviews—ME
- 4.2.9 Dependability audit—ME
- 4.2.10 Dependability assessment—ME
- 4.2.11 Release for production—DB
- 5. Product definition [Go to Page]
- 5.1 Objectives
- 5.2 General
- 5.3 Inputs
- 5.4 Requirements and recommendations [Go to Page]
- 5.4.1 User story, user feature, and addressable market
- 5.4.2 System/life profile—DL, DB [Go to Page]
- 5.4.2.1 System/life profile—DL
- 5.4.2.2 System/life profile—DB
- 5.4.3 Hardware/software/system triggering conditions—DB
- 5.4.4 Operating situations and operating modes—DL, ME [Go to Page]
- 5.4.4.1 Operating situations and operating modes—DL
- 5.4.4.2 Operating situations and operating modes—ME
- 5.4.5 Item interdependency—DL
- 5.4.6 External measures for safety and security—DL, DB [Go to Page]
- 5.4.6.1 External measures for safety and security—DL
- 5.4.6.2 External measures for safety and security—DB
- 5.4.7 System level considerations for enabling deterministic performance—DB
- 5.4.8 Operating situations, operating modes, performance metrics, and dynamic conditions—DB
- 5.4.9 Environment use—DB
- 6. Generic requirements elicitation process of dependability lifecycle [Go to Page]
- 6.1 Objectives
- 6.2 General
- 6.3 Inputs
- 6.4 Requirements and recommendations [Go to Page]
- 6.4.1 Safety requirements—ME, DL [Go to Page]
- 6.4.1.1 Safety requirements—ME
- 6.4.1.2 Safety requirements—DL
- 6.4.2 Concept—DL
- 6.4.3 Risk level/ automotive safety integrity level (ASIL) alignment matrix—ME
- 6.4.4 Safety goal—DL
- 6.4.5 Hazards and risks—ME, DB [Go to Page]
- 6.4.5.1 Hazards and risks—ME
- 6.4.5.2 Hazards and risks—DB
- 6.4.6 Impact assessment vs. requirements in case of reuse of element(s)—ME, DL [Go to Page]
- 6.4.6.1 Impact assessment vs. requirements in case of reuse of element(s)—ME
- 6.4.6.2 Impact assessment vs. requirements in case of reuse of element(s)—DL
- 6.4.7 Threat and risk—DL
- 6.4.8 Platform tuning for safety critical real time applications—ME
- 6.4.9 Real time considerations for safety analysis—ME
- 6.4.10 Modeling of the radiation working environment—ME
- 6.4.11 HW and SW requirements traceability—DL
- 6.4.12 Ensuring deterministic performance for safety applications—ME
- 6.4.13 Common mode failures—DB
- 6.4.14 Radiation testing requirements for safety analysis—DB
- 6.4.15 Parameters for real time and safety metrics—DB
- 6.4.16 Contention/Shared resources of functional safety real time intersections—DB
- 6.4.17 System level considerations for enabling deterministic performance—DB
- 7. Generic design of dependable architecture [Go to Page]
- 7.1 Objectives
- 7.2 General
- 7.3 Inputs [Go to Page]
- 7.3.1 Prerequisites
- 7.4 Requirements and recommendations [Go to Page]
- 7.4.1 Failure mode—DL
- 7.4.2 Functional safety HW design—DL
- 7.4.3 Cybersecurity software testing—ME
- 7.4.4 Software architectural design (SAD)—ME, DL [Go to Page]
- 7.4.4.1 Software architectural design (SAD)—ME
- 7.4.4.2 Software architectural design (SAD)—DL
- 7.4.5 Artificial intelligence (AI) software configuration and calibration—ME, DL [Go to Page]
- 7.4.5.1 Artificial intelligence software configuration and calibration—ME
- 7.4.5.2 Artificial intelligence software configuration and calibration—DL
- 7.4.6 Safety mechanism and safety envelope—DL
- 7.4.7 Automotive safety integrity level (ASIL) decomposition—ME
- 7.4.8 System architectural design—DL
- 7.4.9 SW design/algorithm impact analysis—ME
- 7.4.10 Confidence in use of software tools evaluation—ME, DL [Go to Page]
- 7.4.10.1 Confidence in use of software tools evaluation—ME
- 7.4.10.2 Confidence in use of software tools evaluation—DL
- 7.4.11 Criteria for coexistence of elements—ME
- 7.4.12 Impact assessment vs. requirements in case of reuse of element(s)—ME, DL
- 7.4.13 Threat and risk—DL
- 7.4.14 Software development environment—DL
- 7.4.15 Model interoperability—ME, DL [Go to Page]
- 7.4.15.1 Model interoperability—ME
- 7.4.15.2 Model interoperability—DL
- 7.4.16 Platform tuning for safety critical real time applications—ME
- 7.4.17 Real time considerations for safety analysis—ME
- 7.4.18 Modeling of the radiation working environment—ME
- 7.4.19 Ensuring deterministic performance for safety applications—ME
- 7.4.20 System level considerations for deterministic performance—ME
- 7.4.21 Module design, integration, and testing report—DL
- 7.4.22 Dependent failure initiators (DFIs)—DB
- 7.4.23 Interface behavior parameters—DB
- 7.4.24 Failure modes including foreseeable misuse and known specification gaps—DB
- 7.4.25 Artificial intelligence training data—DB
- 7.4.26 Failures sources—DB
- 7.4.27 Hardware metrics assumptions—DB
- 7.4.28 Safety mechanisms—DB
- 7.4.29 Software tools safety evaluation benchmarks—DB
- 7.4.30 Failure modes for software—DB
- 7.4.31 System reliability-availability-and-serviceability (RAS) architecture capabilities—DB
- 7.4.32 Monitoring of parameters for prognostics—DB
- 7.4.33 Systematic faults—DB
- 7.4.34 Common mode failure—DB
- 7.4.35 Key parameters to consider for tradeoffs between real-time and safety metrics—DB
- 7.4.36 Contention/shared resources of functional safety-real time intersections—DB
- 7.4.37 System level considerations for enabling deterministic performance—DB
- 8. Software, hardware co-design and the interface to non-electrical/electronic system (E/E) technology [Go to Page]
- 8.1 Objectives
- 8.2 General
- 8.3 Inputs [Go to Page]
- 8.3.1 Prerequisites
- 8.4 Requirements and recommendations [Go to Page]
- 8.4.1 Hardware software interface—DL
- 8.4.2 Electrical/electronic (E/E) to non-electrical/electronic interface—DL
- 9. Implementation aspects [Go to Page]
- 9.1 Objectives
- 9.2 General
- 9.3 Inputs [Go to Page]
- 9.3.1 Prerequisites
- 9.3.2 Further supporting information
- 9.4 Requirements and recommendations [Go to Page]
- 9.4.1 Cybersecurity software testing—ME
- 9.4.2 Artificial intelligence training—ME, DB
- 9.4.3 Fault model for side channel threats (HW)/fault extraction/injection—ME
- 9.4.4 Software development environment—DL
- 9.4.5 Coding guidelines/code review—ME
- 9.4.6 Module design, integration, and testing report—DL
- 10. Verification, integration, and analysis [Go to Page]
- 10.1 Objectives
- 10.2 General [Go to Page]
- 10.2.1 V-model for verification and analysis
- 10.3 Inputs [Go to Page]
- 10.3.1 Prerequisites
- 10.4 Requirements and recommendations [Go to Page]
- 10.4.1 Failure modes and effects analysis (FMEA)/failure modes effects and diagnostics analysis (FMEDA)—ME, DL, DB [Go to Page]
- 10.4.1.1 Failure modes effects and diagnostics analysis—DL
- 10.4.1.2 Failure modes effects and diagnostics analysis—ME
- 10.4.1.3 Failure mode—DB
- 10.4.1.4 Failure modes and effects analysis—DB
- 10.4.2 Action priority (AP)—ME
- 10.4.3 Fault tree analysis (FTA)—ME, DB [Go to Page]
- 10.4.3.1 Fault tree analysis—ME
- 10.4.3.2 Fault tree analysis—DB
- 10.4.4 Dependent failure analysis (DFA)—ME, DL, DB [Go to Page]
- 10.4.4.1 Dependent failure analysis—ME
- 10.4.4.2 Dependent failure analysis—DL
- 10.4.4.3 Dependent failure analysis—DB
- 10.4.5 Dependability manual—DL
- 10.4.6 Base failure rate (BFR)—DL, DB [Go to Page]
- 10.4.6.1 Base failure rate—DL
- 10.4.6.2 Base failure rate—DB
- 10.4.7 Functional interface analysis (FIA)—ME
- 10.4.8 Hardware random failures evaluation—ME
- 10.4.9 Vulnerability factors modeling—ME
- 10.4.10 Stochastic behavior analysis—ME
- 10.4.11 Systematic analysis—ME
- 10.4.12 Operational situations and operating modes—ME, DL
- 10.4.13 Requirement’s traceability in verification, validation, and testing—DL
- 10.4.14 Safety mechanism verification—DB
- 10.4.15 Safety mechanism integration database—DB
- 10.4.16 AI System stimulus and safety performance indicator—DB
- 10.4.17 Systems theoretic process analysis (STPA)—ME
- 10.4.18 Hazard analysis and risk assessment (HARA)—ME, DB
- 10.4.19 Coexistence analysis—ME
- 10.4.20 Software components qualification—ME
- 10.4.21 Cybersecurity software testing—ME
- 10.4.22 Safety verification for safety goal violation—DL, ME [Go to Page]
- 10.4.22.1 Safety verification for safety goal violation—ME
- 10.4.22.2 Safety verification for safety goal violation—DL
- 10.4.23 Fault model for side channel threats (HW)/fault extraction/injection—ME
- 10.4.24 Best practice for system integration and testing of intended functionality—ME
- 10.4.25 Freedom from interference (FFI)—ME, DL [Go to Page]
- 10.4.25.1 Freedom from interference—ME
- 10.4.25.2 Freedom from interference—DL
- 10.4.26 Artificial intelligence safety validation—ME
- 10.4.27 Use of formal methods to verify real time performance—ME
- 10.4.28 Functional insufficiency of the intended functionality—ME, DL [Go to Page]
- 10.4.28.1 Functional Insufficiency of the intended functionality—ME
- 10.4.28.2 Functional insufficiency of the intended functionality—DL
- 10.4.29 Collection, inferring, and standardization of failures sources—ME
- 10.4.30 Common mode analysis (CMA)—ME
- 10.4.31 Commercial off-the-shelf (COTS) safety analysis—ME
- 10.4.32 Artificial intelligence system safety performance indicator—ME
- 10.4.33 Production verification of safety mechanisms—ME
- 10.4.34 Methodology for the validation of vulnerability factors—ME
- 10.4.35 Single event effects—DL, DB [Go to Page]
- 10.4.35.1 Single event effects—DL
- 10.4.35.2 Spectra of energetic particles—DB
- 10.4.35.3 Single event effects—DB
- 10.4.36 Software tools safety evaluation—DB
- 10.4.37 Effects and software real time constraints—DB
- 11. Dependability validation of the system integrated into the overall product with regard to the feature behavior in the operational domain [Go to Page]
- 11.1 Objectives
- 11.2 General
- 11.3 Inputs [Go to Page]
- 11.3.1 Prerequisites
- 11.3.2 Further supporting information
- 11.4 Requirements and recommendations [Go to Page]
- 11.4.1 Dependability validation environment
- 11.4.2 Specification of dependability validation
- 11.4.3 Execution of dependability validation
- 11.4.4 Evaluation
- 11.4.5 Safety requirements—ME, DL
- 11.4.6 Safety requirements evaluation—ME
- 11.4.7 Artificial intelligence system safety performance indicator—ME, DB
- 11.4.8 Artificial intelligence safety validation—ME
- 11.4.9 Operational situations and operating modes—ME, DL
- 11.4.10 Methodology for the validation of vulnerability factors—ME
- 11.4.11 System level considerations for deterministic performance—ME
- 11.4.12 Assumptions of use—DL
- 11.4.13 Safety diagnostic information—DL
- 11.4.14 Safety goal—DL
- 11.4.15 System/Component/IP-Level hardware and software requirements traceability—DL
- 11.4.16 Requirements traceability in verification, validation, and testing—DL
- 11.4.17 Operational situations and modes, use environment, performance metrics, and dynamic conditions—DB
- 12. Post-release activities [Go to Page]
- 12.1 Objectives
- 12.2 General
- 12.3 Inputs [Go to Page]
- 12.3.1 Prerequisites
- 12.4 Requirements and recommendations [Go to Page]
- 12.4.1 Safety diagnostic information—DL
- 12.4.2 Monitoring of parameters for prognostics—DB
- 12.4.3 Identification, impact, and resolution of safety anomalies—ME
- 12.4.4 Artificial intelligence models update—ME
- 12.4.5 Proven in use evaluation—ME
- 13. Dependability evaluation [Go to Page]
- 13.1 Objectives
- 13.2 General
- 13.3 Requirements and recommendations [Go to Page]
- 13.3.1 Safety requirements evaluation—ME
- 13.3.2 Safety assessment for software updates—ME
- 13.3.3 Hardware elements evaluation—ME, DL [Go to Page]
- 13.3.3.1 Hardware elements evaluation—ME
- 13.3.3.2 Hardware elements evaluation—DL
- 13.3.4 Safety case—DL
- 13.3.5 Assessment for conflicts between safe and secure system reactions—ME
- 13.3.6 Identification, impact, and resolution of safety anomalies—ME
- 13.3.7 Tradeoff assessment for real time and safety metrics—ME
- 13.3.8 Confirmation measures—DL
- Annex A (informative) Proposed safety security alignment flow [Go to Page]
- A.1 Overview
- A.2 Alignment flow at item, system, and IP/SoC levels
- A.3 Safety security alignment matrix [Go to Page]
- A.3.1 Deliverables from each discipline for requirements alignment [Go to Page]
- A.3.1.1 Safety team
- A.3.1.2 Security team
- A.3.2 Example use case—Power steering system
- Annex B (informative) SIPOC analysis-based needs traceability [Go to Page]
- B.1 Objectives
- B.2 General
- B.3 Inputs [Go to Page]
- B.3.1 Prerequisites
- B.3.2 Further supporting information
- B.4 Recommendations
- B.5 Work products
- Annex C (informative) Dependability clauses and requirements [Go to Page]
- C.1 Introduction
- C.2 Generic E/E system description
- C.3 Generic dependability lifecycle definition [Go to Page]
- C.3.1 Product lifecycle phases
- C.3.2 Development phase
- C.3.3 Dependable product development lifecycle [Go to Page]
- C.3.3.1 Design and verification of design
- C.3.3.2 Integration and verification, and validation
- C.3.4 Focusing on functional safety engineering [Go to Page]
- C.3.4.1 Guaranteeing dependability by common rules on systematics
- C.3.4.2 Dependability by balancing and arbitrating contradicting measures
- C.3.4.3 Affordable dependability
- C.3.4.4 Conclusion
- C.3.5 Lifecycle phases beyond development [Go to Page]
- C.3.5.1 Production
- C.3.5.2 Commissioning, service, and maintenance
- C.3.5.3 Operation
- C.3.5.4 Decommissioning
- C.4 Dependability management [Go to Page]
- C.4.1 Methodology and description language for dependability management
- C.4.2 Database (DB) for dependability management
- C.5 Product definition [Go to Page]
- C.5.1 User story, user feature, and addressable market
- C.5.2 Methodology, description language, and database for user story, user feature, and the addressable market
- C.5.3 Overall system feature behavior in operational domain, system/item definition addressing all dependability attributes
- C.5.4 Methodology, description language, and database for operational domain, system/item definition addressing all dependability attributes
- C.6 Generic requirements elicitation process of dependability lifecycle [Go to Page]
- C.6.1 General
- C.6.2 Methodological approach to requirement elicitation [Go to Page]
- C.6.2.1 Prerequisites for elicitation
- C.6.2.2 Flow compliant requirements
- C.6.2.3 Formal and informal aspects of requirements elicitation
- C.6.3 Identification of requirement types [Go to Page]
- C.6.3.1 Requirements for product development
- C.6.3.2 Requirements for post release activities
- C.6.3.3 Requirements for verification and validation
- C.6.4 Proposed data description language for requirements [Go to Page]
- C.6.4.1 Elaboration of the data description language
- C.6.5 Methodology and description language for requirement elicitation
- C.6.6 Database for requirement elicitation
- C.7 Generic design of dependable architecture [Go to Page]
- C.7.1 Modeling languages
- C.7.2 Modeling technique [Go to Page]
- C.7.2.1 Modeling language premises and architectural views
- C.7.2.2 Description language
- C.7.3 Methodology, description language, and database for dependable architecture
- C.8 Software and hardware co-design and the interface to non-E/E technology [Go to Page]
- C.8.1 Description language or SW, HW co-design
- C.9 Implementation aspects [Go to Page]
- C.9.1 Elements to be developed
- C.9.2 Reusing existing elements
- C.9.3 Methodology and description language of implementation aspects
- C.10 Verification, integration, and analysis [Go to Page]
- C.10.1 Introduction
- C.10.2 V-model for functional verification and analysis [Go to Page]
- C.10.2.1 Layering model
- C.10.3 Analysis activities [Go to Page]
- C.10.3.1 Hazard analysis and risk assessment (HARA)
- C.10.3.2 Types of functional safety analysis supporting verification [Go to Page]
- C.10.3.2.1 Failure modes and effects analysis
- C.10.3.2.2 Failure modes effects and diagnostics analysis
- C.10.3.2.3 Fault tree analysis (FTA)
- C.10.3.2.4 Dependent failure analysis (DFA)
- C.10.3.2.5 Coexistence analysis
- C.10.3.2.6 Freedom from interference
- C.10.3.2.7 Detailed FMEDA and safety mechanism verification
- C.10.3.3 Safety mechanism integration database
- C.10.3.4 Verification activities [Go to Page]
- C.10.3.4.1 Informal reviews
- C.10.3.4.2 Formal reviews
- C.10.3.4.3 Functional verification activities
- C.10.4 Methodology and description language for verification, integration, and analysis [Go to Page]
- C.10.4.1. Database for verification, integration, and analysis
- C.11 Dependability validation of the system integrated into the overall product with regard to the feature behavior in OD [Go to Page]
- C.11.1 Methodology and description language for dependability validation
- C.12 Post-release activities [Go to Page]
- C.12.1 Methodology for post-release activities
- C.13 Dependability evaluation [Go to Page]
- C.13.1 General
- C.13.2 Method and description language [Go to Page]
- C.13.2.1 Systematic approach
- C.13.2.2 Procedure
- C.13.2.3 Description language
- C.13.2.4 Database
- C.13.3 Methodology and description language for dependability evaluation [Go to Page]
- C.13.3.1 Database
- Annex D (informative) Bibliography
- Back cover [Go to Page]
Copyright 2025 Compu-tecture, Inc.
All Rights Reserved.
About Us /
Careers /
support@madcad.com /
1.800.798.9296