1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 12b: User Interface Design Software Engineering: A Practitioner’s Approach, 6/e Chapter.

Slides:



Advertisements
Similar presentations
Chapter 12 User Interface Design
Advertisements

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 slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.1.
Chapter 12 User Interface Design
Chapter 12 User Interface Design
Chapter 12 User Interface Analysis and Design
Chapter 5 Understanding Requirements
Developed by Justin Francisco, SUNY Fredonia USER INTERFACE DESIGN By: Justin Francisco.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
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.
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.
1 CMPS115 Class 6 : User Interface Design Due today –Scenarios –Decomposing paper Next class –Deliverable: Requirements look at template and at example.
Performing User Interface Design
1.  Areas of concern 1. The design of interfaces between software components 2. The design of interfaces between the software and other nonhuman producers.
Software Engineering User Interface
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7 Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.
1 Interface Design Easy to use? Easy to understand? Easy to learn?
These slides are designed to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 12 User Interface Design Highlights of user (human) interface design concepts.
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 slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.1.
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.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
Developed by Reneta Barneva, SUNY Fredonia User Interface Design (Chapter 11)
INFS 6225 Object-Oriented Systems Analysis & Design Chapter 10: Human Computer Interaction Layer.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Chapter 12 Class will start momentarily. Please Stand By … CS 8532: Advanced Software Engineering.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 8: Analysis Modeling Software Engineering: A Practitioner’s Approach, 6/e Chapter.
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.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7: Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e.
1 Chapter 5 Lecture 5: Understanding Requirements Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
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.
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.
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
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.
By Germaine Cheung Hong Kong Computer Institute
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.
Software Engineering B.Tech Ii csE Sem-II Unit-V PPT SLIDES By Hanumantha Rao.N Newton’s Institute of Engineering 1.
Chapter 15 사용자 인터페이스 설계 User Interface Design
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.
Importance of user interface design – Useful, useable, used Three golden rules – Place the user in control – Reduce the user’s memory load – Make the.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.1.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 9: Design Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Programming Techniques Lecture 11 User Interface Design Based on: Software Engineering, A Practitioner’s Approach, 6/e, R.S. Pressman Software Engineering.
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.
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.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7: Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e.
CompSci 280 S Introduction to Software Development
Software Engineering User Interface
User Interface Design The Golden Rules: Place the user in control.
Slide Set to accompany Web Engineering: A Practitioner’s Approach
User Interface Design.
Chapter 15 User Interface Design
Software Engineering: A Practitioner’s Approach, 6/e Chapter 12 User Interface Design copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Chapter 15 User Interface Design
Chapter 12 User Interface Analysis and Design
Chapter 9 Requirements Modeling: Scenario-Based Methods
Chapter 15 User Interface Design
Highlights of user (human) interface design concepts and principles
CS 8532: Advanced Software Engineering
Chapter 5 Understanding Requirements
Chapter 11 User Interface Design
Chapter 5 Understanding Requirements
Interface Design Easy to learn? Easy to use? Easy to understand?
Chapter 11 User Interface Design
Chapter 11 User Interface Design.
COSC 4406 Software Engineering
Presentation transcript:

1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 12b: User Interface Design Software Engineering: A Practitioner’s Approach, 6/e Chapter 12b: User Interface Design copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited.

2 Interface Analysis Interface analysis means understanding Interface analysis means understanding (1) the people (end-users) who will interact with the system through the interface; (1) the people (end-users) who will interact with the system through the interface; (2) the tasks that end-users must perform to do their work, (2) the tasks that end-users must perform to do their work, (3) the content that is presented as part of the interface (3) the content that is presented as part of the interface (4) the environment in which these tasks will be conducted (4) the environment in which these tasks will be conducted.

