1 / 24

The Play-Engine

The Play-Engine. Executable Visual Languages for System Development, Fall 2010. This lecture. The Play-Engine Play-In Installing Getting Started Tips & references Play-out Samples. The Play-Engine. The Play Engine tool developed in Wis by R. Marrely.

rex
Download Presentation

The Play-Engine

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. The Play-Engine Executable Visual Languages for System Development, Fall 2010

  2. This lecture • The Play-Engine • Play-In • Installing • Getting Started • Tips & references • Play-out • Samples Executable Visual Languages for System Development

  3. The Play-Engine • The Play Engine tool developed in Wis by R. Marrely. • Currently maintained by Smadar & Yaarit. Executable Visual Languages for System Development

  4. Play-In • Open sample project from <PlayEngineInstallDir>/Samples • Load a GUI – in the project use ‘Generic’ GUI • Or • Start by opening the Generic workspace • Projects shall be created using the Generic GUI. Executable Visual Languages for System Development

  5. Play-Engine General • Project Explorer • Toolbar • User hints • Play-In Panel • GUI (can be undocked) • Gui / Internal objects, properties & methods Executable Visual Languages for System Development

  6. Simple Play-In Play-In mode • Change to Play-In mode • Add a Use Case, and a LSC • Do action • Move to mainchart • Do action • Test using play-out Executable Visual Languages for System Development

  7. Initializing • Add a jump start • Get application state to start from current state • Or • Make changes in GUI or internal objects, you want the initialization to include Executable Visual Languages for System Development

  8. Play-In Messages • Method calls • Property changes Executable Visual Languages for System Development

  9. Symbolic Instances • Binding: by message • Instance changes to dashed line Executable Visual Languages for System Development

  10. If-Then-Else • Add If-Then-Else • Play-in condition (color=green) • Click finish to close the construct • Add else, add End • Note: better to finish operations before starting new ones Executable Visual Languages for System Development

  11. If-Then-Else • Move cut and add If and Else parts. Executable Visual Languages for System Development

  12. Symbolic Instances • Binding: by binding condition • Change lblText to symbolic (right click menu) • Select binding condition (by ID of btn) Executable Visual Languages for System Development

  13. Symbolic Instances • Binding by Property • Binding condition appears in round note Executable Visual Languages for System Development

  14. Variables & Internal objects • Green can be changed to a variable (use internal object with property ‘color’) • Can be done in a different LSC • Can use random selection Executable Visual Languages for System Development

  15. Random Select • Use random selection • Set the Variables Color property Executable Visual Languages for System Development

  16. Function Libraries • String and Math function libraries are useful • Add variable construct • Use concat from String library Executable Visual Languages for System Development

  17. Symbolic Variables • Variables can be changed to symbolic / exact • Default is according to symbolic button • Now can change n previous chart the reference to ‘Green’ to be a variable Executable Visual Languages for System Development

  18. Time constructs • Store the time, add a time constraint, add as forbidden to previous chart • See also using assertion as sync for creating order between messages Executable Visual Languages for System Development

  19. Play-In Forbidden Elements Executable Visual Languages for System Development

  20. Play-out • Play-out options: step, super step, pause at chart completion, random seed. • Select charts for execution • See some examples Executable Visual Languages for System Development

  21. Resources • Play-Engine User Guide (with installation) • Book: Come, Let’s Play • LSC reference • Demo movies in book website • Questions and Answers in course website Executable Visual Languages for System Development

  22. Technical • Installation: In course website • Support • Technical: Yaarit / Smadar • Theoretical: Assaf / Michal Executable Visual Languages for System Development

  23. Tips • Use LSCs as interleaved scenarios. • Avoid using LSCs as scenario triggering scenario, the procedural way… • Right click menus on texts may require double click to see Play-In menu. • No type checking • See more pointers in website Executable Visual Languages for System Development

  24. Projects • The second project can be part of the system created for the first project that can be connected to the first project. • The second project can be an inter-object implementation of the first project. • It is more important to use the cababilities of the LSC language than to create a perfectly working system. Executable Visual Languages for System Development

More Related