Lines Matching refs:of
9 The safety committee leads the effort to gather requirements that reflect the **actual** state of
11 approach of the project's safety effort. The goal is **NOT** to create new requirements to request
21 Below are the guidelines for the requirements repository and the expectations of the safety
27 The scope of the requirements covers the KERNEL functionalities.
32 Maintain consistency across all requirements. The language and choice of words shall be consistent.
35 Levels of requirements in the repository
39 System requirements describe the behaviour of the Zephyr RTOS (= the system here).
40 They describe the functionality of the Zephyr RTOS from a very high-level perspective,
41 without going into details of the functionality itself.
42 The purpose of the system requirements is to get an overview of the currently implemented features
43 of the Zephyr RTOS.
44 In other words a person writing these requirements usually has some knowledge of the Zephyr RTOS
51 behavior of the feature.
83 * Adhere to the :ref:`contribute_guidelines` of the Zephyr Project.
91 Characteristics of a good requirement
105 Characteristics of a set of requirements
115 * Use of a recognized Requirements Syntax is recommended.
120 * Other formats are accepted as long as the characteristics of a requirement from above are met.