Tool Requirements#

πŸ“ˆ Status#

This section provides an overview of current process requirements and their clarification & implementation status.

Note

All open issues and pull requests in the process repository are considered as if they are already part of the process requirements. They address a lot of the requirements that are referenced in this document, so we would be blocked if we would not consider them as part of the process requirements.

Docs-As-Code Requirements Status

πŸ—‚οΈ Common Attributes#

Note

To stay consistent with sphinx-needs (the tool behind docs-as-code), we’ll use need for any kind of model element like a requirement, an architecture element or a feature description.

πŸ”’ ID#

Enforces need ID uniqueness
status: valid
security: NO
safety: ASIL_B
tags: Common Attributes
implemented: YES
parent_covered: NO
version: 1

Docs-as-Code shall enforce that all Need IDs are globally unique across all included documentation instances.

Note

Within each docs-instance (as managed by sphinx-needs), IDs are guaranteed to be unique. When linking across instances, unique prefixes are automatically applied to maintain global uniqueness.

Enforces need ID scheme
status: valid
security: NO
safety: ASIL_B

Enforce that Need IDs follow the following naming scheme:

  • A prefix indicating the need type (e.g. feature__)

  • A middle part matching the hierarchical structure of the need:
    • For requirements: a portion of the feature tree or a component acronym

    • For architecture elements: the structural element (e.g. a part of the feature tree, component acronym)

    • For safety analysis (FMEA, DFA): name of analyzed structural element (e.g. Persistency, FEO, etc.)

  • Additional descriptive text to ensure human readability

🏷️ Title#

Enforces title wording rules
status: valid
security: NO
safety: ASIL_B

Enforce that all needs have titles and titles do not contain the following words:

  • shall

  • must

  • will

πŸ“ Description#

Enforces description wording rules
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall enforce that requirement descriptions do not contain the following weak words: ju-st, ab-out, rea-lly, so-me, th-ing, absol-utely

This rule applies to:

Note

Artificial β€œ-” added to avoid triggering violation of this requirment in this document.

πŸ”’ Security Classification#

πŸ›‘οΈ Safety Classification#

🚦 Status#

Status: enforce attribute
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall enforce that the status attribute has one of the following values:

  • valid

  • invalid

This rule applies to:

Versioning#

Versioning: enforce attribute
status: valid
security: NO
safety: ASIL_B
tags: Common Attributes
implemented: YES
parent_covered: YES
version: 1

Docs-As-Code shall enable and enforce a versioning attribute for all needs.

Note

Current implementation is handled mainly by sphinx-needs. In our enviroment it supports whole numbers e.g. (1,2,10,34)

Suspicious: Enforce attribute
status: invalid
security: NO
safety: ASIL_B
tags: Common Attributes
implemented: YES
parent_covered: NO: parent talks about setting covered to false, but we want to issue a build error.
version: 1

Docs-as-Code shall check if linked parent needs have different versions, compared to the version the need was originally linked to.

πŸ“š Documents#

Document Types
status: valid
security: NO
safety: ASIL_B
tags: Documents
implemented: YES
parent_covered: YES
version: 1

Docs-as-Code shall support the following document types:

  • Generic Document (document)

  • Tool Verification Report (doc_tool)

  • Change Request is also a generic document

Mandatory attributes of Generic Documents
status: valid
security: NO
safety: ASIL_B

Enforce that each Generic Document doc__* has the following attributes:

  • status (one of: valid, draft, invalid)

  • security

  • safety

  • realizes

Mapping#

πŸ“‹ Requirements#

πŸ”’ Requirement Types#

Requirements Types
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall support the following requirement types:

  • Stakeholder requirement (stkh_req)

  • Feature requirement (feat_req)

  • Component requirement (comp_req)

  • Assumption of use requirement (aou_req)

  • Process requirement (gd_req)

  • Tool requirement (tool_req)

🏷️ Attributes#

Enforces rationale attribute
status: valid
security: NO
safety: ASIL_B
tags: Requirements
implemented: YES
parent_covered: NO: Can not ensure correct reasoning
version: 1

