Systems Interface

Neelima Satyam D
 Systems Interface
One of the crucial factors of system
success is determined by what
happens at its internal and external
interfaces.

The most elegant algorithms,

equations, and decision logic, but if
the system does not perform at its
interfaces, the elegance is of no value.
 Systems Interface
interface?
The functional/logical relationships
and physical characteristics required
to exist at a SYSTEM or entity
boundary with its OPERATING
ENVIRONMENT that enable the entity
to provide a mission capability.

purpose of an interface?
Human-Machine Interface The actions, reactions,
and interactions between humans and other system
components.

Interchangeability The ability to interchange,

without restriction, like equipments or portions
thereof in manufacture, maintenance, or operation.
Interface Control ?

(1)identifying all functional and physical

characteristics relevant to the interfacing of two or
more items provided by one or more
organizations; and

(2)ensuring that proposed changes to these

characteristics are evaluated and approved prior
to implementation.
Interface Device An item which provides mechanical and
electrical connections and any signal conditioning required
between the equipment and the unit under test (UUT); also
known as an interface test adapter or interface adapter
unit.

Interface Ownership The assignment of accountability to

an individual, team, or organization regarding the definition,
specification, development, control, operation, and support
of an interface.

Interoperability The ability of two or more systems or

components to exchange information and to use the
information that has been exchanged.
 Peer level Interactions SYSTEM OF INTEREST (SOI)
interactionsnamely MISSION SYSTEM and SUPPORT
SYSTEMwith external systems in the OPERATING
ENVIRONMENT. For analytical purposes, we aggregate these
systems into a single entity abstraction referred to as the
PHYSICAL ENVIRONMENT SYSTEMS domain.

Point-to-Point An interface configuration that

characterizes the physical connectivity between two points,
typically accomplished via dedicated, direct line.
 Systems Interface
1. The composition of the system architecture.
2. How those elements interact with each other and
their OPERATING ENVIRONMENT.

You can develop the most innovative devices, computers,

and algorithms. Yet, if those innovations are unable to
reliably interact and interoperate with their OPERATING
ENVIRONMENT when required, they may be of limited or
no value to the entity or SYSTEM.

Interfaces occur between combinations of two or more

system elementssuch as EQUIPMENT, PERSONNEL, and
FACILITIESor between entities within system element
levels of abstractions.
Interface Purposes
The purpose of an interface is to associate or physically connect a
SYSTEM, PRODUCT,
SUBSYSTEM, ASSEMBLY, SUBASSEMBLY, or PART level component to
other components
within its OPERATING ENVIRONMENT. A component may associate or
connect to several
components; however, each linkage represents a single interface. If a
component has multiple interfaces, the performance of that interface
may have an influence or impact on the others.
Interface Purposes

The purpose stated above is a very broad description of WHY an

interface exists. The question is: HOW does an interface accomplish
this? An interface has at least one or more objectives, depending on the
components application. Typical interface objectives include the
following:

Physically link or bind two or more system elements or entities.

Adapt one or more incompatible system elements or entities.

Buffer the effects of incompatible system elements.

Leverage human capabilities.

Restrain system element or its usage.

 InteroperabilityThe Ultimate Interface
Challenge
The ultimate success of any interface resides in its capability to
interact with friendly and hostile systems in its intended
OPERATING ENVIRONMENT as envisioned by the User, specified
by the Acquirer, and designed by the System Developer.

Interfaces exhibit three types of operation: active, passive, or

active/passive

Active interfaces interact with external systems or components

in a friendly, benign, or cooperative manner.
Radio stations, as active on the air systems, radiate signals at
a designated frequency via patterns to specific areas for
coverage.
 Passive interface interactions with external components
simply receive or accept data without responding. Ex: A car
radio

Active/passive interfaces perform under the control of

transmitters or receivers. Ex: A two-way walkie-talkie
LOGICAL AND PHYSICAL
INTERFACES
1. WHO interacts with WHOM?

2. WHAT is transferred and translated?

3. WHEN does the transference or translation

occur?

4. Under WHAT conditions?

Then, we translate the logical/functional connectivity

into a physical interface that represents HOW and
WHERE the interface will be implemented.

Analytically, system interfaces provide the mechanism

for point-to-point connectivity.
 Logical interfaces Represent a direct or
