Vocabulary Flashcards
Component State Persistence
A portable Components Segment, Platform-Specific Services Segment, or Transport Services Segment Unit of Conformance internal state saved to a Data Store.
A set of related models, specifications, and governance policies with the primary purpose of providing an unambiguous description of the exchanged data and an
Data Architecture
A language specified as an EMOF metamodel or OCL constraints used to capture data element syntax and semantics
Data Model Language
PCS
Portable Components Segment
TSS
Transport Services Segment
PSSS
Platform-Specific Services Segment
IOSS
Input/Output Services Segment
OSS
Operating System Segment
Name the Five Segments of the FACE Reference Architecture
- Portable Component Segment
- Transport Services Segment
- Platform Specific Services Segment
- Operating System Segment
- Input/Output Standardized Interfaces
A segment where the normalization of vendor-supplied interface hardware device drivers occurs.
I/O Service Segment
A segment where normalization of vendor-supplied interface hardware device drivers occurs.
I/O Services Segment
The segment where foundational system services used by all other segment and vendor-supplied code reside
Operating System Segment
Sub-segment where management of data and translation between platform-unique ICDs and the FACE Data Model occurs
Platform-Specific Common Services
Sub-segment where management of data and translation between platform-unique ICDs and the FACE Data Model occurs.
Platform-Specific Device Services
Platform-Specific Services Segment
Segment comprised of sub-segments including Platform-Specific Common Services, Platform Specific Device Services, and Platform-Specific Graphic Services.
What are the three sub-segments of the Platform-Specific Services Segment?
- Platform-Specific Common Services
- Platform-Specific Device Services
- Platform-Specific Graphic Services
Portable Components Segment
A segment where software components providing capabilities and/or business logic reside.
Security Transformation
Transformation of data to meet system-level security controls.
Security Transformation Boundary
A boundary between a software component function and the Security Transformation algorithm. This boundary may exist at a FACE Interface, or internal to a Unit of Conformance that contains its own Security Transformation.
Shared Data Model
An instance of a Data Model whose purpose is to define the commonly used item and to serve as a basis for all other data models
TPM enables interoperability between Transport services Domains providing connectivity to physical transport (eg, TCP, UDP, RTPS, IIOP, Queues, IPC, IP, shared memory) not natively supported by a TSS.
Transport Protocol Module
A Segment that abstracts transport mechanisms and data access from software components facilitating integration into disparate architectures and platforms using different transports.
Transport Services Segment
The ability to exchange and use information between Transport Services Domains without re-engineering the TSS UoCs in either TSS Domain. Configuration and/or access to additional TSS capabilities may be required.
TS to TS Interoperability
Unit of Conformance
A software component or domain-specific