1 / 4

UML-models, UPPAAL track

UML-models, UPPAAL track. B. Polgár, BME May 27, 2010, Oxford, MOGENTES Meeting. UML models in UPPAAL vs. AS track. UPPAAL specialities not support attributes of signals it is not trivial because of the reduced expressibility of the UPPAAL model language some efforts will be investigated

holt
Télécharger la présentation

UML-models, UPPAAL track

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML-models, UPPAAL track B. Polgár, BME May 27, 2010, Oxford, MOGENTES Meeting

  2. UML models in UPPAAL vs. AS track • UPPAAL specialities • not support attributes of signals • it is not trivial because of the reduced expressibility of the UPPAAL model language • some efforts will be investigated • state machines for environment classes receiving signals are needed • only variables can be observed directly, Operation calls or Signal receptions not • Stimuli shall be defined (which instance can get which signal event)

  3. FFA – CAS (AlarmSystem_6  AlarmSystem_7) • Track specific elements are added • Applied the SMTE profile • Stimulus classes added • Model extended with the "model with stimuli" stereotype • Observable properties are added to environment classes with setting its value in operations • Conceptual changes are performed • Replaced signal events "delta*" with corresponding time events • Superfluous elements are deleted • Removed unused time events • Removed receptions corresponding to deleted signal events • Removed two invalid transitions (probably a junction pseudostate was deleted and these transitions had no source or target respectively) • Some errors are fixed • Links between instance specifications replaced by slots • Syntax errors in AGSL code fragments fixed (missing semicolons added) • Some elements are renamed for better readability • Assigned meaningful names to remaining signal events • Assigned meaningful names to instance specifications

  4. PROL – State decoder model • Functionally complete for the points decoder • Other will be added later • Some minor changes needed for AS track • application of MOGENTES stereotypes • elimination of while loop in AGSL expressions • conversion of if statements in AGSL expressions to decisions in state machines • or support for if in AS track • Some other changes needed for UPPAAL track • conversion of signals with attributes to signal sets, where signal types holds possible values of attributes

More Related