March 9, 2008 Vermelding onderdeel organisatie 1 SEARIS'08 Workshop IEEEVR 2008, Reno NV, USA Gerwin de Haan G. de Haan, F.H. Post Data Visualization Group.

Slides:



Advertisements
Similar presentations
10 september 2002 A.Broersen Developing a Virtual Piano Playing Environment By combining distributed functionality among independent Agents.
Advertisements

A Workflow Engine with Multi-Level Parallelism Supports Qifeng Huang and Yan Huang School of Computer Science Cardiff University
Eindhoven Technische Universiteit What offers VR to the Designer Bauke de Vries Henri Achten.
ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Towards a Practical Composition Language Oscar Nierstrasz Software Composition Group University of Bern.
Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.
Visualization Kenny Inthirath.  Reviewing a Suitable Technique to Use  Scope and Purpose  What types of models can be represented?  Architectural.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Chess Review May 8, 2003 Berkeley, CA Classes and Inheritance in Actor- Oriented Models Stephen Neuendorffer Edward Lee UC Berkeley.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
6/14/2015 How to measure Multi- Instruction, Multi-Core Processor Performance using Simulation Deepak Shankar Darryl Koivisto Mirabilis Design Inc.
Unified Modeling (Part I) Overview of UML & Modeling
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
DIVES Alur, Lee, Kumar, Pappas: University of Pennsylvania  Charon: high-level modeling language and a design environment reflecting the current state.
May 6, 2006 Vermelding onderdeel organisatie 1 Intent and Interaction EGVE 2006, Lisboa, Portugal Gerwin de Haan MediaMatics, Computer Graphics & CAD/CAM.
Visual Basic 6.0 Derived from BASIC Developed by Microsoft in 1998 An event driven programming language Associated with a development environment.
Architectural Design.
02/06/05 “Investigating a Finite–State Machine Notation for Discrete–Event Systems” Nikolay Stoimenov.
Marco Blumendorf I July 21th, 2009 Towards a Model-Based Framework for the Development of Adaptive Multimodal User Interfaces.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
Architecture-Based Runtime Software Evolution Peyman Oreizy, Nenad Medvidovic & Richard N. Taylor.
CS 360 Lecture 6.  A model is a simplification of reality  We build models to better understand the system being developed.  We build models of complex.
Dart: A Meta-Level Object-Oriented Framework for Task-Specific Behavior Modeling by Domain Experts R. Razavi et al..OOPSLA Workshop DSML‘ Dart:
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Unified Modeling Language, Version 2.0
Formalizing the Asynchronous Evolution of Architecture Patterns Workshop on Self-Organizing Software Architectures (SOAR’09) September 14 th 2009 – Cambrige.
Software Engineering Research paper presentation Ali Ahmad Formal Approaches to Software Testing Hierarchal GUI Test Case Generation Using Automated Planning.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
For accurate communication, since a project can have several participants, each from different background. Represent a given aspect of the system We will.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
Group 3: Architectural Design for Enhancing Programmability Dean Tullsen, Josep Torrellas, Luis Ceze, Mark Hill, Onur Mutlu, Sampath Kannan, Sarita Adve,
PROC-1 1. Software Development Process. PROC-2 A Process Software Development Process User’s Requirements Software System Unified Process: Component Based.
Future Work  Formal specification of modeling language semantic is key issue  Reliance on well-established formal models of computation (i.e. finite.
Introduction to OOAD and the UML
Introduction to Interactive Media Interactive Media Tools: Authoring Applications.
12 Chapter 12: Advanced Topics in Object-Oriented Design Systems Analysis and Design in a Changing World, 3 rd Edition.
1 Copyright  2001 Pao-Ann Hsiung SW HW Module Outline l Introduction l Unified HW/SW Representations l HW/SW Partitioning Techniques l Integrated HW/SW.
Visualization Four groups Design pattern for information visualization
Modeling the ODP Computational Viewpoint with UML 2.0: The Templeman Library Example José Raúl Romero, Antonio Vallecillo Universidad de Málaga, Spain.
1 Unified Modeling Language, Version 2.0 Chapter 2.
4+1 View Model of Software Architecture
Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
Toward product architecture oriented requirements analysis for product line development in systems engineering Kei Kurakawa Nara Institute of Science and.
Visualizing Complex Software Systems
The Movement To Objects
Main issues: • What do we want to build • How do we write this down
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Object-Oriented Analysis and Design
Introduction to Design Patterns
Unified Modeling Language
University of Central Florida COP 3330 Object Oriented Programming
Unified Modeling Language
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Michael LeGore Thomas Jefferson High School for Science and Technology
Copyright 2007 Oxford Consulting, Ltd
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Appendix A Object-Oriented Analysis and Design
Design.
ONAP Architecture Principle Review
Presentation transcript:

March 9, 2008 Vermelding onderdeel organisatie 1 SEARIS'08 Workshop IEEEVR 2008, Reno NV, USA Gerwin de Haan G. de Haan, F.H. Post Data Visualization Group & VRLab Flexible Architecture for the Development of Real-Time Interaction Behavior (p.71)‏

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Real-Time Interaction Behavior (VR) application behavior is interaction/event-based Interaction Trends: Multi – Object Multi – User Multi – Cursor Multi – System Interaction Trends: Multi – Object Multi – User Multi – Cursor Multi – System Development Cycle: Implementation Architecture Interaction Model Front-End (Storyboard)‏ Unexpected complexity, behavior, structure Prototype, Experiment, Analyse

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Work in Progress Prototyping Interaction Software: Base Architecture: VRMeer Interaction Model: StateStream Run-time/Development Environment -> Unifying through a dynamic language

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Architecture: VRMeer [2] G.de Haan et. al. “Flexible Abstraction Layers for VR application development” IEEE VR '07

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop StateStream Model Low-level design of techniques, relations Actors Conceptual containers e.g. VR Objects, Interactors, (Algorithms)‏ Dual aproach for Interaction Modeling Statemachine: Discrete behavior Streammachine: Continuous exchange of data [6] R.Jacob et. al. “A Software Model and Specification Language for Non-WIMP user interfaces”, ACM TOCHI '99

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop StateStream Model: StateMachines StateCharts: Hierarchical, Concurrent Statemachines Functionality in callbacks of Events, Transitions

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop StateStream Model: StreamMachines Data Flow Graph: Nodes, Connections, Ports Functionality in callbacks of ports

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop StateStream Model: Relations

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Integration with Python StateStream components are Python Classes Methods: expressive functionality Dynamic Typing: Flexible with restructuring Inheritance: Derive and override Introspection: run-time decisions, accessible Mix-ins: Quick integration with base arch. Instantiation: Create new components on-the-fly Python in control: Intercept and introspect “anywhere, anytime”

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Iterated Development Challenges: containment, hierarchy, timing, order Gradual maturing Model Extension Transfer to Model e.g. Templated sub-statemachines Complexity explosion unevitable Supporting analysis tools (e.g. Visualisation, logging)‏ Run-Time Environment Towards end-user environment

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Run-Time Environment Python glue ~ concurrent w. VR GUI components Introspection Scripting Mix event models (d.tools)‏ [4] B. Hartmann, “Reflective Pysichal Prototyping through integrated design, test, and analysis”, UIST 2006

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Conclusions, Future Directions StateStream model and architecture Work in progress Visibility, flexibility, expressiveness Speed up prototyping, development Future work Extensible prototyping environment (Semi-) Formal model properties Serialization, Optimization, Distribution Multiple Python instances

March 9, G. de Haan, F.H. Post “Flexible Architecture for the Development of Real-Time Interaction Behavior” SEARIS'08 Workshop Questions ? Remarks ! - !