![](https://csdnimg.cn/release/download_crawler_static/12271662/bg12.jpg)
©ISO 2017 – Allrightsreserved 11
EXAMPLE While operating on a highway, a vehicle’s automated emergency braking (AEB) system273
misidentifiesaroadsignasaleadvehicleresultinginbrakingatXgforYseconds.Inthisexample,thetriggering274
conditionsaretheroadsignwhileoperatingonahighway.275
3.27276
usecase277
specificationofageneralizedfieldofapplication,possiblyentailingthefollowinginformationaboutthe278
system:279
• oneorseveralscenarios(3.22);280
• thefunctionalrange;281
• thedesiredbehaviour;and282
• thesystemboundaries.283
Note1toentry:Theusecasedescriptiontypicallydoesnotincludeadetailedlistofallrelevantscenarios(3.22)for284
thisusecase.Insteadamoreabstractdescriptionofthesescenarios(3.22)isused.285
3.28286
validation287
setofactivitiesgainingconfidencethatanitemisableto accomplishitsexpectedfunctionalitiesand288
missions289
Note1toentry: Verification activities address mainly Area 2 of Figure 7, Figure 8, and Figure 9 including the290
verification ofknown use cases,whereas validation activities address mainly Area 3 of Figure 7,Figure 8, and291
Figure 9 includingthevalidationofSOTIF(3.21)inunknownusecases(3.27).292
293
4 Overviewandorganizationofactivitiesinthedevelopmentprocess294
4.1 Overviewofactivitiesinthedevelopmentprocess295
Theobjectiveclausesofthisdocument (Clauses5.1,6.1,7.1,8.1,9.1,10.1,11.1,and12.1)arenormative.296
Allothercontentisinformative.Compliancetothisdocumentcanbeclaimedbylistingtheobjectivesand297
providinganargumentthattheobjectiveshavebeenachieved anddocumentedintheircorresponding298
workproducts.299
Adevelopmentinterfaceagreementcanbedefinedbetweenalldevelopmentpartieswhenapplicablefor300
adistributedproductdevelopment.Thegoalofanagreementistoconfirminthe earlystagesofaproject301
all responsibilities of the SOTIF activities. Please see Sub-clause 4.1 below for further detail on302
distributedSOTIFdevelopmentactivities.303
AchievingSOTIFrequiressomeactivitieswhicharecomplementarytotheISO26262:2018 series.Oneof304
themainobjectivesofthisdocument istodescribe theprocessandrationaleusedtoensurethatthe305
likelihoodofahazardouseventissufficientlylow.Furthermore,thisdocument alsoseekstoassessthat306
theremainingresidualriskfrom307
i. asystemnotabletoprocessagivenscenarioinasafemannerand308
ii. the involved persons (driver, other vehicle occupants, or bystanders) are not capable of309
mitigatingthehazardousevent,isacceptable(seeFigure 6).310
The function, system specification and design includes relevant use cases and those use cases are311
comprisedofseveralrelevantscenarios.Thesescenarioscouldcontaintriggeringconditions(seeClause312
3definitions)thatleadtoharm(seeFigure 6).313