This glossary defines the most important technical terms and abbreviations used in the CORDET 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.
|An old name for the 'Control Framework' (one of the two software frameworks defined in the CORDET Project).
|A software program that can be deployed and run as a single executable.
|The process whereby a component-based application is constructed by configuring and linking individual components.
|Same as 'software component' below.
|A software framework that has software components as its building blocks.
|A computational resource that has memory and processing capabilities.
|A software framework covering on-board control systems, and in particular the Attitude and Orbit Control Subsystem. This is one of the two software frameworks defined in the CORDET Project.
|A widely used middleware infrastructure.
|A description of an abstract design solution for a recurrent design problem.
|The Data Handling Subsystem of satellites.
|A software framework for the DH subsystem (one of the two software frameworks defined in the CORDET Project).
|A shorthand for either 'family domain' or 'framework domain'.
|Domain Specific Language (a language that is created to describe applications or components in a very narrow domain).
|Document Type Definition. The DTD defines the legal building blocks of an XML document by defining the document structure with a list of legal elements and their legal combinations. Its purpose is similar to that of an XML Schema, although it is not as feature rich and the syntax is different.
|A modeling framework and code generation facility for building tools and other applications based on a structured data model.
|The set of systems whose implementation is supported by a system family.
|A characteristic of a system that is relevant to its users.
|A description of a set of features and their legal combinations.
|The set of applications whose implementation is supported by a software framework.
|The process whereby a software framework is adapted to the needs of a specific application within its domain.
|A property that can be expressed as a logical relationship among the variables that define the state of an application or system.
|A software engineering paradigm that promotes the automatic generation of an implementation from a set of specifications.
|A set of reusable and adaptable software assets to support the instantiation of systems within a certain target domain. In the CORDET project, a generic architecture consists of a system family, to model the non-functional aspects of systems in the architecture's target domain, and a set of software frameworks, to model their functional aspects. The objective of the CORDET Project is to define a generic architecture for satellite on-board systems.
|Graphical User Interface.
|An abstract specification of services to be provided by any concrete realisation of it.
|Java Native Interface, a mechanism for interfacing Java code with non-Java code.
|Java Virtual Machine.
|A property other than a functional property.
|Object Oriented Software Framework
|A software framework that uses inheritance and object composition as its chief adaptation mechanisms.
|The On-Board Software.
|Outside-the-Model Adaptability. An adaptability mechanism that is defined outside the UML2 model.
|A set of applications or systems that can be built from a pool of shared assets.
|Same as feature above.
|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 kind of product family where the shared assets are software components embedded within an architecture optimized for a certain domain.
|A group of independent but interrelated hardware and software elements comprising a unified whole.
|A kind of product family where the 'product' to be built using the reusable assets provided by the family is the architectural infrastructure (the 'middleware') of a complex system.
|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.
|A means for defining the structure, contents and semantics of XML documents. XML Schemas are written in an XML-based language called XSD.
|Within-the-Model Adaptability Mechanism. An adaptability mechanism that is defined within the UML2 model.