Skip to content

add stakeholder need - #1243

Draft
stevenc-stb wants to merge 65 commits into
spdx:developfrom
stevenc-stb:stevenc-add-StakeholderNeed
Draft

add stakeholder need #1243
stevenc-stb wants to merge 65 commits into
spdx:developfrom
stevenc-stb:stevenc-add-StakeholderNeed

Conversation

@stevenc-stb

Copy link
Copy Markdown
Collaborator

This is a stakeholder need class and definition for review
added hasStakeholderNeed, requirementRefinesStakeholderNeed Relationship Type
added class of StakeholderNeed

Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
@stevenc-stb stevenc-stb added Profile:FuSa FunctionalSafety profile and related matters labels Apr 2, 2026
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Co-authored-by: Chuck Wolber <chuckwolber@gmail.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
@stevenc-stb
stevenc-stb requested review from chuckwolber and kestewart and removed request for chuckwolber June 6, 2026 13:58
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
@stevenc-stb

Copy link
Copy Markdown
Collaborator Author

@nicpappler @chuckwolber @kestewart Here is the update based on Friday's june 5 meeting. Thoughts?

- reportedBy: Designates a `from` Vulnerability was first reported to a project, vendor, or tracking database for formal identification by each `to` Agent.
- republishedBy: Designates a `from` Vulnerability's details were tracked, aggregated, and/or enriched to improve context (i.e. NVD) by each `to` Agent.
- resolved: The `to` OutOfSpecAction is resolved in the `from` ResolutionAction.
- satisfies: The `from` Requirement satisfies `to` need. Note: The Requirement is not intended to singularly satisfy a particular need. It is more likely than a set of higher level requirements.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- satisfies: The `from` Requirement satisfies `to` need. Note: The Requirement is not intended to singularly satisfy a particular need. It is more likely than a set of higher level requirements.
- satisfies: The `from` Requirement satisfies `to` Need. Note: The Requirement is not intended to singularly satisfy a particular Need. It is more likely than a set of higher level requirements.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

i think this is fixed now.

- reportedBy: Designates a `from` Vulnerability was first reported to a project, vendor, or tracking database for formal identification by each `to` Agent.
- republishedBy: Designates a `from` Vulnerability's details were tracked, aggregated, and/or enriched to improve context (i.e. NVD) by each `to` Agent.
- resolved: The `to` OutOfSpecAction is resolved in the `from` ResolutionAction.
- satisfies: The `from` Requirement satisfies `to` need. Note: The Requirement is not generally intended to singularly satisfy a particular need. It is more likely that a set of higher level requirements is required to achieve a reasonable satisfaction of an expressed need.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- satisfies: The `from` Requirement satisfies `to` need. Note: The Requirement is not generally intended to singularly satisfy a particular need. It is more likely that a set of higher level requirements is required to achieve a reasonable satisfaction of an expressed need.
- satisfies: The `from` Requirement satisfies `to` Need. Note: The Requirement is not generally intended to singularly satisfy a particular Need. It is more likely that a set of higher level requirements is required to achieve a reasonable satisfaction of an expressed Need.

Actually not entirely sure where should do the capitalized. Just flag.

Comment thread model/FunctionalSafety/Classes/Need.md Outdated

A Need represents the high-level intent expressed by Agent during the Needs Analysis phase of the life cycle. It defines the problem space or desired capability before it is translated into verifiable system requirements.

This entity captures the natural language expression of the need via the statement property, ensuring the Agent's voice is preserved in the model. The AgentPriority property allows for the ranking of needs, which is critical for scope management, trade-off analysis, and requirement prioritization. Agent Needs are distinct from System Requirements; while requirements must be technically verifiable, needs express the underlying value or necessity that justifies the system's existence. Traceability from derived requirements back to Needs is essential to ensure alignment with stakeholder expectations with the RelationshipType 'satisfies'.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
This entity captures the natural language expression of the need via the statement property, ensuring the Agent's voice is preserved in the model. The AgentPriority property allows for the ranking of needs, which is critical for scope management, trade-off analysis, and requirement prioritization. Agent Needs are distinct from System Requirements; while requirements must be technically verifiable, needs express the underlying value or necessity that justifies the system's existence. Traceability from derived requirements back to Needs is essential to ensure alignment with stakeholder expectations with the RelationshipType 'satisfies'.
This entity captures the natural language expression of the Need via the statement property, ensuring the Agent's voice is preserved in the model. The AgentPriority property allows for the ranking of needs, which is critical for scope management, trade-off analysis, and requirement prioritization. Agent Needs are distinct from System Requirements; while requirements must be technically verifiable, needs express the underlying value or necessity that justifies the system's existence. Traceability from derived requirements back to Needs is essential to ensure alignment with stakeholder expectations with the RelationshipType 'satisfies'.

Not sure.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

fixed removed unneeded text and made change.

Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
Comment thread model/Core/Vocabularies/RelationshipType.md Outdated
stevenc-stb and others added 3 commits June 6, 2026 08:53
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
@stevenc-stb
stevenc-stb requested a review from bact June 6, 2026 15:13
@bact

bact commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

We may like to update the description of Requirement too, as it refer to "need" and we introduce Need here.

2nd paragraph of Requirement's description:

A requirement element is a distinct unit that defines an expectation, need, behavior, or design intent of an item that either already exists or is to be created in accordance with this requirement.

Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Profile:FuSa FunctionalSafety profile and related matters

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants