Skip to content

DRAFT: Req: Refine Thread requierements#73

Closed
simhein wants to merge 4 commits into
zephyrproject-rtos:mainfrom
simhein:thread_refinement
Closed

DRAFT: Req: Refine Thread requierements#73
simhein wants to merge 4 commits into
zephyrproject-rtos:mainfrom
simhein:thread_refinement

Conversation

@simhein

@simhein simhein commented Jun 24, 2024

Copy link
Copy Markdown
Collaborator

Add new missing thread requirements.
Refine the existing requirements.
Remove the user stories from the thread sections and change the thread requirement type

simhein added 4 commits June 10, 2024 11:08
The user story for threads have no value because
most of the time it repeats the requirements
statement.

Signed-off-by: Simon Hein <shein@baumer.com>
Change the requirement type for the Threads
to Non-Functional.

Signed-off-by: Simon Hein <shein@baumer.com>
Add new thread requirements to the software
requirements

Signed-off-by: Simon Hein <shein@baumer.com>
Update the thread requirements to align better to the guidelines
how to write requirements and to make them more specific and aligned
to the current implementation.

Signed-off-by: Simon Hein <shein@baumer.com>
@simhein simhein added the Requirements Requirements work label Jun 24, 2024
@simhein simhein linked an issue Jun 24, 2024 that may be closed by this pull request
3 tasks
@simhein simhein changed the title DRAFT:system: remove user story for threads DRAFT: Req: Refine Thread requierements Jun 25, 2024

@nicpappler nicpappler left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok for me

nashif added a commit to nashif/reqmgmt that referenced this pull request Jul 18, 2026
The thread requirements cover the dedicated per-thread stack
(ZEP-SRS-1-8) and the run-time stack allocation and release paths
(ZEP-SRS-1-24/25), but no requirement captures defining a thread stack
of a chosen size at compile time, which is the primary way applications
provide thread stacks.

Add ZEP-SRS-1-35 for the compile-time stack definition mechanism.

Derived from the gap identified in reqmgmt PR zephyrproject-rtos#73.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
nashif added a commit to nashif/reqmgmt that referenced this pull request Jul 18, 2026
Remove the generic user stories from the thread software requirements
and the thread system requirements. Per the requirements checklist a
USER_STORY is only added when it clarifies intent beyond the statement;
these restated the requirement in as-a-user form without adding
information.

Adopts the cleanup proposed for the thread sections in reqmgmt PR zephyrproject-rtos#73.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
@nashif

nashif commented Jul 18, 2026

Copy link
Copy Markdown
Member

incorportated any remaining improvements into #142, closing.

@nashif nashif closed this Jul 18, 2026
@github-project-automation github-project-automation Bot moved this from In Progress to Done in Safety WG Jul 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Requirements Requirements work

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Thread Requirements

3 participants