P4_PIEX Physical Internal Exchange Viewpoint
Domain | Aspect | Maturity |
---|---|---|
Physical | Interaction & Collaboration | released |
Example
Purpose
The Physical Internal Exchange Viewpoint serves for the identification and definition of interfaces of elements of the physical system. also, the delegation of system element interfaces to the physical system boundary interfaces is covered. The Physical Internal Exchange Viewpoint
- identifies system element interfaces on a physical level
- states to which other physical elements the interfaces are connected to
- assigns physical interface definitions to interfaces
- defines the usage of interfaces, e.g., if only a subset of the interfaces is used
- defines the delegation of physical system element interfaces to physical system boundary interfaces
Applicability
The Physical Internal Exchange Viewpoint supports the “Design Definition Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§2.3.5.5] and contributes to the artifacts “System Design Description” and “System Interface Definition”. It also supports the “Interface Management” method of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§3.2.4].
Presentation
One or more IBDs featuring the SOI boundary, the parts representing physical elements of the SOI. At the SOI boundary, the interfaces of the SOI represented as proxy ports. At the parts, proxy ports representing the SOI parts interfaces. Binding Connectors for each identified SOI interface delegated to physical SOI elements interfaces. connectors representing connections between interfaces of SOI parts. Item flows are defined for each planned exchange on the identified interfaces. Note: Please use more than one IBD focused on different areas of interest to keep the view comprehensive. Note: Ports may be nested to organize interfaces, but it is recommended to use only only one level.
A Table representing the content or part of the ibd content.
Stakeholder
- Hardware Developer
- IV&V Engineer
- Mechanic Developer
- Safety Expert
- Security Expert
- Software Developer
- System Architect
Concern
- How do physical system elements interact to provide system functions?
- How do the physical system elements interact to provide the system function?
- Which are the protocols for exchanging physical items on a specific interface?
- Which kind of physical items (energy, material, information, etc.) are used on an interface of a physical architecture element?
- Which physical items (energy, material, information, etc.) are exchanged within the system?
- Which standards, protocols, and format specifications apply to a physical interface?
Profile Model Reference
The following Stereotypes / Model Elements are used in the Viewpoint:
- FlowProperty
- SAF_PhysicalExchangeType
- FlowProperty typed by SAF_PhysicalExchangeType
- SAF_PhysicalInterfaceDefinition contained in ProxyPort
- ProxyPort contained in SAF_PhysicalItem
- ProxyPort
- SAF_PhysicalSoftwareElement
- SAF_PhysicalElement
- SAF_PhysicalHardwareElement
- SAF_InterfaceLayerRelationship
- ItemFlow
- attribute realizingConnector of type Connector at InformationFlow
- Connector
- ItemFlow typed by SAF_PhysicalExchangeType
- ProxyPort typed by SAF_PhysicalInterfaceDefinition