Authors: Juan Muñoz Jaime Muñoz Francisco J. Álvarez Ricardo Mendoza Workshop on Perspectives, Challenges and Opportunities for Human-Computer Interaction.

Slides:



Advertisements
Similar presentations
User Interface Design CIS 322 Office hours: Tuesday 1-2pm Thursday 12-1pm Room
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Chapter 9 Understanding Work Teams
Programming Languages for End-User Personalization of Cyber-Physical Systems Presented by, Swathi Krishna Kilari.
1 Using Octave to Introduce Programming to Technical Science Students Nuno C. Marques Francisco Azevedo CENTRIA, DI-
Demonstrators: Mudasir Nazir(08-CS-41).  I am highly addicted to this field.  Working with W3C in research program(building CSS for creating web site.
Human Computer Interaction Course Overview. 16/01/2008Human Computer Interaction Spring 2008: Lecture #1 2 Course Objectives Four basic objectives of.
HCI in the software process Chapter 6
Software Process Models
1http://img.cs.man.ac.uk/stevens Interaction Models of Humans and Computers CS2352: Lecture 7 Robert Stevens
User-Centred Design: Design Guidelines (lecture-6) Prof. Dr. Matthias Rauterberg Faculty Industrial Design Technical University of Eindhoven
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Automated Analysis and Code Generation for Domain-Specific Models George Edwards Center for Systems and Software Engineering University of Southern California.
Analysis Modeling Over view of today’s lesson T he analysis model is the first technical representation of a system. Analysis modeling uses a combination.
Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.
A Formal Model of Computation for Sensory-Based Robotics
James Tam CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 4-1 Chapter 4 Modeling and Analysis Turban,
User-Centred Design: Task Analysis (lecture-5) Prof. Dr. Matthias Rauterberg Faculty Industrial Design Technical University of Eindhoven
The Need of Unmanned Systems
Chapter 10: Architectural Design
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
User Centered Design Lecture # 5 Gabriel Spitz.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Formal Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Chapter 6: The Traditional Approach to Requirements
Human Interface Engineering1 Main Title, 60 pt., U/L case LS=.8 lines Introduction to Human Interface Engineering NTU Seminar Amy Ma HIE Global Director.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Chapter 10 Architectural Design
Human Computer Interaction Semester 1, 2013/2013.
Copyright © 2002 by The McGraw-Hill Companies, Inc. Information Technology & Management 2 nd Edition, Thompson Cats-Baril Chapter 8 I/S and Organizational.
Technology in Action Chapter 10 Behind the Scenes: Software Programming Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
The Architecture of Secure Systems Jim Alves-Foss Laboratory for Applied Logic Department of Computer Science University of Idaho By, Nagaashwini Katta.
Lecture 6 User Interface Design
SCV2113 Human Computer Interaction Semester 1, 2013/2013.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Styles.
SOFTWARE DESIGN.
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
Human – Computer Interaction
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Human Computer Interaction
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
TAL7011 – Lecture 4 UML for Architecture Modeling.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Basic Concepts of Component- Based Software Development (CBSD) Model-Based Programming and Verification.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 13. Review Shared Data Software Architectures – Black board Style architecture.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a: Architectural Design Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a:
BPEL Business Process Engineering Language A technology used to build programs in SOA architecture.
Organizational Design, Competences, and Technology.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
Principles of Information Systems, Sixth Edition An Introduction to Information Systems Chapter 1.
1 Learning through Interactive Behavior Specifications Tolga Konik CSLI, Stanford University Douglas Pearson Three Penny Software John Laird University.
CS223: Software Engineering
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
1 Visual Computing Institute | Prof. Dr. Torsten W. Kuhlen Virtual Reality & Immersive Visualization Till Petersen-Krauß | GUI Testing | GUI.
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
CHAPTER 2 CREATING AN ARCHITECTURAL DESIGN.
Model-Driven Analysis Frameworks for Embedded Systems
BPMN - Business Process Modeling Notations
Chapter 9 Architectural Design.
Map of Human Computer Interaction
Georg Umgiesser and Natalja Čerkasova
Automated Analysis and Code Generation for Domain-Specific Models
Implementation support
Modeling and Analysis Tutorial
Introduction to Modelica and FMI
Implementation support
Presentation transcript:

Authors: Juan Muñoz Jaime Muñoz Francisco J. Álvarez Ricardo Mendoza Workshop on Perspectives, Challenges and Opportunities for Human-Computer Interaction in Latin America (CLIHC 2007) September 10-11, 2007 Rio de Janeiro, Brasil

 Synchronous interaction A synchronous interaction is given by a set of one or more sequential action – reaction events which occurs one in response to other, while this sequence occurs the flow of the system is blocked.  Asynchronous interaction An asynchronous interaction represents a set of one or more events that will cause one or more results that not necessary are generated immediately or sequentially.

 Describes system components and connectors and rationality used to build and distribute them.  Establishes mechanisms of interaction among components of the system itself, with components from other systems and with users.

 Usability must be supported by well designed architectures.  Asynchronous relations between users and software systems are hardly studied.  A lot of systems must implement synchronous (SSI) and asynchronous interactions (ASI).  Some processes need to switch between both modes.  System usability perception can be improved by managing both kinds of interactions.  Architectural design of mechanism for management of ASI-SSI interactions could be too complicated.

 Very flexible  Can be adopted to processes without a defined behavioral pattern  User can take control of situations that requires of precision and immediate response  Follows people decisions  Is difficult to control it when parallel events occur

 Suitable for management of large volumes of information that take a lot of processing time and doesn’t require of human attention  Used to reduce process variability and to simplify applications  It’s useful in situations where is hard to establish communication  It doesn’t give immediate feedback

 A component to coordinate ASI and SSI in a system will help to reduce the effort for developing HCI instruments  It can help to guarantee that all events are processed in the right sequence  Helpful to manage multiple input devices or users acting in parallel

Interaction control Task Exception Dispatching Handling Synchronous Output End Input NO Finish Valid User NO

 Tags to identify sequences, flows, contexts and outputs  Multiple dispatching lists for ASI  Sorting capabilities  Definition of time policies  Feedback about changes and mechanisms for solving deadlocks and performance improvement  Multiple outputs device independent  Capacity to translate outputs to different languages and graphical representations

 Asking for commentaries about homework in a remote assisted session  Use of SSI for assisted session and individual tests  Use of ASI for download of self-study material and management of homework  Combination of both modes when designing and correcting models  Management of modes switching for a natural system behavior

 Virtual meetings  Help desk services  Remote CCTV surveillance system  Control of robots that must work on difficult situations  Etc.

 The ASI-SSI system interaction control mechanism makes easier to implement traditional functionalities  Well managed interactions have impact in user perception of system usability  The mechanism isn´t a pattern, nor a transformation mechanism but an architectural reference component  Scripting language for validating actions in the component could help to make the component more reusable and less coupled

[1 ] Hewett, T., Baecker, R., Card, S., Carey, T., Gasen, J., Mantei, M., Perlman, G., Strong, G., Verplank, W., ACM SIGCHI Curricula for Human-Computer Interaction, ACM SIGCHI (1996) [2] Bass, L., John, B., Kates, J., Achieving Usability Through Software Architecture, Technical Report CMU/SEI-2001-TR-005 ESC-TR , Carnegie Mellon Software Engineering Institute, Pittsburg, PA (2001) 1-87 [3] ISO, ISO TR 18529: Ergonomics for human-system interaction-Human-centered lifecycle process descriptions, ISO (2000) [4] Muñoz, J., Muñoz, J., Álvarez, F. J., Rodríguez, G., Specification and Evaluation of the Needed Requirements for the Design of Software Architectures, IASTED conference on Software Engineering and Applications 2006, Dallas, TX, USA (2006) [5] Muñoz, A., Rodríguez, F., Garza, L., Pinales, F., Modelo Para el Aprendizaje Colaborativo de Análisis y Diseño Orientado a Objetos Soportado Por Computadora, Revista Apertura del Sistema Universidad Virtual, Univesidad de Guadalajara, No. 1, México (2005) [6] Folmer, E., Bosch, J., Architecturally Sensitive Usability Patterns, Department of Mathematics and Computing Science, University of Gronigen, Netherlands (2003) 1-19

[7] Graunke, P., Krishnamurthi, S., Advanced Control Flows for Flexible Graphical User Interfaces. Or, growing GUIs on Trees; or Bookmarking GUIs, ICSE’02, ACM, Orlando FL, USA (2002) [8] Garton, I., Essential Software Architecture, Springer-Verlag, Germany (2006) [9] Rozanski, N., Woods, E., Software Systems Architecture, Addison Wesley, Pearson Education Inc., USA (2005) [10] ISO/IEC, “ISO/IEC CD 25012: Software engineering: Software Quality Requirements and Evaluation (SQuaRE) Data Quality Model”, ISO/IEC JTC1/SC7, Canadá, (2005) 1-32 [11] Malan, R., Bredemeyer, D., Defining Non-Functional Requirements, Bredemeyer Consulting, USA (2001) 1-8 [12] ISO/IEC, ISO/IEC Software Engineering – Product Quality – Part 1 Quality Model, ISO/IEC, Canada (2001)

[13] Maciasek, L., Roundtrip Architectural Modeling, Second Asia-Pacific Conference on Concpetual Modelling (APCCM2005), Conferences in Research and Practice in Information Technology Vol. 43, Australian Computer Society/Sven Hartman and Markus Strumper, ACM, Newcastle, Australia (2005) [14] Avouris, N., An Introduction to Software Usability, Report Research, University of Patras, Rio Patras, Greece (2001) 1-10 [15] Pregui¸ca, N., Legatheaux, J., Domingos, H., Duarte, S., Integrating Synchronous and Asynchronous Interactions in Groupware Applications, Proceedings of CRIWG’2005, Springer, Costa Rica (2005) 1-16 [16] Abran, A., Khelifi, A., Suryn W., Usability Meanings and Interpretations in ISO Standards, Software Quality Journal, 11, Kluwer Academic Publishers, Netherlands (2003) [17] Preece, J., Rogers, Y., Sharp, H., Benyon, D., Holland, S., Carey, T., Human- Computer Interaction, Addison Wesley, USA (1994). [18] Dix, A., Finlay, J., Abowd, G., Beale, R., Human-Computer Interaction (3 rd Edition), Prentice-Hall, USA (2003).

{JMunoz, JMunozAr,