Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clearly state hardware/software separation in product_tree #817

Open
tschmidtb51 opened this issue Oct 30, 2024 · 0 comments
Open

Clearly state hardware/software separation in product_tree #817

tschmidtb51 opened this issue Oct 30, 2024 · 0 comments
Assignees
Labels
csaf 2.1 csaf 2.1 work motion_passed A motion has passed

Comments

@tschmidtb51
Copy link
Contributor

Currently, the requirement to separate hardware and software in the product_tree is hidden in the PIH. We should make that more visible by adding a section to chapter 5.

@tschmidtb51 tschmidtb51 self-assigned this Oct 30, 2024
@santosomar santosomar added the motion_passed A motion has passed label Nov 27, 2024
@tschmidtb51 tschmidtb51 added csaf 2.1 csaf 2.1 work and removed tc-discussion-needed labels Nov 27, 2024
tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue Jan 16, 2025
- addresses parts of oasis-tcs#817
- add section about hardware/software separation with example
- add full describe rule
tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue Jan 16, 2025
- addresses parts of oasis-tcs#817
- add optional test to detect potential mixing of hard- and software (6.2.31)
- add invalid example
- add valid examples
tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue Jan 16, 2025
- addresses parts of oasis-tcs#817
- clarify the informative note about test failure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
csaf 2.1 csaf 2.1 work motion_passed A motion has passed
Projects
None yet
Development

No branches or pull requests

2 participants