Docs-as-Code shall enforce that each stakeholder requirement (stkh_req) contains a rationale attribute.

Enforces requirement type classification
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall enforce that each need of type Requirements Types (tool_req__docs_req_types) except process and tool requirements has a reqtype attribute with one of the following values:

  • Functional

  • Interface

  • Process

  • Non-Functional

Support requirements test coverage
status: invalid
security: NO
safety: ASIL_B

Docs-As-Code shall allow for every need of type Requirements Types (tool_req__docs_req_types) to have a testcovered attribute, which must be one of:

  • Yes

  • No

Note

No concept yet

Enforce validity attribute correctness
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall enforce that the valid_from and valid_until attributes of stakeholder and feature requirements are correct.

The format of a milestone is something like β€œv0.5” or β€œv1.0.1”. No suffixes like β€œ-SNAPSHOT” or β€œ-beta” are allowed.

Enforce validity start is before end
status: valid
security: NO
safety: ASIL_B
tags: Requirements
implemented: YES
parent_covered: YES
version: 2

Docs-as-Code shall enforce that valid_from is before valid_until attribute in stakeholder and feature requirements. We consider β€œfrom” is inclusive but β€œuntil” is exclusive, so from v0.5 until v1.0 means valid for v0.5 but not for v1.0. If either attribute is missing, no check is performed.

πŸ›οΈ Architecture#

πŸ”’ Architecture Types#

Architecture Types
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall support the following architecture element types:

  • Feature Static View (feat_arc_sta)

  • Feature (feat)

  • Logical Interface (logic_arc_int)

  • Logical Interface Operation (logic_arc_int_op)

  • Component Static View (comp_arc_sta)

  • Component (comp)

  • Interface (real_arc_int)

  • Interface Operation (real_arc_int_op)

Architecture Attributes#

Architecture Mandatory Attributes
status: valid
security: NO
safety: ASIL_B
tags: Architecture
implemented: YES
parent_covered: YES
parent_has_problem: NO
version: 2

Docs-as-Code shall enforce that the following attributes are present in all needs of type Architecture Types (tool_req__docs_arch_types)

  • Safety

  • Security

  • Status

  • UID

πŸ”— Linkage#

πŸ’» Detailed Design & Code#

πŸ”— Code Linkage#

Feature Flags
status: valid
security: NO
safety: ASIL_B
tags: Detailed Design & Code
implemented: NO
parent_covered: YES
version: 1

Docs-as-Code shall allow for a to-be-defined list of checks to be non-fatal for non release builds. These are typically better suited for metrics than for checks.

e.g. gd_req__req_linkage_architecture

Testing#

Extract Metadata from Tests
status: valid
security: NO
safety: ASIL_B
tags: Testing
implemented: PARTIAL
parent_covered: YES: Together with tool_req__docs_test_metadata_mandatory_2, tool_req__docs_test_metadata_link_levels
version: 1

Docs-as-Code shall ensure that each test case has TestType and DerivationTechnique set.

Extract Metadata from Tests
status: invalid
security: NO
safety: ASIL_B
tags: Testing
implemented: PARTIAL
parent_covered: YES: Together with tool_req__docs_test_metadata_mandatory_1, tool_req__docs_test_metadata_link_levels
version: 1

Docs-as-Code shall ensure that each test case has a non empty description.

Note

this will probably be implemented outside of docs-as-code.

Provide Metrics for linked requirements
status: valid
security: NO
safety: ASIL_B

Docs-AS-Code shall provide a way to gather statistics on linkages to implementation(source_code_links) & tests(testlink) for all needs. It shall also be possible to filter these by type and use the provided statistics in the documentation (via diagrams drawn from it etc.)

πŸ§ͺ Tool Verification Reports#

Enforce safety classification
status: valid
security: NO
safety: ASIL_B
tags: Tool Verification Reports
implemented: YES
parent_covered: YES
version: 1

Docs-as-Code shall enforce that every Tool Verification Report (doc_tool) includes a safety_affected attribute with one of the following values:

  • YES

  • NO

