This document contains mandatory API design features that must be strongly considered when
creating a new Khronos API or refactoring an existing Khronos API whose implementation is to be
considered for safety critical (SC) software development.
--> 'design features' to be changed to 'design attributes' or 'design artifacts' as for example deterministic behavior is not a feature but an attribute.
--> 'strongly considered' to be changed 'highly recommended'
The requirements contained are given on the advice from experts in various SC fields or domains.
Khronos SCAP adopts requirements based on development and implementation experience of those
experts when satisfying a domain’s software or hardware development requirements, safety
requirements and development standard. Additionally, some requirements are necessary for a
Khronos API to be acceptable in a particular domain, however this does not mean any requirement
in this document can be omitted because the API being developed is known not to be used in the
domain where the requirement is mandated. All the requirements apply to all Khronos SC API
being developed irrespective of whether it is known in advance what limited SC domains an API
will be used for.
--> "The requirements contained are given on the advice from experts in various SC fields or domains." need to be changed to
"The requirements contained are formulated based on the recommendations from experts in various SC fields or domains."
--> "Khronos SCAP adopts requirements based on development and implementation experience of those experts when satisfying a domain’s software or hardware development requirements, safety
requirements and development standard."
need to be changed to
"Khronos SCAP adopts requirements based on development and implementation experience of those
experts, while fulfilling a domain’s software or hardware development requirements, safety
requirements or following specific software development standard."
--> "Additionally, some requirements are necessary for a
Khronos API to be acceptable in a particular domain, however this does not mean any requirement
in this document can be omitted because the API being developed is known not to be used in the
domain where the requirement is mandated."
I couldnt comprehend the above statement. It needs to be rephrased.
irudkin
commented
5 years ago
This document contains mandatory API design features that must be strongly considered when creating a new Khronos API or refactoring an existing Khronos API whose implementation is to be considered for safety critical (SC) software development.
--> 'design features' to be changed to 'design attributes' or 'design artifacts' as for example deterministic behavior is not a feature but an attribute.
--> 'strongly considered' to be changed 'highly recommended'
The requirements contained are given on the advice from experts in various SC fields or domains. Khronos SCAP adopts requirements based on development and implementation experience of those experts when satisfying a domain’s software or hardware development requirements, safety requirements and development standard. Additionally, some requirements are necessary for a Khronos API to be acceptable in a particular domain, however this does not mean any requirement in this document can be omitted because the API being developed is known not to be used in the domain where the requirement is mandated. All the requirements apply to all Khronos SC API being developed irrespective of whether it is known in advance what limited SC domains an API will be used for.
--> "The requirements contained are given on the advice from experts in various SC fields or domains." need to be changed to "The requirements contained are formulated based on the recommendations from experts in various SC fields or domains."
--> "Khronos SCAP adopts requirements based on development and implementation experience of those experts when satisfying a domain’s software or hardware development requirements, safety requirements and development standard." need to be changed to "Khronos SCAP adopts requirements based on development and implementation experience of those experts, while fulfilling a domain’s software or hardware development requirements, safety requirements or following specific software development standard."
--> "Additionally, some requirements are necessary for a Khronos API to be acceptable in a particular domain, however this does not mean any requirement in this document can be omitted because the API being developed is known not to be used in the domain where the requirement is mandated." I couldnt comprehend the above statement. It needs to be rephrased.