372
Glossary of Terms
source to enable or sustain the interactions necessary for a system.
The outputs of EMMI can be received by other objects and interact
with those objects.
Type 1 interactions: Type 1 interactions result from the complete absorption
of EMMI without external provocation, resulting only from the
nature and enactment of its internal mechanism. A type 1 interaction
is potentially receivable by objects, but is either not received, is
received and not recognizable as an accurate representation of the
sending object, or is received and the receiving object does not
respond to the sending object. Type 1 interactions are inhibited or
masked by physical, functional, or behavioral reasons (internal
or external to the receiving object). A type 1 interaction is initiated
from within. Type 1 interactions reflect the internal needs or
intentions of an entity, for example, the self-initiated requirements for
survival. Type 1 interactions are in response to internal processes, the
mechanically induced self-regulation for fulfilling basic needs.
Type 2 interactions: Type 2 interactions are sent and received. A type 2 interaction eliminates (or discharges or “sends”) EMMI due to some
external receipt of EMMI. Type 2 interactions are the responses to
external stimuli, the simultaneous or reflexive reactions based on
are capabilities within the entities structure.
Types of requirements: Requirements are either stated or unstated. Unstated
requirements are the result of not knowing (i.e., unanticipated or
unforeseen); or knowing but not incorporating. Misstated requirements result from an inadequate appreciation for relations or context,
and adequate appreciation, but with a different interpretation, or an
adequate appreciation, but with a different priority. Pretermitting
requirements are acknowledged, but unincorporated.
Use: Use is the putting of the product into service for a particular purpose.
The use of an object is the result of the building process and the functions that are enabled by design, by application, and by accident.
Validation: Validation is an assessment of the operational system that
exposes and quantifies the systems’ limitations. The intent of validation is to determine if the user’s needs are satisfied for different uses
(often referred to as scenarios). When the functions are provided, the
physical entities are adequate, and the user’s behaviors are as needed,
the product or service is deemed fit for the uses intended by the set
of requirements. The concept of validation suggests that requirements can be mapped into physical, functional, and behavioral
needs of key stakeholders. Validation is also the process of demonstrating the effectiveness of the new product or service. Validation
is  direct evidence that the new product or service meets the
requirements through its design, architecture, and implementation.
From the perspective of integration, validation is the confirmation
that integration had satisfactory results.