KhronosGroup KSCAF_DocGuidelines issues

KhronosGroup / KSCAF_DocGuidelines

Khronos Safety Critical Advisory Forum’s guidelines for developing a safety critical technology specification.

1 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Please rename default branch from 'master' to 'main' per Khronos policy

#46 oddhack closed 9 months ago
2
Approaches: modification of standard and extensions

#45 bnaodovic opened 6 years ago
0
Approaches: subset of a standard

#44 bnaodovic opened 6 years ago
0
Approaches: safety-environment constraints

#43 bnaodovic opened 6 years ago
0
EGL: extensions-compactness of implementation

#42 bnaodovic opened 6 years ago
0
EGL: extensions-lengthy process for small changes

#41 bnaodovic opened 6 years ago
0
EGL: extensions

#40 bnaodovic opened 6 years ago
0
EGL: unsuitable functions

#39 bnaodovic opened 6 years ago
0
EGL: finite-state-machine model

#38 bnaodovic opened 6 years ago
0
EGL: types of parameters

#37 bnaodovic opened 6 years ago
0
EGL: number of functions

#36 bnaodovic opened 6 years ago
0
EGL

#35 bnaodovic opened 6 years ago
1
Implementation details: impact on testability

#34 bnaodovic opened 6 years ago
2
Implementation details: OS support

#33 bnaodovic opened 6 years ago
2
Implementation details

#32 bnaodovic opened 6 years ago
1
API working groups first task is to perform a hazard risk analysis and safety goals report

#31 irudkin opened 6 years ago
1
Provide initialisation and shutdown functions

#30 irudkin opened 7 years ago
1
Development out of context

#29 irudkin opened 7 years ago
1
Cybersecurity

#28 irudkin opened 7 years ago
1
Layout ongoing: Add hyper links between guideline chapters

#27 irudkin opened 7 years ago
0
Admin: When is SCAP Guidelines and Requirements to be made public?

#26 irudkin opened 7 years ago
0
Admin: Investigate to get accreditation from Tüv or ISO for better acceptance of SC API

#25 irudkin opened 7 years ago
0
Guidelines_3_2_8_16159_Scheduling in the 1st person, needs rewrite

#24 irudkin opened 7 years ago
1
RealTime & Scheduling texts

#23 bittinen closed 7 years ago
0
Cybersecurity Assurance Program (UL CAP)

#22 irudkin opened 7 years ago
1
Formatting issues

#21 shadazar opened 7 years ago
1
Write Introduction to Guidelines

#20 shadazar opened 7 years ago
1
Guideline 6 MISRA: new guideline entry in to the document

#19 irudkin closed 6 years ago
0
Adding text from Issue #2

#18 shadazar closed 7 years ago
0
Preventing Denial-of-Service (DoS) attacks

#17 irudkin opened 7 years ago
3
Non recoverable error conditions and reporting implementation status

#16 irudkin opened 7 years ago
3
Explicit Timeout Values (Bug 16024)

#15 DeOrellana closed 7 years ago
1
The SC API should be a subset of the general purpose API (Bug 16012)

#14 DeOrellana closed 7 years ago
1
Conformance testing (Bug 15993)

#13 DeOrellana closed 7 years ago
1
Real time (Bug 16018)

#12 DeOrellana opened 7 years ago
1
Lost context (Bug 16134)

#11 DeOrellana opened 7 years ago
2
An SC API should not allow/encourage use of C++ exception handling (Bug 16057)

#10 DeOrellana opened 7 years ago
2
Memory Management (Bug 15991)

#9 DeOrellana opened 7 years ago
2
Handling of error conditions shall be detailed not generalised (Bug 16059)

#8 DeOrellana opened 7 years ago
1
SC API guideline to reduce options to a minimum (Bug 16056)

#7 DeOrellana opened 7 years ago
1
An SC API shall provide the client with unique version identification on request (Bug 16054)

#6 DeOrellana opened 7 years ago
3
Extensions to the SC API do not have to meet all the requirements of the SCAP (Bug 16023)

#5 DeOrellana opened 7 years ago
1
Debug functionality (Bug 16011)

#4 DeOrellana opened 7 years ago
1
Misra (Bug 15996)

#3 DeOrellana opened 7 years ago
3
Create a list of SC RTOS and their unique features (Bug 15008)

#2 DeOrellana opened 7 years ago
1
Document in the specification where the implementer needs to describe task scheduling (Bugzilla 16159)

#1 DeOrellana opened 7 years ago
1