Systems engineering interfaces: A model based approach

Abstract

Abstract-The engineering of interfaces is a critical function of the discipline of Systems Engineering. Included in interface engineering are instances of interaction. Interfaces provide the specifications of the relevant properties of a system or component that can be connected to other systems or components while instances of interaction are identified in order to specify the actual integration to other systems or components. Current Systems Engineering practices rely on a variety of documents and diagrams to describe interface specifications and instances of interaction. The SysML[1] specification provides a precise model based representation for interfaces and interface instance integration. This paper will describe interface engineering as implemented by the Operations Revitalization Task using SysML, starting with a generic case and culminating with a focus on a Flight System to Ground Interaction. The reusability of the interface engineering approach presented as well as its extensibility to more complex interfaces and interactions will be shown. Model-derived tables will support the case studies shown and are examples of model-based documentation products.

Interface modeling for product‐service system integration

“…According to ISO/IEC 2382:2015, the interface is the “shared boundary between two functional units, defined by various characteristics of the functions, physical interconnections, signal exchanges, and other characteristics.” In SoS, the interaction logic is based on defining the details of interactions between the systems’ components. The global view is that system entities (internal and external) have software, hardware, and human interaction . In this matter, the logical sequence of functions (flows and interfaces) is analyzed by the functional view of the system to define the blocks of the final system architecture .…”

“…In this matter, the logical sequence of functions (flows and interfaces) is analyzed by the functional view of the system to define the blocks of the final system architecture . The interaction can “connect to other operational entities according to its interaction specification.” The proposed model for interface adopted the same logic from SE and the enumerations are detailed with the tangible and intangible elements of PSS (Figure ).…”

“…These specifications describe the components interacting and the way they interact with interface types. They also describe how an operational entity (system, organization, or service) can affect another operational entity when a connection exists . The interaction is an “instance of an operational entity” (system, organization, or services) interface .…”

“…The global view is that system entities (internal and external) have software, hardware, and human interaction. 62 In this matter, the logical sequence of functions (flows and interfaces) is analyzed by the functional view of the system to define the blocks of the final system architecture. 63 The interaction can "connect to other operational entities according to its interaction specification."…”

“…63 The interaction can "connect to other operational entities according to its interaction specification." 62 The proposed model for interface adopted the same logic from SE and the enumerations are detailed with the tangible and intangible elements of PSS ( Figure 3).…”