SE4d03CS4HC3SE 6D03 Design of the User Interface

Document Sample
SE4d03CS4HC3SE 6D03 Design of the User Interface Powered By Docstoc
      Design of the User Interface
• Dr Baber s Overview:
  – The Problems
     • Too many human computer interfaces (HCI) are
       designed by computer specialists, which end up being
          d i t ti      ll by       t       i li t
       used unintentionally, b computer specialists.
     • Although the computer specialist designers often
            i   l try to design the human computer i t f
       consciously t t d i th h                t interfaces
       for other categories of users, it is very difficult for
                                jump                  skins
       computer specialists to "jump out of their own skins" and
       realize how others will use and interact.

                                se4d03                           slide L1-1

        Dr.Baber’s View of HCI -- I

• More Problems:
   – The designers all too often cannot imagine the
     often very different attitudes, background,
     psychology knowledge and expectations of the
     ultimate end-users of the systems they design.
   – The designer usually implicitly assumes that the
     user will form the same mental model of the
     system that the designer had in mind.
   – Often, however, the user forms a very different
     mental model of the system.
     Different users form quite different mental models.
   – Diff    t        f        it diff   t    t l  d l

                                se4d03                           slide L1-2
          Dr.Baber’s View of HCI -- II

 • More thoughts:
     – It is, of course, necessary to consider technical
       possibilities and limitations when designing a
       human computer interface, but this is never
     – Many technically good system designs have been
       rejected in practice because they do not
       adequately cater for the users' subjective as well
             bj ti        d d i        d limitations.
       as objective needs, desires and li it ti
     – Also, software issues (e.g. testing, maintainability,
       etc ) arising from the human computer interface
       design must be considered in practice.

                                se4d03                       slide L1-3

             Dr.Baber’s Considerations
             (               )
         and (MY MAJOR TOPICS) for this course

• The involved Software/Computer Specialist must therefore:
   – learn about the relevant aspects of human psychology
   – the variety of uses (intended and unintended) to which the systems
     they design might be put,
   – the variety of ways users might interact with those systems
     (                                                   ),
   – understand the impossibility of predicting how the various types of
     users will view the system and what they will expect of it,
   – the need for obtaining information, views and feedback from
     representatives of all intended and expected types of users when
     designing human computer interfaces,
   – The impact of hardware and software for implementing human
     computer interfaces and their advantages, limitations and
     i li ti                                      SYSTEMS--PSS)
                                se4d03                       slide L1-4
  in the

                         se4d03                slide L1-5

 Our Approach to Tackle these Problems
  • In this course we shall program GUI’s using a
    Visual Programming Language and learn
               g        g     g g
    about the interface by doing.
  • We shall examine current concepts, theories
    and models employed in the discipline.
  • We will discuss case studies where
    spectacular events have occurred due to HCI
    / end-user mismatches.
  • We shall take particular note of the graphical
    nature of the WWW and its impact on HCI by
                                   p              y
    programming in script, wikis and virtual reality
        g g

                         se4d03                slide L1-6
    SE4D03 – Computer User Interfaces
    Change of th T diti
• A Ch                              l Lecture P
                    f the Traditional L t     Pace (even before
  we really get started)
     NOTE:               that      i         i        f the t d t
   – NOTE we assume th t previous experiences of th student
     with coding language has already been mastered; therefore
     only the idiosyncrasies of this language will be highlighted
     in this course pack for completeness (See the Appendices)
     but NOT be part of these lectures. It is the responsibility of
     the t d t t l        th l             t       h
     th student to learn the language syntax as homework and k d
     through assignment completion. (Syntax and Examples can be
     found in the quoted supplementary materials such as in the three
                  q        pp        y
     Appendices of this course pack and (“How-to” books) listed in the
     Course Outline.).

                                     se4d03                           slide L1-7

           SE4D03 Course Logistics -- I
    W d b t
     • When ANY code is submitted for marking, it will always “count” to have it
       well documented with comments. At the very least, for every coded
       statement, there should be at least, located somewhere, one line of
       documentation for it; in other words, 50% of any code listing MUST contain
       that many comments -- the remainder being raw (valid) language
     • For those of you that require more motivation, then consider this: Any
       code written for marks (be it assignment, test or exam) whose operation is
       not properly communicated to the marker will be assigned reduced marks
       EVEN IF the source language code itself is technically correct! If you
       cannot tell us what you are doing with the code then YOU are part of the
       problem in Software Engineering!
• The SE4D03 web site as a Resource
  – At this point do NOT forget the WWW site Examples Section
  – The are worked VB programs for download, execution or examination.
     • Student assignment submissions done in VB do NOT require adherence to
       the Microsoft Naming Conventions (Eg. Prefix fra- for a FORM object, or
             for t t l       t t )
       txt- f a text element, etc.)

                                     se4d03                           slide L1-8
          SE4D03 Course Logistics -- II
• Material requirements to be included in the assignment
  solution submissions as listed below:
   – Printout of User-created Electronic Files
                                                    t t li ti   for d
       • LISTINGS -- VISUAL BASIC or C# or J# output listings f code.
       • COMPLIANCE REPORT -- use of a word processor for generating a
         technical report which explains how the code creates a User Interface and
         why that interface solves the assignment problem
           – Included should be a series of “screen dumps” to aid in the explanation
             process. (These are to be labeled with Figure Captions.)
           – the answer to any embedded questions which are given in the assignment.
       • README file – this contains the following:
           – student name and number
           – the environment used to execute the code (model & version #),
                     filenames necessary t run your solution i th f
             source fil                     to                                f
                                                          l ti in the form of a
             directory listing of what is supposed to be in the file (filenames and
             subdirectory names and contents).
   – Submission
       • Place the printed output in a stapled set and hand-in to the CORRECTLY
         labeled drop boxes (CS4HC3 and SE4D03/6D03) that are found just
         outside the CAS Drop-in-Centre at ITB-101 (known affectionately as the
         DIC) in the main hall of ITB before the due date and time.

                                     se4d03                             slide L1-9

         SE4D03 Course Logistics -- II
  • Accessing CAS Resources:
     – for those who are transfers or exchange students,
       the ITB (Information Technology Building – not to be
       confused with the adjacent building which is the new
       Engineering Technology Building (        )) s usua y
          g ee g ec o ogy u d g (ETB)) is usually
       open most days (except holidays) for 12 or so hours
       (Fridays and Saturdays are slightly less).
                                      us,           ITB-235
     – accessing CAS facilities (for us it is room ITB 235
       which have computers equipped with Visual Studio
       and other support programs) requires a key card
         ih           i    i      h b k Th ld “key fob”
       with a magnetic strip on the back. The old “k f b”
       or flat metal button that previously open the doors
       has now been phased out.
     – Key cards can be obtained from the Engineering
       DocuCentre, JHE-201, 2nd floor, right above the
       main entrance of the old Engineering Building
                                     se4d03                            slide L1-10
           SE4D03 –
         • The is the main
           magazine for the
           Association for
           Co put g
           Machinery (but
           people can join too!)
         • This is a recent
           edition where "end-
           user" computing via
              f        l i    is
           software solutions i
         • Are SE's obsolete
                SE s
se4d03               slide L1-11

Shared By: