Dieser Extraktions-Bericht beschreibt die Aenderungen an der Pipeline seit der letzten Berichtsaenderung. Oben stehen die wichtigsten offenen Kurationsanfragen; darunter folgen die bereits umgesetzten Fixes, standardmaessig eingeklappt, jeweils mit Screenshot und aktuellem Extraktionsergebnis.
Berichtsversion v12 (vorherige: v11)
Script-Stand: 3b6d6f32 (2026-08-11T13:27:09+02:00), fdba7e28 (2026-08-12T03:51:33+02:00). Keine Aenderung an den maßgeblichen Extraktionsskripten seit der vorherigen Berichtsversion.
Kennzahlen
Kurationsanfragen — bitte zuerst entscheiden
Jeder Fall zeigt den heutigen Extraktionsstand, eine kompakte Screenshot-Vorschau der Quelle und in einfacher Sprache, welche Entscheidung benoetigt wird. Deine Antwort landet im vorhandenen Review-Framework und kann spaeter aus dem GitHub-Issue in einen umsetzbaren Aenderungsvorschlag fuer die Pipeline ueberfuehrt werden.
RS_SAF_21101 — AUTOSAR_AP_RS_PlatformHealthManagement
Originaldokument: AUTOSAR_AP_RS_PlatformHealthManagement
So verarbeitet das Werkzeug die Daten heute: Kein Record wird angelegt; die Extraktion verwirft die ID, weil auf dieser und der Folgeseite keine zugehoerige Definition (Ueberschrift + Beschreibung) gefunden wird.
Warum es hier nicht automatisch entscheiden kann: Die ID taucht hier nur als Verweis in eckigen Klammern auf, z. B. „[RS_SAF_21101]“ — wie eine Fussnote, die auf ein Requirement an anderer Stelle zeigt. Es gibt an dieser Stelle keinen eigenen Beschreibungstext.
Welche Entscheidung wir von der Kuratorin / dem Kurator brauchen: Ist es richtig, diese reine Zitierstelle zu ignorieren, oder soll trotzdem ein leerer Platzhalter-Record angelegt werden, damit die ID nicht ganz fehlt?
Was mit deiner Antwort passiert: Deine Antwort wird im bestehenden Review-Framework gespeichert und als GitHub-Issue-Paket abgegeben. Daraus kann spaeter eine konkrete Aenderung fuer die Extraktions-Pipeline abgeleitet werden.
Wichtig: Wenn fuer die Umsetzung Textverstehen oder Regelableitung noetig ist, darf ein KI-Agent einen Aenderungsvorschlag aus den zugehoerigen Dokumenten erstellen — aber die Person, die die Extraktionsskripte ausfuehrt, hat immer das letzte Wort und uebernimmt die Aenderung nur nach eigener Pruefung.
Validate requirementIst es richtig, diese reine Zitierstelle zu ignorieren, oder soll trotzdem ein leerer Platzhalter-Record angelegt werden, damit die ID nicht ganz fehlt?
RS_LT_00001 — AUTOSAR_FO_RS_LogAndTrace
Originaldokument: AUTOSAR_FO_RS_LogAndTrace
So verarbeitet das Werkzeug die Daten heute: Die Extraktion legt den Record ohne eigene Ueberschrift an (Feld „heading“ bleibt leer); Beschreibungstext und Metadaten werden trotzdem uebernommen.
Warum es hier nicht automatisch entscheiden kann: Bei diesem und rund einem Dutzend weiterer Requirements in diesem Dokument fehlt im Original-PDF die sonst uebliche Titelzeile zwischen der eckigen ID und dem Beschreibungstext — das Layout dieser Tabelle hat schlicht keine eigene Spalte dafuer vorgesehen.
Welche Entscheidung wir von der Kuratorin / dem Kurator brauchen: Soll fuer diese Faelle dauerhaft eine leere Ueberschrift akzeptiert werden, oder soll das Werkzeug ersatzweise die erste Textzeile als Ueberschrift uebernehmen?
Was mit deiner Antwort passiert: Deine Antwort wird im bestehenden Review-Framework gespeichert und als GitHub-Issue-Paket abgegeben. Daraus kann spaeter eine konkrete Aenderung fuer die Extraktions-Pipeline abgeleitet werden.
Wichtig: Wenn fuer die Umsetzung Textverstehen oder Regelableitung noetig ist, darf ein KI-Agent einen Aenderungsvorschlag aus den zugehoerigen Dokumenten erstellen — aber die Person, die die Extraktionsskripte ausfuehrt, hat immer das letzte Wort und uebernimmt die Aenderung nur nach eigener Pruefung.
Validate requirementSoll fuer diese Faelle dauerhaft eine leere Ueberschrift akzeptiert werden, oder soll das Werkzeug ersatzweise die erste Textzeile als Ueberschrift uebernehmen?
Alle offenen Kurationsfragen als Liste2 Eintraege
| Record-ID | Dokument | Seite | Entscheidungsfrage |
|---|---|---|---|
RS_SAF_21101 | AUTOSAR_AP_RS_PlatformHealthManagement | 9 | Ist es richtig, diese reine Zitierstelle zu ignorieren, oder soll trotzdem ein leerer Platzhalter-Record angelegt werden, damit die ID nicht ganz fehlt? |
RS_LT_00001 | AUTOSAR_FO_RS_LogAndTrace | 41 | Soll fuer diese Faelle dauerhaft eine leere Ueberschrift akzeptiert werden, oder soll das Werkzeug ersatzweise die erste Textzeile als Ueberschrift uebernehmen? |
Aufgeloeste Kurationsanfragen (seit fruehreren Versionen)1 Eintraege
Aufgeloest RS_DIAG_04005 — AUTOSAR_FO_RS_Diagnostics
Originaldokument: AUTOSAR_FO_RS_Diagnostics
Was zuvor beobachtet wurde: Die Extraktion verwechselte zwei benachbarte Requirements auf derselben Seite: Beim Record RS_DIAG_04005 landete der Rest des vorherigen Items, weil die Inline-Referenz „Dependencies: [RS_Diag_04005] ...“ aus RS_Diag_04006 als Start des Records erkannt wurde.
Status: Aufgeloest seit Commit cfcf23a3 (2026-08-11) — keine Kurator-Entscheidung mehr noetig.
Parser-Fix in spec_scrape.py::_record_slice: bevorzugt echten Definitionsanker „[ID] ... ⌈“ statt Inline-Zitat. RS_DIAG_04005 und RS_Diag_04006 werden seither korrekt als zwei getrennte Requirements extrahiert (Security Access Handling bzw. Session Handling).
Fixes seit der letzten Aenderung — vollstaendige Extraktionsergebnisse
Mehrseitige „Document Change History“-Fortsetzungbae18b1c — 37 IDs auf 5 Seiten
Problem: Mehrseitige Changelog-Tabellen (datiertes „AUTOSAR / Release / Management“-Format) wurden auf Folgeseiten nicht mehr als Historie erkannt, weil dort keine neue Ueberschrift auftrat. IDs, die dort nur als Aenderungshistorie referenziert werden, wurden als lokale Definitionen fehlinterpretiert.
Fix: Zustandsbehafteter Fortsetzungs-Check: Endet eine Seite in einer Historie-Region, gilt die naechste Seite als Fortsetzung, solange sie mit dem bekannten Changelog-Muster beginnt.
AUTOSAR_AP_RS_Cryptography — Seite 2 (18 betroffene IDs)
RS_CRYPTO_02406Seite 2
AUTOSAR Release Management • Removed: [RS_CRYPTO_02406] • Updated: [RS_CRYPTO_02201] 2019-11-28 19-11 AUTOSAR Release Management • Removed: [RS_CRYPTO_02114] [RS_CRYPTO_ 02311] [RS_CRYPTO_02404] • Updated: [RS_CRYPTO_02009] [RS_CRYPTO_02110] 2019-03-29 19-03 AUTOSAR Release Management • Editorial changes and rephrasing • Improved requirements description and rationale (Updated : [RS_CRY
RS_CRYPTO_02201Seite 2
Removed: [RS_CRYPTO_02406] • Updated: [RS_CRYPTO_02201] 2019-11-28 19-11 AUTOSAR Release Management • Removed: [RS_CRYPTO_02114] [RS_CRYPTO_ 02311] [RS_CRYPTO_02404] • Updated: [RS_CRYPTO_02009] [RS_CRYPTO_02110] 2019-03-29 19-03 AUTOSAR Release Management • Editorial changes and rephrasing • Improved requirements description and rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002]
RS_CRYPTO_02114Seite 2
AUTOSAR Release Management • Removed: [RS_CRYPTO_02114] [RS_CRYPTO_ 02311] [RS_CRYPTO_02404] • Updated: [RS_CRYPTO_02009] [RS_CRYPTO_02110] 2019-03-29 19-03 AUTOSAR Release Management • Editorial changes and rephrasing • Improved requirements description and rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [
RS_CRYPTO_02404Seite 2
: [RS_CRYPTO_02114] [RS_CRYPTO_ 02311] [RS_CRYPTO_02404] • Updated: [RS_CRYPTO_02009] [RS_CRYPTO_02110] 2019-03-29 19-03 AUTOSAR Release Management • Editorial changes and rephrasing • Improved requirements description and rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [R
RS_CRYPTO_02009Seite 2
O_ 02311] [RS_CRYPTO_02404] • Updated: [RS_CRYPTO_02009] [RS_CRYPTO_02110] 2019-03-29 19-03 AUTOSAR Release Management • Editorial changes and rephrasing • Improved requirements description and rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_0
RS_CRYPTO_02110Seite 2
TO_02404] • Updated: [RS_CRYPTO_02009] [RS_CRYPTO_02110] 2019-03-29 19-03 AUTOSAR Release Management • Editorial changes and rephrasing • Improved requirements description and rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_0
RS_CRYPTO_02001Seite 2
s description and rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR
RS_CRYPTO_02002Seite 2
rationale (Updated : [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management
RS_CRYPTO_02003Seite 2
: [RS_CRYPTO_02001] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requir
RS_CRYPTO_02004Seite 2
1] [RS_CRYPTO_02002] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are correct
RS_CRYPTO_02005Seite 2
2] [RS_CRYPTO_02003] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional re
RS_CRYPTO_02007Seite 2
3] [RS_CRYPTO_02004] [RS_CRYPTO_02005] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are add
RS_CRYPTO_02109Seite 2
5] [RS_CRYPTO_02007] [RS_CRYPTO_02009] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are added 2017-10-27 17-10 AUTOSAR Release
RS_CRYPTO_02202Seite 2
] [RS_CRYPTO_02109] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are added 2017-10-27 17-10 AUTOSAR Release Management • Initial release
RS_CRYPTO_02206Seite 2
] [RS_CRYPTO_ 02116] [RS_CRYPTO_02202] [RS_CRYPTO_02206]) 2018-10-31 18-10 AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are added 2017-10-27 17-10 AUTOSAR Release Management • Initial release
RS_CRYPTO_02303Seite 2
AUTOSAR Release Management • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are added 2017-10-27 17-10 AUTOSAR Release Management • Initial release
RS_CRYPTO_02402Seite 2
ment • Removed : [RS_CRYPTO_02303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are added 2017-10-27 17-10 AUTOSAR Release Management • Initial release
RS_CRYPTO_02006Seite 2
303] and [RS_CRYPTO_02402] • Updated : [RS_CRYPTO_02006] 2018-03-29 18-03 AUTOSAR Release Management • Existing requirements are corrected • Additional requirements are added 2017-10-27 17-10 AUTOSAR Release Management • Initial release
AUTOSAR_AP_RS_ExecutionManagement — Seite 2 (1 betroffene ID)
RS_EM_00014Seite 2
RS_EM_00110 and RS_EM_00111. • Added: [RS_EM_00014]. 2018-03-29 18-03 AUTOSAR Release Management • Removed: RS_EM_00006, RS_EM_00007 and RS_EM_00012 • Minor changes and document clean up 2017-10-27 17-10 AUTOSAR Release Management • Minor changes, document clean up 2017-03-31 17-03 AUTOSAR Release Management • Initial release
AUTOSAR_AP_RS_General — Seite 2 (10 betroffene IDs)
RS_AP_00111Seite 2
lowing requirements have been revised: [RS_AP_00111], [RS_AP_ 00113], [RS_AP_00114], [RS_AP_ 00115], [RS_AP_00122], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] • Following requirements have been deleted: [RS_AP_00117], [RS_AP_ 00118] • Following requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_
RS_AP_00114Seite 2
evised: [RS_AP_00111], [RS_AP_ 00113], [RS_AP_00114], [RS_AP_ 00115], [RS_AP_00122], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] • Following requirements have been deleted: [RS_AP_00117], [RS_AP_ 00118] • Following requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00122Seite 2
00113], [RS_AP_00114], [RS_AP_ 00115], [RS_AP_00122], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] • Following requirements have been deleted: [RS_AP_00117], [RS_AP_ 00118] • Following requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00121Seite 2
00115], [RS_AP_00122], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] • Following requirements have been deleted: [RS_AP_00117], [RS_AP_ 00118] • Following requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00125Seite 2
00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] • Following requirements have been deleted: [RS_AP_00117], [RS_AP_ 00118] • Following requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00117Seite 2
lowing requirements have been deleted: [RS_AP_00117], [RS_AP_ 00118] • Following requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00127Seite 2
ollowing requirements have been added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00129Seite 2
added: [RS_AP_00127], [RS_AP_ 00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00131Seite 2
00128], [RS_AP_00129], [RS_AP_ 00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
RS_AP_00134Seite 2
00130], [RS_AP_00131], [RS_AP_ 00132], [RS_AP_00134]
AUTOSAR_AP_RS_General — Seite 3 (3 betroffene IDs)
RS_AP_00115Seite 3
now to ISO/IEC 14882 • Description of [RS_AP_00115] revised • Description of [RS_AP_00116], [RS_ AP_00117], [RS_AP_00118], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] revised (in general "all ara libraries" changed to "all functional clusters"). 2017-10-27 17-10 AUTOSAR Release Management • Minor fixes 2017-03-31 17-03 AUTOSAR Release Management • Initial release
RS_AP_00116Seite 3
[RS_AP_00115] revised • Description of [RS_AP_00116], [RS_ AP_00117], [RS_AP_00118], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] revised (in general "all ara libraries" changed to "all functional clusters"). 2017-10-27 17-10 AUTOSAR Release Management • Minor fixes 2017-03-31 17-03 AUTOSAR Release Management • Initial release
RS_AP_00118Seite 3
tion of [RS_AP_00116], [RS_ AP_00117], [RS_AP_00118], [RS_AP_ 00120], [RS_AP_00121], [RS_AP_ 00124], [RS_AP_00125] revised (in general "all ara libraries" changed to "all functional clusters"). 2017-10-27 17-10 AUTOSAR Release Management • Minor fixes 2017-03-31 17-03 AUTOSAR Release Management • Initial release
AUTOSAR_AP_RS_OperatingSystemInterface — Seite 2 (5 betroffene IDs)
RS_OSI_00201Seite 2
lease Management • Added: use case for [RS_OSI_00201] and [RS_OSI_00202] 2018-10-31 18-10 AUTOSAR Release Management • Removed: RS_OSI_00102 and RS_OSI_00105 • Added: [RS_OSI_00207], [RS_OSI_00208]. 2018-03-29 18-03 AUTOSAR Release Management • Removed: RS_OSI_00101, RS_OSI_00200 and RS_OSI_00205. • Added: [RS_OSI_00103]. 2017-10-27 17-10 AUTOSAR Release Management • Minor changes, docum
RS_OSI_00202Seite 2
Added: use case for [RS_OSI_00201] and [RS_OSI_00202] 2018-10-31 18-10 AUTOSAR Release Management • Removed: RS_OSI_00102 and RS_OSI_00105 • Added: [RS_OSI_00207], [RS_OSI_00208]. 2018-03-29 18-03 AUTOSAR Release Management • Removed: RS_OSI_00101, RS_OSI_00200 and RS_OSI_00205. • Added: [RS_OSI_00103]. 2017-10-27 17-10 AUTOSAR Release Management • Minor changes, document clean up 2017-0
RS_OSI_00207Seite 2
RS_OSI_00102 and RS_OSI_00105 • Added: [RS_OSI_00207], [RS_OSI_00208]. 2018-03-29 18-03 AUTOSAR Release Management • Removed: RS_OSI_00101, RS_OSI_00200 and RS_OSI_00205. • Added: [RS_OSI_00103]. 2017-10-27 17-10 AUTOSAR Release Management • Minor changes, document clean up 2017-03-31 17-03 AUTOSAR Release Management • Initial release
RS_OSI_00208Seite 2
RS_OSI_00105 • Added: [RS_OSI_00207], [RS_OSI_00208]. 2018-03-29 18-03 AUTOSAR Release Management • Removed: RS_OSI_00101, RS_OSI_00200 and RS_OSI_00205. • Added: [RS_OSI_00103]. 2017-10-27 17-10 AUTOSAR Release Management • Minor changes, document clean up 2017-03-31 17-03 AUTOSAR Release Management • Initial release
RS_OSI_00103Seite 2
S_OSI_00200 and RS_OSI_00205. • Added: [RS_OSI_00103]. 2017-10-27 17-10 AUTOSAR Release Management • Minor changes, document clean up 2017-03-31 17-03 AUTOSAR Release Management • Initial release
„Requirements Tracing“-Tabellenc2334c43 / ffa42b17 — 81 IDs auf 4 Seiten
Problem: Seiten, die mit „N Requirements Tracing“ beginnen, listen Upstream- oder fremde Requirement-IDs auf, keine lokalen Definitionen. Diese IDs wurden trotzdem als Definitionskandidaten fuer das aktuelle Dokument gezaehlt.
Fix: Neue „traceability“-Region ab der Ueberschrift bis zum Seitenende; IDs darin zaehlen nicht mehr als lokale Definition. Backend-symmetrisch (toleriert fuehrende Leerzeilen des builtin-Backends).
AUTOSAR_AP_RS_General — Seite 33 (57 betroffene IDs)
RS_AP_00170Seite 33
neralFunctional_ WithInstanceSpecifier [RS_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177] TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [R
RS_AP_00171Seite 33
l_ WithInstanceSpecifier [RS_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177] TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [R
RS_AP_00172Seite 33
eSpecifier [RS_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177] TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [R
RS_AP_00173Seite 33
_AP_00170] [RS_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177] TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [R
RS_AP_00177Seite 33
_AP_00171] [RS_AP_00172] [RS_AP_00173] [RS_AP_00177] TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [R
RS_AP_00111Seite 33
S_AP_00177] TG_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [
RS_AP_00114Seite 33
_AP_GeneralNonFunctional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [
RS_AP_00115Seite 33
Functional [RS_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [
RS_AP_00116Seite 33
_AP_00111] [RS_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [
RS_AP_00119Seite 33
_AP_00114] [RS_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [
RS_AP_00120Seite 33
_AP_00115] [RS_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [
RS_AP_00121Seite 33
_AP_00116] [RS_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [
RS_AP_00122Seite 33
_AP_00119] [RS_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [
RS_AP_00124Seite 33
_AP_00120] [RS_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [
RS_AP_00125Seite 33
_AP_00121] [RS_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [
RS_AP_00127Seite 33
_AP_00122] [RS_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [
RS_AP_00128Seite 33
_AP_00124] [RS_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [
RS_AP_00129Seite 33
_AP_00125] [RS_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [
RS_AP_00130Seite 33
_AP_00127] [RS_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [
RS_AP_00134Seite 33
_AP_00128] [RS_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [
RS_AP_00135Seite 33
_AP_00129] [RS_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [
RS_AP_00136Seite 33
_AP_00130] [RS_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [
RS_AP_00137Seite 33
_AP_00134] [RS_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [
RS_AP_00138Seite 33
_AP_00135] [RS_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [
RS_AP_00139Seite 33
_AP_00136] [RS_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [
RS_AP_00140Seite 33
_AP_00137] [RS_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [
RS_AP_00141Seite 33
_AP_00138] [RS_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [
RS_AP_00142Seite 33
_AP_00139] [RS_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [
RS_AP_00143Seite 33
_AP_00140] [RS_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [
RS_AP_00144Seite 33
_AP_00141] [RS_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [
RS_AP_00145Seite 33
_AP_00142] [RS_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [
RS_AP_00146Seite 33
_AP_00143] [RS_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [
RS_AP_00147Seite 33
_AP_00144] [RS_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] T
RS_AP_00148Seite 33
_AP_00145] [RS_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trac
RS_AP_00149Seite 33
_AP_00146] [RS_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of th
RS_AP_00150Seite 33
_AP_00147] [RS_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00151Seite 33
_AP_00148] [RS_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00153Seite 33
_AP_00149] [RS_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00154Seite 33
_AP_00150] [RS_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00155Seite 33
_AP_00151] [RS_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00156Seite 33
_AP_00153] [RS_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00157Seite 33
_AP_00154] [RS_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00158Seite 33
_AP_00155] [RS_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00159Seite 33
_AP_00156] [RS_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00160Seite 33
_AP_00157] [RS_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00161Seite 33
_AP_00158] [RS_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00162Seite 33
_AP_00159] [RS_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00163Seite 33
_AP_00160] [RS_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00164Seite 33
_AP_00161] [RS_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00165Seite 33
_AP_00162] [RS_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00166Seite 33
_AP_00163] [RS_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00167Seite 33
_AP_00164] [RS_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00169Seite 33
_AP_00165] [RS_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00174Seite 33
_AP_00166] [RS_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00175Seite 33
_AP_00167] [RS_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00176Seite 33
_AP_00169] [RS_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
RS_AP_00178Seite 33
_AP_00174] [RS_AP_00175] [RS_AP_00176] [RS_AP_00178] Table 5.1: Trace Groups of this document
AUTOSAR_AP_RS_Persistency — Seite 17 (4 betroffene IDs)
RS_SAF_10037Seite 17
. Requirement Description Satisfied by [RS_SAF_10037] AUTOSAR shall provide mechanisms to prevent unintended alteration of data. [RS_PER_00008] [RS_SAF_10040] AUTOSAR shall support data recovery mechanisms. [RS_PER_00009] Table 5.1: Requirements Tracing
RS_PER_00008Seite 17
prevent unintended alteration of data. [RS_PER_00008] [RS_SAF_10040] AUTOSAR shall support data recovery mechanisms. [RS_PER_00009] Table 5.1: Requirements Tracing
RS_SAF_10040Seite 17
ded alteration of data. [RS_PER_00008] [RS_SAF_10040] AUTOSAR shall support data recovery mechanisms. [RS_PER_00009] Table 5.1: Requirements Tracing
RS_PER_00009Seite 17
hall support data recovery mechanisms. [RS_PER_00009] Table 5.1: Requirements Tracing
AUTOSAR_AP_RS_PlatformHealthManagement — Seite 17 (10 betroffene IDs)
RS_HM_09249Seite 17
. Requirement Description Satisfied by [RS_HM_09249] Health Monitoring shall support building safety-related systems. [RS_PHM_00114] [RS_SAF_10005] AUTOSAR shall provide mechanisms to support safe shutdown and termination of application software and embedded middleware. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition
RS_PHM_00114Seite 17
pport building safety-related systems. [RS_PHM_00114] [RS_SAF_10005] AUTOSAR shall provide mechanisms to support safe shutdown and termination of application software and embedded middleware. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition of states in embedded middleware or service life cycle. [RS_PHM_00115] [RS_PHM
RS_SAF_10005Seite 17
safety-related systems. [RS_PHM_00114] [RS_SAF_10005] AUTOSAR shall provide mechanisms to support safe shutdown and termination of application software and embedded middleware. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition of states in embedded middleware or service life cycle. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM
RS_PHM_00115Seite 17
tion software and embedded middleware. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition of states in embedded middleware or service life cycle. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10030] AUTOSAR shall provide mechanisms to support safe program execution. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00118] [R
RS_PHM_00116Seite 17
nd embedded middleware. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition of states in embedded middleware or service life cycle. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10030] AUTOSAR shall provide mechanisms to support safe program execution. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00118] [RS_PHM_00119] Ta
RS_PHM_00117Seite 17
dleware. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition of states in embedded middleware or service life cycle. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10030] AUTOSAR shall provide mechanisms to support safe program execution. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00118] [RS_PHM_00119] Table 5.1: Requir
RS_SAF_10006Seite 17
M_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10006] AUTOSAR shall provide mechanisms to support safe transition of states in embedded middleware or service life cycle. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10030] AUTOSAR shall provide mechanisms to support safe program execution. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00118] [RS_PHM_00119] Table 5.1: Requirements Tracing
RS_SAF_10030Seite 17
M_00115] [RS_PHM_00116] [RS_PHM_00117] [RS_SAF_10030] AUTOSAR shall provide mechanisms to support safe program execution. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00118] [RS_PHM_00119] Table 5.1: Requirements Tracing 5.1 Not applicable requirements [RS_PHM_NA] Status: DRAFT ⌈These requirements are not applicable as they are not within the scope of this re- lease.⌋
RS_PHM_00118Seite 17
ecution. [RS_PHM_00115] [RS_PHM_00116] [RS_PHM_00118] [RS_PHM_00119] Table 5.1: Requirements Tracing 5.1 Not applicable requirements [RS_PHM_NA] Status: DRAFT ⌈These requirements are not applicable as they are not within the scope of this re- lease.⌋
RS_PHM_00119Seite 17
M_00115] [RS_PHM_00116] [RS_PHM_00118] [RS_PHM_00119] Table 5.1: Requirements Tracing 5.1 Not applicable requirements [RS_PHM_NA] Status: DRAFT ⌈These requirements are not applicable as they are not within the scope of this re- lease.⌋
AUTOSAR_FO_RS_E2E — Seite 14 (10 betroffene IDs)
RS_SAF_31301Seite 14
. Requirement Description Satisfied by [RS_SAF_31301] E2E Protection with E2E T ransformer and E2E Library [RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08538Seite 14
with E2E T ransformer and E2E Library [RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08544Seite 14
sformer and E2E Library [RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08545Seite 14
Library [RS_E2E_08538] [RS_E2E_08544] [RS_E2E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08546Seite 14
E_08538] [RS_E2E_08544] [RS_E2E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08547Seite 14
E_08544] [RS_E2E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_SAF_31302Seite 14
E_08545] [RS_E2E_08546] [RS_E2E_08547] [RS_SAF_31302] Allow integrators to configure safety mechanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08528Seite 14
hanisms to detect communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08539Seite 14
ct communication faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
RS_E2E_08543Seite 14
n faults [RS_E2E_08528] [RS_E2E_08539] [RS_E2E_08543] Table 5.1: Requirements Tracing
Anhangs-Tabellen „Number Heading“e554a1a8 — 183 IDs auf 20 Seiten
Problem: Mehrseitige Anhangs-Tabellen „Added/Changed/Deleted Requirements“ beginnen mit „Number Heading“ und tragen ihre Beschriftung erst am Ende der Tabelle. Ohne erneute Ueberschrift auf Folgeseiten wurden solche Zeilen als normaler Fliesstext behandelt und ihre IDs als lokale Definitionen gezaehlt.
Fix: Zweites Fortsetzungsmuster: Eine Seite gilt als Historie-Fortsetzung, wenn sie mit „Number Heading“ beginnt UND eine „Added/Changed/Deleted Requirements|Constraints“-Beschriftung traegt. Die Kombination verhindert Fehltreffer bei regulaeren SWS-Schnittstellentabellen im gleichen Layout ohne diese Beschriftung.
AUTOSAR_AP_RS_CommunicationManagement — Seite 36 (3 betroffene IDs)
RS_CM_00413Seite 36
nication Management Number Heading [RS_CM_00413] Support of IEEE1722 Stream handling Table A.2: Added Requirements in R24-11 A.2.2 Changed Requirements in R24-11 none A.2.3 Deleted Requirements in R24-11 Number Heading [RS_CM_00600] Creation of CommunicationGroups [RS_CM_00601] Provide origin of information Table A.3: Deleted Requirements in R24-11 A.3 Traceable item history of this
RS_CM_00600Seite 36
Requirements in R24-11 Number Heading [RS_CM_00600] Creation of CommunicationGroups [RS_CM_00601] Provide origin of information Table A.3: Deleted Requirements in R24-11 A.3 Traceable item history of this document according to AUTOSAR Release R23-11 A.3.1 Added Requirements in R23-11 none A.3.2 Changed Requirements in R23-11 Number Heading [RS_CM_00600] Creation of CommunicationGroups [
RS_CM_00601Seite 36
00600] Creation of CommunicationGroups [RS_CM_00601] Provide origin of information Table A.3: Deleted Requirements in R24-11 A.3 Traceable item history of this document according to AUTOSAR Release R23-11 A.3.1 Added Requirements in R23-11 none A.3.2 Changed Requirements in R23-11 Number Heading [RS_CM_00600] Creation of CommunicationGroups [RS_CM_00601] Provide origin of information Tab
AUTOSAR_AP_RS_ExecutionManagement — Seite 21 (10 betroffene IDs)
RS_EM_00152Seite 21
xecution Management Number Heading [RS_EM_00152] Execution Management shall support standardized trace points throughout the state transitions. Table A.1: Changed Requirements in R25-11 A.1.3 Deleted Requirements in R25-11 none A.2 Traceable item history of this document according to AU- TOSAR Release R24-11 A.2.1 Added Requirements in R24-11 none A.2.2 Changed Requirements in R24-11
RS_EM_00002Seite 21
Requirements in R24-11 Number Heading [RS_EM_00002] Execution Management shall set-up one process for the execution of each Modelled Process. [RS_EM_00005] Execution Management shall support the configuration of OS resource budgets for process and groups of processes. [RS_EM_00008] Execution Management shall support the binding of all threads of a given process to a specified set of pro
RS_EM_00005Seite 21
he execution of each Modelled Process. [RS_EM_00005] Execution Management shall support the configuration of OS resource budgets for process and groups of processes. [RS_EM_00008] Execution Management shall support the binding of all threads of a given process to a specified set of processor cores. [RS_EM_00009] Execution Management shall control the right to create child process for eac
RS_EM_00008Seite 21
s for process and groups of processes. [RS_EM_00008] Execution Management shall support the binding of all threads of a given process to a specified set of processor cores. [RS_EM_00009] Execution Management shall control the right to create child process for each process it starts. [RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of processes. [RS_EM_001
RS_EM_00009Seite 21
to a specified set of processor cores. [RS_EM_00009] Execution Management shall control the right to create child process for each process it starts. [RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of processes. [RS_EM_00101] Execution Management shall support State Management functionality . [RS_EM_00103] Execution Management shall support process lifec
RS_EM_00011Seite 21
ld process for each process it starts. [RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of processes. [RS_EM_00101] Execution Management shall support State Management functionality . [RS_EM_00103] Execution Management shall support process lifecycle management. [RS_EM_00150] Error Handling. [RS_EM_00151] Execution Management shall be implemented at least
RS_EM_00101Seite 21
tiated graceful shutdown of processes. [RS_EM_00101] Execution Management shall support State Management functionality . [RS_EM_00103] Execution Management shall support process lifecycle management. [RS_EM_00150] Error Handling. [RS_EM_00151] Execution Management shall be implemented at least according the highest safety integrity level from any process that is supported on the platform
RS_EM_00103Seite 21
pport State Management functionality . [RS_EM_00103] Execution Management shall support process lifecycle management. [RS_EM_00150] Error Handling. [RS_EM_00151] Execution Management shall be implemented at least according the highest safety integrity level from any process that is supported on the platform. [RS_EM_00152] Execution Management shall support standardized trace points throu
RS_EM_00150Seite 21
support process lifecycle management. [RS_EM_00150] Error Handling. [RS_EM_00151] Execution Management shall be implemented at least according the highest safety integrity level from any process that is supported on the platform. [RS_EM_00152] Execution Management shall support standardized trace points throughout the state transitions. Table A.2: Changed Requirements in R24-11
RS_EM_00151Seite 21
agement. [RS_EM_00150] Error Handling. [RS_EM_00151] Execution Management shall be implemented at least according the highest safety integrity level from any process that is supported on the platform. [RS_EM_00152] Execution Management shall support standardized trace points throughout the state transitions. Table A.2: Changed Requirements in R24-11
AUTOSAR_AP_RS_ExecutionManagement — Seite 22 (5 betroffene IDs)
RS_EM_00050Seite 22
Requirements in R24-11 Number Heading [RS_EM_00050] Execution Management shall perform Machine-wide coordination of process. [RS_EM_00051] Execution Management shall provide APIs to the process for configuring external trigger conditions for its activities. [RS_EM_00052] Execution Management shall provide APIs to the process for configuring cyclic triggering of its activities. [RS_EM_00
RS_EM_00051Seite 22
Machine-wide coordination of process. [RS_EM_00051] Execution Management shall provide APIs to the process for configuring external trigger conditions for its activities. [RS_EM_00052] Execution Management shall provide APIs to the process for configuring cyclic triggering of its activities. [RS_EM_00053] Execution Management shall provide APIs to the process to support deterministic re
RS_EM_00052Seite 22
trigger conditions for its activities. [RS_EM_00052] Execution Management shall provide APIs to the process for configuring cyclic triggering of its activities. [RS_EM_00053] Execution Management shall provide APIs to the process to support deterministic redundant execution of process. [RS_EM_00113] Execution Management shall support time-triggered execution. Table A.3: Deleted Requireme
RS_EM_00053Seite 22
g cyclic triggering of its activities. [RS_EM_00053] Execution Management shall provide APIs to the process to support deterministic redundant execution of process. [RS_EM_00113] Execution Management shall support time-triggered execution. Table A.3: Deleted Requirements in R24-11 A.3 Traceable item history of this document according to AU- TOSAR Release R23-11 A.3.1 Added Requirements i
RS_EM_00113Seite 22
nistic redundant execution of process. [RS_EM_00113] Execution Management shall support time-triggered execution. Table A.3: Deleted Requirements in R24-11 A.3 Traceable item history of this document according to AU- TOSAR Release R23-11 A.3.1 Added Requirements in R23-11 Number Heading [RS_EM_00152] Execution Management shall support standardized trace points throughout the state transi
AUTOSAR_AP_RS_ExecutionManagement — Seite 29 (6 betroffene IDs)
RS_EM_00006Seite 29
xecution Management Number Heading [RS_EM_00006] The Execution Management shall support the analysis of available and required OS resource budgets for Executables and groups of Executables during installation and run-time [RS_EM_00007] The Execution Management shall support of the allocation of dedicated resources for the Executable (e.g GPU) [RS_EM_00008] The Execution Management sh
RS_EM_00007Seite 29
ables during installation and run-time [RS_EM_00007] The Execution Management shall support of the allocation of dedicated resources for the Executable (e.g GPU) [RS_EM_00008] The Execution Management shall support the binding of Executable threads to a specified set of processor cores. [RS_EM_00009] Only Execution Management shall start Executables [RS_EM_00010] The Execution Management
RS_EM_00010Seite 29
ion Management shall start Executables [RS_EM_00010] The Execution Management shall support multiple instantiation of Executables [RS_EM_00011] Execution Management shall support self-initiated graceful shutdown of Executable instances [RS_EM_00012] Application Manifest shall support unambiguous identification of Executable instances [RS_EM_00013] Execution Management shall support confi
RS_EM_00012Seite 29
ceful shutdown of Executable instances [RS_EM_00012] Application Manifest shall support unambiguous identification of Executable instances [RS_EM_00013] Execution Management shall support configurable recovery actions [RS_EM_00100] The Execution Management shall support the ordered startup and shutdown of Executables [RS_EM_00050] The Execution Management shall do a system-wide coordinat
RS_EM_00013Seite 29
identification of Executable instances [RS_EM_00013] Execution Management shall support configurable recovery actions [RS_EM_00100] The Execution Management shall support the ordered startup and shutdown of Executables [RS_EM_00050] The Execution Management shall do a system-wide coordination of activities. [RS_EM_00051] The Execution Management shall provide functions to the Executable
RS_EM_00100Seite 29
support configurable recovery actions [RS_EM_00100] The Execution Management shall support the ordered startup and shutdown of Executables [RS_EM_00050] The Execution Management shall do a system-wide coordination of activities. [RS_EM_00051] The Execution Management shall provide functions to the Executable for configuring external trigger conditions for its activities [RS_EM_00052] Th
AUTOSAR_AP_RS_General — Seite 37 (16 betroffene IDs)
RS_AP_00132Seite 37
o Adaptive Platform Number Heading [RS_AP_00132] noexcept behavior of API functions [RS_AP_00133] noexcept behavior of move and swap operations [RS_AP_00134] noexcept behavior of class destructors [RS_AP_00135] Avoidance of shared ownership [RS_AP_00140] Usage of "final specifier" [RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Av
RS_AP_00133Seite 37
32] noexcept behavior of API functions [RS_AP_00133] noexcept behavior of move and swap operations [RS_AP_00134] noexcept behavior of class destructors [RS_AP_00135] Avoidance of shared ownership [RS_AP_00140] Usage of "final specifier" [RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_001
RS_AP_00134Seite 37
t behavior of move and swap operations [RS_AP_00134] noexcept behavior of class destructors [RS_AP_00135] Avoidance of shared ownership [RS_AP_00140] Usage of "final specifier" [RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the A
RS_AP_00135Seite 37
noexcept behavior of class destructors [RS_AP_00135] Avoidance of shared ownership [RS_AP_00140] Usage of "final specifier" [RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the ARA framework [RS_AP_00147] Classes that are created w
RS_AP_00140Seite 37
P_00135] Avoidance of shared ownership [RS_AP_00140] Usage of "final specifier" [RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the ARA framework [RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are
RS_AP_00141Seite 37
S_AP_00140] Usage of "final specifier" [RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the ARA framework [RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not copyable, but at most movable. [RS_AP
RS_AP_00144Seite 37
[RS_AP_00141] Usage of out parameters [RS_AP_00144] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the ARA framework [RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not copyable, but at most movable. [RS_AP_00149] Error handling for non-initial
RS_AP_00145Seite 37
4] Availability of a named constructor [RS_AP_00145] Availability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the ARA framework [RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not copyable, but at most movable. [RS_AP_00149] Error handling for non-initialized Functional Cluster [RS_AP_00150] Provide only
RS_AP_00146Seite 37
ailability of special member functions [RS_AP_00146] Classes whose construction requires interaction by the ARA framework [RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not copyable, but at most movable. [RS_AP_00149] Error handling for non-initialized Functional Cluster [RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR App
RS_AP_00147Seite 37
uires interaction by the ARA framework [RS_AP_00147] Classes that are created with an InstanceSpecifier as an argument are not copyable, but at most movable. [RS_AP_00149] Error handling for non-initialized Functional Cluster [RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR Applications and Functional Clusters [RS_AP_00151] C++ Core Guidelines [RS_AP_00155] A
RS_AP_00149Seite 37
are not copyable, but at most movable. [RS_AP_00149] Error handling for non-initialized Functional Cluster [RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR Applications and Functional Clusters [RS_AP_00151] C++ Core Guidelines [RS_AP_00155] Avoidance of cluster-specific initialization functions [RS_AP_00156] Naming conventions for L&T Context ID Table A.5: Ch
RS_AP_00150Seite 37
for non-initialized Functional Cluster [RS_AP_00150] Provide only interfaces that are intended to be used by AUTOSAR Applications and Functional Clusters [RS_AP_00151] C++ Core Guidelines [RS_AP_00155] Avoidance of cluster-specific initialization functions [RS_AP_00156] Naming conventions for L&T Context ID Table A.5: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Nu
RS_AP_00151Seite 37
R Applications and Functional Clusters [RS_AP_00151] C++ Core Guidelines [RS_AP_00155] Avoidance of cluster-specific initialization functions [RS_AP_00156] Naming conventions for L&T Context ID Table A.5: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_AP_00152] Faults inside constructor. Table A.6: Deleted Requirements in R24-11 A.3 Change History
RS_AP_00155Seite 37
ters [RS_AP_00151] C++ Core Guidelines [RS_AP_00155] Avoidance of cluster-specific initialization functions [RS_AP_00156] Naming conventions for L&T Context ID Table A.5: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_AP_00152] Faults inside constructor. Table A.6: Deleted Requirements in R24-11 A.3 Change History of this document according to AUTO
RS_AP_00156Seite 37
ster-specific initialization functions [RS_AP_00156] Naming conventions for L&T Context ID Table A.5: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_AP_00152] Faults inside constructor. Table A.6: Deleted Requirements in R24-11 A.3 Change History of this document according to AUTOSAR Re- lease 23-11 A.3.1 Added Requirements in R23-11 none
RS_AP_00152Seite 37
Requirements in R24-11 Number Heading [RS_AP_00152] Faults inside constructor. Table A.6: Deleted Requirements in R24-11 A.3 Change History of this document according to AUTOSAR Re- lease 23-11 A.3.1 Added Requirements in R23-11 none
AUTOSAR_AP_RS_General — Seite 42 (1 betroffene ID)
RS_AP_00131Seite 42
o Adaptive Platform Number Heading [RS_AP_00131] Use of verbal forms to express requirement levels. Table A.16: Deleted Requirements in 19-11
AUTOSAR_AP_RS_OperatingSystemInterface — Seite 18 (12 betroffene IDs)
RS_OSI_00211Seite 18
ng System Interface Number Heading [RS_OSI_00211] The Operating System shall provide a mechanism to export low-level scheduling and trace information to applications. Table A.1: Changed Requirements in R25-11 A.1.3 Deleted Requirements in R25-11 none A.2 Traceable item history of this document according to AU- TOSAR Release R24-11 A.2.1 Added Requirements in R24-11 none A.2.2 Changed
RS_OSI_00100Seite 18
Requirements in R24-11 Number Heading [RS_OSI_00100] POSIX PSE51 Compliance [RS_OSI_00103] The Operating System Interface shall support C++. [RS_OSI_00104] The Operating System Interface shall support the reaction on Process-external stimuli from devices. [RS_OSI_00105] The Operating System Interface shall support the start of Execution Management. [RS_OSI_00201] The Operating System sh
RS_OSI_00103Seite 18
[RS_OSI_00100] POSIX PSE51 Compliance [RS_OSI_00103] The Operating System Interface shall support C++. [RS_OSI_00104] The Operating System Interface shall support the reaction on Process-external stimuli from devices. [RS_OSI_00105] The Operating System Interface shall support the start of Execution Management. [RS_OSI_00201] The Operating System shall provide mechanisms for system memo
RS_OSI_00104Seite 18
ng System Interface shall support C++. [RS_OSI_00104] The Operating System Interface shall support the reaction on Process-external stimuli from devices. [RS_OSI_00105] The Operating System Interface shall support the start of Execution Management. [RS_OSI_00201] The Operating System shall provide mechanisms for system memory budgeting. [RS_OSI_00202] The Operating System shall provide m
RS_OSI_00105Seite 18
Process-external stimuli from devices. [RS_OSI_00105] The Operating System Interface shall support the start of Execution Management. [RS_OSI_00201] The Operating System shall provide mechanisms for system memory budgeting. [RS_OSI_00202] The Operating System shall provide mechanisms for CPU time budgeting. [RS_OSI_00203] The Operating System should provide mechanisms for binding Process
RS_OSI_00201Seite 18
ort the start of Execution Management. [RS_OSI_00201] The Operating System shall provide mechanisms for system memory budgeting. [RS_OSI_00202] The Operating System shall provide mechanisms for CPU time budgeting. [RS_OSI_00203] The Operating System should provide mechanisms for binding Processes to CPU cores. [RS_OSI_00204] The Operating System shall support authorized operating system
RS_OSI_00202Seite 18
echanisms for system memory budgeting. [RS_OSI_00202] The Operating System shall provide mechanisms for CPU time budgeting. [RS_OSI_00203] The Operating System should provide mechanisms for binding Processes to CPU cores. [RS_OSI_00204] The Operating System shall support authorized operating system object access for the software entities which are allowed to do so. [RS_OSI_00206] The Ope
RS_OSI_00203Seite 18
ide mechanisms for CPU time budgeting. [RS_OSI_00203] The Operating System should provide mechanisms for binding Processes to CPU cores. [RS_OSI_00204] The Operating System shall support authorized operating system object access for the software entities which are allowed to do so. [RS_OSI_00206] The Operating System shall provide multi-Process support for isolation of applications. [RS_
RS_OSI_00204Seite 18
ms for binding Processes to CPU cores. [RS_OSI_00204] The Operating System shall support authorized operating system object access for the software entities which are allowed to do so. [RS_OSI_00206] The Operating System shall provide multi-Process support for isolation of applications. [RS_OSI_00207] The Operating System shall provide the capability to share code and data in an implicit
RS_OSI_00206Seite 18
e entities which are allowed to do so. [RS_OSI_00206] The Operating System shall provide multi-Process support for isolation of applications. [RS_OSI_00207] The Operating System shall provide the capability to share code and data in an implicit manner. [RS_OSI_00208] The Operating System shall allow Processes to access only required functionality .
RS_OSI_00207Seite 18
support for isolation of applications. [RS_OSI_00207] The Operating System shall provide the capability to share code and data in an implicit manner. [RS_OSI_00208] The Operating System shall allow Processes to access only required functionality .
RS_OSI_00208Seite 18
e code and data in an implicit manner. [RS_OSI_00208] The Operating System shall allow Processes to access only required functionality .
AUTOSAR_AP_RS_OperatingSystemInterface — Seite 19 (2 betroffene IDs)
RS_OSI_00209Seite 19
ng System Interface Number Heading [RS_OSI_00209] The Operating System shall support error handling including unrecoverable errors. [RS_OSI_00210] The Operating System shall provide a mechanism to observe scheduling of CPU time to T ask, Process [RS_OSI_00211] The Operating System shall provide a mechanism to export low-level scheduling and trace information to applications. Table A.
RS_OSI_00210Seite 19
ndling including unrecoverable errors. [RS_OSI_00210] The Operating System shall provide a mechanism to observe scheduling of CPU time to T ask, Process [RS_OSI_00211] The Operating System shall provide a mechanism to export low-level scheduling and trace information to applications. Table A.2: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 none A.3 Traceable item hi
AUTOSAR_AP_RS_PlatformHealthManagement — Seite 21 (9 betroffene IDs)
RS_PHM_00107Seite 21
Requirements in R24-11 Number Heading [RS_PHM_00107] Platform Health Management shall support multiple instantiation on different platforms. Table A.6: Changed Requirements in R24-11 A.3.3 Deleted Requirements in R24-11 Number Heading [RS_PHM_00001] The Platform Health Management shall provide a standardized header file structure for each service. [RS_PHM_00002] The service header files
RS_PHM_00001Seite 21
Requirements in R24-11 Number Heading [RS_PHM_00001] The Platform Health Management shall provide a standardized header file structure for each service. [RS_PHM_00002] The service header files shall define the namespace for the respective service. [RS_PHM_00003] The Platform Health Management shall define how language specific data types are derived from modeled data types. [RS_PHM_0010
RS_PHM_00002Seite 21
eader file structure for each service. [RS_PHM_00002] The service header files shall define the namespace for the respective service. [RS_PHM_00003] The Platform Health Management shall define how language specific data types are derived from modeled data types. [RS_PHM_00102] Platform Health Management shall provide a standardized C++ interface for the reporting of Health Channel . [RS_
RS_PHM_00003Seite 21
namespace for the respective service. [RS_PHM_00003] The Platform Health Management shall define how language specific data types are derived from modeled data types. [RS_PHM_00102] Platform Health Management shall provide a standardized C++ interface for the reporting of Health Channel . [RS_PHM_00108] Platform Health Management shall provide a standardized interface between Platform H
RS_PHM_00102Seite 21
s are derived from modeled data types. [RS_PHM_00102] Platform Health Management shall provide a standardized C++ interface for the reporting of Health Channel . [RS_PHM_00108] Platform Health Management shall provide a standardized interface between Platform Health Management components used in a daisy chain. [RS_PHM_00109] Platform Health Management shall provide the Daisy chaining int
RS_PHM_00108Seite 21
for the reporting of Health Channel . [RS_PHM_00108] Platform Health Management shall provide a standardized interface between Platform Health Management components used in a daisy chain. [RS_PHM_00109] Platform Health Management shall provide the Daisy chaining interface over ara::com. [RS_PHM_09255] Platform Health Management shall provide an interface to receive Health Channel superv
RS_PHM_00109Seite 21
ment components used in a daisy chain. [RS_PHM_00109] Platform Health Management shall provide the Daisy chaining interface over ara::com. [RS_PHM_09255] Platform Health Management shall provide an interface to receive Health Channel supervision status [RS_PHM_09257] Platform Health Management shall provide an interface to Supervised Entities to report their health status. Table A.7: Del
RS_PHM_09255Seite 21
aisy chaining interface over ara::com. [RS_PHM_09255] Platform Health Management shall provide an interface to receive Health Channel supervision status [RS_PHM_09257] Platform Health Management shall provide an interface to Supervised Entities to report their health status. Table A.7: Deleted Requirements in R24-11 A.4 Traceable item history of this document according to AUTOSAR Release
RS_PHM_09257Seite 21
eive Health Channel supervision status [RS_PHM_09257] Platform Health Management shall provide an interface to Supervised Entities to report their health status. Table A.7: Deleted Requirements in R24-11 A.4 Traceable item history of this document according to AUTOSAR Release R25-11 A.4.1 Added Requirements in R25-11 none A.4.2 Changed Requirements in R25-11 none
AUTOSAR_AP_RS_SafeHardwareAcceleration — Seite 17 (9 betroffene IDs)
RS_SHWA_00014Seite 17
rdware Acceleration Number Heading [RS_SHWA_00014] Device Properties [RS_SHWA_00015] Device Abstraction [RS_SHWA_00016] Event-based Synchronization [RS_SHWA_00017] Data Access [RS_SHWA_00018] Environment Information Table B.2: Added Requirements in R25-11 B.2.2 Changed Requirements in R25-11 Number Heading [RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator [RS_SHWA_000
RS_SHWA_00015Seite 17
ding [RS_SHWA_00014] Device Properties [RS_SHWA_00015] Device Abstraction [RS_SHWA_00016] Event-based Synchronization [RS_SHWA_00017] Data Access [RS_SHWA_00018] Environment Information Table B.2: Added Requirements in R25-11 B.2.2 Changed Requirements in R25-11 Number Heading [RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator [RS_SHWA_00007] Synchronous Errors Handling Me
RS_SHWA_00016Seite 17
ies [RS_SHWA_00015] Device Abstraction [RS_SHWA_00016] Event-based Synchronization [RS_SHWA_00017] Data Access [RS_SHWA_00018] Environment Information Table B.2: Added Requirements in R25-11 B.2.2 Changed Requirements in R25-11 Number Heading [RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator [RS_SHWA_00007] Synchronous Errors Handling Mechanism [RS_SHWA_00009] Data Integr
RS_SHWA_00017Seite 17
HWA_00016] Event-based Synchronization [RS_SHWA_00017] Data Access [RS_SHWA_00018] Environment Information Table B.2: Added Requirements in R25-11 B.2.2 Changed Requirements in R25-11 Number Heading [RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator [RS_SHWA_00007] Synchronous Errors Handling Mechanism [RS_SHWA_00009] Data Integrity Support [RS_SHWA_00010] Allocated Resour
RS_SHWA_00018Seite 17
ronization [RS_SHWA_00017] Data Access [RS_SHWA_00018] Environment Information Table B.2: Added Requirements in R25-11 B.2.2 Changed Requirements in R25-11 Number Heading [RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator [RS_SHWA_00007] Synchronous Errors Handling Mechanism [RS_SHWA_00009] Data Integrity Support [RS_SHWA_00010] Allocated Resources Clean Up Table B.3: Chan
RS_SHWA_00001Seite 17
Requirements in R25-11 Number Heading [RS_SHWA_00001] SHWA Operations Execution on Hardware Accelerator [RS_SHWA_00007] Synchronous Errors Handling Mechanism [RS_SHWA_00009] Data Integrity Support [RS_SHWA_00010] Allocated Resources Clean Up Table B.3: Changed Requirements in R25-11 B.2.3 Deleted Requirements in R25-11 none
RS_SHWA_00007Seite 17
ions Execution on Hardware Accelerator [RS_SHWA_00007] Synchronous Errors Handling Mechanism [RS_SHWA_00009] Data Integrity Support [RS_SHWA_00010] Allocated Resources Clean Up Table B.3: Changed Requirements in R25-11 B.2.3 Deleted Requirements in R25-11 none
RS_SHWA_00009Seite 17
Synchronous Errors Handling Mechanism [RS_SHWA_00009] Data Integrity Support [RS_SHWA_00010] Allocated Resources Clean Up Table B.3: Changed Requirements in R25-11 B.2.3 Deleted Requirements in R25-11 none
RS_SHWA_00010Seite 17
[RS_SHWA_00009] Data Integrity Support [RS_SHWA_00010] Allocated Resources Clean Up Table B.3: Changed Requirements in R25-11 B.2.3 Deleted Requirements in R25-11 none
AUTOSAR_AP_RS_StateManagement — Seite 18 (9 betroffene IDs)
RS_SM_00101Seite 18
Requirements in R22-11 Number Heading [RS_SM_00101] State Management shall support diagnostic reset cause Table A.7: Deleted Requirements in R22-11 A.4.4 Added Constraints in R22-11 none A.4.5 Changed Constraints in R22-11 none A.4.6 Deleted Constraints in R22-11 none A.5 Traceable item history of this document according to AUTOSAR Release R21-11 A.5.1 Added Requirements "in R21-11" Num
RS_SM_00001Seite 18
equirements "in R21-11" Number Heading [RS_SM_00001] State Management shall coordinate and control multiple sets of Adaptive Applications . [RS_SM_00004] State Management shall provide standardized interfaces. [RS_SM_00005] State Management internal states. [RS_SM_00100] State Management shall support ECU reset [RS_SM_00101] State Management shall support diagnostic reset cause [RS_SM_00
RS_SM_00004Seite 18
ltiple sets of Adaptive Applications . [RS_SM_00004] State Management shall provide standardized interfaces. [RS_SM_00005] State Management internal states. [RS_SM_00100] State Management shall support ECU reset [RS_SM_00101] State Management shall support diagnostic reset cause [RS_SM_00200] State Management shall provide an interface between State Management instances. [RS_SM_00300] St
RS_SM_00005Seite 18
shall provide standardized interfaces. [RS_SM_00005] State Management internal states. [RS_SM_00100] State Management shall support ECU reset [RS_SM_00101] State Management shall support diagnostic reset cause [RS_SM_00200] State Management shall provide an interface between State Management instances. [RS_SM_00300] State Management shall support variant handling based on calibration dat
RS_SM_00100Seite 18
005] State Management internal states. [RS_SM_00100] State Management shall support ECU reset [RS_SM_00101] State Management shall support diagnostic reset cause [RS_SM_00200] State Management shall provide an interface between State Management instances. [RS_SM_00300] State Management shall support variant handling based on calibration data. [RS_SM_00400] State Management shall establis
RS_SM_00200Seite 18
t shall support diagnostic reset cause [RS_SM_00200] State Management shall provide an interface between State Management instances. [RS_SM_00300] State Management shall support variant handling based on calibration data. [RS_SM_00400] State Management shall establish communication paths dynamically . [RS_SM_00401] State Management shall control Adaptive Applications depending on dynamic
RS_SM_00300Seite 18
ce between State Management instances. [RS_SM_00300] State Management shall support variant handling based on calibration data. [RS_SM_00400] State Management shall establish communication paths dynamically . [RS_SM_00401] State Management shall control Adaptive Applications depending on dynamic communication paths . Table A.8: Added Requirements "in R21-11"
RS_SM_00400Seite 18
nt handling based on calibration data. [RS_SM_00400] State Management shall establish communication paths dynamically . [RS_SM_00401] State Management shall control Adaptive Applications depending on dynamic communication paths . Table A.8: Added Requirements "in R21-11"
RS_SM_00401Seite 18
lish communication paths dynamically . [RS_SM_00401] State Management shall control Adaptive Applications depending on dynamic communication paths . Table A.8: Added Requirements "in R21-11"
AUTOSAR_AP_RS_StateManagement — Seite 21 (1 betroffene ID)
RS_SM_00500Seite 21
d Requirements in 19-11 Number Heading [RS_SM_00500] State Management shall support efficient resource usage. Table A.11: Deleted Requirements in 19-11 A.7.4 Added Constraints in 19-11 none A.7.5 Changed Constraints in 19-11 none A.7.6 Deleted Constraints in 19-11 none A.8 Traceable item history of this document according to AUTOSAR Release R19-03 A.8.1 Added Requirements in 19-03 Number
AUTOSAR_AP_RS_StateManagement — Seite 22 (2 betroffene IDs)
RS_SM_00002Seite 22
d Requirements in 19-03 Number Heading [RS_SM_00002] State Management shall support Component State change requests. [RS_SM_00201] State Management shall provide the interface over ara::com. Table A.14: Deleted Requirements in 19-03 A.8.4 Added Constraints in 19-03 none A.8.5 Changed Constraints in 19-03 none A.8.6 Deleted Constraints in 19-03 none
RS_SM_00201Seite 22
pport Component State change requests. [RS_SM_00201] State Management shall provide the interface over ara::com. Table A.14: Deleted Requirements in 19-03 A.8.4 Added Constraints in 19-03 none A.8.5 Changed Constraints in 19-03 none A.8.6 Deleted Constraints in 19-03 none
AUTOSAR_FO_RS_Diagnostics — Seite 75 (9 betroffene IDs)
RS_DIAG_04235Seite 75
ics AUTOSAR FO R25-11 Number Heading [RS_Diag_04235] Client certificate validity [RS_Diag_04236] Client certificate target identification [RS_Diag_04237] Client certificate evaluation [RS_Diag_04238] Logging certificate evaluation Table A.4: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_Diag_04059] Configuration of timing parameters [RS_Diag_042
RS_DIAG_04236Seite 75
iag_04235] Client certificate validity [RS_Diag_04236] Client certificate target identification [RS_Diag_04237] Client certificate evaluation [RS_Diag_04238] Logging certificate evaluation Table A.4: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_Diag_04059] Configuration of timing parameters [RS_Diag_04222] Independence of clearing DTC status and
RS_DIAG_04237Seite 75
ient certificate target identification [RS_Diag_04237] Client certificate evaluation [RS_Diag_04238] Logging certificate evaluation Table A.4: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_Diag_04059] Configuration of timing parameters [RS_Diag_04222] Independence of clearing DTC status and system degradation Table A.5: Deleted Requirements in R24
RS_DIAG_04238Seite 75
g_04237] Client certificate evaluation [RS_Diag_04238] Logging certificate evaluation Table A.4: Changed Requirements in R24-11 A.2.3 Deleted Requirements in R24-11 Number Heading [RS_Diag_04059] Configuration of timing parameters [RS_Diag_04222] Independence of clearing DTC status and system degradation Table A.5: Deleted Requirements in R24-11 A.3 Traceable item history of this documen
RS_DIAG_04059Seite 75
Requirements in R24-11 Number Heading [RS_Diag_04059] Configuration of timing parameters [RS_Diag_04222] Independence of clearing DTC status and system degradation Table A.5: Deleted Requirements in R24-11 A.3 Traceable item history of this document according to AUTOSAR Release R23-11 A.3.1 Added Requirements in R23-11 Number Heading [RS_Diag_04270] Notify applications about the changes
RS_DIAG_04222Seite 75
59] Configuration of timing parameters [RS_Diag_04222] Independence of clearing DTC status and system degradation Table A.5: Deleted Requirements in R24-11 A.3 Traceable item history of this document according to AUTOSAR Release R23-11 A.3.1 Added Requirements in R23-11 Number Heading [RS_Diag_04270] Notify applications about the changes of enable conditions [RS_Diag_04271] Support of T
RS_DIAG_04270Seite 75
Requirements in R23-11 Number Heading [RS_Diag_04270] Notify applications about the changes of enable conditions [RS_Diag_04271] Support of T ransmit Certificate [RS_Diag_04272] Support of secure data coding Table A.6: Added Requirements in R23-11 A.3.2 Changed Requirements in R23-11 none A.3.3 Deleted Requirements in R23-11 none
RS_DIAG_04271Seite 75
about the changes of enable conditions [RS_Diag_04271] Support of T ransmit Certificate [RS_Diag_04272] Support of secure data coding Table A.6: Added Requirements in R23-11 A.3.2 Changed Requirements in R23-11 none A.3.3 Deleted Requirements in R23-11 none
RS_DIAG_04272Seite 75
4271] Support of T ransmit Certificate [RS_Diag_04272] Support of secure data coding Table A.6: Added Requirements in R23-11 A.3.2 Changed Requirements in R23-11 none A.3.3 Deleted Requirements in R23-11 none
AUTOSAR_FO_RS_HealthMonitoring — Seite 29 (14 betroffene IDs)
RS_HM_09253Seite 29
ing AUTOSAR FO R25-11 Number Heading [RS_HM_09253] Health Monitoring shall support mode-dependent behavior of Supervised Entities. [RS_HM_09254] Health Monitoring shall provide an interface to Supervised Entities to report the currently reached Checkpoint. [RS_HM_09257] Health Monitoring shall support a variable number of supervised entity occurences at runtime [RS_HM_09300] System Hea
RS_HM_09254Seite 29
ndent behavior of Supervised Entities. [RS_HM_09254] Health Monitoring shall provide an interface to Supervised Entities to report the currently reached Checkpoint. [RS_HM_09257] Health Monitoring shall support a variable number of supervised entity occurences at runtime [RS_HM_09300] System Health Monitor shall transmit Health Indicators as standardized service events [RS_HM_09301] SHM
RS_HM_09257Seite 29
port the currently reached Checkpoint. [RS_HM_09257] Health Monitoring shall support a variable number of supervised entity occurences at runtime [RS_HM_09300] System Health Monitor shall transmit Health Indicators as standardized service events [RS_HM_09301] SHM shall receive relevant health information from local health monitors [RS_HM_09302] Communication between SHM and local health
RS_HM_09300Seite 29
upervised entity occurences at runtime [RS_HM_09300] System Health Monitor shall transmit Health Indicators as standardized service events [RS_HM_09301] SHM shall receive relevant health information from local health monitors [RS_HM_09302] Communication between SHM and local health monitors shall be E2E protected [RS_HM_09303] SHM shall be platform agnostic [RS_HM_09304] SHM shall determ
RS_HM_09301Seite 29
icators as standardized service events [RS_HM_09301] SHM shall receive relevant health information from local health monitors [RS_HM_09302] Communication between SHM and local health monitors shall be E2E protected [RS_HM_09303] SHM shall be platform agnostic [RS_HM_09304] SHM shall determine Health Indicators. [RS_HM_09305] SHM should support redundancy concepts [RS_HM_09306] SHM shall
RS_HM_09302Seite 29
information from local health monitors [RS_HM_09302] Communication between SHM and local health monitors shall be E2E protected [RS_HM_09303] SHM shall be platform agnostic [RS_HM_09304] SHM shall determine Health Indicators. [RS_HM_09305] SHM should support redundancy concepts [RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms [RS_HM_09307] SHM shall be conf
RS_HM_09303Seite 29
health monitors shall be E2E protected [RS_HM_09303] SHM shall be platform agnostic [RS_HM_09304] SHM shall determine Health Indicators. [RS_HM_09305] SHM should support redundancy concepts [RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms [RS_HM_09307] SHM shall be configurable within Abstract Platform Description information [RS_HM_09308] Communication bet
RS_HM_09304Seite 29
_09303] SHM shall be platform agnostic [RS_HM_09304] SHM shall determine Health Indicators. [RS_HM_09305] SHM should support redundancy concepts [RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms [RS_HM_09307] SHM shall be configurable within Abstract Platform Description information [RS_HM_09308] Communication between SHM instances shall be E2E protected [RS
RS_HM_09305Seite 29
SHM shall determine Health Indicators. [RS_HM_09305] SHM should support redundancy concepts [RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms [RS_HM_09307] SHM shall be configurable within Abstract Platform Description information [RS_HM_09308] Communication between SHM instances shall be E2E protected [RS_HM_09309] Cyclic communication between SHM and local
RS_HM_09306Seite 29
SHM should support redundancy concepts [RS_HM_09306] SHM shall be able to interact with Non-AUTOSAR software platforms [RS_HM_09307] SHM shall be configurable within Abstract Platform Description information [RS_HM_09308] Communication between SHM instances shall be E2E protected [RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used for aliveness checks [
RS_HM_09307Seite 29
ct with Non-AUTOSAR software platforms [RS_HM_09307] SHM shall be configurable within Abstract Platform Description information [RS_HM_09308] Communication between SHM instances shall be E2E protected [RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used for aliveness checks [RS_HM_09310] Cyclic communication between SHM instances shall be used for aliven
RS_HM_09308Seite 29
tract Platform Description information [RS_HM_09308] Communication between SHM instances shall be E2E protected [RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used for aliveness checks [RS_HM_09310] Cyclic communication between SHM instances shall be used for aliveness checks Table A.2: Changed Requirements in R25-11 A.4.3 Deleted Requirements in R25-11
RS_HM_09309Seite 29
n SHM instances shall be E2E protected [RS_HM_09309] Cyclic communication between SHM and local health monitors shall be used for aliveness checks [RS_HM_09310] Cyclic communication between SHM instances shall be used for aliveness checks Table A.2: Changed Requirements in R25-11 A.4.3 Deleted Requirements in R25-11 none
RS_HM_09310Seite 29
ors shall be used for aliveness checks [RS_HM_09310] Cyclic communication between SHM instances shall be used for aliveness checks Table A.2: Changed Requirements in R25-11 A.4.3 Deleted Requirements in R25-11 none
AUTOSAR_FO_RS_LogAndTrace — Seite 41 (31 betroffene IDs)
RS_LT_00029Seite 41
ace AUTOSAR FO R25-11 Number Heading [RS_LT_00029] [RS_LT_00030] [RS_LT_00031] [RS_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during productio
RS_LT_00030Seite 41
R25-11 Number Heading [RS_LT_00029] [RS_LT_00030] [RS_LT_00031] [RS_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_L
RS_LT_00031Seite 41
er Heading [RS_LT_00029] [RS_LT_00030] [RS_LT_00031] [RS_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_L
RS_LT_00032Seite 41
_LT_00029] [RS_LT_00030] [RS_LT_00031] [RS_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_L
RS_LT_00033Seite 41
_LT_00030] [RS_LT_00031] [RS_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_L
RS_LT_00034Seite 41
_LT_00031] [RS_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_L
RS_LT_00035Seite 41
_LT_00032] [RS_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_L
RS_LT_00036Seite 41
_LT_00033] [RS_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_L
RS_LT_00037Seite 41
_LT_00034] [RS_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_L
RS_LT_00038Seite 41
_LT_00035] [RS_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_L
RS_LT_00039Seite 41
_LT_00036] [RS_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_L
RS_LT_00040Seite 41
_LT_00037] [RS_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_L
RS_LT_00041Seite 41
_LT_00038] [RS_LT_00039] [RS_LT_00040] [RS_LT_00041] L T shall be a central software component for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_L
RS_LT_00042Seite 41
for the log and trace functionality . [RS_LT_00042] The Log and trace SW component shall be part of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00
RS_LT_00043Seite 41
of the system during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile
RS_LT_00044Seite 41
during production phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_0
RS_LT_00045Seite 41
ion phase. [RS_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shal
RS_LT_00046Seite 41
_LT_00043] [RS_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configura
RS_LT_00047Seite 41
_LT_00044] [RS_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ART
RS_LT_00048Seite 41
_LT_00045] [RS_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process t
RS_LT_00049Seite 41
_LT_00046] [RS_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing inf
RS_LT_00050Seite 41
_LT_00047] [RS_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table
RS_LT_00051Seite 41
_LT_00048] [RS_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Re
RS_LT_00052Seite 41
_LT_00049] [RS_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in
RS_LT_00056Seite 41
_LT_00050] [RS_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 C
RS_LT_00057Seite 41
_LT_00051] [RS_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 Changed Require
RS_LT_00058Seite 41
_LT_00052] [RS_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 Changed Requirements in R23-1
RS_LT_00059Seite 41
_LT_00056] [RS_LT_00057] [RS_LT_00058] [RS_LT_00059] L T shall provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 Changed Requirements in R23-11 none
RS_LT_00060Seite 41
provide an interface for trace points [RS_LT_00060] L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 Changed Requirements in R23-11 none
RS_LT_00061Seite 41
L T shall send modeled trace messages [RS_LT_00061] T racing shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 Changed Requirements in R23-11 none
RS_LT_00062Seite 41
shall be configurable at compile time [RS_LT_00062] L T shall be configurable to use ARTI to process the tracing information Table A.1: Added Requirements in R23-11 A.1.2 Changed Requirements in R23-11 none
AUTOSAR_FO_RS_LogAndTrace — Seite 44 (1 betroffene ID)
RS_LT_00006Seite 44
Requirements in R25-11 Number Heading [RS_LT_00006] Table A.4: Deleted Requirements in R25-11
AUTOSAR_FO_RS_NetworkManagement — Seite 37 (16 betroffene IDs)
RS_NM_02537Seite 37
ent AUTOSAR FO R25-11 Number Heading [RS_Nm_02537] The Nm Coordinator shall be able to abort the coordinated shutdown [RS_Nm_02540] The Nm Control Bit Vector shall contain a PN shutdown request bit. [RS_Nm_02541] Nm shall define a common layout of Nm messages. [RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown request bit if a least one PNC is released
RS_NM_02540Seite 37
able to abort the coordinated shutdown [RS_Nm_02540] The Nm Control Bit Vector shall contain a PN shutdown request bit. [RS_Nm_02541] Nm shall define a common layout of Nm messages. [RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown request bit if a least one PNC is released [RS_Nm_02544] Nm shall forward the indication of a PN shutdown message [RS_Nm_02
RS_NM_02541Seite 37
all contain a PN shutdown request bit. [RS_Nm_02541] Nm shall define a common layout of Nm messages. [RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown request bit if a least one PNC is released [RS_Nm_02544] Nm shall forward the indication of a PN shutdown message [RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial Network
RS_NM_02542Seite 37
define a common layout of Nm messages. [RS_Nm_02542] The <Bus>Nm of the top-level PNC coordinator shall set the PN shutdown request bit if a least one PNC is released [RS_Nm_02544] Nm shall forward the indication of a PN shutdown message [RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial Networking Learning (optional) [RS_Nm_02548] <Bus>Nm shall be able to
RS_NM_02544Seite 37
est bit if a least one PNC is released [RS_Nm_02544] Nm shall forward the indication of a PN shutdown message [RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial Networking Learning (optional) [RS_Nm_02548] <Bus>Nm shall be able to propagate and evaluate the need for synchronized PNC shutdown in the role of a top-level PNC coordinator or intermediate PNC co
RS_NM_02547Seite 37
he indication of a PN shutdown message [RS_Nm_02547] <Bus>Nm shall be able to propagate and evaluate the need for Partial Networking Learning (optional) [RS_Nm_02548] <Bus>Nm shall be able to propagate and evaluate the need for synchronized PNC shutdown in the role of a top-level PNC coordinator or intermediate PNC coordinator (optional) [RS_Nm_02549] Nm shall offer interfaces to Request
RS_NM_02548Seite 37
Partial Networking Learning (optional) [RS_Nm_02548] <Bus>Nm shall be able to propagate and evaluate the need for synchronized PNC shutdown in the role of a top-level PNC coordinator or intermediate PNC coordinator (optional) [RS_Nm_02549] Nm shall offer interfaces to Request and indicate Repeat Message Request (optional) [RS_Nm_02562] Nm shall support channel-specific storage of IRA [RS
RS_NM_02549Seite 37
ntermediate PNC coordinator (optional) [RS_Nm_02549] Nm shall offer interfaces to Request and indicate Repeat Message Request (optional) [RS_Nm_02562] Nm shall support channel-specific storage of IRA [RS_Nm_02563] Nm shall calculate the combined partial network request status EIRA [RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA [RS_Nm_02565] <Bus>
RS_NM_02562Seite 37
cate Repeat Message Request (optional) [RS_Nm_02562] Nm shall support channel-specific storage of IRA [RS_Nm_02563] Nm shall calculate the combined partial network request status EIRA [RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA [RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers using dedicated APIs [RS_Nm_02566]
RS_NM_02563Seite 37
upport channel-specific storage of IRA [RS_Nm_02563] Nm shall calculate the combined partial network request status EIRA [RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA [RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers using dedicated APIs [RS_Nm_02566] Nm shall support channel-specific configuration for ERA [RS_Nm_
RS_NM_02564Seite 37
ed partial network request status EIRA [RS_Nm_02564] Nm shall calculate the status of the external partial network requests ERA [RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers using dedicated APIs [RS_Nm_02566] Nm shall support channel-specific configuration for ERA [RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels Table A.
RS_NM_02565Seite 37
external partial network requests ERA [RS_Nm_02565] <Bus>Nm shall communicate EIRA and ERA requests to the upper layers using dedicated APIs [RS_Nm_02566] Nm shall support channel-specific configuration for ERA [RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels Table A.2: Changed Requirements in R22-11 A.1.3 Deleted Requirements in R22-11 Number Heading [RS
RS_NM_02566Seite 37
the upper layers using dedicated APIs [RS_Nm_02566] Nm shall support channel-specific configuration for ERA [RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels Table A.2: Changed Requirements in R22-11 A.1.3 Deleted Requirements in R22-11 Number Heading [RS_Nm_02543] NM shall forward requests for synchronized PNC shutdown [RS_Nm_02545] <Bus>NM shall handle r
RS_NM_02567Seite 37
channel-specific configuration for ERA [RS_Nm_02567] Nm shall support a global configuration for EIRA over all channels Table A.2: Changed Requirements in R22-11 A.1.3 Deleted Requirements in R22-11 Number Heading [RS_Nm_02543] NM shall forward requests for synchronized PNC shutdown [RS_Nm_02545] <Bus>NM shall handle requests for synchronized PNC shutdown Table A.3: Deleted Requirements
RS_NM_02543Seite 37
Requirements in R22-11 Number Heading [RS_Nm_02543] NM shall forward requests for synchronized PNC shutdown [RS_Nm_02545] <Bus>NM shall handle requests for synchronized PNC shutdown Table A.3: Deleted Requirements in R22-11 A.1.4 Added Constraints in R22-11 none A.1.5 Changed Constraints in R22-11 none
RS_NM_02545Seite 37
requests for synchronized PNC shutdown [RS_Nm_02545] <Bus>NM shall handle requests for synchronized PNC shutdown Table A.3: Deleted Requirements in R22-11 A.1.4 Added Constraints in R22-11 none A.1.5 Changed Constraints in R22-11 none
AUTOSAR_FO_RS_TimeSync — Seite 46 (14 betroffene IDs)
RS_TS_20036Seite 46
ion AUTOSAR FO R25-11 Number Heading [RS_TS_20036] The Timesync over CAN module shall use the time measurement and synchronization protocol to transmit and receive an offset value [RS_TS_20044] The Timesync over FlexRay module shall use the time measurement and synchronization protocol to transmit and receive an offset value [RS_TS_20063] The Timesync over Ethernet module shall use the
RS_TS_20044Seite 46
o transmit and receive an offset value [RS_TS_20044] The Timesync over FlexRay module shall use the time measurement and synchronization protocol to transmit and receive an offset value [RS_TS_20063] The Timesync over Ethernet module shall use the Time Synchronization protocol for Synchronized Time Bases to transmit and receive Offset Time Bases Table A.2: Deleted Requirements in R24-11
RS_TS_20063Seite 46
o transmit and receive an offset value [RS_TS_20063] The Timesync over Ethernet module shall use the Time Synchronization protocol for Synchronized Time Bases to transmit and receive Offset Time Bases Table A.2: Deleted Requirements in R24-11 A.2 Change History of this document according to AUTOSAR Re- lease R25-11 A.2.1 Added Requirements in R25-11 none A.2.2 Changed Requirements in R25
RS_TS_00002Seite 46
Requirements in R25-11 Number Heading [RS_TS_00002] The Implementation of Time Synchronization shall maintain its own Time Base independently of the acting role. [RS_TS_00003] The TS shall initialize the Local Time Base with a configurable startup value [RS_TS_00004] The Implementation of Time Synchronization shall initialize the Global Time Base with a configurable startup value. [RS_T
RS_TS_00003Seite 46
Base independently of the acting role. [RS_TS_00003] The TS shall initialize the Local Time Base with a configurable startup value [RS_TS_00004] The Implementation of Time Synchronization shall initialize the Global Time Base with a configurable startup value. [RS_TS_00005] The Implementation of Time Synchronization shall allow customers to have access to the Synchronized Time Base [RS_T
RS_TS_00004Seite 46
Base with a configurable startup value [RS_TS_00004] The Implementation of Time Synchronization shall initialize the Global Time Base with a configurable startup value. [RS_TS_00005] The Implementation of Time Synchronization shall allow customers to have access to the Synchronized Time Base [RS_TS_00006] The Implementation of Time Synchronization shall provide time information to TSP mo
RS_TS_00005Seite 46
ase with a configurable startup value. [RS_TS_00005] The Implementation of Time Synchronization shall allow customers to have access to the Synchronized Time Base [RS_TS_00006] The Implementation of Time Synchronization shall provide time information to TSP modules [RS_TS_00007] The Implementation of Time Synchronization shall synchronize the Time Base of a Time Slave, on reception of a
RS_TS_00006Seite 46
e access to the Synchronized Time Base [RS_TS_00006] The Implementation of Time Synchronization shall provide time information to TSP modules [RS_TS_00007] The Implementation of Time Synchronization shall synchronize the Time Base of a Time Slave, on reception of a Time Master value [RS_TS_00008] The Implementation of Time Synchronization shall continuously maintain its Time Bases based
RS_TS_00007Seite 46
rovide time information to TSP modules [RS_TS_00007] The Implementation of Time Synchronization shall synchronize the Time Base of a Time Slave, on reception of a Time Master value [RS_TS_00008] The Implementation of Time Synchronization shall continuously maintain its Time Bases based on a Time Base reference clock [RS_TS_00009] The Implementation of Time Synchronization shall maintain
RS_TS_00008Seite 46
e, on reception of a Time Master value [RS_TS_00008] The Implementation of Time Synchronization shall continuously maintain its Time Bases based on a Time Base reference clock [RS_TS_00009] The Implementation of Time Synchronization shall maintain the synchronization status of a Time Base [RS_TS_00010] The Implementation of Time Synchronization shall allow customer on master side to set
RS_TS_00009Seite 46
s based on a Time Base reference clock [RS_TS_00009] The Implementation of Time Synchronization shall maintain the synchronization status of a Time Base [RS_TS_00010] The Implementation of Time Synchronization shall allow customer on master side to set the Global Time [RS_TS_00011] The Implementation of Time Synchronization shall allow customers on master side to trigger time transmissio
RS_TS_00010Seite 46
synchronization status of a Time Base [RS_TS_00010] The Implementation of Time Synchronization shall allow customer on master side to set the Global Time [RS_TS_00011] The Implementation of Time Synchronization shall allow customers on master side to trigger time transmission by the TSP module [RS_TS_00014] The Implementation of Time Synchronization shall allow customers to read User Da
RS_TS_00011Seite 46
on master side to set the Global Time [RS_TS_00011] The Implementation of Time Synchronization shall allow customers on master side to trigger time transmission by the TSP module [RS_TS_00014] The Implementation of Time Synchronization shall allow customers to read User Data propagated via the TSP modules.
RS_TS_00014Seite 46
er time transmission by the TSP module [RS_TS_00014] The Implementation of Time Synchronization shall allow customers to read User Data propagated via the TSP modules.
AUTOSAR_FO_RS_TimeSync — Seite 49 (13 betroffene IDs)
RS_TS_20059Seite 49
ion AUTOSAR FO R25-11 Number Heading [RS_TS_20059] The Timesync over Ethernet module shall access all communication ports belonging to Time Synchronization [RS_TS_20060] The Timesync over Ethernet module shall provide a Time Base after reception of a valid protocol information [RS_TS_20061] The Timesync over Ethernet module shall support means to protect the Time Synchronization protoc
RS_TS_20060Seite 49
orts belonging to Time Synchronization [RS_TS_20060] The Timesync over Ethernet module shall provide a Time Base after reception of a valid protocol information [RS_TS_20061] The Timesync over Ethernet module shall support means to protect the Time Synchronization protocol [RS_TS_20062] The Timesync over Ethernet module shall support user specific data within the time measurement and syn
RS_TS_20061Seite 49
eption of a valid protocol information [RS_TS_20061] The Timesync over Ethernet module shall support means to protect the Time Synchronization protocol [RS_TS_20062] The Timesync over Ethernet module shall support user specific data within the time measurement and synchronization protocol [RS_TS_20066] The Timesync over Ethernet module shall support measuring the peer-to-peer delay using
RS_TS_20062Seite 49
tect the Time Synchronization protocol [RS_TS_20062] The Timesync over Ethernet module shall support user specific data within the time measurement and synchronization protocol [RS_TS_20066] The Timesync over Ethernet module shall support measuring the peer-to-peer delay using the IEEE 802.1AS peer-to-peer delay mechanism. [RS_TS_20068] The Timesync over CAN module shall support classic
RS_TS_20066Seite 49
asurement and synchronization protocol [RS_TS_20066] The Timesync over Ethernet module shall support measuring the peer-to-peer delay using the IEEE 802.1AS peer-to-peer delay mechanism. [RS_TS_20068] The Timesync over CAN module shall support classic CAN and CAN FD [RS_TS_20069] The TimeSync over Ethernet module shall provide read / write access to bus protocol specific parameters [RS_T
RS_TS_20068Seite 49
802.1AS peer-to-peer delay mechanism. [RS_TS_20068] The Timesync over CAN module shall support classic CAN and CAN FD [RS_TS_20069] The TimeSync over Ethernet module shall provide read / write access to bus protocol specific parameters [RS_TS_20070] The Timesync over CAN module shall support hardware and software timestamping [RS_TS_20071] The Timesync over Ethernet module shall enable
RS_TS_20069Seite 49
e shall support classic CAN and CAN FD [RS_TS_20069] The TimeSync over Ethernet module shall provide read / write access to bus protocol specific parameters [RS_TS_20070] The Timesync over CAN module shall support hardware and software timestamping [RS_TS_20071] The Timesync over Ethernet module shall enable time synchronization on peer-to-peer and multidrop topologies [RS_TS_20072] The
RS_TS_20070Seite 49
ss to bus protocol specific parameters [RS_TS_20070] The Timesync over CAN module shall support hardware and software timestamping [RS_TS_20071] The Timesync over Ethernet module shall enable time synchronization on peer-to-peer and multidrop topologies [RS_TS_20072] The Timesync over Ethernet module shall support means to secure the Time Synchronization protocol [RS_TS_20073] The Timesy
RS_TS_20071Seite 49
ort hardware and software timestamping [RS_TS_20071] The Timesync over Ethernet module shall enable time synchronization on peer-to-peer and multidrop topologies [RS_TS_20072] The Timesync over Ethernet module shall support means to secure the Time Synchronization protocol [RS_TS_20073] The Timesync over CAN module shall support means to secure the Time Synchronization protocol [RS_TS_20
RS_TS_20072Seite 49
peer-to-peer and multidrop topologies [RS_TS_20072] The Timesync over Ethernet module shall support means to secure the Time Synchronization protocol [RS_TS_20073] The Timesync over CAN module shall support means to secure the Time Synchronization protocol [RS_TS_20074] The Timesync over FlexRay module shall support means to secure the Time Synchronization protocol [RS_TS_20075] Rate Ra
RS_TS_20073Seite 49
cure the Time Synchronization protocol [RS_TS_20073] The Timesync over CAN module shall support means to secure the Time Synchronization protocol [RS_TS_20074] The Timesync over FlexRay module shall support means to secure the Time Synchronization protocol [RS_TS_20075] Rate Ratio Calculation Table A.3: Changed Requirements in R25-11 A.2.3 Deleted Requirements in R25-11 none
RS_TS_20074Seite 49
cure the Time Synchronization protocol [RS_TS_20074] The Timesync over FlexRay module shall support means to secure the Time Synchronization protocol [RS_TS_20075] Rate Ratio Calculation Table A.3: Changed Requirements in R25-11 A.2.3 Deleted Requirements in R25-11 none
RS_TS_20075Seite 49
cure the Time Synchronization protocol [RS_TS_20075] Rate Ratio Calculation Table A.3: Changed Requirements in R25-11 A.2.3 Deleted Requirements in R25-11 none
Ueberschrift faelschlich als Label-Zeile verworfen751013a2 — 54 IDs auf 27 Seiten
Problem: Die Ueberschriften-Erkennung nutzte einen ungebundenen Praefix-Abgleich gegen bekannte Feldbezeichner. Echte Requirement-Titel, die zufaellig mit denselben Woertern beginnen wie ein Feldname („Header file“, „Type“, „Return value“), wurden dadurch verworfen und ergaben eine leere Ueberschrift.
Fix: Eigenes, strengeres Muster nur fuer die Ueberschriften-Pruefung: ein Feldbezeichner zaehlt nur als Label-Zeile, wenn ihm ein Doppelpunkt folgt oder er die gesamte Zeile bildet.
AUTOSAR_AP_RS_General — Seite 13 (1 betroffene ID)
RS_AP_00116Seite 13
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Header file name
onale: – Dependencies: – Use Case: – ⌋ [RS_AP_00116] Header file name ⌈ Description: All Functional Clusters should provide a self-contained header file for each public class. The header file name shall be derived from the class name. All header file names shall have the extension .h. Additional information: • Scoped enums, non-member functions, and exceptions are not required to have a
AUTOSAR_AP_RS_General — Seite 14 (1 betroffene ID)
RS_AP_00122Seite 14
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Type names
ements specific to Adaptive Platform [RS_AP_00122] Type names ⌈ Description: For all Functional Clusters: the name of their public types - classes, structs, type aliases, and type template parameters • shall be standardized in upper-camel case. • underscores shall not be used. Except for fixed width integer types, postfix _t shall not be used. • capitalized acronyms shall be used as si
AUTOSAR_AP_RS_General — Seite 16 (1 betroffene ID)
RS_AP_00119Seite 16
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Return values / application errors
return values to output parameters. ⌋ [RS_AP_00119] Return values / application errors ⌈ Description: All API function specifications shall give the exact list of standardized errors (linked to the ErrorDomains which define them) that can originate from them, and which situations can cause which of those errors. Furthermore, for return values (especially integral, floating-point, enumer
AUTOSAR_FO_RS_LogAndTrace — Seite 12 (2 betroffene IDs)
RS_LT_00047Seite 12
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall support initialization and registration
pport initialization and registration. [RS_LT_00047] ⌈ Description: Logging shall support to initialize the logging framework and to register the source of logging information. Rationale: T o be able to filter and associate logging information with the origin, it is necessary that applications register themselves at the logging framework. AppliesTo: CP ,AP Use Case: Associate logging inf
RS_LT_00048Seite 12
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall enable applications to provide meta information
lications to provide meta information. [RS_LT_00048] ⌈ Description: Logging shall enable applications to provide additional information about themselves. Rationale: Being able to identify the origin of generated logging information. AppliesTo: CP ,AP Use Case: Sort, filter and associate received logging information. Dependencies: – Supporting Material: – ⌋
AUTOSAR_FO_RS_LogAndTrace — Seite 13 (3 betroffene IDs)
RS_LT_00049Seite 13
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall enable applications to provide Logging Information
ations to provide Logging Information. [RS_LT_00049] ⌈ Description: Logging shall enable applications to provide logging information. The logging information shall include information about its severity . Rationale: While developing applications, it is important to get additional information what is going on internally of an application. AppliesTo: CP ,AP Use Case: Getting internal infor
RS_LT_00050Seite 13
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall support grouping of Logging Information
pport grouping of Logging Information. [RS_LT_00050] ⌈ Description: Logging shall support to logically group logging information. Rationale: Cluster logging information which logically belongs together. AppliesTo: CP ,AP Use Case: Associate or filter all logging information which belongs together. Dependencies: –
RS_LT_00057Seite 13
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall enable tracing of communication between applications
of communication between applications. [RS_LT_00057] ⌈ Description: It shall be possible to trace the communication between applications. Rationale: More and more applications are integrated on one ECU. As a consequence, the communication between applications is done locally and not over an external traceable bus like CAN. AppliesTo: CP ,AP Use Case: Trace the communication between appli
AUTOSAR_FO_RS_LogAndTrace — Seite 14 (2 betroffene IDs)
RS_LT_00051Seite 14
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall allow to select the destination of logging information
he destination of logging information. [RS_LT_00051] ⌈ Description: Logging shall allow to select the destination of the provided logging information. Rationale: There are different possibilities where the logging information can be stored. AppliesTo: CP ,AP Use Case: Forward logging information to the console, to the file system or to send it via the communication bus. Dependencies: – S
RS_LT_00052Seite 14
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall provide early logging capabilities
ll provide early logging capabilities. [RS_LT_00052] ⌈ Description: Logging framework shall provide early logging possibility . The API shall be able to handle log message attempts as well as creating new log contexts instances before the main initialization phase of the Logging back-end was accomplished. Rationale: Calling the initialization procedure at earliest is possible when the pr
AUTOSAR_FO_RS_LogAndTrace — Seite 15 (2 betroffene IDs)
RS_LT_00001Seite 15
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall transmit log and trace messages from several sources over a communication interface to a receiving external
erface to a receiving external client. [RS_LT_00001] ⌈ Description: The L T module shall be a BSW module. It shall receive log and trace messages from several sources, like Applications, some BSW modules and the RTE. These messages may be transmitted over a communication interface to an external client. Log and trace is a debugging mechanism needed by a lot of ECU’s. A log and trace modu
RS_LT_00002Seite 15
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): All log and trace messages sent by an ECU shall have a standardized transmission format and a standardized storage forma
mat and a standardized storage format. [RS_LT_00002] ⌈ Description: A specified format shall be defined, which covers all requirements of log and trace. Some examples of the information stored in a log or trace message are the source, the context and the timestamp of the message to be able to filter the log and trace messages.
AUTOSAR_FO_RS_LogAndTrace — Seite 16 (1 betroffene ID)
RS_LT_00003Seite 16
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Applications shall have the possibility to send log or trace messages to the LT module
og or trace messages to the LT module. [RS_LT_00003] ⌈ Description: L T shall offer a generic interface for Applications independent from the type of log and trace message. Rationale: T o reduce the amount of interfaces a generic and message independent interface may be implemented. AppliesTo: AP , CP Use Case: • Interfacing Application with L T module • T racing or logging messages from
AUTOSAR_FO_RS_LogAndTrace — Seite 17 (3 betroffene IDs)
RS_LT_00043Seite 17
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall provide an interface for logging information
an interface for logging information. [RS_LT_00043] ⌈ Description: Logging shall provide interfaces for applications to forward its logging information, including the associated severity level. Rationale: Forward logging information to the logging framework. AppliesTo: CP ,AP Use Case: Forward logging information to a logging framework for further processing (e.g. store it locally or fo
RS_LT_00044Seite 17
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall be able to handle raw buffer content as logging informa- tion
ffer content as logging informa- tion. [RS_LT_00044] ⌈ Description: Logging shall support to provide the content of a raw buffer as logging information. Rationale: The original content of a buffer might be of interest for developing purpose. AppliesTo: CP ,AP Use Case: Get the exact raw data which is located in the memory . Dependencies: – Supporting Material: – ⌋ 4.2.1.2.4 Logging shall
RS_LT_00045Seite 17
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall enable applications to check the current severity level
s to check the current severity level. [RS_LT_00045] ⌈ Description: Logging shall provide the possibility for applications to check the current active severity level. Rationale: T o avoid unnecessary CPU and/or memory consumption, which is needed for the generation of logging information, applications shall have the possibility to first check whether or not its created logging informatio
AUTOSAR_FO_RS_LogAndTrace — Seite 18 (2 betroffene IDs)
RS_LT_00004Seite 18
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall provide the actual set of log levels and the trace status to an Application
nd the trace status to an Application. [RS_LT_00004] ⌈ Description: Application shall be aware of its log levels and trace status in order not to generate unnecessary log and trace messages. Log level and trace status should be checked by the Applications before sending the messages. Rationale: The generation of unnecessary load on the communication interface and for the system has to be
RS_LT_00046Seite 18
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall provide conversion functions for hexadecimal and bi- nary values
s for hexadecimal and bi- nary values. [RS_LT_00046] ⌈ Description: Logging shall provide the possibility for applications to convert decimal values into the hexadecimal or binary system. Rationale: Provide some debug information as a hexadecimal or as a binary value, instead of a decimal value. AppliesTo: CP ,AP Use Case: Providing logging information as hexadecimal value or as binary v
AUTOSAR_FO_RS_LogAndTrace — Seite 19 (2 betroffene IDs)
RS_LT_00005Seite 19
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): For each Application the interface to LT shall be configured
e interface to LT shall be configured. [RS_LT_00005] ⌈ Description: The generation of the L T interface of each Application shall be enabled by the configuration. Rationale: Only the configured interfaces to the Applications, which are using log and trace, shall be generated. AppliesTo: CP ,AP Dependencies: – Supporting Material: – ⌋ 4.2.1.3 DEM trace interface 4.2.1.3.1 The DEM shall fo
RS_LT_00007Seite 19
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The DEM shall forward error events to the LT module
forward error events to the LT module. [RS_LT_00007] ⌈ Description: The DEM may forward error events to the L T module. Rationale: It may be possible to get an overview of all error messages in an ECU. It may be possible to set them in the correct context with the error events reported by DEM. This makes an analysis of the reported errors more efficient and gives a correct picture of a f
AUTOSAR_FO_RS_LogAndTrace — Seite 20 (2 betroffene IDs)
RS_LT_00008Seite 20
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): RTE shall provide an interface for LT to trace RTE/VFB calls
terface for LT to trace RTE/VFB calls. [RS_LT_00008] ⌈ Description: RTE shall provide the possibility to trace the VFB. Rationale: In the future more and more Applications will be integrated in one ECU. As a consequence the communication between Application is done locally and not over an external traceable bus like CAN or Flexray . It is important to trace the internal communication ove
RS_LT_00009Seite 20
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall implement an interface to trace the RTE/VFB
ent an interface to trace the RTE/VFB. [RS_LT_00009] ⌈ Description: VFB-T racing shall be provided to the RTE generation system. The L T module shall implement the handling of the RTE/VFB trace events. Rationale: T o understand the communication between the Applications it is important to trace all function calls to the Applications except the RTE system function calls. AppliesTo: CP Use
AUTOSAR_FO_RS_LogAndTrace — Seite 21 (3 betroffene IDs)
RS_LT_00010Seite 21
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A global switch shall be defined to switch on and off the RTE tracing
to switch on and off the RTE tracing. [RS_LT_00010] ⌈ Description: There shall be a global switch to turn on and off the RTE tracing of L T at configuration time and at run time. Rationale: T o have a high level activation for all RTE tracing messages a global switch is needed. AppliesTo: CP Use Case: T urning all tracing events for L T on/off Dependencies: – Supporting Material: – ⌋ 4.
RS_LT_00011Seite 21
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall implement the handling of the RTE/VFB trace events
handling of the RTE/VFB trace events. [RS_LT_00011] ⌈ Description: The L T may implement the handling of the RTE/VFB trace events. The groups may be configured at configuration time and the events may be assigned to one group. At run time the log level of each group can be set individually . Rationale: T o understand the communication between the Applications it is important to trace th
RS_LT_00012Seite 21
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): LT shall provide a solution to trace events linked to implicit communi- cation mechanism
to implicit communi- cation mechanism. [RS_LT_00012] ⌈ Description: L T may provide a solution to trace events linked to implicit communication mechanism. The implicit communication may be traced at runnable invocation and termination.
AUTOSAR_FO_RS_LogAndTrace — Seite 22 (2 betroffene IDs)
RS_LT_00013Seite 22
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The transmitted data shall be packetized
transmitted data shall be packetized. [RS_LT_00013] ⌈ Description: The log and trace messages shall be packet oriented. Each packet shall have one or several headers and a payload. The headers may be used for identifying, filtering and classifying the log and trace message. The payload shall contain the parameters given from the Application or BSW. Rationale: L T shall not care about th
RS_LT_00014Seite 22
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The transport format shall be binary
The transport format shall be binary. [RS_LT_00014] ⌈ Description: The log and trace messages shall be in binary format. This is necessary for reducing the bandwidth and the CPU consumption. Rationale: Scope of the L T component is to log and trace events without perturbing the ECU behavior. CPU consumption and bandwidth occupation may be reduced by using a binary format for the protoco
AUTOSAR_FO_RS_LogAndTrace — Seite 23 (2 betroffene IDs)
RS_LT_00016Seite 23
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The format shall deal with Big and Little Endianess
ll deal with Big and Little Endianess. [RS_LT_00016] ⌈ Description: The Endian format shall be considered in the message specification. The message shall signal which Endianess mode is actually used. Rationale: Big and Little Endianess of data representation has mixed occurrences in automotive ECUs. The message format shall be able to deal with both. T o reduce CPU load it shall be possi
RS_LT_00017Seite 23
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Each log and trace message shall contain a timestamp, which will be added to the message during reception of the message
ion of the message in the LT mod- ule. [RS_LT_00017] ⌈ Description: Each log and trace message may contain a timestamp, which shall be added to the message during reception of the message in the L T module. Rationale: For comparing and analyzing complex systems a timestamp is important. The time shall be in a defined granularity . AppliesTo: CP ,AP Use Case: – Dependencies: – Supporting
AUTOSAR_FO_RS_LogAndTrace — Seite 24 (3 betroffene IDs)
RS_LT_00018Seite 24
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A global message counter shall be implemented, to detect messages loss
implemented, to detect messages loss. [RS_LT_00018] ⌈ Description: Every time a message from an Application is received by the L T module or other software module, it shall increment its global messages counter and set the counter in the message. Rationale: It is important to know if a message is lost. A receiving external client may then detect if messages are lost (e.g.because of a bu
RS_LT_00019Seite 24
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): For each log message, a log level shall be provided
essage, a log level shall be provided. [RS_LT_00019] ⌈ Description: Log levels shall be for example error, fatal, debug, information or verbose. Rationale: Standard for logging tools AppliesTo: CP ,AP Use Case: – Dependencies: – Supporting Material: – ⌋ 4.2.2.7 The log and trace message shall contain a parameter, which represents the source of the log and trace message. [RS_LT_00020] ⌈ D
RS_LT_00020Seite 24
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The log and trace message shall contain a parameter, which represents the source of the log and trace message
e source of the log and trace message. [RS_LT_00020] ⌈ Description: The log and trace message may contain a parameter, which represents the source of the log and trace message. Rationale: The source can be identified by the Session ID of the port interface (port defined argument value) which was used to send the message from Application to L T .
AUTOSAR_FO_RS_LogAndTrace — Seite 25 (2 betroffene IDs)
RS_LT_00021Seite 25
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): There shall be a logical grouping for log messages by using different identifiers
ssages by using different identifiers. [RS_LT_00021] ⌈ Description: There shall be additional parameters describing the group of the log and trace message. Rationale: Identifying some logically groups of log and trace to define some filtering action on the external client. AppliesTo: CP ,AP Use Case: – Dependencies: – Supporting Material: – ⌋ 4.2.2.9 Each ECU shall have its unique ECU ID
RS_LT_00022Seite 25
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Each ECU shall have its unique ECU ID
Each ECU shall have its unique ECU ID. [RS_LT_00022] ⌈ Description: Each ECU may have its unique ECU ID, which may be a parameter of each log and trace message. Rationale: An external client receives tracing from different ECU’s so it’s important to know the source. AppliesTo: CP ,AP Use Case: Distinguish tracing from different ECU’s Dependencies: – Supporting Material: – ⌋
AUTOSAR_FO_RS_LogAndTrace — Seite 26 (3 betroffene IDs)
RS_LT_00023Seite 26
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The payload shall transport the parameters of a log and trace message
parameters of a log and trace message. [RS_LT_00023] ⌈ Description: In the payload the parameters of each log and trace message from the Application shall be transported. It may be possible to transport more than one parameter. Rationale: – AppliesTo: CP ,AP Use Case: – Dependencies: – Supporting Material: – ⌋ 4.2.2.11 It shall be possible to transmit the parameters in a raw format. [RS_
RS_LT_00024Seite 26
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): It shall be possible to transmit the parameters in a raw format
ansmit the parameters in a raw format. [RS_LT_00024] ⌈ Description: In most cases the parameter shall be transmitted in the raw format. This means that a separate file shall be provided containing the information about the transmitted parameters. Rationale: The non-verbose mode is for saving memory and bandwidth, because on the ECU only the ID’s of the log and trace messages shall be sto
RS_LT_00056Seite 26
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): There shall be the possibility to transmit the parameters with additional information about themselves (self-description
n about themselves (self-description). [RS_LT_00056] ⌈ Description: The log and trace messages shall contain a description of the parameters in verbose mode. No additional description file needs to be provided in this case. Rationale: In the verbose mode all parameters of the payload contain a self-description of their own type (e.g. integer/float, bit length) and some additional informa
AUTOSAR_FO_RS_LogAndTrace — Seite 27 (2 betroffene IDs)
RS_LT_00025Seite 27
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): It shall be possible to transmit ASCII text in log or trace messages
t ASCII text in log or trace messages. [RS_LT_00025] ⌈ Description: Because log and trace messages often consists of texts, there shall be the possibility to transmit text strings. It may be possible to replace the given text by an ID which may be replaced by the text in the external client (Compare verbose - non-verbose mode). Rationale: In small ECU strings can not be stored because of
RS_LT_00026Seite 27
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The data in non-verbose mode shall be described by an extra file
de shall be described by an extra file [RS_LT_00026] ⌈ Description: The data in non-verbose mode need to be described by an extra file. This file may be in a ARXML format. Rationale: In small ECUs memory is very limited, so temporarily buffered data shall be very small. AppliesTo: CP ,AP Use Case: – Dependencies: – Supporting Material: – ⌋
AUTOSAR_FO_RS_LogAndTrace — Seite 28 (2 betroffene IDs)
RS_LT_00027Seite 28
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Each message in non-verbose mode shall have a unique Message ID significant for identifying the source of the tracing
identifying the source of the tracing. [RS_LT_00027] ⌈ Description: Each message may have a unique identifier significant for identifying the source of the tracing. The ID of a specific message shall be permanent over the developing phase and shall be unique for a given ECU. Rationale: Easy identifying the right information in the log and trace message is very important. Unique message I
RS_LT_00028Seite 28
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A control message shall be implemented to permit the external client to evaluate the round trip time
lient to evaluate the round trip time. [RS_LT_00028] ⌈ Description: A control message shall be implemented to permit the external client to evaluate the round trip time. The external client shall use this message to synchronize the individual log and trace messages from the different ECUs. Rationale: The log and trace time information may enable a user to understand what happens if there
AUTOSAR_FO_RS_LogAndTrace — Seite 29 (2 betroffene IDs)
RS_LT_00029Seite 29
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A protection against unauthorized access in production phase shall be provided
in production phase shall be provided. [RS_LT_00029] ⌈ Description: In production phase, the communication module (see RS_LT_00034) shall be disabled by default. In production phase L T shall use the security mechanisms provided by DCM to handle the access to the log and trace messages. A mechanism shall be implemented to enable the communication module for testing phase permanently . Ra
RS_LT_00030Seite 29
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): Logging shall be able to monitor and shape the amount of LT log and trace events
the amount of LT log and trace events. [RS_LT_00030] ⌈ Description: L T may shape the traffic bandwidth depending on which transport interface is used for communication. The traffic shaping shall be done at runtime. Rationale: Since L T shall be used also in production phase, it is important that the traffic produced by the L T component will not cause an overload of the network and the
AUTOSAR_FO_RS_LogAndTrace — Seite 30 (2 betroffene IDs)
RS_LT_00031Seite 30
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall be configurable at runtime
e LT shall be configurable at runtime. [RS_LT_00031] ⌈ Description: L T shall be configurable at runtime. L T shall have for this propose runtime configurable variables which are initialized with the corresponding configuration parameters. It shall be possible to query the L T runtime configuration. The configuration variables shall be writeable and readable over with some control .mecha
RS_LT_00032Seite 30
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A protocol shall be implemented to be able to set and query the trace status and log levels of log and trace sources of
of log and trace sources of each ECU. [RS_LT_00032] ⌈ Description: L T shall support control messages to set the trace status and log level of each source of each ECU. Rationale: – AppliesTo: CP ,AP Use Case: • Enabling/disabling trace and log messages at different levels. • Set the level of the log messages generated by different sources of each ECU. Dependencies: – Supporting Material
AUTOSAR_FO_RS_LogAndTrace — Seite 31 (2 betroffene IDs)
RS_LT_00033Seite 31
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A list of all log and trace sources of an ECU shall be accessible from the external client
e accessible from the external client. [RS_LT_00033] ⌈ Description: It shall be possible to get a list of all Application IDs and context IDs with corresponding trace status and log levels which are registered to the L T module.Each Application or BSW module which wants to produce trace or log messages shall register to the L T module. Rationale: Users need to know what information can b
RS_LT_00034Seite 31
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): LT shall support a generic API for communicating over a LT communi- cation module
ting over a LT communi- cation module. [RS_LT_00034] ⌈ Description: At debugging phase a communication interface with a high bandwidth is needed. This communication interface is out of scope of the AUTOSAR specification. T o use this communication interface with L T a generic API shall be defined. The user shall be able to implement a board specific communication module to communicate ov
AUTOSAR_FO_RS_LogAndTrace — Seite 32 (2 betroffene IDs)
RS_LT_00035Seite 32
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The DCM shall provide an interface for LT to transport log and trace messages over a diagnostic session
ce messages over a diagnostic session. [RS_LT_00035] ⌈ Description: DCM shall provide an interface for L T to send and receive data over the diagnostic service. Log and trace messages are sent over this service and control messages for L T are received. Because log and trace messages are event triggered and the storage on the ECU is limited, these messages shall be sent when they occur.
RS_LT_00036Seite 32
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall provide a buffer for storing log and trace messages before initialization
d trace messages before initialization [RS_LT_00036] ⌈ Description: The L T may provide a buffer for storing log and trace messages. This may be a standard C-initialized buffer which shall be read out after init of L T . Rationale: This requirement shall guarantee that the L T module can provide its services to other BSW modules also before the complete initialization of all BSW modules.
AUTOSAR_FO_RS_LogAndTrace — Seite 33 (2 betroffene IDs)
RS_LT_00037Seite 33
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): There shall be a buffer to store log and trace message locally
o store log and trace message locally. [RS_LT_00037] ⌈ Description: If the communication module is not enabled or no external client for dumping log and trace message is connected, log and trace messages shall be stored locally in a memory buffer. The size of the buffer shall be set at configuration time. Rationale: T o prevent a lack of communication e.g. at startup or if no external cl
RS_LT_00038Seite 33
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): A mechanism shall be implemented to be able to set the trace status and log levels of registered Application IDs and con
s and context IDs of each Application. [RS_LT_00038] ⌈ Description: L T shall permit to turn off or on traces or to set log levels for registered Application IDs and context IDs at runtime. Rationale: T o gain efficiency in bandwidth and ECU resource usage a mechanism shall be provided to tune the transmission from Applications to L T . The L T module shall provide some control variables
AUTOSAR_FO_RS_LogAndTrace — Seite 34 (2 betroffene IDs)
RS_LT_00039Seite 34
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT shall provide the possibility to store configuration data in a persistent way
onfiguration data in a persistent way. [RS_LT_00039] ⌈ Description: Log and Trace configuration shall be stored persistent. Rationale: The L T can be configured at runtime. L&T configuration data has to be stored to guarantee that at every startup the configuration would be the same. AppliesTo: CP ,AP Use Case: — Dependencies: – Supporting Material: – ⌋ 4.2.4.2.4 The LT component shall b
RS_LT_00040Seite 34
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): The LT component shall be able to filter log and trace messages
able to filter log and trace messages. [RS_LT_00040] ⌈ Description: In order to adapt network traffic to bandwidth availability , the L T component may be able to filter log and trace messages. A policy shall be defined to distinguish messages by different log and trace levels. The configuration of the filter level may be different for storing log and trace messages temporarily and commu
AUTOSAR_FO_RS_LogAndTrace — Seite 35 (1 betroffene ID)
RS_LT_00058Seite 35
Vorher (Ueberschrift): leer
Nachher (Ueberschrift): AUTOSAR Log and Trace shall support harmonized logging
race shall support harmonized logging. [RS_LT_00058] ⌈ Description: AUTOSAR shall define globally usable log messages with a unique ID that can be used by all software parts (system software, AUTOSAR functional clusters and other basic software, application). This shall be enabled by using a mandatory Extension Header with pre-defined message IDs and context IDs that are reserved for eac
Erzeugt mit _src/tools/extraction_report.py direkt aus dem versionierten PDF-Cache. Antworten auf Kurationsanfragen werden ueber das bestehende Review-Framework als Paket gespeichert; wenn zur Umsetzung KI noetig ist, darf sie nur einen Vorschlag aus den zugehoerigen Dokumenten ableiten. Die Person, die die Extraktionsskripte ausfuehrt, hat immer das letzte Wort und uebernimmt Aenderungen erst nach eigener Pruefung.