ARText - Timing LanguageThe timing language lets you model timing constraints for AUTOSAR systems. You can benefit from the easy syntax to create timing artifacts, which completely conforms to the AUTOSAR standard as of R4.0.
The language focuses on the AUTOSAR Timing Extensions, and supports the following features:
- Different Timing Exentsions: SWC, VFB, System or ECU
- VFB Timing Events
- Internal Behavior Timing Events
- Flexray Cycle Start Timing Event
- Frame Timing Events
- Execution Order Timing Constraint
- Offset Timing Constraint
- Latency Timing Constraint
- Triggering Timing Constraint
- Synchronization Timing Constraint
- and more...
Unidirectional transformationTiming artifacts defined with the timing language can be converted to AUTOSAR R4.0 XML.
Succesfully used in practiceThe language is successfully used in projects today to define timing constraints for AUTOSAR systems.
Syntax examplesHere are some examples of the timing language for some main timing model elements:
Import - Import statements make the specification easier to read, since model elements can be referenced without qualifying them with the fully qualified name.
Scope - Select the type of Timing Extension (e.g. System Timing) and define the respective scope.
Events - Easily and quickly define timing events.
Event Chains - Define event chains by relating events.
Timing Constraints - Constrain the timing behavior of AUTOSAR systems.