Interface Management with MBSE

Whitepaper by Joseph D. Gaskell

07 Feb 2020
 Interface Management with MBSE Doc Number: TBD
Revision: Draft

Revision History

Revision Date Change Description/Rationale

- 07-Feb-2020 Initial Release

Author: Joseph D. Gaskell Page |2 Distribution Statement TBD

 Interface Management with MBSE Doc Number: TBD
Revision: Draft

Table of Contents
Introduction .................................................................................................................................................. 4
1.1 Scope ............................................................................................................................................. 4
1.2 Objective ....................................................................................................................................... 4
2 Process .................................................................................................................................................. 4
2.1 Inputs from Concept Development .............................................................................................. 5
2.2 Identify IF ...................................................................................................................................... 5
2.2.1 Definition of Interfaces ......................................................................................................... 5
2.2.2 Complexity ............................................................................................................................ 6
2.2.3 Interface Index (Mad Libs) .................................................................................................... 6
2.3 IF design: ....................................................................................................................................... 7
2.4 IF management: ............................................................................................................................ 7
3 References ............................................................................................................................................ 8

Author: Joseph D. Gaskell Page |3 Distribution Statement TBD

 Interface Management with MBSE Doc Number: TBD
Revision: Draft

Introduction
Interfaces are the functional and physical connections at the boundaries of systems that are designed to
interoperate with other systems. The practice of Interface Management is related to requirements and
configuration management, but it is applied more specifically to the management of interfaces as a
subcomponent of systems [1]. Implementing an interface management process on a project streamlines
communication, identifies critical interfaces, and monitors ongoing work progress while mitigating risks
[2]. This white paper defines a developed method for implementing interface management and
development within a Model Based System Engineering Environment (MBSEE). Utilizing a MBSEE
improves visibility and control over the complexity commonly associated with interfaces. Additionally,
when multiple systems exist within the MBSEE, updates and impacts to interfaces are more accessible to
all stakeholders.

1.1 Scope
The focus of this paper is on the managements and control of interfaces between Systems of Systems,
but could also be applied to interfaces within a system. However, this document does not include
anything relating to the definition or design of interfaces.

The information is focused towards the activities of the Systems Engineering Authority (SEA), but is also
informative the Design Agent for impacted systems.

1.2 Objective
This paper will provide a defined high-level process for interface management for the SEA within a
MBSEE. Additionally, the process will include a description of various tools developed to enable
interface management.

2 Process

Figure 2-1: Systems Engineering "Vee"

Author: Joseph D. Gaskell Page |4 Distribution Statement TBD

 Interface Management with MBSE Doc Number: TBD
Revision: Draft

Interface management takes place throughout the system engineering process. The concept
development phase provides the outline of the system that determine where any inputs exist between
the system and others. These identified interfaces are captured as a part of the requirements
engineering / definition phase as system requirements. In the process of building the system
architecture, the interfaces are built into the functional and physical aspect of the architecture. If
utilizing a SysML based Descriptive System Model (DSM), these interfaces are captured as ports within
the DSM. The system architecture develops the interface index for system design and development. This
index is used as the foundation for multiple interfacing systems to appropriately designing the system to
interface with external systems as intended. The designed interfaces are then associated to interface
index for further management. As the system progresses through integration, implementation, Test and
Evaluation, and finally Transition, Operation and Maintenance, the interface index is used to control the
interface design. Should an issue be identified or a modification required, the interface index is
referenced and updated to show impacted systems and stakeholders as well as the status and approvals
for any input.

2.1 Inputs from Concept Development

During concept development, from the Concept of Operations (CONOPS), the boundaries of the system
are defined by the SEA, with inputs from system stakeholders. Additionally, any other systems or
entities that the system being developed will interact with are identified. Upon their identification by
the SEA, these interactions are captured in the DSM as Use Case definitions and block diagrams of the
system’s context and domains.

2.2 Identify IF
Using the CONOPs as a source, the SEA begins to identify the system interfaces. The SEA interprets the
CONOPs to identify where the system is interacting with other systems. These instances indicate an
interface.

In modeling terms, the Use Case definitions will include activities and activity diagrams. In these
diagrams functions of systems are placed into swimlanes representing their respective system. Anytime
there is an “object flow” that crosses between swimlanes, an interface exists. Within the same DSM,
these interfaces are capture on an internal block diagram using various connectors and ports. The
Interface index, defined using the meta-model developed by STS LLC, combines all interfaces into a table
that provides an easy to interpret summary of details for each interface.

2.2.1 Definition of Interfaces

