1. SCHOOL OF COMPUTING QUEEN’S UNIVERSITY 08/03/2013 Andrew Forward, Omar Badreddin, Timothy C. Lethbridge, and Julian Solano School of Electrical Engineering and Computer Science, University of Ottawa, K1N 6N5, Canada

2. Outlines Introduction Problem Definition Umple Features Model-Driven Software Development and its Challenges Properties of Prototypes Umple Modeling and Prototyping Approach Class Diagram In Umple Umple User-Interface Prototype Generator State Machines in Umple Mixins and Substitution Umple’s Architecture Conclusions

3. Introduction Umple:  Stands for “UML Programming Language”  Currently, Model-driven software development brings new opportunities and challenges for rapid prototyping.  Modeling process is inherently abstract, removing the prototyper from details.  Modeling process allows the prototyper to focus on exploring design alternatives for various aspects of the system.

4. Problem Definition Most popular modeling languages and tools entirely omit the modeling and generating of user interfaces. The benefit of user interface prototypes as a medium for interaction with the user and customer is lost.

5. Model-Driven Software Development The philosophy of MDSD is that these models should be used to directly generate executable systems. It should always be inherently possible to generate prototypes from a model.

6. MDSD Challenges The most popular types of models are not intended for modeling the user interface. Combining code generated from models with other necessary code is not easy. There is a need to generate tangible artifacts and prototypes for business-domain stakeholders. Software modellers often do not fully understand the consequences of their modeling decisions. There are limitations in existing approaches to prototype generation from UML models.

7. Attempts to address the previous issues

8. Umple allows end users to quickly create class and state machine models and to incrementally embed implementation artifacts. At any point in the modeling process, users can quickly generate a fully functional prototype that exposes modeling implications on the user interface (Quick user interface creation). Umple provides a set of textual notations for UML modeling abstractions such as classes, associations, states, and transitions. Quickly and abstractly prototype the data and behavior of a software system. Umple Features

9. Umple can be embedded directly in several programming languages to reduce the amount of code required and speed up the programming process. Umple provides a tool to allow editing of UML class diagrams in their graphical form. Subsequent editing of the model can be performed textually or visually. Umple Features - conti

10. Desirable Properties of Prototypes 1. Accurate reflection of system components (data & Design). 2. Quick and cheap generation of a prototype. 3. Maximized potential for reuse and composition. 4. Support for different levels of abstraction. 5. Support for incremental development. Umple Support all of these properties

11. Umple Modeling and Prototyping Approach Umple supports modeling either visually or textually. Textual Editor Supports: o Syntax-Driven editing o Searching o Auto indentation o Mixins Graphical Models Support: o Better communication & collaboration. o Relationships are clearer.

12. Umple Modeling and Prototyping Approach

13. Class Diagram In Umple class Student {} class CourseSection {} class Registration { String grade; // an attribute: get and set methods are generated * -- 1 Student; // an association: A registration has 1 Student * -- 1 CourseSection; // another association } A class diagram corresponding to Umple code Code Sample

14. Umple User-Interface Prototype Generator At any point in the modeling or development activities, the user can automatically generate a system prototype. The system prototype has the following features: 1. It allows the user to create instances of classes (objects) and links of associations. 2. Semantic rules are respected at run time (Error message is displayed if violation of the multiplicity). 3. The user can view and update an object’s attributes. 4. The user can follow links. 5. The user can change predefined themes.

15. Umple User-Interface Prototype Generator School_Person Example:

16. Generated Prototype

17. State Machines in Umple Umple supports the specification of state machines. Umple adheres to UML semantics except as described later. State machines provide a very compact representation of behavior, and hence are ideal for rapid prototyping.

18. State Machines in Umple Delivery of a courier package example: class Customer { String name; // An ordinary attribute with a primitive type Address address; // An attribute with an Umple type } class CourierShipment { Time ArrivalTime; Time DeliveryTime; Money price; Boolean billToRecipient; * -- 1 Customer sender; // An association * -- 1 Customer recipient; packageStatus { // State machine, like an enumerated attribute Initial { // One of the states; this is the initial state createDraft -> Draft; // If createDraft called state changes createFinal -> Ready; } Draft { // Another state createFinal -> Ready; } Ready { dropAtCourierDepot -> Transit; pickUpByDeliverer -> Picked; } Picked { dropAtCourierDepot -> Transit; } Transit { transferToNextStage -> Transit; deliver -> Delivered; } Delivered { billingSettled -> Done; } Done {} }

19. State Machines in Umple Traffic Control System Example: class trafficLightSystem { carTraffic { Red { Entry / {goingRed();} // Call this when entering the state // The following is a timed transition that is also // guarded, meaning the state changes only if the condition // in square brackets (arbitrary Java) evaluates to true after(redTimer)[!emergency] -> Yellow; emergencyNotice -> AllRed; } Yellow {... }... } pedestrianTraffic { DontWalk { goingRed [!emergency] -> Walk; emergencyNotice -> DontWalk; }... }... }

20. Mixins and Substitution Statemachine coreTrafficController { Red { After(redTimer) -> Green; } Green { After(greenTimer) -> Yellow; } Yellow { After(yellowTimer) -> Red; } Mixin allows independently-developed code to be injected into a set of classes Mixin Substituti on

21. Mixin Benefits Code Reuse Easy to add and remove transitions Quickly draft Iterative refinement

22. Umple’s Architecture Layout Information Umple Core System Visual Editor Textual Editor XMI Third Part Tools Repository Ecore Umple Compiler Umple Code Generator Interface Generator Runtime Object Persistence Mechanism

23. Conclusions Umple Provides: 1. Accurate reflection of system components and data. 2. Accurate reflection of current system design directions. 3. Quick and cheap generation of a prototype. 4. Maximized potential for reuse and composition. 5. Support for different levels of abstraction. 6. Support for incremental development.