Documentation Management Plan
|
status: valid
security: YES
safety: ASIL_B
|
||||
Documentation Management Plan#
Purpose#
The documentation management plan describes how documents are handled in the S-CORE project.
Objectives and scope#
Goal of this plan is to describe
which documents exist
which attributes and lifecycle they have
how they are reviewed
Approach#
Some of the work products of the S-CORE project are modelled specifically (e.g. the requirements and architecture have a specific set of attributes) Others are modelled as general documents (e.g. the plans which are part of the program management plan or the verification reports).
This plan deals with these documents, which have the following manually set attributes:
Title: the name of the document (mandatory)
Unique Id: Id following the naming pattern of the document Title (mandatory)
Safety: which ASIL the document supports (mandatory)
Author: Who is the main committer to the document (mandatory)
Status: describing where in the lifecycle of the document it currently is (mandatory)
Tags: can be used to group documents for subsequent filtering (optional)
Also the “Documentation Management” is a document, so an example for a correct document definition can be seen in the header section above, see Documentation Management Plan (doc__documentation_mgt_plan).
The following additional attributes of the document are generated automatically during the documentation build:
Approver: from the github information on who was the last CODEOWNER performing the github review
Reviewer: any additional reviewer performing the github review without CODEOWNER rights
The lifecycle of S-CORE documents has two states:
Draft: The document is filled with content but not completed, the existing content is reviewed and already applicable
Valid: The document is completed and approved
If a document is invalidated it is removed from the project entirely. A document can also transition from valid to draft, for example if a release was done with a valid verification report and then the development for the next release is started.
Invalidated documents are still observable as part of the git history in the unlikely case of later referral (e.g. for design decisions or audit). In this way, there is even an option to recover the content.
The review of each document is done as defined for this type of work product in the respective process description. This means that for some of the work products dedicated checklists are defined, but for others there are not. In any case the reviews are done in a github review at least by one CODEOWNER who is not the author of the document.
Generally all work products (specific and general documents) are subject to a documentation build, which always contains the latest version of the documents for each pull-request. Versioning of documents is done as for every work product with github means and is defined in the configuration management plan.
The time schedule is not part of the documentation management plan. As described in the project management plan GitHub issues is used to plan and track the work.
The following tables lists all documents. The documentation is structured in several folders Platform Folder Structure, each representing a specific aspect of the project. The following sections lists all documents that are available in each folder. Afterwards an additional section is provided with the collected documents for the features, modules and components. Missing documents are listed as well, so that it is easy to identify missing documents.
Platform documentation#
docs/glossary#
No needs passed the filters
docs/contribute#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
API Guidelines |
draft |
|||
Contribution Guideline |
QM |
valid |
||
Contribution |
ASIL_B |
valid |
||
Static Code Analysis C++ |
valid |
|||
Coding Guidelines C++ |
valid |
|||
MISRA C++:2023 Rule Mapping |
draft |
|||
Development Environment |
ASIL_B |
valid |
||
Feature Request Guideline |
valid |
|||
Git Guidelines |
ASIL_B |
valid |
||
Issue Guideline |
QM |
valid |
||
Naming Conventions |
ASIL_B |
valid |
||
Pull Request Guideline |
QM |
valid |
||
Coding Guidelines Python |
valid |
|||
Rust API design guidelines |
draft |
|||
Coding Guidelines Rust |
valid |
docs/platform_management_plan#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Change Management Plan |
ASIL_B |
YES |
valid |
|
Configuration Management Plan |
ASIL_B |
YES |
draft |
|
Documentation Management Plan |
ASIL_B |
YES |
valid |
|
Platform Management Plan |
ASIL_B |
draft |
||
Problem Resolution Plan |
ASIL_B |
YES |
draft |
|
Project Management Plan |
ASIL_B |
YES |
draft |
|
Platform Quality Management Plan |
ASIL_B |
YES |
valid |
|
Release Management Plan |
ASIL_B |
NO |
draft |
|
Platform Safety Manager |
ASIL_B |
YES |
valid |
|
Platform Safety Plan |
ASIL_B |
NO |
draft |
|
Platform Security Plan |
ASIL_B |
YES |
draft |
|
Software Development Plan |
ASIL_B |
YES |
valid |
|
Software Verification Plan |
ASIL_B |
YES |
draft |
|
Tool Management Plan |
ASIL_B |
YES |
valid |
docs/requirements#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
SW-platform Assumptions |
ASIL_B |
YES |
draft |
docs/quality#
No needs passed the filters
docs/safety#
No needs passed the filters
docs/security#
No needs passed the filters
docs/score_tools#
Title |
ID |
Safety Affected |
Security Affected |
Status |
|---|---|---|---|---|
Bazel |
YES |
YES |
draft |
|
Doc-as-Code |
YES |
YES |
evaluated |
|
gtest |
YES |
YES |
draft |
|
rustfmt |
YES |
YES |
evaluated |
docs/verification_report#
No needs passed the filters
platform_integration_tests#
No needs passed the filters
docs/manuals#
No needs passed the filters
docs/score_releases#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
S-Core v0.5-alpha release note |
ASIL_B |
draft |
Feature documentation#
In the following sections all documents of the features and related modules (components), that are planned for release v0.5, are listed.
docs/features/baselibs#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Base Libraries |
ASIL_B |
valid |
||
Baselibs Architecture Inspection Checklist |
ASIL_B |
draft |
||
Baselibs Architecture |
ASIL_B |
valid |
||
Baselibs DFA |
ASIL_B |
draft |
||
Baselibs FMEA |
ASIL_B |
draft |
||
Baselibs Requirements Inspection Checklist |
ASIL_B |
draft |
||
Baselibs Requirements |
ASIL_B |
draft |
||
Baselibs Safety WPs |
ASIL_B |
draft |
docs/features/communication#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
ABI Compatible Datatypes |
ASIL_B |
valid |
||
Communication |
valid |
|||
Inter-process Communication |
valid |
|||
Communication Requirements |
ASIL_B |
YES |
valid |
|
IPC Architecture |
ASIL_B |
YES |
valid |
|
IPC DFA |
ASIL_B |
NO |
draft |
|
IPC FMEA |
ASIL_B |
NO |
draft |
|
IPC Requirements |
ASIL_B |
YES |
valid |
|
SOME_IP-Gateway |
ASIL_B |
valid |
docs/features/frameworks#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
FEO Feature Architecture Inspection Checklist |
ASIL_B |
NO |
draft |
|
Deterministic App Abstraction Layer |
QM |
valid |
||
FEO Safety Work Products |
ASIL_B |
NO |
valid |
|
Fixed execution order framework |
ASIL_B |
NO |
valid |
|
FEO Assumptions of Use Requirements |
ASIL_B |
NO |
draft |
|
FEO Feature DFA |
ASIL_B |
NO |
draft |
|
FEO Feature Architecture |
ASIL_B |
NO |
valid |
|
FEO Feature Requirements |
ASIL_B |
NO |
valid |
|
FEO Feature FMEA |
ASIL_B |
NO |
draft |
|
FEO Feature Requirements Inspection Checklist |
ASIL_B |
NO |
draft |
|
FEO Feature Safety Analysis Inspection Checklist |
ASIL_B |
NO |
draft |
docs/features/orchestration#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Orchestration |
ASIL_B |
YES |
valid |
|
Orchestration Architecture |
ASIL_B |
YES |
draft |
|
Orchestration DFA |
ASIL_B |
YES |
draft |
|
Orchestration FMEA |
ASIL_B |
YES |
draft |
|
Orchestration Requirements |
ASIL_B |
YES |
valid |
|
Orchestration Safety WPs |
ASIL_B |
YES |
draft |
docs/features/persistency#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Persistency KVS Feature Architecture |
ASIL_B |
NO |
valid |
|
DFA |
ASIL_B |
NO |
valid |
|
FMEA |
ASIL_B |
NO |
valid |
|
Persistency Key-Value-Storage |
ASIL_B |
NO |
valid |
|
Persistency KVS Feature Requirements |
ASIL_B |
NO |
valid |
|
Persistency KVS Safety WPs |
ASIL_B |
NO |
valid |
|
Requirements Inspection Checklist Persistency KVS |
ASIL_B |
NO |
valid |
Modules documentation#
docs/modules/baselibs/docs#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Baselibs Release Note |
ASIL_B |
valid |
||
Baselibs Safety Manual |
ASIL_B |
draft |
||
Baselibs Safety Package Formal Review |
ASIL_B |
draft |
||
Baselibs Safety Plan |
ASIL_B |
draft |
||
Baselibs Safety Plan Formal Review |
ASIL_B |
draft |
||
Baselibs Verification Report |
ASIL_B |
draft |
docs/modules/communication/docs#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Communication Assumptions of Use |
ASIL_B |
NO |
valid |
|
Communication Release Note |
ASIL_B |
YES |
valid |
|
Communication Safety Manual |
ASIL_B |
NO |
draft |
|
Communication Safety Package Formal Review |
ASIL_B |
NO |
draft |
|
Communication Safety Plan |
ASIL_B |
NO |
draft |
|
Communication Safety Plan Formal Review |
ASIL_B |
NO |
draft |
|
Communication Verification Report |
ASIL_B |
YES |
draft |
docs/modules/feo/docs#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
FEO Module Release Note |
ASIL_B |
NO |
draft |
|
FEO Module Safety Manual |
ASIL_B |
NO |
draft |
|
FEO Module Safety Package Formal Review |
ASIL_B |
NO |
draft |
|
FEO Module Safety Plan |
ASIL_B |
NO |
valid |
|
FEO Module Safety Plan Formal Review |
ASIL_B |
NO |
draft |
|
FEO Module Verification Report |
ASIL_B |
NO |
draft |
docs/modules/logging/docs#
No needs passed the filters
docs/modules/os/docs#
No needs passed the filters
docs/modules/persistency/docs#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Persistency Release Note |
ASIL_B |
NO |
valid |
|
Persistency Safety Manual |
ASIL_B |
NO |
valid |
|
Persistency Safety Package Formal Review |
ASIL_B |
NO |
valid |
|
Persistency Safety Plan |
ASIL_B |
NO |
valid |
|
Persistency Safety Plan Formal Review |
ASIL_B |
NO |
valid |
|
Persistency Verification Report |
ASIL_B |
NO |
valid |
docs/modules/tracing/docs#
No needs passed the filters
Components documentation#
docs/modules/baselibs/components#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Bit Manipulation Library |
ASIL_B |
draft |
||
bitmanipulation Architecture |
ASIL_B |
valid |
||
bitmanipulation DFA |
ASIL_B |
draft |
||
bitmanipulation FMEA |
ASIL_B |
draft |
||
Bit Manipulation Requirements |
ASIL_B |
draft |
||
Containers Library |
ASIL_B |
draft |
||
Container Architecture |
ASIL_B |
valid |
||
containers DFA |
ASIL_B |
draft |
||
containers FMEA |
ASIL_B |
draft |
||
Containers Library Requirements |
ASIL_B |
draft |
||
Filesystem Library |
ASIL_B |
draft |
||
Filesystem Architecture |
ASIL_B |
draft |
||
filesystem DFA |
ASIL_B |
draft |
||
filesystem FMEA |
ASIL_B |
draft |
||
Filesystem Library Requirements |
ASIL_B |
draft |
||
JSON-Library |
ASIL_B |
valid |
||
JSON Architecture |
ASIL_B |
draft |
||
JSON DFA |
ASIL_B |
draft |
||
JSON FMEA |
ASIL_B |
draft |
||
JSON Requirements |
ASIL_B |
draft |
||
JSON Wrapper Requirements |
ASIL_B |
valid |
||
OS Library |
ASIL_B |
draft |
||
Result Library |
ASIL_B |
draft |
||
Result Architecture |
ASIL_B |
valid |
||
result DFA |
ASIL_B |
draft |
||
result FMEA |
ASIL_B |
draft |
||
Result Library Requirements |
ASIL_B |
draft |
||
Result Library Requirements Inspection Checklist |
ASIL_B |
draft |
||
Utils Library |
ASIL_B |
draft |
||
Utils Library Requirements |
ASIL_B |
draft |
docs/modules/communication/components#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
LoLa |
ASIL_B |
YES |
draft |
|
LoLa Architecture |
ASIL_B |
YES |
draft |
|
lola Component Classification |
ASIL_B |
NO |
draft |
|
LoLa Detailed Design |
ASIL_B |
YES |
draft |
|
lola DFA |
ASIL_B |
NO |
draft |
|
lola FMEA |
ASIL_B |
NO |
draft |
|
LoLa Requirements |
ASIL_B |
YES |
draft |
docs/modules/feo/components#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
FEO Component Architecture Inspection Checklist |
ASIL_B |
NO |
draft |
|
FEO Component Assumptions of Use Requirements |
ASIL_B |
NO |
valid |
|
FEO Component Architecture |
ASIL_B |
NO |
draft |
|
FEO Component Detailed Design |
ASIL_B |
NO |
draft |
|
FEO Component DFA |
ASIL_B |
NO |
draft |
|
FEO FMEA |
ASIL_B |
NO |
draft |
|
FEO Component Requirements |
ASIL_B |
NO |
draft |
|
FEO Component |
ASIL_B |
draft |
||
FEO Component Classification |
ASIL_B |
NO |
draft |
|
FEO Implementation Inspection Checklist |
ASIL_B |
NO |
draft |
|
FEO Component Requirements Inspection Checklist |
ASIL_B |
NO |
draft |
|
FEO Safety Analysis Inspection Checklist |
ASIL_B |
NO |
draft |
docs/modules/logging/components#
No needs passed the filters
docs/modules/os/components#
No needs passed the filters
docs/modules/persistency/components#
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Persistency Component Classification |
ASIL_B |
NO |
valid |
|
Persistency KVS Module Architecture |
ASIL_B |
NO |
valid |
|
KVS DFA |
ASIL_B |
NO |
valid |
|
KVS FMEA |
ASIL_B |
NO |
valid |
|
Persistency KVS Module Requirements |
ASIL_B |
NO |
valid |
|
Persistency JSON |
ASIL_B |
NO |
valid |
|
Persistency KVS |
ASIL_B |
NO |
valid |
docs/modules/tracing/components#
No needs passed the filters