1 Vrije Universiteit Faculty of Sciences Department of Computer Science Section Information Management & Software Engineering Subsection Human Computer.

Slides:



Advertisements
Similar presentations
Inference without the Engine!. What is EZ-Xpert 3.0? EZ-Xpert is a Rapid Application Development (RAD) environment for creating fast and accurate rule-based.
Advertisements

Change Requirements: An Explanation of What Stakeholders Try to Avoid and What They Try to Achieve Johan F. Hoorn, Elly A. Konijn, H. van Vliet, & G. vd.
User Interface Design Main issues: What is the user interface How to design a user interface.
Companies can suffer numerous problems due to poor management of resources and careless decisions. In real-world decision- making, many organizations lack.
1 1 vrije Universiteit, 2 VirTouch Ltd, 3 The Mediator Group, 4 Exact Holding NV Johan F. Hoorn 1, Simon van Dam 2, Guido Fambach 3, Arco van Nieuwland.
1 Department of Production and Quality Engineering Rethinking Project Risk Management PUS Seminar, November 30, 2010 Professor Asbjorn Rolstadas Norwegian.
© AgiliX Agile Development Consulting Agile Software Architecture Cesario Ramos.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
1 Vrije Universiteit Faculty of Sciences Department of Computer Science Section Information Management & Software Engineering Subsection Human Computer.
Personal before business in requirements prior-IT-ization Johan F. Hoorn & Mark E. Breuker Vrije Universiteit Computer Science Information Management and.
1 R&D SDM 1 Software Project Management Requirements Analysis 2010 Theo Schouten.
Software Engineering Management Main issues:  Plan - as much as possible, but not too much, up front  Control - continuously.
Communicating with ugly but efficient characters Henriette van Vugt Elly Konijn Johan Hoorn Vrije Universiteit Amsterdam 24 nov 2005 Etmaal van de communicatiewetenschap.
Introduction to the Child & Adolescent Needs and Strengths Assessment (CANS) Our Community. Our Kids. Dr. Gary Buff, Ed.D. President and COO.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
1 CHAPTER 3 INTORMATION DESIGN Prepared by CIK AJUNE WANIS BINTI ISMAIL Department of Computer Graphics & Multimedia Faculty of Computer Science and Information.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 1 (cont ’d) Title : Client requirements (Review) Mandatory reading: I.
1 THE USER INTERFACE Interface Design. 2 Requirements for a good HCI appropriate for the level and domain of expertise good interface mechanics –menus,
International Commun tion Association Johan F. Hoorn Vrije Universiteit Faculty of Sciences, Department of Computer Science Section Information Management.
Introduction to Human Computer Interaction Dr. Cheryl Seals Computer Science & Software Engineering Auburn University.
VENDORS, CONSULTANTS AND USERS
Natural Language Processing and Speech Enabled Applications by Pavlovic Nenad.
Lecture # 22 Software Evolution
Coping with Moore and more: HCI research in a moving world Gerrit C. van der Veer Vrije Universiteit Amsterdam Department Computer Science Open University.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
1 Vrije Universiteit Faculty of Sciences Department of Computer Science Section Information Management & Software Engineering Sub section Human Computer.
GCSE OCR 3 A451 Computing Professional standards
Model-View-Controller Ku-Yaw Chang Assistant Professor, Department of Computer Science and Information Engineering Da-Yeh University.
Usability Issues Documentation J. Apostolakis for Geant4 16 January 2009.
TAUCHI – Tampere Unit for Computer-Human Interaction 1 Statistical Models of Human Performance I. Scott MacKenzie.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Assignment Paired Prototyping Some content based on GDC 2006, Gingold and Hecker Brent M. Dingle 2014 Game Design and Development Program Mathematics,
Lecture-3.
ISECON 2003 Conference San Diego, California, USA November 6-9, 2003 K.H.VAT (Mr) Department of Computer and Information Science Faculty of Science & Technology.
Software Engineering COSC 4460 Class 4 Cherry Owen.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Computer Systems Week 14: Memory Management Amanda Oddie.
ERGONOMICS HNC/HND Engineering Engineering Design.
Chapter 7 What Can Computers Do For Me?. How important is the material in this chapter to understanding how a computer works? 4.
COMP 7620/7626 Cheryl Seals Computer Science & Software Engineering Auburn University.
Introduction to HCI Lecture #1.
Operating Systems (CS 340 D) Dr. Abeer Mahmoud Princess Nora University Faculty of Computer & Information Systems Computer science Department.
Information Systems Dr. Ken Cosh Lecture 9.
Team Skill 3 - Defining the System (Chapters of the requirements text ) Sriram Mohan 1.
1 Requirements Engineering for Agile Methods Lecture # 41.
Copyright 2006 John Wiley & Sons, Inc Chapter 5 – Cognitive Engineering HCI: Developing Effective Organizational Information Systems Dov Te’eni Jane Carey.
How to Move into the Future M.E.R.P.. What is MERP  MERP is an extension of ERP - Enterprise Resources Planning  Enterprise Resources Planning (ERP)
1.10 Report Findings to Communicate Research Information to Others SEM2.
(I) Chapter One: Marketing Concepts Lecturer: Dr. Mazen Rohmi.
Real-Time Operating Systems RTOS For Embedded systems.
Natural Language Processing and Speech Enabled Applications
Chapter 16: User Interface Design
Paper 1 | GCSE Computer Science | Ethical, legal, cultural & environmental issues | Required knowledge How to investigate & discuss Computer Science technologies.
Operating Systems (CS 340 D)
The Web Application Development Process Models
Informing Science + IT Education Conferences
System Design Basics IB Computer Science.
Software engineering USER INTERFACE DESIGN.
Operating Systems (CS 340 D)
Introduction to Human Computer Interaction
Onno Kubbe Design Rule Ontology Onno Kubbe 12/2/2018.
Introduction to International Relations Lecture # 1.
Chapter 3 – Agile Software Development
CSCI1600: Embedded and Real Time Software
Importance Rankings (Hi to Lo - T to B, L to R)
Computer Science Section
Software Analysis.
HCI What ? HCI Why ? What happens when a human and a computer system interact to perform a task? task -write document, calculate budget, solve equation,
Planning process in river basin management
Designing Scalable Architectures
Presentation transcript:

