Methodology Model Overview. Figure 4 gives an overview about the most abstract view on the methodology. The methodology follows one to one the abstraction level principle of the EAST-ADL language, starting from the most abstract level, the vehicle phase, to the most concrete level, the implementation phase. The methodology shows an idealized forward process oriented view only. Iterations are not illus- trated in the methodology. This is reserved to the process instantiation in a concrete project. Standards managing functional safety aspects (e.g. ISO26262) usually are structured in a pro- cess-oriented manner. On the other hand standards which describe FEV specific features often refer to a concrete work product or to a specified vehicle part. Following these strategies the safety aspects given in the tables in chapter 4 (Methodology analy- sis) and in chapter 8 (Appendix ISO26262 Requirements) are grouped according the development process. The FEV aspects described in chapter 5 (Design Methodology Checklist for FEVs) are assigned to a specific subject. To define the MAENAD EAST-ADL methodology, the ATESST2 methodology was used as a basis. The normative regulation for functional safety in the automotive domain, ISO 26262, has phases with sub-phases comprised by work products, tools and the responsible role. Both process models were compared regarding functional safety to identify needs on methodology content. The follow- ing tables show an excerpt of this analysis. ISO Part Phase Sub-phase Work Products Tools Activity Responsible LINK to Product Development Work Flow (EAST-ADL Based) EAST-ADL artifacts P a r t 2 S a f e t y m a n a g e m e n t Overall safety management Organization-specific rules and processes for functional safety Not applicable Product Liability Manager Vehicle Level Analysis Level Design Level N/A Evidence of competence Not applicable Product Liability Manager Vehicle Level Analysis Level Design Level N/A Evidence of quality management Not applicable Product Liability Manager Vehicle Level Analysis Level Design Level N/A Safety management during the concept phase and the product development Safety plan Compatible with traceability requirements, change mangement, configuration… Safety Manager Vehicle Level Analysis Level Design Level VVCase for detailed activities, SafetyCase structure for overall information structure, Requirements with Satisfy relation to Ground to detail the evidence required. Project plan (refined) Not applicable Project Manager N/A Safety case...
