KhronosGroup / KhronosGroup/KSCAF_DocRequirements
Design goals: impact of API change on safety shall be analyzed
- Dominant language
- CSS
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When a change to API is planned, impact of the change on the safety is rarely analyzed, mostly due to additional effort required and due to lack of strict enforcement of requirements of the safety environment.
For reference, general issue "Design goals" is defined as issue #26.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the general “Design goals” issue #26 and the surrounding requirements in this repository. Clarify how the safety impact of planned API changes should be addressed in the requirements document and what completion would look like; the current issue does not identify a file, test, or concrete change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100