indirect association or relationship
between two entities.
1. WHOPoint Acommunicates with WHOM
Point B.
2. Under WHAT scenarios and conditions the
communications occur.
3. WHEN the communications occur.

Logical interfaces are referred to as

generalized interfaces.
 Physical interfaces represent physical
interactions between two interfacing
entities. Physical interfaces express
HOW devices or components (boxes,
wires, etc.) will be configured to
enable Point A to communicate with
Point B. Physical interfaces are
referred to as specialized interfaces
because of their dependency on
specific mechanisms (electronics,
optics,etc.) to realize the interface.
The preceding discussion highlighted two levels of
connectivity. This is an important point, especially from a
system design perspective involving humans. Engineers
have a strong tendency to jump to defining the physical
interface BEFORE anyone has decided WHAT the interface
is to accomplish. Therefore, you must:

1. Identify which system elements or entities must

associate or interact.

2. Understand WHY they need to connect.

3. Determine WHEN the associations or interactions

occur.
 INTERFACE METHODOLOGY
The preceding discussions enable SEs to establish a basic
methodology for identifying and characterizing interfaces.

Step 1: Identify logical interfaces. When systems are

designed, logical interfaces enable us to acknowledge that
an association or relationship exists. Therefore, the
interface becomes a logical means of expression that
enables us to characterize WHAT the interface is required
to accomplish.

Step 2: Identify and define physical interfaces. The

physical implementation of a logical or generalized
interface requires selection from a range of candidate
solutions subject to technical, technology, cost, schedule,
and risk constraints. This being the case, SEs typically
conduct one or more trade studies to select the most
appropriate implementation.
 PHYSICAL INTERFACE TYPES
Physical interfaces occur in mechanical, electrical,
optical, acoustical, natural environment, chemical,
and biological forms, and as combinations of these
forms. For all these types of physical interfaces there are
specialized solutions.

Mechanical Interfaces

Mechanical interfaces consist of boundaries that exist

between two physical objects and include
characterizations such as function, form, and fit.
Characterizations include:
1.Material Properties Composition;
2. Dimensional Properties Length, width, and depth;
mass properties such as weight, density, and shape;
Electrical Interfaces

Electrical interfaces consist of direct electrical or electronic

connections as well as electromagnetic transmission in free air
space. Attributes and properties include voltages, current,
resistance, inductance, capacitance, grounding, shielding,
attenuation, and transmission delays.

Optical Interfaces
Optical interfaces consist of the transmission and/or receipt of
visible and invisible wavelengths of light. Attributes and
properties include intensity, frequency, special ranges,
resolution, distortion, contrast, reflection, refraction, filtering,
modulation, attenuation, and polarization.

Acoustical Interfaces
Acoustical interfaces consist of the creation, transmission, and
receipt of frequencies that may be audible or inaudible to
humans. Attributes and properties include volume, frequency,
modulation, and attenuation.
Interfaces allow us to establish logical or physical
relationships between system elements via a common,
compatible, and interoperable boundary. If you analyze the
most common types of interfaces are

1) standard, modular interfaces and

2) unique, dedicated interfaces

Lets define the context of each type.

Standard, Modular Interfaces System developers typically

agree to employ a modular, interchangeable interface
approach that complies with a standard.
 Unique, Dedicated Interfaces

Where standard interfaces may not be available or

adequate due to the uniqueness of the interface, SE
designers may elect to create a unique, dedicated
interface design for the sole purpose limiting
compatibility with other system elements or entities.
Examples include special form factors and encryption
that make the interface unique.
 ELECTRONIC DATA INTERFACES
When the Users logical interfaces are identified in the SYSTEM
or entity architecture, one of the first decisions is to determine
HOW the interface is to be implemented. Key questions include:

1. Does each interface require discrete inputs and

outputs?
2. WHAT function does the interface perform (data
entry/output, event driven interrupt, etc.)?
3. Are the data periodic (i.e., synchronous or
asynchronous)?
4. WHAT is the quantity of data to be transmitted or
received?
5. WHAT are the time constraints for transmitting or
receiving the data?

Electronic data communications mechanisms employ analog or

digital techniques to communicate information.

Analog Data Communications

 Digital Data Communications
Digital mechanisms include synchronous and
asynchronous bipolar signals that employ specific
transmission protocols to encapsulate encoded
information content. Digital data communications consists
of three basic types of data formats: discrete, serial, or
parallel.

