• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Model-Based Visual Software Specification
 

Model-Based Visual Software Specification

on

  • 644 views

Model-Based Visual Software Specification

Model-Based Visual Software Specification

Statistics

Views

Total Views
644
Views on SlideShare
644
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Model-Based Visual Software Specification Model-Based Visual Software Specification Presentation Transcript

    • UNIVERSITY OF KONSTANZ Computer & Information Science Human-Computer Interaction Model-Based Visual Software Specification Thomas Memmel, Mathias Heilig, Harald Reiterer IADIS International Conference Interfaces and Human Computer Interaction 2007 Lisbon, Portugal, 6-8 July 2007UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • hci.uni-konstanz.de  Design  Implementation  Evaluation  Mobile Devices  Desktop Computer  Large-scale Displays (Powerwall)  Digital Libraries  WebPages  Visual Information Systems  Embedded Systems  New User interface Paradigm: ZOIL Zoomable Object-Oriented Information Landscape.UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Content of the presentation 1 Introduction and challenges 2 Concept of the tool-chain 3 Parts of the tool-chain 4 Conclusion and perspectiveUNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Development of automotive HMIs ?Functionality  Instrument cluster  Climate control  Infotainment (Radio, CD, (Mobile-)Phone, SMS, E-Mail, Navigation, Voice control)  Speedo/odometer  Instrument cluster  Radio  Climate control  Radio  Phone 1960 1970 1980 1990 2000 2010 Time 1UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Participants in an networked development processes Manufacturer Specification Product features (Graphical layout) Market analyses Product Supplier Designer manager Requirement FinalPrototypes Programmer Purchaser specification product Ergonomists Technical experts Interaction concepts Technical requirements Media disruption 1 UNIVERSITY OF KONSTANZ Computer & Information Science Human-Computer Interaction
    • Heterogeneous and proprietary tool landscapes Tool landscape 12 10 7 6 4 2 1 Developers use different tools for same development tasks 1UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Model-Driven Development in UE • Adapt model-driven methods into a usability development • From the UE perspective • Bridge the disciplines • Generation of a Visual Specification Low-Fi Hi-Fi Visual Prototype Prototype Specification 2UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Model-Driven Development in UE • Adapt model-driven methods into a usability development • From the UE perspective • Bridge the disciplines • Generation of a Visual Specification “Model Driven development makes it possible, to describe software systems continuously by models. Low-Fi Hi-Fi artifacts.”1 Thus it offers the chance to generate Visual Prototype Prototype Specification 2UNIVERSITY OF KONSTANZ Computer & Information Science 1colected definition from Stahl, 2005; Völter, 2004.Human-Computer Interaction
    • Consistent and continuous tool-chain Overall requirements High problem orientation: Even for non experts ONE model for specification and simulation Prevent overhead and complexity  consistency of specification and High abstraction level: prototype Appropriate abstraction level  no additional effort for prototyping (hide implementation details/ due to code generation show details-on-demand)  Bridge gaps of understanding due to Intuitive notation: standardization Familiar graphical representation Early verification of specifications Formal specification Enables code generation 2UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Dimensions of a Usability Development Layout Content Main ANTENNE1 D1-Telefon 22°C 13:12 18.04.05Ergonomists Designers Technical Experts Product Manager Behaviour Separation of content, layout and behaviour Ergonomists Programmers  Separation of Concerns 2 UNIVERSITY OF KONSTANZ Computer & Information Science Human-Computer Interaction
    • Setup of the tool-chain technical technical ergonomist designer expert technical expert designer expert programmer programmer Widgets & Templates Domain-Specific Modellinglanguage (DSL) designer ergonomist ergonomist technical technical ergonomist expert expert ergonomist ergonomist Domain-Specific Domain-Specific GUI-Builder: CASE-Tool: CASE-Tool: Layout Content Behaviour programmer Codegenerator programmer Domain-Framework Output: Simulation, Specification etc. 2UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • Creation of a DSL Identify domain Add graphical concepts notation (Visual) 1 2 3 4 Domain-specific Language (DSL) Define Create code constraints generator/framework1 Identify domain conceptsExample: Development of a meta-model for modelling the Infotainmentsystem:A) Objects: B) Relationships:  Different Screen -> States  Push/rotary knobs  Primary keys (main keys)  Secondary keys  Etc. 3 UNIVERSITY OF KONSTANZ Computer & Information Science Human-Computer Interaction
    • Creation of a DSL Identify domain Add graphical concepts notation (Visual) 1 2 3 4 Domain-specific Language (DSL) Define Create code constraints generator/framework2 Define domain constraints 3 Add graphical notationDefinition of modeling rules, e.g.: Provide intuitive visual representation for domain Only one connection (=transition) is allowed concepts between a menu item and a subsequent menu  Schematic symbols for menu screens and keys screen for a specific event (e.g. Left push/rotary knob pressed) Menu screen, items right + left Menuitem 1 Numeric key Menuitem 2 DDS left pressed Menuitem 3 Menuitem 4 Menuitem 5 Push/rotary Menuitem 6 Subsequent knob menu screen 3 UNIVERSITY OF KONSTANZ Computer & Information Science Human-Computer Interaction
    • Creation of a DSL Identify domain Add graphical concepts notation (Visual) 1 2 3 4 Domain-specific Language (DSL) Define Create code constraints generator/framework4 Create code generator/frameworkDefinition of transformation rules: Templates for the code generator of the Language Templates Models Workbench catch the information of the models and pack it into logical arrays for the domain framework Code GeneratorImplementation of a domain framework: LA LA LA LA LA Basic code for the output of the models. Domain Framework All constant parts of the output should be Output implemented in the framework. 3 UNIVERSITY OF KONSTANZ Computer & Information Science Human-Computer Interaction
    • Conclusion Benefits Drawbacks  More flexibility  Initial effort  Standardization  Acceptance among developers  Avoid duplicate work  Can only be applied after basic  Simulations are available significantly activities earlier  Changes can only be transported in  Conceptual problems are recognized one direction (model -> prototype) earlier  Less effort for late changes due to frontloading  Disciplines are bridged  Paper-based specifications substituted by living specifications 4UNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction
    • QuestionsUNIVERSITY OF KONSTANZ Computer & Information ScienceHuman-Computer Interaction