Difference between revisions of "ISO26262/Supporting Processes"
(Created page with "{{ISO26262}}") |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{ISO26262}} | {{ISO26262}} | ||
+ | |||
+ | '''8-5 Interfaces within distributed developments''' | ||
+ | |||
+ | |||
+ | '''8-6 Specification and management of safety requirements''' | ||
+ | |||
+ | |||
+ | '''8-7 Configuration management''' | ||
+ | |||
+ | "General: | ||
+ | Configuration management is a well established practice within the automotive industry and can be applied according to ISO/TS 16949, ISO 10007 and ISO/IEC 12207. Each work product of ISO 26262 is managed by configuration management." | ||
+ | - ISO 26262-8:2011, 6.5.1 | ||
+ | |||
+ | |||
+ | The norm refers to ISO/TS 16949 for configuration management. However, when searching the ISO/TS 16949 it becomes quickly clear that simply searching for "configuration management" will not bring up anything useful. Instead, have a look at chapter 7.5.3 "Identification and Traceability" and chapter 4.2.4 "Control of Records". | ||
+ | |||
+ | |||
+ | Please note that according to ISO26262-8:2011, 7.4.2 software development has to comply with the clause on configuration management in ISO/IEC12207. | ||
+ | |||
+ | |||
+ | '''Work product:''' | ||
+ | |||
+ | * Configuration Management Plan (resulting from ISO26262-8:2011 chapter 7.4.1, 7.4.2 and 7.4.5) | ||
+ | |||
+ | |||
+ | '''8-8 Change management''' | ||
+ | |||
+ | |||
+ | |||
+ | '''Prerequisites:''' | ||
+ | |||
+ | * Configuration Management Plan | ||
+ | * Safety Plan | ||
+ | |||
+ | '''Work products:''' | ||
+ | |||
+ | * Change management plan | ||
+ | * Change request | ||
+ | * Impact analysis and change request plan | ||
+ | * Change report | ||
+ | |||
+ | |||
+ | '''8-9 Verification''' | ||
+ | |||
+ | |||
+ | '''8-10 Documentation''' | ||
+ | |||
+ | |||
+ | '''8-11 Confidence in the use of software tools''' | ||
+ | |||
+ | |||
+ | '''8-12 Qualification of software components''' | ||
+ | |||
+ | |||
+ | '''8-13 Qualification of hardware components''' | ||
+ | |||
+ | |||
+ | '''8-14 Proven in use argument''' | ||
+ | |||
+ | |||
+ | An example of the proven in use argument with a template can be downloaded by clicking the link below. | ||
+ | |||
+ | ''Proven in Use template with example'' |
Latest revision as of 08:57, 28 September 2017
8-5 Interfaces within distributed developments
8-6 Specification and management of safety requirements
8-7 Configuration management
"General: Configuration management is a well established practice within the automotive industry and can be applied according to ISO/TS 16949, ISO 10007 and ISO/IEC 12207. Each work product of ISO 26262 is managed by configuration management." - ISO 26262-8:2011, 6.5.1
The norm refers to ISO/TS 16949 for configuration management. However, when searching the ISO/TS 16949 it becomes quickly clear that simply searching for "configuration management" will not bring up anything useful. Instead, have a look at chapter 7.5.3 "Identification and Traceability" and chapter 4.2.4 "Control of Records".
Please note that according to ISO26262-8:2011, 7.4.2 software development has to comply with the clause on configuration management in ISO/IEC12207.
Work product:
- Configuration Management Plan (resulting from ISO26262-8:2011 chapter 7.4.1, 7.4.2 and 7.4.5)
8-8 Change management
Prerequisites:
- Configuration Management Plan
- Safety Plan
Work products:
- Change management plan
- Change request
- Impact analysis and change request plan
- Change report
8-9 Verification
8-10 Documentation
8-11 Confidence in the use of software tools
8-12 Qualification of software components
8-13 Qualification of hardware components
8-14 Proven in use argument
An example of the proven in use argument with a template can be downloaded by clicking the link below.
Proven in Use template with example