Skip to content

Improvement: Add QNX restriction documentation#2702

Draft
aschemmel-tech wants to merge 1 commit intomainfrom
aschemmel-tech-qnx-aou
Draft

Improvement: Add QNX restriction documentation#2702
aschemmel-tech wants to merge 1 commit intomainfrom
aschemmel-tech-qnx-aou

Conversation

@aschemmel-tech
Copy link
Contributor

No description provided.

@github-actions
Copy link

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

@ANegm-ETAS
Copy link

This is a helpful addition but it raises a question:

The process describes linking Assumptions of Use (AoUs) to architecture elements to show compliance. This works well for positive requirements, but a significant number of restrictions in the QNX safety manual are negative—they prohibit the use of certain functions.

How, then, should a feature team 'link' the absence of a forbidden function to an architecture element to demonstrate compliance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants