Showing posts with label Wong Mann Ee. Show all posts
Showing posts with label Wong Mann Ee. Show all posts

Tuesday, December 27, 2011

Week 10 / Eighth Lecture : System prototyping, types and methods. [Wong Mann Ee]

Lecturer : Madam Mastura
Date : 20 Dec 2011



Prototyping



Prototyping is the process of building a model of a system. In terms of an information system, prototypes are employed to help system designers build an information system that intuitive and easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis phase of the systems development life cycle.


During the requirements determination portion of the systems analysis phase, system analysts gather information about the organization's current procedures and business processes related the proposed information system. In addition, they study the current information system, if there is one, and conduct user interviews and collect documentation. This helps the analysts develop an initial set of system requirements.


Prototyping can augment this process because it converts these basic, yet sometimes intangible, specifications into a tangible but limited working model of the desired information system. The user feedback gained from developing a physical system that the users can touch and see facilitates an evaluative response that the analyst can employ to modify existing requirements as well as developing new ones.


Prototyping comes in many forms - from low tech sketches or paper screens(Pictive) from which users and developers can paste controls and objects, to high tech operational systems using CASE (computer-aided software engineering) or fourth generation languages and everywhere in between. Many organizations use multiple prototyping tools. For example, some will use paper in the initial analysis to facilitate concrete user feedback and then later develop an operational prototype using fourth generation languages, such as Visual Basic, during the design stage.



Some Advantages of Prototyping:
-Reduces development time.
-Reduces development costs.
-Requires user involvement.
-Developers receive quantifiable user feedback.
-Facilitates system implementation since users know what to expect.
-Results in higher user satisfaction.
-Exposes developers to potential future system enhancements.
Some Disadvantages of Prototyping:
-Can lead to insufficient analysis.
-Users expect the performance of the ultimate system to be the same as the prototype.
-Developers can become too attached to their prototypes
-Can cause systems to be left unfinished and/or implemented before they are ready.
-Sometimes leads to incomplete documentation.
-If sophisticated software prototypes (4th GL or CASE Tools) are employed, the time saving benefit of prototyping can be lost.

Reference: http://www.umsl.edu/~sauter/analysis/prototyping/intro.html a

Wednesday, December 14, 2011

Week 9 / Seventh Lecture : Design, Prototyping and Construction. [Wong Mann Ee]

Lecturer : Madam Mastura
Date : 13 Dec 2011


What is a prototype?
-A prototype is an early sample or model built to test a concept or process or to act as a thing to be replicated or learned from.

-In Interaction Design it can be (among other things):
  • a series of screen sketches
  • a storyboard, i.e. a cartoon-like series of scenes 
  • a PowerPoint slide show
  • a video simulating the use of a system
  • a lump of wood (e.g. Palm Pilot)
  • a cardboard mock-up
  • a piece of software with limited functionality written in the target language or in another language

-In other design fields a prototype is a small-scale model:

  • a miniature car
  • a miniature building or town

Why prototype?
  • Evaluation and feedback are central to interaction design
  • Stakeholders can see, hold, interact with a prototype more easily than a document or a drawing
  • Team members can communicate effectively
  • You can test out ideas for yourself
  • It encourages reflection: very important aspect of design
  • Prototypes answer questions, and support designers in choosing between alternatives
What to prototype?
  • Technical issues
  • Work flow, task design
  • Screen layouts and information display
  • Difficult, controversial, critical areas
Summary
  1. Prototyping may be low fidelity (such as paper-based) or high fidelity (such as software-based)
  2. High-fidelity prototypes may be vertical or horizontal.
  3. Low-fidelity prototypes are quick and easy to produce and modify and are used in the early stages. There are two aspects to the design activity: conceptual design and physical design.
  4. Conceptual design develops a model of what the product will do and how it will behave, while physical design specifies the details of the design such as screen layout and menu structure.
  5. We have explored three perspectives to help you develop conceptual models: an interaction paradigm point of view, an interaction mode point of view, and a metaphor point of view.
  6. Scenarios and prototypes can be used effectively in conceptual design to explore ideas.
  7. We have discussed four areas of physical design: menu design, icon design, screen design and information display.
  8. There is a wide variety of support tools available to interaction designers.

Sunday, December 11, 2011

Week 8 / Sixth Lecture : Identifying Needs and Establishing Requirements. [Wong Mann Ee]

Lecturer : Miss Edina
Date : 6 Dec 2011


Requirement




What are Requirements?
A requirement is a statement that specifies what an intended product should do, or 
how it should perform. 

● Specific, unambiguous, clear
– Time to download any page is less than 5
seconds on a DSL line of 20Mbits/second
– The playback bar should always indicate the 
position in the audio stream
● Too vague 
– Appealing to teenage girls (too vague) 
– The buttons should be engaging




Different kinds of requirement
● Functional
– Functional requirements specify what the system should do
– Historically the main focus of requirements 
activities 
– Examples: word processor must support variety of formatting styles, Calculate 
                  total cost of purchases
● Non­-Functional
– Non-Functional requirements specify what constraints there are on the system or its 
development.
– Run on a variety of platforms
– Function on 64M of RAM
– Delivered in 6 months


*Interaction design requires us to understand both the functionality required and the 
constraints for development or operation of the product.*


Different Requirements

● Environment or context of use 
– Physical ( Dusty ? Noisy ? Vibrations ? Light ? Heat ? Humidity ? )
Example:Noisy and busy environment, users maybe talking while using the system
– Social : Sharing of files, displays, privacy, locking
– Organizational: Hierarchy, IT departments, user support,
communications structure, availability of training
– Users
   ● Novice : step-­by-­step, constrained, clear information
   ● Expert  : flexibility, access, power
   ● Frequent: short cuts
   ● Casual/infrequent: clear instructions, menu paths
Example: Majority of users under 25,comfortable dealing 
              with technology. 
● Usability
– Learnability, flexibility, throughput 
Example: Simple for new users, memorable for frequent users, efficient, 
              deal easily with user errors 
●IMPORTANT
– User requirements and usability requirements 
refer to different things.
● Kinds of requirements 
– What factors (enviornmental, user, usability) ?
    ● Self­service cafeteria ­ paying using credit system 
    ● Nuclear plant control room
    ● Distributed car design team





Thursday, November 24, 2011

Week 6 | 5th Lecture: User Centered Design. [Wong Mann Ee]

Lecturer : Miss Edina
Date : 22 Nov 2011


User-Centered Design


User-Centered Design process (UCD) is also called Human-centered design process.

"User-Centered Design (UCD) is a user interface design process that focuses on usability goals, user characteristics, environment, tasks, and workflow in the design of an interface. UCD follows a series of well-defined methods and techniques for analysis, design, and evaluation of mainstream hardware, software, and web interfaces. The UCD process is an iterative process, where design and evaluation steps are built in from the first stage of projects, through implementation." (Shawn Lawton Henry and Mary Martinson, Accessibility in User-Centered Design)



In UCD, all "development proceeds with the user as the center of focus." (Jeffrey Rubin, Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests, John Wiley and Sons, Inc., 1984) Rubin depicts the User-Centered Design Process as follows:

  • The users are in the center of a double circle.
  • The inner ring contains: Context; Objectives; Environment and Goals.
  • The outer ring contains: Task Detail; Task Content; Task Organization and Task Flow.




UCD Process Steps

While the basic principles and techniques are the same, different variations of user-centered design processes exist. The following example is typical of a UCD process for designing Web applications.


1. Analysis
-Vision, goals, objectives
        Image (feeling)
        Challenges and constraints
-User/Audience analysis
User Categories List
User Categories Matrix with knowledge, experience, and skill (KES) in www, accessibility, html, etc.; connection, environment; hardware, software; AT; frequency of use
Profiles (details, facts, figures)
Personas/Characterizations (made up "person" with name, etc.)
Technique: Field studies, contextual inquiry
-Task/Purpose analysis
Task List
User-Task Matrix
-Information architecture analysis
Content list
Content-User Matrix
Hierarchy, Web relationships
-Workflow analysis
Workflow
Scenarios
2. Design
 - add the usability iceberg image 10% presentation, 30% interaction, 60% conceptual model.
- Conceptual/Mental model, metaphors, design concepts
- Navigation design
- Storyboards, wireframes
- Detailed design
- Paper prototypes
- Online mockups
- Functional online prototypes
3. Evaluation (iterate back to Design)
- Design walkthoughs ("cognitive walkthroughs")
- Heuristic evaluation
- Guidelines reviews
- Usability testing - paper, low fidelity - high fidelity; informal - formal
4. Implementation
5. Deployment