Enforce security classification
status: valid
security: NO
safety: ASIL_B
tags: Tool Verification Reports
implemented: YES
parent_covered: YES
version: 1

Docs-as-Code shall enforce that every Tool Verification Report (doc_tool) includes a security_affected attribute with one of the following values:

  • YES

  • NO

Enforce status classification
status: valid
security: NO
safety: ASIL_B
tags: Tool Verification Reports
implemented: YES
parent_covered: YES
version: 1

Docs-as-Code shall enforce that every Tool Verification Report (doc_tool) includes a status attribute with one of the following values:

  • draft

  • evaluated

  • qualified

  • released

  • rejected

Enforce version attribute
status: valid
security: NO
safety: ASIL_B
tags: Tool Verification Reports
implemented: YES
parent_covered: YES
version: 2

Docs-as-Code shall enforce that every Tool Verification Report (doc_tool) includes a tool_version attribute.

Enforce confidence level classification
status: valid
security: NO
safety: ASIL_B
tags: Tool Verification Reports
implemented: YES
parent_covered: YES
version: 1

Docs-as-Code shall enforce that every Tool Verification Report (doc_tool) includes a tcl attribute with one of the following values:

  • LOW

  • HIGH

βš™οΈ Process / Other#

Workflow Types
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall support the following workflow types:

  • Workflow (wf)

Workproduct Types
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall support the following workproduct types:

  • Workproduct (wp)

Standard Requirement Types
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall support the following requirement types:

  • Standard requirement (std_req)

Standard Workproduct Types
status: valid
security: NO
safety: ASIL_B

Docs-as-Code shall support the following requirement types:

  • Standard Workproduct (std_wp)

πŸ›‘οΈ Safety Analysis (DFA + FMEA)#

Safety Analysis Need Types
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall support the following need types:

  • Feature FMEA (Failure Modes and Effect Analysis) -> feat_saf_fmea

  • Component FMEA (Failure Modes and Effect Analysis) -> comp_saf_fmea

  • Platform DFA (Dependent Failure Analysis) -> plat_saf_dfa

  • Feature DFA (Dependend Failure Analysis) -> feat_saf_dfa

  • Component DFA (Dependent Failure Analysis) -> comp_saf_dfa

Safety Analysis Mandatory Attributes
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: YES
parent_covered: YES
version: 1

All safety analysis elements in Safety Analysis Need Types (tool_req__docs_saf_types) shall have the following mandatory attributes:

  • DFA-only attribute: failure_id

  • FMEA-only attribute: fault_id

  • attribute: failure_effect

  • attribute: status

  • attribute: sufficient

  • attribute: title (all Needs elements have a title)

  • attribute: id (all Needs elements have an id)

Safety Analysis Mitigation Attribute
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall enforce valid needs (status == valid) of type Safety Analysis Need Types (tool_req__docs_saf_types) to have at least one mitigated_by link to a requirement on the corresponding level.

At least one of the linked requirements must have the same ASIL level or a higher one.

It can be comp_req or aou_req.

Safety Analysis Mitigation Issue Attribute
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: YES
parent_covered: NO: Can not enforce 'sufficent' status being no until mitigation is ok
version: 1

Docs-As-Code shall allow needs of type Safety Analysis Need Types (tool_req__docs_saf_types) to have a mitigation_issue attribute which links to a GitHub issue.

Safety Analysis Sufficient Attribute
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall enforce needs of type Safety Analysis Need Types (tool_req__docs_saf_types) to have a sufficient attribute , which can have one of the following values:

  • yes

  • no

Safety Analysis Sufficient Check
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: NO
parent_covered: YES
version: 1

Docs-As-Code shall ensure needs of type Safety Analysis Need Types (tool_req__docs_saf_types) with sufficient == yes have a mitigated_by entry.

Safety Analysis Mandatory Content
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall enforce needs of type Safety Analysis Need Types (tool_req__docs_saf_types) to have a non empty content.

Safety Analysis Linkage Violates
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall enforce that needs of type Safety Analysis Need Types (tool_req__docs_saf_types) have a violates links to at least one dynamic / static diagram according to the table.

