1. An Integrated Event-Driven Framework Supporting MDD Lizhang Qin, Hongming Liu Chris Jones, Xiaoping Jia

2. Agenda Introduction An Approach to MDD ZOOM Models Event Framework Prototype Development Conclusion

3. Introduction Model-Driven Development (MDD) Z-based Object-Oriented Modeling(ZOOM) UML-2 Event-Driven Framework

4. An Approach to MDD Model Definition  Mellor: “a coherent set of formal elements describing a system built for a purpose that is amenable to a particular form of analysis”.  Seidewitz: a model is “a set of statements about so system under study.  Our definition: a model is “a consistent and complete set of formal elements describing a system that is amenable to analysis”.

5. An Approach to MDD Current modeling language of choice: UML-2 for MDD We argue that the true benefits of MDD requires models that are abstract, understandable, formal, analyzable and complete. The ZOOM approach consists of a set of notations and supporting tools that attempts to provide an infrastructure that delivers all of these capabilities.

6. ZOOM Models

7. Separation of Concerns  Allows each aspect of the system to be specified separately, making each aspect easier to write, understand, and change.  Use different specification languages to describe different aspects of the system

8. Structure Model Structural models in ZOOM are object-oriented models with classes, relations, and formal specifications of the functionality of the entities. ZOOM-M, is a Z and OCL based language with a Java/C++ like syntax to make it easy for practitioners to adopt. A set of supporting tools has been built for ZOOM-M, including, parser, type checker, interpreter, animator, and an automated theorem prover (ATP).

9. Behavioral Model The behavioral model is the central communication mechanism that links the structural models with the UI models ZOOM-FSM include a rich syntactical grammar with formal semantics an intrinsic mechanism to use the structural models specific by ZOOM-M, a strong compatibility with the UML-2 state chart.

10. User Interface Model Unlike UML-2 and MDA notations, ZOOM separates UI models from other aspects. We use a User Interface Description Language ZOOM- UIDL to specify the design of UI in a formal way ZOOM-UIDL is a hierarchical description framework containing a set of predefined UIDL schemas.

11. Event-Driven Framework

12. A Login Scenario

13. Event-Driven Framework(Cont.) <xs:attribute name="text" type="xs:string" use="optional"/> <xs:attribute name="selected" type="xs:boolean" use="optional"/> (a) A simplified version of Button schema in UIDL public struct UIButton extends UIComponent { public String whenclick; public String text; public boolean selected; } (b) UIButton struct

14. Event-Driven Framework(Cont.) 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: public struct TLoginDialog { public UITextBox status; public UITextBox userID; public UITextBox password public UIButton okButton; public UIButton cancelButton; }

15. Event-Driven Framework(Cont.) FSM Machines Event: UIOk …… ……

16. Event-Driven Framework(Cont.)

17. FSM UIOk Wrong Login Info login Object State Change R1R2R3

18. Prototype Development ZOOM-M ZOOM-FSM & ZOOM-UIDL A translation engine for the behavioral models A set of rule-based tools for UI generation

19. Conclusion ZOOM: An Approach to MDD Separation the model design to three parts. An event-based approach for model integration

20. Thank you Questions?