This section provides a brief overview of the MC-3020 architecture components by describing the Mechanisms, Archetypes, Marks, Build Tools, and Diagnostic Tools that make up the product.
The mechanisms for MC-3020 are implemented as ANSI C source code. This code compiles at build time to provide support for:
collections
xtUML timer interfaces
The BridgePoint translation approach employs two different types of rule files, structural rule files and fragment generation rule files. Structural rule files produce the structure of the system (e.g. structure definitions, function definitions, state transition tables, etc.). Fragment generation rule files are used during the translation of the action language modeling the processing of the system.
MC-3020 provides the capability to direct the translation of the xtUML models by marking them to:
register xtUML and non-xtUML domains,
identify external entities as either xtUML or non-xtUML domains,
identify bridge objects for use by non-xtUML domains,
assign domain and system wide data type precisions,
tag initialization objects and objects to be excluded from translation,
establish limits to the extents of instance collections,
A detailed description of these capabilities is provided in Chapter 4, Marking
MC-3020 is shipped with a set of build tools implemented in the Eclipse IDE used to translate models and compile and link the resulting code.
After an application has been specified with Shlaer-Mellor xtUML models, MC-3020 provides the capability to translate those models into ANSI C source code. This source can be compiled, linked and located to produce an executable load image. This executable can be run on various targets. It can be converted into an Intel Hex format file or Motorola S-record format file for loading into an EPROM or flash memory.