Link Source

Allowed Link Target

feat_saf_dfa

feat_arc_sta

comp_saf_dfa

comp_arc_sta

feat_saf_fmea

feat_arc_dyn, feat_arc_sta

comp_saf_fmea

comp_arc_dyn, comp_arc_sta

FMEA: fault id attribute
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: YES
parent_covered: NO
version: 2

Docs-As-Code shall enforce that needs of type FMEA (see Safety Analysis Need Types (tool_req__docs_saf_types)) have a fault_id attribute.

Allowed values are listed as ID in tables at gd_guidl__dfa_failure_initiators.

DFA: failure id attribute
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: YES
parent_covered: NO
version: 2

Docs-As-Code shall enforce that needs of type DFA (see Safety Analysis Need Types (tool_req__docs_saf_types)) have a failure_id attribute.

Note: Allowed values are listed as ID in tables at gd_guidl__dfa_failure_initiators. This is not verified.

Failure Effect
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: NO
parent_covered: YES
version: 1

Docs-As-Code shall enforce that every Safety Analysis has a short description of the failure effect (e.g. failure lead to an unintended actuation of the analysed element)

Safety Analysis (DFA + FMEA) Process to Tool Requirement Mapping#

Safety Analysis Safety Relevant Attribute
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: YES
parent_covered: YES
version: 1

Docs-As-Code shall allow needs of type Safety Analysis Need Types (tool_req__docs_saf_types) and plat_saf_dfa to have an optional safety_relevant attribute. The allowed values are:

  • yes

  • no

FMEA: Root Cause Attribute
status: valid
security: NO
safety: ASIL_B
tags: Safety Analysis
implemented: YES
parent_covered: YES
version: 1

Docs-As-Code shall allow FMEA needs (feat_saf_fmea, comp_saf_fmea) to have an optional root_cause attribute with non-empty content.

πŸ”’ Security Analysis#

Security Analysis Need Types
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall support the following need types:

  • Feature Security Analysis Threat (STRIDE) -> feat_sec_threat

  • Component Security Analysis Threat (STRIDE) -> comp_sec_threat

  • Platform Security Analysis Threat (STRIDE) -> plat_sec_threat

  • Feature Security Analysis (Threat Scenario) -> feat_sec_ana

  • Component Security Analysis (Threat Scenario) -> comp_sec_ana

  • Platform Security Analysis (Threat Scenario) -> plat_sec_ana

Security Analysis: STRIDE Threat ID Attribute
status: valid
security: NO
safety: ASIL_B

Docs-As-Code shall enforce that STRIDE threat needs (feat_sec_threat, comp_sec_threat, plat_sec_threat) have a mandatory threat_id attribute.

Security Analysis Threat Scenario Mandatory Attributes
status: valid
security: NO
safety: ASIL_B

Enforce that threat scenario needs (feat_sec_ana, comp_sec_ana, plat_sec_ana) have the following mandatory attributes:

  • threat_scenario_id

  • status: valid or invalid

  • sufficient: yes or no

  • threat_effect: short description of the threat impact

Security Analysis Optional Attributes
status: valid
security: NO
safety: ASIL_B
tags: Security Analysis
implemented: YES
parent_covered: YES
version: 1

Allow threat scenario needs (feat_sec_ana, comp_sec_ana, plat_sec_ana) to have the following optional attributes and links:

  • mitigation_issue: link to a GitHub issue

  • mitigated_by: link to aou_req

πŸ—ΊοΈ Full Mapping#

Process to tools:

ID

tool_req

tool_req__docs_arch_attr_mandatory; tool_req__docs_arch_link_fulfils

tool_req__docs_arch_link_fulfils_aou

tool_req__docs_arch_attr_mandatory

tool_req__docs_common_attr_safety

tool_req__docs_common_attr_security

tool_req__docs_common_attr_status

tool_req__docs_common_attr_id; tool_req__docs_common_attr_id_scheme

tool_req__docs_arch_types

tool_req__docs_arch_types

tool_req__docs_arch_link_aou_check