1 Vrije Universiteit Faculty of Sciences Department of Computer Science Section Information Management & Software Engineering Subsection Human Computer Interaction, Multimedia & Culture Johan F. Hoorn and Gerrit C. van der Veer Requirements Analysis and Task Design in Dynamic Environments HCI International 2003Heraklion, Crete, Greece

2 Contents  Problem  Aim  Theory  Model  Prospects  Questions Dutch Ministry of Economic Affairs

3 Problem Business models change in reaction to the outside world Therefore, business goals and work processes change IT systems become outdated even before release This costs time, money, effort, and anger

4 Public service? Serves general public No break even Commercial? Serves itself Beyond break even Business model Government demand changes Slow work process allowed Work process must be fast Supporting IT can leave much to the user Supporting IT is not allowed to leave much to the user

5 Supporting IT can leave much to the user Supporting IT is not allowed to leave much to the user Public serviceCommercial Make new incidentFill out 8 action windowsEach action a new window Make 4 different files 

6 Supporting IT is not allowed to leave much to the user Public serviceCommercial Minimal number of complex windows is 12 Takes at least 30 minutes Error probability high Does not support the public Not cost extensive Expensive redesign

7 Aim  Can we make up a system structure that can handle changes in business goals and work processes? To this end we need to isolate the factors that remain stable throughout the process of change

8 Examples of goals Personal concerns Group concerns Get an exciting jobHelp juvenile delinquents

9 Examples of processes Speed Accuracy

10 Theory Evolving business models cause shifts in personal and business goals They also affect the speed of work processes and thus, (human) accuracy All this explains the changes in system requirements

11 Business goals: - break even / make profitegotistic - to serve and protectaltruistic Personal goals: - make a careeregotistic - commitment to companyaltruistic Where, then, can we find the stable factors? New business model changes priorities

12 Client Sources of conflict, regarding goals Business goalsPersonal goals Changing system requirements Stakeholders ManagementWorkfloor egotistic vs. altruistic egotistic vs. altruistic vs. Event

13 Accurate processes: - getting an e-dossierfast - breath analysisslow Inaccurate processes: - summary justicefast - incident administrationslow Stable process mechanisms Help me! New business model changes priorities

14 Client Sources of conflict, regarding processes Accurate processInaccurate process Changing system requirements Stakeholders ManagementWorkfloor speed vs. accuracy speed vs. accuracy vs. Event

15 Agreed requirements change’ Break evenServe, protectCareerCommitmentE-dossierBreath analysisSummary justiceIncident adm. egotistic altruistic business personalinaccurate accurate fast slow Relevance Process Goals Valence Model

16 Prospects  Adaptive system structure?  Ethnography  Structured questionnaires  Confirmative factor analysis  Model fit

17 Questions?