Discrete Data Communications.

Discrete data consist of dedicated, independent instances
of static ON or OFF data that enable a device such as a
computer to monitor the state or status condition(s) or
initiate actions by remote devices. Digital discrete data
represent electronic representations for various conditions
or statessuch as ON/OFF, INITIATED, COMPLETE, and
OPEN/CLOSED.
Parallel Data Communications. Some systems require
high-speed communications between electrical devices.
Where this is the case, parallel data communications
mechanisms may be employed to improve SYSTEM
performance by simultaneously transmitting synchronous
data
simultaneously over discrete lines. Consider the following
example:

Parallel data communications mechanisms may increase

hardware component counts, development and unit costs,
and risks. In these cases, performance must be traded off
against cost and risk.
Serial Data Communications.
Some systems require the transmission of data to and
from external systems at rates that can be accomplished
using serial data communications bandwidths.

Where applicable, serial data communication approaches

minimize parts counts, thereby affecting PC board
layouts, weight, or complexity.

Serial data communications mechanisms may be

synchronousmeaning periodicor asynchronous,
depending on the application. Serial data
communications typically conform to a number of
standards such as RS-232, RS-422 and Ethernet.
LIMITING ACCESS TO SYSTEM
INTERFACES
1. authorized log-on accounts,
2. data encryption devices and
methods,
3. floating access keys,
4. personal ID cards,
5. personal ID scanners, and
6. levels of need to know
access.
 INTERFACE PERFORMANCE AND
INTEGRITY

Interfaces, as an entry point or portal into a system, are

vulnerable to threats and failures, both internally and
externally. Depending on the extent of the physical
interface interaction and resulting damage or failure, the
interface capability or performance may be limited or
terminated.
Interface Failure

There are differing contexts regarding WHAT constitutes

an interface failure including degrees of failure. An
interface might be considered failed if it ceases to provide
the required capability at a specified level of performance
when required as part of an overall system mission.
Interface failures may or may not jeopardize a system
mission.

Consequences of an Interface Failure

Interface Failures
Interfaces fail in a number of ways. In general, physical
interfaces can fail in at least four types of scenarios: 1)
disruption, 2) intrusion, 3) stress loading, and 4) physical
destruction.

Disruptions can be created by acts of nature, component

reliability, poor quality work, animals, lack of proper
maintenance, and sabotage.

Examples include:
1) failed components, 2) cable disconnects; 3) loss of
power,
4) poor data transmission; 5) lack of security; 6)
mechanical wear, compression, tension, friction, shock,
and vibration; 7) optical attenuation and scattering; and
8) signal blocking.
 Intrusion include:
1) unauthorized electromagnetic environment effects
(E3);
2) data capture through monitoring, tapping, or listening;
and
3) injection of spurious signals.

Stress Loading includes the installation of devices that

load, impede, or degrade the quality or performance of
an interface.
Physical Attack includes physical threat contact by
accident or purposeful action by an external entity on
the system to inflict physical harm, damage, or
destruction to a SYSTEM, entity, or one of their
capabilities
Interface Vulnerabilities
Interface integrity can be compromised through
inherent design defects, errors, flaws, or vulnerabilities.
Interface integrity and vulnerability issues encompass
electrical, mechanical, chemical, optical, and
environmental aspects of interface design. Today most
awareness to interface vulnerability tends to focus on
secure voice and data transmissions, and network
firewalls.

Interface Latency
Interface latency is a critical issue for some systems,
especially if one interfacing element requires a response
within a specified time frame. As an SE, you will be
expected to lead the effort that determines and
specifies time constraints that must be placed on
interface responses. If time constraints are critical, what
is the allowable time budget that ensures the overall
system can meet its own time constraints.
Interface Failure Mitigation and Prevention

When you design system interfaces, there are a

number of approaches to mitigate the occurrence of
interface failures or results.
In general, the set of solutions have a broad range of
costs. SEs often focus exclusively on the hardware and
software aspects of the interface design.

As a natural starting point, hardware and software

reliability, availability, and maintainability (RAM), in
combination with failure modes and effects analysis
(FMEA), should be investigated. System operation
involves all of the system elements: PERSONNEL,
EQUIPMENT, and SUPPORT. The point is that there may
be combinations of system element actions or tactics
that allow you to optimize system performance while
reducing system cost.