tool_req__docs_arch_link_safety_to_req; tool_req__docs_arch_link_qm_to_safety_req

tool_req__docs_arch_link_fulfils

tool_req__arch_linkage_safety

tool_req__docs_req_arch_link_safety_to_arch

tool_req__docs_arch_link_security

tool_req__docs_arch_link_fulfils

tool_req__docs_arch_views

tool_req__docs_doc_generic_mandatory

tool_req__docs_doc_generic_mandatory

tool_req__docs_doc_generic_mandatory

tool_req__docs_doc_types

tool_req__docs_arch_links

tool_req__docs_common_attr_description

tool_req__docs_arch_links

tool_req__docs_common_attr_title

tool_req__docs_common_attr_id_scheme

tool_req__docs_common_attr_description

tool_req__docs_common_attr_id_scheme

tool_req__docs_common_attr_description

tool_req__docs_common_attr_id_scheme

tool_req__docs_stdreq_types; tool_req__docs_wf_types; tool_req__docs_stdwp_types; tool_req__docs_wp_types

tool_req__docs_stdreq_types; tool_req__docs_wf_types; tool_req__docs_stdwp_types; tool_req__docs_wp_types

tool_req__docs_common_attr_description

tool_req__docs_dd_link_source_code_link

tool_req__docs_req_attr_rationale

tool_req__docs_common_attr_safety

tool_req__docs_common_attr_security

tool_req__docs_common_attr_status

tool_req__docs_req_attr_testcov

tool_req__docs_test_link_testcase

tool_req__docs_common_attr_title

tool_req__docs_req_attr_reqtype

tool_req__docs_common_attr_id; tool_req__docs_common_attr_id_scheme

tool_req__docs_req_attr_validity_correctness

tool_req__docs_req_attr_validity_correctness

tool_req__docs_common_attr_version

tool_req__docs_common_attr_id_scheme; tool_req__docs_common_attr_security; tool_req__docs_common_attr_safety; tool_req__docs_common_attr_status; tool_req__docs_req_attr_rationale; tool_req__docs_common_attr_description

tool_req__docs_common_attr_desc_wording

tool_req__docs_req_link_satisfies_allowed

tool_req__docs_req_link_covers_aou

tool_req__docs_dd_feature_flag

tool_req__docs_arch_link_fulfils

tool_req__docs_common_attr_safety_link_check; tool_req__docs_req_arch_link_safety_to_arch

tool_req__docs_req_types

tool_req__docs_common_attr_suspicious

tool_req__docs_req_link_satisfies_allowed

tool_req__docs_req_attr_validity_consistency; tool_req__docs_req_attr_validity_correctness

tool_req__docs_saf_attrs_content

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_saf_attr_dfa_failure_id

tool_req__docs_saf_attrs_root_cause

tool_req__docs_saf_attr_fmea_fault_id

tool_req__docs_saf_attr_fmea_failure_effect

tool_req__docs_saf_attrs_mandatory

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_saf_attrs_mitigation_issue

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_saf_attrs_safety_relevant

tool_req__docs_common_attr_status

tool_req__docs_saf_attrs_sufficient_check; tool_req__docs_saf_attrs_sufficient

tool_req__docs_common_attr_title

tool_req__docs_common_attr_id; tool_req__docs_common_attr_id_scheme; tool_req__docs_saf_types

tool_req__docs_saf_attrs_violates

tool_req__docs_saf_attrs_violates

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_saf_types

tool_req__docs_common_attr_description

tool_req__docs_sec_attrs_optional

tool_req__docs_saf_attrs_mandatory

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_sec_attrs_optional

tool_req__docs_saf_attrs_mitigated_by

tool_req__docs_sec_attrs_mandatory

tool_req__docs_sec_attr_stride_threat_id

tool_req__docs_sec_attrs_mandatory

tool_req__docs_sec_attrs_mandatory

tool_req__docs_sec_attrs_mandatory

tool_req__docs_saf_attrs_violates

tool_req__docs_saf_attrs_violates

tool_req__docs_sec_types

tool_req__docs_tvr_safety

tool_req__docs_tvr_security

