F1_SCXE System Context Exchange Viewpoint

Domain Aspect Maturity
Functional Context & Exchange released

Purpose

The System Context Exchange Viewpoint serves for the identification and definition of external interfaces of the SOI that are used to interact, e.g., users, external systems, and other external entities defined in the given context of the SOI. The System Context Exchange Viewpoint

  • identifies system interfaces on a functional level,
  • states to which external entities the system interfaces are connected to,
  • and defines the usage of interfaces, e.g., when only a subset of the interface is used.

Applicability

The System Context Exchange Viewpoint supports the “prepare for system requirement definition” activity included in the “System Requirements Definition Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§2.3.5.3] and contributes to the artifact “System Requirements Definition Report”.

Supported Processes

Supported Information Items

Presentation

An internal block diagram (IBD) - associated to a system context - featuring the SOI, the system context elements, and the connectors for each identified interface from SOI to the respective context elements. An interface is an interaction point for interaction of the SOI to with context elements. Item flows are defined for each exchange on the identified interface. Connectors/ports may contain reference to the interface documents if applicable. Ports may be structured as appropriate to manage and structure the information. Note: more than one IBD focused on different areas of interest may be used in oder to keep the view comprehensive. Depending on the Stakeholder concerns the item exchange information might be suppressed.

A tabular format listing the identified interfaces of the soi (ports), referencing interface definitions (port types) ,connections (connector) to system context elements, and information exchange (item flows) conveyed over these connections. It is advised to have multiple tables focusing on certain aspects to keep the view comprehensive, e.g. table focusing on contexts or on certain interface partners.

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
Logical ConnectionSpecifies the connection of two interaction points on Logical Level. Note: Connections between logical components indicate that item flows are passed from one output of a source component to one or more inputs of target components.
LIPapplyingToLETSpecifies the fact that a Logical Interaction Point applies to a Logical Element.
Logical Interaction PointSpecifies the existence of an interaction point on Logical Level.
Logical Item ExchangeSpecifies the exchange that is to take place on a connection of two interaction points on Logical Level.
LIPapplyingToLCESpecifies the fact that a Logical Interaction Point applies to a Logical Context Element.
Logical Interaction Point DefinitionSpecifies the exchange capabilities of an interaction point on Logical Level.
Logical SOI RoleSpecifies the fact that a Logical Context SOI exists in a given Logical System Context.
Logical System ContextSpecifies the fact that a System Context for a System of Interest is defined on Logical Level.
Logical Context Element RoleSpecifies the fact that a Logical Context Element exists in a given Logical System Context.

Realization of exposed Concepts

The Diagram shows the realization of exposed concepts.

The Table shows the realization of exposed concepts.

Required Viewpoints

Example