This glossary defines the most important technical terms and abbreviations used in the EODiSP project.
|A definition of the signature and semantics of a set of related operations without any implementation details.
|The Attitude and Orbit Control Subsystem of satellites.
|The process whereby a component-based application is constructed by configuring and linking individual components.
|A unit of binary reuse that exposes one or more interfaces and that is seen by its clients only in terms of these interfaces.
|A software framework that has components as its building blocks.
|A computational resource that has memory and processing capabilities.
|A widely used middleware infrastructure.
|Central RTI Component.
|A description of an abstract design solution for a common
|Domain Specific Language (a language that is created to describe applications or components in a very narrow domain).
|Document Type Definition. It defines the legal building blocks of an XML document. It defines the document structure with a list of legal elements. Its purpose is similar to the one of an XML Schema, although it is not as feature rich and the syntax is different.
|Eclipse Modeling Framework . A modeling framework and code generation facility for building tools and other applications based on a structured data model.
|EOSiSP Open and Distributed Simulation Environment. The set of applications that are used to configure and execute a simulation.
|The software framework provided by the EODiSP.
|The middleware selected for the EODiSP.
|An application that may be or is currently coupled with other software applications under a Federation Object Model Document Data (FDD) and a runtime infrastructure (RTI).
|A named set of federate applications and a common Federation Object Model (FOM) that are used as a whole to achieve some specific objective.
|The actual operation, over time, of a set of joined federates that are interconnected by a runtime infrastructure (RTI).
|Federation Object Model (FOM)
|A specification defining the information exchanged at runtime to achieve a given set of federation objectives. This includes object classes, object class attributes, interaction classes, interaction parameters, and other relevant information.
|The set of functionalities whose implementation is supported by the framework.
|The process whereby a framework is adapted to the needs of a specific application within its domain.
|A software engineering paradigm that promotes the automatic generation of an implementation from a set of specifications.
|Graphical User Interface. Allows the user to interact with an application through a graphical interface.
|High Level Architecture. A standard to provide a common architecture for distributed modeling and simulation. Available as IEEE standard 1516.
|This is a collective term that refers to the menu bar, the tool bar, and the context menu. It is used in the EODiSP GUI documentation.
|Internet Service Provider.
|Java Native Interface, a mechanism for interfacing Java code with non-Java code.
|Java Virtual Machine.
|A network infrastructure aimed at peer to peer (P2P) networks. The core is a set of specifications for which a Java and a C implementation is available.
|Local RTI Component
|The model owner is a person in charge of one or more simulation models. The model owner decides when to make his simulation models available to a simulation and when to terminate their availability. The model owner interacts with the EODiSP through a Model Manager Application.
|Object Oriented Framework
|A framework that uses inheritance and object composition as its chief adaptation mechanisms.
|The On-Board Software.
|Runtime Infrastructure (RTI)
|The software that provides common interface services during a High Level Architecture (HLA) federation execution for synchronizing and data exchange.
|Service Data Objects. SDO is based on the concept of disconnected data graphs supporting building of portable server applications.
|Simulation Manager Application
|A GUI-based environment. Through this environment, a simulation owner can perform the tasks to overall control a simulation. This includes the control of the configuration and tasks like start, stop or hold a simulation experiment.
|Simulation Model Application
|A GUI-based environment. Through this environment, a model owner can perform the tasks to overall control the models he is in charge of.
|Simulation Object Model (SOM)
|A specification of the types of information that an individual federate could provide to High Level Architecture (HLA) federations as well as the information that an individual federate can receive from other federates in HLA federations.
|A set of one or more simulation run executed in sequence with different configurations.
|This is the person who is in overall control of a complete simulation. The simulation owner decides how the simulation models should be configured and when a simulation should start and terminate. The simulation owner interacts with the EODiSP through the Simulation Manager Application.
|A piece of software that implements part of the functionalities required for an end-to-end simulation and that is delivered as a single unit.
|A single end-to-end simulation for one particular configuration of a set of simulation packages.
|A reusable artifact that captures the commonalities of a set of applications in a specific domain and provides reusable software building blocks to facilitate the instantiation of applications in that domain.
|Simulation Model Portability, a set of interfaces to support the development of simulation applications.
|A set of self-contained applications that are provided together with the EODiSP to assist users in off-line tasks to be performed prior to starting a simulation (such as the generation of wrappers to transform generic simulation packages into HLA-compliant models ready to be integrated in the EODiSP).
|Extensible Markup Language. XML documents consist (mainly) of text and tags, and the tags imply a tree structure upon the document. An XML document is said to be valid if it conforms to an XML Schema or a DTD.
|The XML Schema language is also referred to as XML Schema Definition (XSD). They provide a means for defining the structure, contents and semantics of XML documents. XML Schemas are written in XML.
|An implementation of the HLA runtime infrastructure (RTI).