P1_PCXE Physical Context Exchange Viewpoint

Domain Aspect Maturity
Physical Context & Exchange released

Purpose

The Physical Context Exchange Viewpoint focuses on the identification of the physical interfaces with external entities and relevant documentation. It is used to capture interface design requirements, applicable standards, protocols and format specifications, that are agreed upon the interfaces.

Applicability

The Physical Context Exchange Viewpoint supports the “create system design” activity part of 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”.

Furthermore, the viewpoint supports the “Interface Management” approach of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§3.2.4].

Supported Processes

Supported Information Items

Presentation

A) For each given context, an internal block diagram (IBD is used to identify the physical interfaces, the item flows, that are exchanged on that interfaces, and related documentation. Note: To understand the interfaces, a mapping of protocol layers may be depicted.

B) A tabular format providing a list of all the defined external interfaces and the applicable documentation

  • context element kind (environment, external entity, physical user, etc.)
  • context element role name
  • port name and reference to port type
  • reference to context element type

C) A tabular format listing the applicable standards, protocols and formats for the item flows exchanged via the identified interfaces.

Stakeholder

Concern

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.

ConceptDocumentation
Physical UserThe Physical User is the representation for a human in the physical domain, outside the SOI scope, interacting with the SOI.
Physical SOIRepresents the Physical SOI on Physical Level.
Physical External SystemThe Physical External System in the Physical Domain, outside the SOI scope, interacting with the SOI. E.g. power grid, mobile network, fresh water system (in a house).
Physical Interaction PointSpecifies the existence of an interaction point on Physical Level.
PIPapplyingToAPESpecifies the fact that a Physical Interaction Point applies to an Abstract Physical Element.
Physical EnvironmentThe Physical Environment in the Physical Domain, outside the SOI scope, interacting with the SOI. E.g. air, dirt, sun, road.
Physical ConnectionSpecifies 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.
PIPapplyingToPCESpecifies the fact that a Physical Interaction Point applies to a Physical Context Element.
PCPOverPCPSpecifies 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 ExchangeSpecifies the exchange that is to take place on a Physical Connection.
PEKtypingPIESpecifies the fact that a Physical Exchange Kind defines the type of a Physical Item Exchange.
PIPDdefiningDetailOfPIPSpecifies the fact that a Physical Interaction Point Definition defines the exchange capabilities of a Physical Interaction Point.
PCNallowingPIESpecifies the fact that a Physical Item Exchange is allowed on the Physical Connection.

Realization of exposed Concepts

The Diagram shows the realization of exposed concepts.

The Table shows the realization of exposed concepts.

Required Viewpoints

Example