CS 501: Programming Building Fall 1999.

Uploaded on:
Category: Fashion / Beauty
Interface configuration is incompletely a workmanship; there are general standards: ... Client interface advancement may be a noteworthy piece of a product improvement venture ...
Slide 1

CS 501: Software Engineering Fall 1999 Lecture 23 Design for Usability I

Slide 2

Administration  Assignment 4 grades

Slide 3

Software Reuse (Application Packages)  Package underpins a standard application (e.g., finance, client interface to Internet data)  Functionality can be improved by: => arrangement parameters (e.g., table driven) => extensibility at characterized interfaces => custom composed sources code expansions

Slide 4

Reuse and Object Oriented Languages Example: Java is a moderately direct dialect with an exceptionally rich arrangement of class chains of command.  Java programs infer quite a bit of their usefulness from standard classes  Learning and comprehension the classes is troublesome. => Java specialists can compose complex frameworks immediately =>Inexperienced Java developers compose inelegant and carriage programs

Slide 5

Design for Usability of a PC framework is a blend of components:  User interface outline  Functionality  Performance  Help frameworks and documentation  Freedom from blunders Anything else?

Slide 6

Iterative Design Requirements Evaluation Implementation (model) Design

Slide 7

Methods for Evaluation of Usability  Observing clients (client conventions)  Focus bunches  Measurements effectiveness in doing assignments speed  Expert survey  Client\'s conclusions  Competitive examination

Slide 8

Levels of Usability interface plan useful outline information and metadata PC frameworks and systems theoretical model

Slide 9

The Conceptual Model The applied model is the client\'s interior model of what the framework gives:  The work area top illustration - records and envelopes  The web model - click on hyperlinks  The library model - seek and recover  The structure filling model - fill structure, submit Example: The Mercury page turner

Slide 10

Interface Design The interface configuration is the appearance on the screen and the real control by the client  Fonts, hues, logos, console controls, menus, catches  Mouse control or console control?  Conventions (e.g., "back", "help") Example: Screen space use in the Mercury page turner

Slide 11

Principles of Interface Design Interface outline is halfway a workmanship; there are general standards:  Consistency - in appearance, controls, and capacity.  Feedback - what is the PC framework is doing? why does the client see certain outcomes?  Users ought to have the capacity to hinder or switch activities  Error taking care of ought to be straightforward and simple to appreciate  Skilled clients offered alternate ways; beginners have basic, very much characterized alternatives The client ought to feel in control

Slide 12

Disabilities  What if the client: is outwardly impeded or visually challenged? does not communicate in English? is a poor typist?  There is a custom of visually impaired software engineers  Navigation of sites need not be just visual You may have a legitimate prerequisite to bolster individuals with inabilities

Slide 13

Functional Design T he practical outline , decides the capacities that are offered to the client  Selection of parts of an advanced article  S earching a rundown or sorting the outcomes  H elp data  M anipulation of items on a screen  Pan or zoom

Slide 14

Same Functions, Different Interface Example: The work area top analogy  Mouse - 1 catch (Macintosh), 2 catch (Windows) or 3 catch (Unix)  Close catch - left of window (Macintosh) right of window (Windows)

Slide 15

Data and Metadata Data and metadata put away by the PC framework empower the capacities and the interface  The desktop representation has the idea of partner a record with an application. This requires a record sort to be put away with every document: - - expansion to filename (Windows and Unix) - - asset fork (Macintosh)  Data approval regularly requires that a client interface has admittance to a database (e.g., names and addresses)

Slide 16

Computer Systems and Networks The execution, unwavering quality and consistency of PC frameworks and systems is critical to ease of use  Response time instantaneous for mouse following and reverberate of key stroke 5 seconds for straightforward exchanges  Example: Pipelined calculation for the Mercury page turner  Quality of Service for constant data

Slide 17

Design Tensions in Networked Systems  Client PCs and system associations shift enormously in limit  Client programming may keep running on different working frameworks; it might be present or a prior variant  System architects wish to control customers; clients wish to arrange their own particular surroundings

Slide 18

Usability and Cost  Performance might be costly in equipment or uncommon programming advancement  User interface improvement might be a noteworthy part of a product improvement venture  Costs are duplicated if a client interface must be utilized on various PCs or relocate to various forms of frameworks Web programs give a universally useful client interface that others keep up

Slide 19

Extensibility in Web Browsers  Data sorts: helper applications, modules  Protocols HTTP, WAIS, Gopher, FTP, and so on intermediaries  Executable code CGI scripts at server JavaScript at customer Java applets  Style sheets

Slide 20

Reading Before next class, read Sommerville Chapters 17, pages 319 to 346

View more...