Next: Primitive Implementation
Up: Component
Previous: WriteNext

Component Implementation

Description

The implementation of a component describes how it is constructed. Components have either primitive implementations, or composite implementations. A primitive implementation describes a component that is implemented by some source document that is external to UniCon (e.g., source code of a programming language, scripts of commands of an operating system shell, data in a file in the file system).

A composite implementation describes a configuration of components and connectors. This mechanism in UniCon allows system designers to progressively build larger subsystems from collections of smaller components or subsystems, or more abstract components from less abstract ones.

Syntax

The following is the syntax for a component implementation in UniCon:

  <component_implementation> :==
    <primitive_implementation>
    | <composite_implementation>

  <primitive_implementation> :==
    IMPLEMENTATION IS
      <property_list>
      <variant_list>
    END IMPLEMENTATION

  <variant> :==  VARIANT <identifier> IN "<filespec>"
      <property_list>
    END <identifier>

  <composite_implementation> :==
    IMPLEMENTATION IS
      <property_list>
      <composite_statement_list>
    END IMPLEMENTATION

  <composite_statement> :==
    <instantiation> 
    | <connection>
    | <bind>
    | <establish>

Next: Primitive Implementation
Up: Component
Previous: WriteNext

Comments? Mail the current maintainer of this page.

Author: Gregory Zelesnik

Last Modified: May 12, 1996