3 User Analysis Are users trained professionals, technician, clerical, or manufacturing workers? Are users trained professionals, technician, clerical, or manufacturing workers? What level of formal education does the average user have? What level of formal education does the average user have? Are the users capable of learning from written materials or have they expressed a desire for classroom training? Are the users capable of learning from written materials or have they expressed a desire for classroom training? Are users expert typists or keyboard phobic? Are users expert typists or keyboard phobic? What is the age range of the user community? What is the age range of the user community? Will the users be represented predominately by one gender? Will the users be represented predominately by one gender? How are users compensated for the work they perform? How are users compensated for the work they perform? Do users work normal office hours or do they work until the job is done? Do users work normal office hours or do they work until the job is done? Is the software to be an integral part of the work users do or will it be used only occasionally? Is the software to be an integral part of the work users do or will it be used only occasionally? What is the primary spoken language among users? What is the primary spoken language among users? What are the consequences if a user makes a mistake using the system? What are the consequences if a user makes a mistake using the system? Are users experts in the subject matter that is addressed by the system? Are users experts in the subject matter that is addressed by the system? Do users want to know about the technology the sits behind the interface? Do users want to know about the technology the sits behind the interface?

4 Task Analysis and Modeling Answers the following questions … Answers the following questions … What work will the user perform in specific circumstances? What work will the user perform in specific circumstances? What tasks and subtasks will be performed as the user does the work? What tasks and subtasks will be performed as the user does the work? What specific problem domain objects will the user manipulate as work is performed? What specific problem domain objects will the user manipulate as work is performed? What is the sequence of work tasks—the workflow? What is the sequence of work tasks—the workflow? What is the hierarchy of tasks? What is the hierarchy of tasks? Use-cases define basic interaction Use-cases define basic interaction Task elaboration refines interactive tasks Task elaboration refines interactive tasks Object elaboration identifies interface objects (classes) Object elaboration identifies interface objects (classes) Workflow analysis defines how a work process is completed when several people (and roles) are involved Workflow analysis defines how a work process is completed when several people (and roles) are involved

5 Swimlane Diagram

6 Analysis of Display Content Are different types of data assigned to consistent geographic locations on the screen (e.g., photos always appear in the upper right hand corner)? Are different types of data assigned to consistent geographic locations on the screen (e.g., photos always appear in the upper right hand corner)? Can the user customize the screen location for content? Can the user customize the screen location for content? Is proper on-screen identification assigned to all content? Is proper on-screen identification assigned to all content? If a large report is to be presented, how should it be partitioned for ease of understanding? If a large report is to be presented, how should it be partitioned for ease of understanding? Will mechanisms be available for moving directly to summary information for large collections of data. Will mechanisms be available for moving directly to summary information for large collections of data. Will graphical output be scaled to fit within the bounds of the display device that is used? Will graphical output be scaled to fit within the bounds of the display device that is used? How will color to be used to enhance understanding? How will color to be used to enhance understanding? How will error messages and warning be presented to the user? How will error messages and warning be presented to the user?

7 Interface Design Steps Using information developed during interface analysis (SEPA, Section 12.3), define interface objects and actions (operations). Using information developed during interface analysis (SEPA, Section 12.3), define interface objects and actions (operations). Define events (user actions) that will cause the state of the user interface to change. Model this behavior. Define events (user actions) that will cause the state of the user interface to change. Model this behavior. Depict each interface state as it will actually look to the end-user. Depict each interface state as it will actually look to the end-user. Indicate how the user interprets the state of the system from information provided through the interface. Indicate how the user interprets the state of the system from information provided through the interface.

8 Interface Design Patterns Patterns are available for Patterns are available for The complete UI The complete UI Page layout Page layout Forms and input Forms and input Tables Tables Direct data manipulation Direct data manipulation Navigation Navigation Searching Searching Page elements Page elements e-Commerce e-Commerce

9 Design Issues Response time Response time Help facilities Help facilities Error handling Error handling Menu and command labeling Menu and command labeling Application accessibility Application accessibility Internationalization Internationalization

10 Design Evaluation Cycle