1 / 20

UML i : The Unified Modeling Language for Interactive Applications

UML i : The Unified Modeling Language for Interactive Applications. Paulo Pinheiro da Silva and Norman W. Paton Department of Computer Science, University of Manchester. User interface (UI) modelling with UML Background UML i ARGO i Conclusions Future work. Outline.

justice
Download Presentation

UML i : The Unified Modeling Language for Interactive Applications

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. UMLi: The Unified Modeling Language for Interactive Applications Paulo Pinheiro da Silva and Norman W. Paton Department of Computer Science, University of Manchester

  2. User interface (UI) modelling with UML Background UMLi ARGOi Conclusions Future work Outline

  3. UML is a standard intended for modelling any software application. User interfaces are a crucial part of most applications. User Interface Modelling with UML (1/2) HOWEVER: UIs are usually not modelled using UML.

  4. The limited use of UML for modelling UIs is evidence that UML may not be entirely suitable for UI design. Which aspects of UIs cannot be modelled effectively using standard UML? How can UML be improved to support modelling of such UI aspects effectively? User Interface Modelling with UML (2/2) But then...

  5. UI modelling difficulties using UML an approach for extending UML support for UI design Background • UML-based interactive application case studies • Model-Based User Interface Development Environment techniques Identify... Provide...

  6. Main features of the UMLi proposal: User Interface Diagrams Activity Diagram Extensions From use cases to activities From activities to action states Methodology UMLi Proposal

  7. Abstract constructors are required to model UI presentations. Abstract constructors should eventually be mapped into widgets. Modelling UI Presentations • 9 instances of 6 widgets.

  8. A UI Presentation • In object diagrams, it is difficult to graphically realise: • Interaction object containment. integrate ConnectionUI: FreeContainer integrate ButtonBox: Container DataBox: Container compose compose compose compose compose PasswordLabel: Displayer LoginText: Inputter compose OK: ActionInvoker Cancel: ActionInvoker PasswordText: Inputter LoginLabel: Displayer

  9. A UI Presentation • In object diagrams, it is difficult to graphically realise: • Interaction object containment • Which abstract roles interaction objects are playing Different roles integrate ConnectionUI: FreeContainer integrate ButtonBox: Container DataBox: Container compose compose compose compose compose PasswordLabel: Displayer LoginText: Inputter compose OK: ActionInvoker Cancel: ActionInvoker PasswordText: Inputter LoginLabel: Displayer Similar roles

  10. A UMLi UI Presentation • UMLi UI diagrams provide graphical representations for: • containment of interaction objects • abstract roles of interaction objects ConnectionUI “Login” “Password” “Cancel” “OK” LoginText PasswordText

  11. ConnectUI From Use Cases and theirScenarios to Activities <<communicates>> Connect Connect LibraryUser Connect <<presents>> John, a library user, must provide his details to gain access to the library system Select Function

  12. The modelling of some categories of transition may be simple using activity diagrams: Sequential transitions Concurrent transitions Choices However, the modelling of other categories of transition may be complex: Optional transitions Order independent transitions Repeatable transitions Modelling Common Interactive Behaviours Connect GetDetails new SelectHist SelectHist Select [GetName in SelectHist] [GetPassord in SelectHist] [GetName] [GetPassword] GetName GetPassword [GetName & GetPassword in SelectHist] TryConnection SelectFunction

  13. UMLi introduces the SelectionState constructors for modelling: Optional transitions Order independent transitions Repeatable transitions UMLi Selection States Connect GetDetails GetName GetPassword TryConnection SelectFunction

  14. UMLi Interaction Object Flow

  15. ARGOi is an extended version of UCI’s ARGO The tool incorporates the following UMLi features: UI diagram editor ARGOi: A UMLi-Based Tool (1/2)

  16. UMLi Extended Activity Diagram features Interaction object flow support UMLi XMI parser/generator ARGOi: A UMLi-Based Tool (2/2)

  17. UML needs to be extended to simplify the modelling of the following aspect of UIs: UI presentations Interactive behaviour (inter-object transitions) Collaboration between interaction objects and non-interaction objects Conclusions (1/2)

  18. UML for Interactive Applications (UMLi) is a proposal for extending UML that addresses these relevant problems of modelling UIs using UML. Further, UMLi provides: a notation, meta-model and XMI DTD specification; ARGOi: A UMLi-based open source tool; A complete UMLi case study modelled in ARGOi. Conclusions (2/2)

  19. An industrial case study of using UMLi Design metric comparison between UML and UMLi UMLi methodology evaluation An implementation of UI software generation from UMLi models Future Work

  20. Further information about UMLi can be obtained at http://img.cs.man.ac.uk/umli Further Information

More Related