wiki:features
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
wiki:features [2012/10/07 20:53] – created pmueller | wiki:features [2023/03/08 10:14] (current) – webmin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Features ====== | + | ~~NOTOC~~ |
- | ===== Overview ===== | + | |
- | A statechart (or state machine) diagram shows the dynamic behavior of an application. It is a graph of states and transitions that describe the response to events depending on the current state that it is in. State machines are used for decades in hardware design. And during the last years also more and more in the area of software development. Especially in the embedded real-time domain the use of statecharts is popular because the behavior of applications and/or devices in this domain can be often described very well with statecharts. The paper of D. Harel „Statecharts: | + | |
+ | {{htmlmetatags> | ||
+ | metatag-keywords=(flat machines, hierarchical machines, signal events, time events, choice, simulation) | ||
+ | metatag-description=(Command line code generator specifically for embedded real-time domain using your already existing UML tool)}} | ||
- | <<< | ||
+ | ====== Features of the Sinelabore state machine code generator ====== | ||
+ | A state machine diagram (or state chart) shows the dynamic behaviour of an application. It is a graph of states and transitions that describe the response to events depending on the current state that it is in. State machines are used for decades in hardware design. And during the last years also more and more in the area of software development. Especially in the embedded real-time domain the use of statecharts is popular because the behavior of applications and/or devices in this domain can be often described very well with statecharts. The paper of D. Harel „Statecharts: | ||
- | An important aspect of statecharts is that the design can be directly transformed into executable code. This means that there is no break between the design and the implementation. This is all the more important if the device under development has to be developed e.g. according to IEC61508. Please note that the code-generator itself is not certified in any way. It is your responsibility to verify and validate that the generated code fulfills your needs! | ||
- | SinelaboreRT was built especially for embedded real-time developers. It focuses on just one task: code generation from state-chart | + | {{: |
+ | |||
+ | |||
+ | An important aspect of state diagrams is that the design can be directly transformed into executable code. This means that there is no break between the design and the implementation. This is all the more important if the device under development has to be developed e.g. according to IEC61508. Please note that the code-generator itself is not certified in any way. It is your responsibility to verify and validate that the generated code fulfills your needs! | ||
+ | |||
+ | SinelaboreRT was built especially for embedded real-time developers. It focuses on just one task: code generation from state diagrams. A command line tool and a configuration file is all what is needed. | ||
The generated code is based on nested switch/case and if/ | The generated code is based on nested switch/case and if/ | ||
Line 15: | Line 21: | ||
SinelaboreRT does not force you in any way on how you design your system. Therefore it is no problem to use the generated code in the context of a real-time operating system or within an interrupt service routine or in a foreground / background system. The generation process can be influenced to meet specific needs. | SinelaboreRT does not force you in any way on how you design your system. Therefore it is no problem to use the generated code in the context of a real-time operating system or within an interrupt service routine or in a foreground / background system. The generation process can be influenced to meet specific needs. | ||
- | How does SinelaboreRT work? From a state-chart design file created with the Cadifra UML editor, Enterprise Architect, UModel or Magic Draw the code-generator generates the complete statemachine implementation. For an example design file called oven.cdd the command line looks like java -jar codegen.jar -p CADIFRA -o oven.cdd. As an result files will be generated: | + | How does SinelaboreRT work? From a state-chart design file created with the Cadifra UML editor, Enterprise Architect, UModel or Magic Draw the code-generator generates the complete statemachine implementation. For an example design file called oven.cdd the command line looks like |
+ | |||
+ | <code bash> | ||
+ | java -cp " | ||
+ | </ | ||
+ | |||
+ | As an result files will be generated: | ||
* oven.c implements the state-machine as graphically specified in the oven.cdd file | * oven.c implements the state-machine as graphically specified in the oven.cdd file | ||
Line 25: | Line 38: | ||
- | ===== Supported State Chart Elements ===== | + | ===== Supported State Diagram Design |
- | Hierarchical state definition: State machines can be hierarchical or flat. A state with sub-states is called a hierarchical state-machine. States can have entry code that is always executed if a state is entered. Exit code is executed whenever the state is left. A state can also have action code. The action code is executed whenever the state is active just before event transitions are evaluated. | + | **Hierarchical state definition**: State machines can be hierarchical or flat. A state with sub-states is called a hierarchical state-machine. States can have entry code that is always executed if a state is entered. Exit code is executed whenever the state is left. A state can also have action code. The action code is executed whenever the state is active just before event transitions are evaluated. |
+ | |||
+ | ** Regions **: Regions allow to model parallel behavior within the same state machine diagram. The benefit | ||
**Transitions**: | **Transitions**: | ||
Line 37: | Line 52: | ||
**History States**: | **History States**: | ||
- | **Interactive Test and Simulation**: | + | **Interactive Test and Simulation**: |
+ | |||
+ | {{: | ||
- | {{: | ||
**Debugging / Trace Support**: In the *_dbg.h file two helper functions are provided that are useful for debugging state machines. The function *_GetNameByState(id) returns the name of the state the function *_GetNameByEvent(id) returns the name of an event each identified by its id. Trace statements can be automatically added to the machine. This allows to follow the flow of events. | **Debugging / Trace Support**: In the *_dbg.h file two helper functions are provided that are useful for debugging state machines. The function *_GetNameByState(id) returns the name of the state the function *_GetNameByEvent(id) returns the name of an event each identified by its id. Trace statements can be automatically added to the machine. This allows to follow the flow of events. | ||
- | **Integrated State-Diagram Editor**: Using the command line flag ‘-E’ brings up the integrated state diagram editor. It provides an efficient tree based entry method. The graphical representation is created automatically. So you can fully focus on the modeling task. | + | **Integrated State-Diagram Editor**: Using the command line flag '' |
- | [[wiki: | + | [[wiki: |
wiki/features.1349636011.txt.gz · Last modified: 2012/10/07 20:53 by pmueller