Search Results

Modern development processes put architecture and design models in the center of system engineering activities. With the increasing application of software (SW) controlled functions such development processes have obtained a high significance in the automotive industry too. In addition, functional safety standards such as ISO 26262 [1] issued by International Standardization Organization (ISO) require safety analysis procedures to be tightly integrated with these engineering activities. The authors show a solution to tackle the need for such integration by using architecture and design models as a single source of information for functional safety analysis activities and methods. Moreover, a seamless round-trip approach between the activities of the system design, the requirements engineering and the functional safety analysis activities is presented.

ISO 26262 is the actual standard for Functional Safety of automotive E/E (Electric/Electronic) systems. One of the challenges in the application of the standard is the distribution of safety related activities among the participants in the supply chain. In this paper, the concept of a Safety Element out of Context (SEooC) development will be analyzed showing its current problematic aspects and difficulties in implementing such an approach in a concrete typical automotive development flow with different participants (e.g. from OEM, tier 1 to semiconductor supplier) in the supply chain. The discussed aspects focus on the functional safety requirements of generic hardware and software development across the supply chain where the final integration of the developed element is not known at design time and therefore an assumption based mechanism shall be used.

ISO 26262 is the actual standard for Functional Safety of automotive E/E (Electric/Electronic) systems. One of the challenges in the application of the standard is the distribution of safety related activities among the participants in the supply chain. In this paper, the concept of a Safety Element out of Context (SEooC) development will be analyzed showing its current problematic aspects and difficulties in implementing such an approach in a concrete typical automotive development flow with different participants (e.g. from OEM, tier 1 to semiconductor supplier) in the supply chain. The discussed aspects focus on the functional safety requirements of generic hardware and software development across the supply chain where the final integration of the developed element is not known at design time and therefore an assumption based mechanism shall be used.