O6_SKRD Stakeholder Requirement Definition Viewpoint
| Domain | Aspect | Maturity |
|---|---|---|
| Operational | Requirement |  released |
Example
Purpose
The Stakeholder Requirement Definition Viewpoint specifies all capabilities, functions and properties, that the intended solution shall possess or expose from the perspective of the Stakeholders. The Stakeholder Requirement Definition Viewpoint also captures constraints for the system to be developed from stakeholders perspective.
Applicability
The Stakeholder Requirement Viewpoint supports the “Stakeholder Needs and Requirements Definition Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§ 2.3.5.2]and contributes to the Stakeholder Needs and Requirements.
Presentation
A tabular format lisiting
- unique requirement ID, text, and attributes,
- traceability reference to justifying model artefacts, e.g. operational stories, operational capabilities, identified concerns of stakeholders, and compliance statements Note: Stakeholder Requirements are to be structured in a way that the Stakeholder behind the Requirement is identifiable. When appropriate, the relationships between identified Stakeholder Requirements are and the justifying model artefacts, Operational Story, Operational Capability, Operational Performer, Operational Process, and Operational Exchange are presented.
- “One Requirement Package for each Stakeholder” is a best-practice modeling rule. A package contains the Requirements specific for one Stakeholder.
- Even if different Stakeholders may have intersecting interests and / or concerns resulting in a similar set of Requirements, each Stakeholder shall have its own set managed in a dedicated Requirement Package. Requirements must not be shared due to their different life cycles. Resolving duplications and conflicts is subject of the requirement analysis resulting in an agreed and consolidated set of System Requirements.
Stakeholder
Concern
- What are the normal and extreme environmental conditions for normal operation, for not operational, for storage, and for transport?
- What are the requirements of environmental conditions imposed on the system?
- What are the requirements that a Stakeholder imposes on the system?
- What defines a valid solution towards the customer?
- What is the range of acceptable system performance, i.e. the critical, top-level performance requirements derived from the operational needs?
- what has to be validated to the customer at system level?
Profile Model Reference
The following Stereotypes / Model Elements are used in the Viewpoint:
- SAF_StakeholderRequirementImposition
- Package
- SAF_StakeholderRequirement
- SAF_Stakeholder
- SAF_OperationalStory
- SAF_SystemOfInterestConcern
- SAF_StakeholderRequirementRefinement
- SAF_OperationalCapability