Lines Matching full:requirements

3 Safety Requirements
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
14 The requirements are gathered in the separate repository:
21 Below are the guidelines for the requirements repository and the expectations of the safety
22 committee when adding requirements to the repository.
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
38 System Requirements
39   System requirements describe the behaviour of the Zephyr RTOS (= the system here).
42   The purpose of the system requirements is to get an overview of the currently implemented features
44   In other words a person writing these requirements usually has some knowledge of the Zephyr RTOS
45   Project as the requirements are specific to an RTOS.
47 Software Requirements
48   Software requirements refine the system-level requirements  at a more granular level so
50   These requirements define the specific actions the feature shall be able to execute and the
56 The tool used to manage requirements, `strictDoc <https://strictdoc.readthedocs.io/en/stable/>`_, is
60 #. Don't add a requirement UID and UID field for new requirements
61 #. After completing work on the new requirements execute: ``strictDoc manage auto-uid .``
62 #. Establish links between the requirements with the new attributed UIDs if needed
64 After doing this, the requirements are ready and a pull request can be created.
65 The CI in the PR will check if the requirements UIDs are valid or if there are duplicates in it.
85   * As long as they are applicable to the requirements repository.
89 * Avoid moving and changing requirements in the same commit.
95 * Verifiable (e.g. testable for functional requirements)
105 Characteristics of a set of requirements
115 * Use of a recognized Requirements Syntax is recommended.
118     unfamiliar with requirements writing.