Friday, November 18, 2011

Week 5 / Fourth Lecture: Layout design, screen assets, graphic design basics. [Wong Mann Ee]

Lecturer : Mr Radzi.Bedu 
Date : 15 Nov 2011





Graphic design is a creative process, most often involving a client and a designer and usually completed in conjunction with producers of form undertaken in order to convey a specific message(s) to a targeted audience. 
The term "graphic design" can also refer to a number of artistic and professional disciplines that focus on visual communication and presentation. The field as a whole is also often referred to as Visual Communication or Communication Design. Various methods are used to create and combine words, symbols, and images to create a visual representation of ideas and messages. A graphic designer may use typography, visual arts and page layout techniques to produce the final result. Graphic design often refers to both the process (designing) by which the communication is created and the products (designs) which are generated.
Common uses of graphic design include identity (logos and branding), web sites, publications (magazines, newspapers, and books), advertisements and product packaging. For example, a product package might include a logo or other artwork, organized text and pure design elements such as shapes and color which unify the piece. Composition is one of the most important features of graphic design, especially when using pre-existing materials or diverse elements.

Tuesday, November 8, 2011

Week 4 / Third Lecture: Understanding and conceptualising interaction [Wong Mann Ee]

Lecturer : Miss Edina
Date : 8 Nov 2011



    Four principles for screen interfaces:
    1. Follow conventional usage, both in the choice of images and the allowable interactions.

    Convention severely constrains creativity. Following convention may also violate intellectual property laws. Sometimes we wish to introduce a new
    kind of action for which there are, as yet, no accepted conventions. On the whole, however, unless we follow the major conventions, we are
    doomed to fail. Those who violate conventions, even when they are convinced that their new method is superior, are doomed to fail. (You cannot
    successfully introduce a non-qwerty keyboard today, or reverse the window scroll bar convention, or suddenly require double-clicking on web
    links. For better or for worse, human culture changes slowly, if at all.)

    2. Use words to describe the desired action (e.g., "click here" or use labels in front of perceived objects).

    This is, of course, why menus can be relatively easy to understand: the resulting action is described verbally. (Of course, the method of using the
    menu has to be learned, and the text still has to be chosen with care -- and user tested.)

    Words alone cannot solve the problem, for there still must be some way of knowing what action and where it is to be done. This requires a
    convention of highlighting, or outlining, or depiction of a actionable object. It is also well known that single word labels fail for most people --
    everyone has a favorite word, but the variety of preferred words is overwhelming. Words also cause problems with international adoption. Thus,
    road signs often use graphics -- an international standard on road sign graphics exists. Alas, most people do not understand those standards. It is
    also the case that words are understood more quickly than graphics -- even a well known, understood graphic. Words plus graphics are even more
    readily understood.

    3. Use metaphor.

    Metaphor is both useful and harmful. I personally believe that metaphors are more harmful than useful, but this is a different topic for a different
    day. For today's topic, the problem with metaphor is that not all users may understand the point. Worse, they may take the metaphor too literally
    and try to do actions that were not intended. Still, this is one way of training users.

    4. Follow a coherent conceptual model so that once part of the interface is learned, the same principles apply to other parts.

    Coherent conceptual models are valuable and, in my opinion, necessary, but there still remains the bootstrapping problem; how does one learn the
    model in the first place? -- why by conventions, words, and metaphors.

    Design and usability principles
    • Visibility 
    • Feedback 
    •  Constraints
    • Mapping
    • Affordance 
    • Consistency


    The word "affordance" was originally invented by the perceptual psychologist J. J. Gibson (1977, 1979) to refer to the actionable properties between the world and an actor (a person or animal). To Gibson, affordances are a relationship. They are a part of nature: they do not have to be visible, known, or desirable. Some affordances are yet to be discovered. Some are dangerous. I suspect that none of us know all the affordances of even everyday objects.



    In product design, where one deals with real, physical objects, there can be both real and perceived affordances, and the two need not be the same.
    In graphical, screen-based interfaces, all that the designer has available is control over perceived affordances. The computer system, with its
    keyboard, display screen, pointing device (e.g., mouse) and selection buttons (e.g., mouse buttons) affords pointing, touching, looking, and
    clicking on every pixel of the display screen. Most of this affordance is of no value. Thus, if the display does not have a touch-sensitive screen, the
    screen still affords touching, but it has no result on the computer system. Mind you, the affordance still has impact: it is useful in multiple-person
    communication, and it helps aid the sale of screen-cleaning tissues and fluids. All screens afford touching: only some detect the touch and are
    capable of responding. But the affordance of touchability is the same in all cases. Touch sensitive screens often make their affordance visibly
    perceivable by displaying a cursor under the pointing spot. The cursor is not an affordance; it is visual feedback.

    In graphical design, one is really talking about conventions, or what I called logical and cultural "constraints" in POET. Physical constraints are
    closely related to real affordances: Thus, it is not possible to move the cursor outside the screen: this is a physical constraint. Logical constraints
    use reasoning to determine the alternatives. Thus, if we ask the user to click on 5 locations and only 4 are immediately visible; the person knows,
    logically, that there is still location left.


    Cultural constraints are learned conventions that are shared by a cultural group. The fact that the graphic on the right hand side of a display is a
    "scroll bar" and that one should move the cursor to it, hold down a mouse button, and "drag" it downward in order to see objects located below the
    current visible set (thus causing the image itself to appear to move upwards) -- all this is a cultural, learned convention. The choice of action is
    arbitrary: there is nothing inherent in the devices or design that requires the system to act in this way.


    In all scrolling bars I have seen, there is a physical constraint as well: the vertical scroll bar only moves vertically, not horizontally. Once again, these cultural constraints are arbitrary. The scroll bar could have been designed very differently. It could have been located on the left, or the top,
    or as a button. Today, its action follows the "outside-in" convention, but in the early days, a number of designs used the "inside-out" convention, so that moving the scroll bar down caused the text to move downwards, exposing the new text at the top of the screen. Today if we were to use that convention, it would be confusing, but only because the convention has already been established. (Some drawing programs still follow that earlier convention and they have adopted the convention of a "hand" graphic to signal that moving the cursor upwards "grabs the text" and moves it upward as well. )
    All this is cultural convention, not affordances.


    In the world of design, what matters is:
    If the desired controls can be perceived
    1.a. In an easy to use design, if they can both readily be perceived and interpreted
    If the desired actions can be discovered
    2.a. Whether standard conventions are obeyed
    In a game, the designer may deliberately violate the A principles (1A and 2A). Sometimes, even in effective, mass-consumer designs, it is useful to
    violate these principles. Thus, sometimes there are "back doors" for those who maintain the system, and it is not desirable that the average user
    know of their existence. But if the user is to be effective at, these principles should be followed.



    Thursday, November 3, 2011

    Week 3 / Second Lecture: Human to machine interaction [Wong Mann Ee]

    Lecturer : Miss Edina
    Date : 1 Nov 2011


    The Human-Machine Interface (ak.a: Man-Machine Interface) is quite literally where the human and the machine meet. It is the area of the human and the area of the machine that interact during a given task. Interaction can include touch, sight, sound, heat transference or any other physical or cognitive function. For Examples: A typical computer station will have four human-machine interfaces, the keyboard (hand), the mouse (hand), the monitor (eyes) and the speakers (ears). Whenever a user pushes a button, turns a switch, clicks with a mouse, writes a command, or in any other way issues a command to a machine, there must be a feedback telling the user that the command has been understood. The feedback can be a sound, a lamp lighting, a text on a screen, etc. The ideal form of feedback is allowing the user to see things happen.



    General Principles:
    • Feedback to user
    • The user should be in control
    • Predictability
    • Transparency
    • Never interrupt the user
    • Can I guess what the user wants?
    • Error tolerance
    • WYSIWYG
    • Speak the user's language
    • Avoid anthropomorphic interfaces
    • Design should reflect the user's logic, not the constructor's logic
    • The design of a button should reflect its importance
    • Provide alternative ways out of a situation
    • Accessibility to handicapped users
    • Novices versus experienced users
    • Standardization
    • Open standards
    Human-machine interaction engineering is to produce a user interface which makes it easy, efficient, and enjoyable to operate a machine in the way which produces the desired result. This generally means that the operator needs to provide minimal input to achieve the desired output, and also that the machine minimizes undesired outputs to the human. 


    How Interfaces Affect Usage and Users??



      Expressive interfaces

      •          What makes us happy, sad, annoyed, anxious, frustrated, motivated, delirious and so on
      –        translating this into different aspects of the user experience
      •          Why people become emotionally attached to certain products (e.g. virtual pets)
      •          Can social robots help reduce loneliness and improve wellbeing?
      •          How to change human behavior through the use of emotive feedback 

      User-created expressiveness
      •          Users have created a range of emoticons - compensate for lack of expressiveness in text communication:
      Happy  :)
      Sad  :<
      Sick :X
      Mad  >:
      Very angry >:-(
      •          Also use of icons and shorthand in texting and instant messaging has emotional connotations, e.g.
      “LOL, I 12 CU 2NITE “


      Frustrating interfaces
      Causes:
      -When an application doesn’t work properly or crashes
      -When a system doesn’t do what the user wants it to do
      -When a user’s expectations are not met
      -When a system does not provide sufficient information to enable the user to know what to do 
      -When error messages pop up that are vague, obtuse or condemning
      -When the appearance of an interface is garish, noisy, gimmicky or patronizing
      -When a system requires users to carry out too many steps to perform a task, only to discover a mistake was made earlier and they need to start all over again

      Anthropomorphism
      -Attributing human-like qualities to inanimate objects (e.g. cars, computers)
      -Well known phenomenon in advertising 
      (Dancing butter, drinks, breakfast cereals)
      -Much exploited in human-computer interaction
      (Make user experience more enjoyable, more motivating, make people feel at ease, reduce anxiety)


      Criticism of anthropomorphism
      •          Deceptive, make people feel anxious, inferior or stupid
      •          People tend not to like screen characters that wave their fingers at the user and say:
      –        Now Chris, that’s not right. You can do better than that.Try again.”
      •          Many prefer the more impersonal:
      –        “Incorrect. Try again.”
      •          Studies have shown that personalized feedback is considered to be less honest and makes users feel less responsible for their actions (e.g. Quintanar, 1982)


      Summary:

      •          Emotional interaction is concerned with how interactive systems make people respond in emotional ways
      •          Well-designed interfaces can elicit good feelings in users
      •          Expressive interfaces can provide reassuring feedback
      •          Badly designed interfaces make people angry and frustrated
      •          Anthropomorphism is the attribution of human qualities to objects
      •          An increasingly popular form of anthropomorphism is to create interface agents and robot pets
      •          Models of affect provide a way of conceptualizing emotional and pleasurable aspects of interaction design


      Resource: Wikipedia, Compendium on user-friendly design by A. Fog, Copenhagen University College of Engineering, 2000., Interaction Design: beyond human-computer interaction (3rd edition)

      Friday, October 28, 2011

      Week 2 / First Lecture: Interaction Design and HCI [Mann Ee]

      Lecturer : Miss Edina
      Date : 25 Oct. 2011




      Interaction design is....

      •  about creating interventions in often complex situations using technology of many kinds including PC software, the web and physical devices. 

        "Interaction design as a design discipline"

      •  designing interactive products to support the way people communicate and interact in their everyday and working lives.   –Sharp, Rogers and Preece (2011)

        "Interaction design as an extension of HCI"

      • The design of spaces for human communication and interaction. –Winograd (1997)



      HCI is an acronym which stands for Human Computer Interaction

      Human–computer Interaction (HCI) is the study,planning and design of the interaction between users and computers. .HCI is also sometimes referred to as man–machine interaction(MMI) or computer–human interaction(CHI). -wikipedia
      HCI is concerned with understanding how people make use of devices and systems that incorporate or embed computation, and how such devices and systems can be more useful and more usable. -Carroll (2003)


      A timeline that showcase the past, present and future of Human Computer Interaction (HCI).
      Past : 
      1943 ENiac(1st computer) 
      1964 The First Mouse
      1981 Xerox star
      1985 Microsoft Windows 1.0
      1989 Nintendo gameboy
      1994 - Sony playstation1
      1995 Windows 95
      Present : PS3, ipad, iphone , macbook, waterproof keyboard, microsoft surface..
      Future : ???





      HCI and Interaction Design
      How Interaction Design relates to Human-Computer Interaction and other fields??