Built-In Usability: A Usage-Centered Design Approach Chapter 2 Betty Wilkins 02/07/06.

Slides:



Advertisements
Similar presentations
IMS5401 Web-based Systems Development Topic 3: Development for the web 3(f) Implications of issues in web site design.
Advertisements

Taavi Tamberg What is screen? Device User Interface Information Service Innovation.
Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Chapter 7 Structuring System Process Requirements
Lesson-16 Systems Analysis(2)
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
8.
1 Agenda: 09/01/2011 Finish preparing information visualization methods. Tables, diagrams, charts, bullet points Words vs. pictures vs. numbers Visualization.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Chapter 7 design rules.
Universal Access to Technology. User-centered system Design is iterative! DESIGN TEST.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Chapter 13: Designing the User Interface
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Architectural Design.
System Analysis & Design
1. Human – the end-user of a program – the others in the organization Computer – the machine the program runs on – often split between clients & servers.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Agile Design Exploration: User Interface Concepts for Future Navigation Systems Volker Paelke, Karsten Nebe Leibniz University Hannover, University of.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
Chapter 7 Structuring System Process Requirements
Copyright © 2003 Pearson Education, Inc. Chapter 8 – Slide 1 by Michael Kay The Web Wizard’s Guide to Flash.
RUP Implementation and Testing
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
Output and User Interface Design
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Chapter 3: Managing Design Processes
10 Software Architecture CSCU 411 Software Engineering.
Comp 15 - Usability & Human Factors Unit 8a - Approaches to Design This material was developed by Columbia University, funded by the Department of Health.
Design Rules-Part B Standards and Guidelines
Content The system development life cycle
INTRO TO USABILITY Lecture 12. What is Usability?  Usability addresses the relationship between tools and their users. In order for a tool to be effective,
1 The Five Parts of an Information System
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Example Template for Project Presentation
Requirement Handling
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
Software Design: Principles, Process, and Concepts Getting Started with Design.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a: Architectural Design Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a:
Java Software Solutions Lewis and Loftus Chapter 15 Copyright 1997 by John Lewis and William Loftus. All rights reserved. 1 Software Development Process.
1 Class exercise II: Use Case Implementation Deborah McGuinness and Peter Fox CSCI Week 8, October 20, 2008.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Software Engineering Lecture 10: System Engineering.
Supporting the design of interactive systems a perspective on supporting people’s work Hans de Graaff 27 april 2000.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Presented by the GMU Win-Win Team March 17, 2004 Status Report.
Systems Analysis & Design David Walkiewicz March 31, 2012.
DOCUMENTATION REF: Essentials of IT (Hamilton et al) Chapter 1.
Chapter 7: Designing solutions to problems OCR Computing for A Level © Hodder Education 2009.
Design rules.
Systems Analysis and Design: What is it?
HCI – DESIGN RATIONALE 20 November 2018.
Usability Techniques Lecture 13.
Systems Engineering for Mission-Driven Modeling
Chapter 7 design rules.
Chapter 7 design rules.
Chapter 7 design rules.
Chapter 26 Estimation for Software Projects.
Chapter 7 design rules.
Presentation transcript:

Built-In Usability: A Usage-Centered Design Approach Chapter 2 Betty Wilkins 02/07/06

2 Topics  Interfacing with Users  Elements of a Usage-Centered Approach  Driving Models  Coordinated Activity

3 Interfacing with Users  Users (end users) Originally were not allowed near early computers Operators and service technicians (not really “users”)  Inputs/Outputs Punched cards (input) Printed reports (output)

4 Interfacing with Users  User Interface Keyboard and keypad  Betty Holberton, Jean Bartik Terminals, minicomputers Timesharing  User-centered Design Shift from technical interface to issues of the user  Usage-centered Design User-centric design (Norman, et. al) Shift to “usage”-centered focusing on the “work” to be accomplished and “how” it is accomplished

5 Elements of a Usage-Centered Approach 1.Pragmatic Design Guidelines Rules of Usability:  General character of well-defined, usable systems  Broad, overall directions for user interface design Principles  Narrower guidance on more specific issues in software usability 2.Model-driven Design Process Nature of uses of system Organization of user interface

6 Elements of a Usage-Centered Approach 3.Organized Development Processes Scaled to suit project size and scope Flexible to suit objectives and constraints 4.Iterative Improvement Successive refinements, inspections, testing 5.Measures of Quality Software metrics Augment inspections, testing

7 Driving Models Help developers to organize their thinking  Attractive Abstractions Attention on larger picture Innovation, imagination  Essentials Models Requirements apart from data structures and algorithms Capture essence of problems through abstract descriptions Highlight purpose – what & why Fewer elements and features; simpler and smaller

8 Driving Models  Architecture of Interfaces Overall structure, total organization Lead up to physical design  Multiple Views Users, their work (usage), user interface  Models Role model – role users can play Task model – tasks to accomplish Content model – tools and materials Operational model – context system is used Implementation model – visual design of interface  Generally Simple

9 Coordinated Activity  Design Activity Model – p 34  Flexible Staging Rearranged, expanded, compressed, omitted  Order and Chaos Feed-forward/work-back Deferred decisions

10 Summary  Interfacing with Users  Elements of a Usage-Centered Approach  Driving Models  Coordinated Activity