The OOD Process - II The Human Interaction Component (HIC) [Coad/Yourdon]

Slides:



Advertisements
Similar presentations
Chapter 19 Design Model for WebApps
Advertisements

Chapter 12 User Interface Design
0 UMN 2011 ERP Terapan SAP BASIS General Concept Session # 3.
COMP 3715 Spring 05. Computer Interface Interaction between human and computer Has to deal with two things  User’s mental model Different user has different.
The Problem Domain Component (PDC) [Coad/Yourdon]
The OOD Process - III The Data Management Component (DMC) [Coad/Yourdon]
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
Developed by Justin Francisco, SUNY Fredonia USER INTERFACE DESIGN By: Justin Francisco.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Object Oriented Design OOD. OOD characteristics - I conceptual compatibility with OOA notational consistency with OOA clean traceability of OOA results.
Ch 7 & 8 Interaction Styles page 1 CS 368 Designing the Interaction Interaction Design The look and feel (appearance and behavior) of interaction objects.
1 THE USER INTERFACE Basic Principles. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance User Interface Model.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Principles and Methods
1Spring 2005 Specification and Analysis of Information Systems A Crush Course in Usability and User Centered Design Eran Toch
The Task Management Component (TMC) [Coad/Yourdon]
James Tam CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework.
1 THE USER INTERFACE Interface Design. 2 Requirements for a good HCI appropriate for the level and domain of expertise good interface mechanics –menus,
The OOD Process Design as a Logical Continuation of Analysis.
COMP1007 Introduction to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis.
Performing User Interface Design
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
User Interface Theory & Design
Systems Analysis and Design in a Changing World, 6th Edition
1 Interface Design Easy to use? Easy to understand? Easy to learn?
FH Augsburg - FB Informatik 1 CADUI' June FUNDP Namur Software Life Cycle Automation for Interactive Applications: The AME Design Environment.
Output and User Interface Design
Guidelines and Prototypes CS774 Human Computer Interaction Spring 2004.
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Computer Graphics Lecture 28 Fasih ur Rehman. Last Class GUI Attributes – Windows, icons, menus, pointing devices, graphics Advantages Design Process.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 12 User Interface Design Highlights of user (human) interface design concepts.
1 WEB Engineering E-Commerce Strategy & Management COM350.
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
1 Chapter 15 User Interface Design. 2 Interface Design Easy to use? Easy to understand? Easy to learn?
Developed by Reneta Barneva, SUNY Fredonia User Interface Design (Chapter 11)
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Chapter 12 Class will start momentarily. Please Stand By … CS 8532: Advanced Software Engineering.
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
A-Level Computing#BristolMet Session Objectives#15 MUST define the term user interface SHOULD describe the characteristics of different UIs and suggest.
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
1 Chapter 4: User Interface Design. 2 Introduction … Purpose of user interface design:-  Easy to learn  Easy to use  Easy to understand.
DMS 546 / DMS 446 INTERFACE DESIGN Spring Al Larsen TASK ANALYSIS slides and lecture based on Chapter 3 of User-Centered Website Development (McCracken.
Software Engineering B.Tech Ii csE Sem-II Unit-V PPT SLIDES By Hanumantha Rao.N Newton’s Institute of Engineering 1.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 7 - Designing the User and System Interfaces.
Design Phase intro & User Interface Design (Ch 8)
Writing to Teach - Tutorials Chapter 2. Writing to Teach - Tutorials The purpose of a tutorial is to accommodate information to the needs of the user.
User Interface Design Make Your Program Easy to Use and Look Good.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Event loops 16-Jun-18.
Usability engineering
Software Engineering: A Practitioner’s Approach, 6/e Chapter 12 User Interface Design copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Objectives To review concepts covered in the Windows Operating Systems units.
Software engineering USER INTERFACE DESIGN.
Cooper Part III Interaction Details Designing for the Desktop
Chapter 15 User Interface Design
Event loops.
Highlights of user (human) interface design concepts and principles
Introduction UI designer stands for User Interface designer. UI designing is a type of process that is used for making interfaces in the software or the.
CS 8532: Advanced Software Engineering
Event loops 17-Jan-19.
Event loops 17-Jan-19.
Proper functionality Good human computer interface Easy to maintain
Event loops 8-Apr-19.
Interface Design Easy to learn? Easy to use? Easy to understand?
Event loops.
Event loops 19-Aug-19.
Presentation transcript:

The OOD Process - II The Human Interaction Component (HIC) [Coad/Yourdon]

The OO Co-Design Process The Human Interface Component TMCHICPDCDMC high-level Design detailed Design Miniworld extend refine & map

HIC - What is it? OOA prototyping user-interfaces fit right in –“user-centered interface design” further elaboration of OOA prototyping results –standardize & unify (external) –work on the ergonomics –clean up and structure (internal) refine and map results to infrastructure –versions and variations of layouts –tool-specific changes –everything as discussed for the PDC

HIC tasks classify the humans describe the humans and their task scenarios design the command hierarchy design detailed interaction design the HIC classes design the GUI (Graphical User Interface)

HIC tasks - classify the humans put yourself in someone else’s shoes... –analyze and read –do their job! classiy by –level of skill novice, occasional, intermediate, advanced –organizational level executive, officer, staff,... –membership in groups (roles) customer, salesperson, contractor,...

HIC tasks - describe the humans and their scenarios I for each category consider –who is it (role & organizational level) –purpose job profile, expected help, tools wanted,... –characteristics age, education, limitations, style of work,... –skill level on the job with the computer

HIC tasks - describe the humans and their scenarios II for each category consider –task scenarios look at your OOA scenarios from the “role-perspective” check for completeness (and adapt your model if necessary) prioritize and structure –main scenario vs. less important one’s –what if something goes wrong? –critical factors for success link steps of the tasks to your GUI

HIC tasks - design the command hierarchy I study existing metaphors –model but don’t just copy existing patterns –copy “look and feel” –improve interaction and flexibility establish a command hierarchy –menu screens, menu bar, icons,... –how are your systems’s services presented to the user?

HIC tasks - design the command hierarchy II refine the command hierarchy –ordering frequency or work-step order –whole-part chunking parts and aggregations of services (tasks) –work along short term memory limits –breadth of about three chunks of three (breadth chunking) –depth of about three levels (depth chunking) –fine tune number of clicks and drags provide shortcuts

HIC tasks - design the detailed interaction (checklist) consistency few steps feedback undo do not rely on the end-user how easy is it to learn? look and feel

HIC tasks - design the HIC classes (for a GUI) depends on your model –see above! depends on your infrastructure –well supported maximize reuse –link to existing classes stick to standards

ATM Window Field Deposit Window Withdraw Window Graphic 0,m 1,1 0,m Selector 1,1 0,m Example of - Window Components - Interaction Classes - Links to PDC Account 0,m 1,1

Work with an expert. Check on (G)UI ergonomics. Make it part of your OOA ?!?!