Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System Initialization Requirements #26

Open
legrand-gregshue opened this issue Feb 22, 2024 · 3 comments
Open

System Initialization Requirements #26

legrand-gregshue opened this issue Feb 22, 2024 · 3 comments

Comments

@legrand-gregshue
Copy link
Contributor

Populate / extend the requirements documents with system initialization / startup requirements.

@legrand-gregshue
Copy link
Contributor Author

legrand-gregshue commented Feb 22, 2024

  • analyse existing requirements in the Zephyr High Level Requirements and Functional Requirements sdoc files regarding completeness to the associated docs and source files
  • add the requirements to the sections associated with System Initialization in the sdoc files, if no section exists, add new section file (including requirements to the Safety Manual)
  • establish linking from Functional to High Level Requirements, using sdoc functionality

@legrand-gregshue
Copy link
Contributor Author

legrand-gregshue commented Feb 22, 2024

gregshue pushed a commit to gregshue/reqmgmt that referenced this issue Feb 26, 2024
@gregshue
Copy link

Please refactor the PR into separate commits per requirement and per section to simplify the review process.

Please remove the UID values of the new requirements and sections. They need to be assigned during merge into upstream.

Please make the requirements phrasing consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants