Abstraction level
Implementation
Use Case Tasks
· Specify timing information according to AUTOSAR 4.0.3 standard
Covered aspect
The SystemDesk Timing Extension Editor (SDTEE) allows specifying the timing
information as described by the AUTOSAR 4.0.3 timing extension standard. The timing information can be specified at
various abstraction layers, i.e., Vfb timing, Swc timing, System timing, Bsw Module timing, and Ecu
Timing.
Algorithm
Manually entering of timing information linked with AUTOSAR system
model
Inputs
Vfb and Swc timings only require software architecture in SystemDesk. For System, Bsw Module and Ecu Timings require complete system
design model.
Particular constraints on inputs
The defined model in SystemDesk must
comply with AUTOSAR 3.x standard in order to specify the system timing information **.
The timing information available in EAST-ADL design model must firstly be transformed
manually to meet the AUTOSAR 4.0.3 timing extensions. The transformed timing information can further be decomposed
using SDTEE.
**Since the particular tool is a prototype, therefore at the moment can be used with
SystemDesk 3.1.
Preparation of input
Load AUTOSAR system design in SystemDesk
i.e.,*.sdp file, workspace
Invocation of the algorithm
Open SystemDeck Timing Extension Editor
from SystemDesk “View” menu to specify the timing events, event chains, and
constraints (requirements and guarantees), at various abstraction layers, i.e., Vfb timing, Swc timing, System timing,
Bsw Module timing, and Ecu Timing, in the design model
Outputs
AUTOSAR Timing Extension file
i.e.,*.arxml file, listing the overall system timing information as specified by AUTOSAR
4.0.3
Visualization of results
By selecting the entries, i.e., event or event chain, in SystemDesk Timing Extension Editor tree view the SystemDesk highlights the corresponding port or path in its graphical user
interface (the particular feature is under development)
|