* Main page  * Automatic Code Generation  * Autocode Glossary  * Publications  * Curriculum Vitae  * Dissertation 

Autocode Glossary (Under Construction)

Last Update: 23/05/2007

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

* 

A

analog signal A signal that is continuous in time and value.
autocode Code generated by a (model-based) code generator.
* * 

B

behavior model A model that specifies the behavior of a function in a graphical way. State machines are typical examples of behavior models. These models are often used as a supplemented or alternative part for the requirements specification.
* * 

C

calibration The process of choosing values and parameters so that a model or algorithm properly represents the real-world situation being analyzed. Such values or parameters are also termed tunable system parameters.
code generator A tool that is capable to translate a graphical (software) model into executable code. In contrast to a compiler, the semantics of the source language is also determined by graphical layout information (e.g. position of states).
* * 

D

digital signal A signal that is discrete in time and value.
* * 

F

functional model An abstraction or graphical representation of an algorithm, which realizes a function as an executable program. Functional models are characteristically executable within specific development environments (e.g. Simulink or Stateflow) and are also termed executable specifications.
The term functional model is a generic term for physical model and implementation model.
* * 

I

implementation model A revision of a physical model (PM) with regard to implementation details. For example, function parts are distributed to different tasks. Furthermore, the floating-point arithmtic contained in the PM is adjusted to the arithmetic of the embedded system with its target processor. This means in particular that only fixed-point data types are used (e.g. int16), which are augmented with scaling information in order to keep imprecision in the representation of fixed-point numbers as low as possible (see also quantization error).

The implementation model contains all the information necessary for code generation!
* * 

M

model In the context of embebed automotive software, a model can be:
  • An abstraction of an algorithm, which realizes a function as an executable program. Such kind of model is also termed functional model.
  • An abstraction of the "reality" which interacts with the functional model. Such kind of model is also termed environment model or plant.
See also physical model and implementation model.
* * 

P

physical model Are conceptual models that are used to realize a functionality (e.g. control function) as specified in the requirements specification and describes the behavior of the functionality related to given input signals as well as internal or external events or states. Implementation details (e.g. data types, task structure) are often not considered and the description of the algorithms takes place through the use of floating-point arithmetic.

See also implementation model.
* * 
*  previous:  * * Automatic Code Generation  next:  * * Publications
* Main page  * Automatic Code Generation  * Autocode Glossary  * Publications  * Curriculum Vitae  * Dissertation 
© 1998-2007 Ingo Stürmer, www.ichmaschine.de (last update: 05/2007)