P4_PIEX Physical Internal Exchange Viewpoint
| Domain | Aspect | Maturity |
|---|---|---|
| Physical | Interaction & Collaboration |  released |
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].
Supported Processes
Supported Information Items
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?
Exposed Concepts
The Diagram shows the concepts exposed by the viewpoint, and related concepts if necessary.
The Table shows the concepts exposed by the viewpoint, and related concepts if necessary.
| Concept | Documentation |
|---|---|
| Physical Interaction Point Property | Specifies a detail of an interaction point on Physical Level. |
| Physical Exchange Kind | Specification for any kind of physical item (energy, material, information, etc.) to be exchanged on Physical Level. This is the realization of the specification made by System Domain Kinds. |
| PEKtypingPIPP | Specifies the fact that a Physical Exchange Kind defines the type of a Physical Interaction Point Property. |
| PCPisPartOfPIPD | specifies that a physical interaction point can be a part of a physical interaction point definition. This fosters reuse and allows structuring of definitions. |
| PIPapplyingToAPE | Specifies the fact that a Physical Interaction Point applies to an Abstract Physical Element. |
| Physical Interaction Point | Specifies the existence of an interaction point on Physical Level. |
| Software Element | Pure Software Elements. Similarity with the V-Model "software unit". |
| Physical Element | A composition of Hardware and Software Elements. Similarity with the V-Model segments and system. See [VXT]. |
| Hardware Element | Pure Hardware Elements. Similarity with the V-Model "hardware unit". |
| PCPOverPCP | Specifies the fact that a physical interaction point communicates / transfers / flows / over an other physical interaction point. Used to define layered physical interfaces, and show layer relationships between interfaces. |
| Physical Item Exchange | Specifies the exchange that is to take place on a Physical Connection. |
| PCNallowingPIE | Specifies the fact that a Physical Item Exchange is allowed on the Physical Connection. |
| Physical Connection | Specifies the connection of two physical interaction points. Note: Connections between physical components indicate that item flows are passed from one output of a source component to one or more inputs of target components. |
| PEKtypingPIE | Specifies the fact that a Physical Exchange Kind defines the type of a Physical Item Exchange. |
| PIPDdefiningDetailOfPIP | Specifies the fact that a Physical Interaction Point Definition defines the exchange capabilities of a Physical Interaction Point. |
Realization of exposed Concepts
The Diagram shows the realization of exposed concepts.
The Table shows the realization of exposed concepts.
Related Viewpoints
Required Viewpoints
Recommended Viewpoints
Example