tool_req__docs_tvr_status

tool_req__docs_tvr_confidence_level

tool_req__docs_common_attr_id

tool_req__docs_tvr_version

tool_req__docs_tvr_status; tool_req__docs_tvr_safety; tool_req__docs_tvr_security

tool_req__docs_test_metadata_mandatory_1; tool_req__docs_test_metadata_mandatory_2; tool_req__docs_test_metadata_link_levels

tool_req__docs_test_linkage_metrics

Overview of Tool to Process Requirements#

Process Requirement

Tool Requirement

Implemented

Source Code Link

tool_req__arch_linkage_safety

YES

tool_req__docs_arch_attr_mandatory

YES

tool_req__docs_arch_link_aou_check

NO

tool_req__docs_arch_link_fulfils

YES

tool_req__docs_arch_link_fulfils_aou

YES

tool_req__docs_arch_link_qm_to_safety_req

PARTIAL

tool_req__docs_arch_link_safety_to_req

PARTIAL

tool_req__docs_arch_link_security

YES

tool_req__docs_arch_links

YES

tool_req__docs_arch_types

YES

tool_req__docs_arch_views

YES

tool_req__docs_common_attr_desc_wording

YES

tool_req__docs_common_attr_description

YES

tool_req__docs_common_attr_id

YES

tool_req__docs_common_attr_id_scheme

YES

tool_req__docs_common_attr_safety

YES

tool_req__docs_common_attr_safety_link_check

YES

tool_req__docs_common_attr_security

YES

tool_req__docs_common_attr_status

YES

tool_req__docs_common_attr_suspicious

YES

tool_req__docs_common_attr_title

YES

tool_req__docs_common_attr_version

YES

tool_req__docs_dd_feature_flag

NO

tool_req__docs_dd_link_source_code_link

YES

tool_req__docs_doc_generic_mandatory

YES

tool_req__docs_doc_types

YES

tool_req__docs_req_arch_link_safety_to_arch

YES

tool_req__docs_req_attr_rationale

YES

tool_req__docs_req_attr_reqtype

YES

tool_req__docs_req_attr_testcov

PARTIAL

tool_req__docs_req_attr_validity_consistency

YES

tool_req__docs_req_attr_validity_correctness

YES

tool_req__docs_req_link_covers_aou

YES

tool_req__docs_req_link_satisfies_allowed

YES

tool_req__docs_req_types

YES

tool_req__docs_saf_attr_dfa_failure_id

YES

tool_req__docs_saf_attr_fmea_failure_effect

NO

tool_req__docs_saf_attr_fmea_fault_id

YES

tool_req__docs_saf_attrs_content

YES

tool_req__docs_saf_attrs_mandatory

YES

tool_req__docs_saf_attrs_mitigated_by

NO

tool_req__docs_saf_attrs_mitigation_issue

YES

tool_req__docs_saf_attrs_root_cause

YES

tool_req__docs_saf_attrs_safety_relevant

YES

tool_req__docs_saf_attrs_sufficient

YES

tool_req__docs_saf_attrs_sufficient_check

NO

tool_req__docs_saf_attrs_violates

YES

tool_req__docs_saf_types

YES

tool_req__docs_sec_attr_stride_threat_id

YES

tool_req__docs_sec_attrs_mandatory

YES

tool_req__docs_sec_attrs_optional

YES

tool_req__docs_sec_types

YES

tool_req__docs_stdreq_types

YES

tool_req__docs_stdwp_types

YES

tool_req__docs_test_link_testcase

YES

tool_req__docs_test_linkage_metrics

YES

tool_req__docs_test_metadata_link_levels

NO

tool_req__docs_test_metadata_mandatory_1

PARTIAL

tool_req__docs_test_metadata_mandatory_2

PARTIAL

tool_req__docs_tvr_confidence_level

YES

tool_req__docs_tvr_safety

YES

tool_req__docs_tvr_security

YES

tool_req__docs_tvr_status

YES

tool_req__docs_tvr_version

YES

tool_req__docs_wf_types

YES

tool_req__docs_wp_types

YES