Each interface, upon being captured in the model is also includes a defined form. These forms assisting
in understanding the kind of interface being captured. These forms help designers and stakeholders set
expectations on what the intended functionality of the interface is. These forms are categorized into the
following four definitions;

1. Physical: Two parts are in direct physical connection if they touch each other, have a reversible
connection between them, or are permanently connected to each other. Typically defined on a
Drawing or physical model.
2. Energy: Energy flow is present if there is a net exchange of work between two components,
usually paired with a physical connection

Author: Joseph D. Gaskell Page |5 Distribution Statement TBD

 Interface Management with MBSE Doc Number: TBD
Revision: Draft

3. Mass: Mass flow implies that matter is being exchanged between two elements, typically imply
a physical connection as well.
4. Information: The two sides communicated sets of data between them. This communication is
always directed.

2.2.2 Complexity
Another aspect of capturing the interface is understanding its level of complexity. This represents the
overall impact the interface has on the systems functionality and design. By clearly identify a complexity
level, the interface can have the right amount of control placed on it to mitigate risk and improve
communication of design. There are three levels of complexity and they are as follows;

1. Complex: A complex interface has multiple other systems or functions interacting together. The
interface design is controlled by each interacting system and will require review from all
impacted stakeholders before changing or modifying. These interfaces require heavy control to
insure requirements are not violated and interfacing systems are not rendered incompatible.
2. Driving: A Driving interface has a master/slave relationship between them. Typically indicative of
a higher importance or driving system interacting with a piece of support equipment. At this
level of complexity the master side of the interface has control over the interface design, though
the design should still be communicated with the opposite sides of the interface to understand
impacts.
3. Direct: A direct interface has no control as it is typically restrained to the inherent properties of
the system. The easiest example is how the system may interface with its environmental
conditions, such as ambient temperatures, sunlight and such.

2.2.3 Interface Index (Mad Libs)

The result of identifying and capturing the interfaces within the DSM will result in an overall interface
index. This index, shown below, displays a summary of key attributes of identified interfaces.

Figure 2-2: Sample Interface Index

1. IF-ID: Unique identification number associated with the interface
2. Name: Given name for interface
3. Active Hyperlink: This attribute is a direct hyperlink to the definition of the designed interface. It
is worth noting that interfaces are unlikely to be defined in detail within the DSM, and this link
provides a method to relate the mode to the detailed information of the interface.
4. IF Form: This is the Interface Form as described in section 2.2.1.
5. Complexity: This is the Interface Complexity described in section 2.2.2
6. Status: The status is used to determine the maturity of the interface as well as if the interface
has an issue or is being modified.
7. Interfacing parts: This column provides a list of any parts that are on the opposite side of the
defined interface. In other words, any other systems or parts that interface with this interface.

Author: Joseph D. Gaskell Page |6 Distribution Statement TBD

 Interface Management with MBSE Doc Number: TBD
Revision: Draft

8. Operations Impact: This column provides a 1st degree look into how the interface is associated
with the system functions and behaviors. This topic was touched on in section 2.2, however, the
model is queried to automatically populate this column with the appropriate behaviors. This
information proves useful for understanding impacts of altering or modifying any interface.
9. Owning Parts: This column provides the system owning the interface.

2.3 IF design:
Upon identifying all of the interfaces of the system, or system of systems, the SEA provides the interface
index to the design agents. Each design agent is responsible for the development and design of all
owned interfaces. Each interface is provided to SEA for review and approval. In most cases the review of
the interface will make a request for input from all stakeholders to ensure compatibility with interfacing
system.

2.4 IF management:
As the design goes through integration, implementation, Test and Evaluation and beyond to operation
the interface index is the centralized point of information used to manage the interface. As stated
before any issues or required modifications identified will use the index.

Owners of an interface are those who are the design agent of the owning part, and any impacted
stakeholders are those who are the design agent for the interfacing parts. In addition to requesting any
impacted party for assessment impacts, any behaviors in identified in the Operations Impact should be
investigated to assess the total impact the interface modification or issue has on the system.

Additionally, the status of the each interface can be tracked to inform all stakeholders of its current
condition.

Author: Joseph D. Gaskell Page |7 Distribution Statement TBD

 Interface Management with MBSE Doc Number: TBD
Revision: Draft

3 References
1. Interface Management. https://www.mitre.org/publications/systems-engineering-guide/se-lifecycle-
building-blocks/systems-integration/interface-managemen

2. Interface Management. ThePD - https://www.theprojectdefinition.com/interface-management/

Author: Joseph D. Gaskell Page |8 Distribution Statement TBD