add stakeholder need - #1243
Conversation
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>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Chuck Wolber <chuckwolber@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>
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>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
|
@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. |
There was a problem hiding this comment.
| - 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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
| - 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.
|
|
||
| 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'. |
There was a problem hiding this comment.
| 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.
There was a problem hiding this comment.
fixed removed unneeded text and made change.
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>
|
We may like to update the description of 2nd paragraph of
|
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>
This is a stakeholder need class and definition for review
added hasStakeholderNeed, requirementRefinesStakeholderNeed Relationship Type
added class of StakeholderNeed