Computing and Software Wiki - User contributions [en]

User:Skip

2009-11-24T16:19:10Z

Hamilr3: /* Topics: */

= Human Computer Interaction =

=='''This is the projects main page for cs4hc3 and se4f03''' -- ''HCI / CHI'' Courses.==

===Objectives===

===Logistics===
<ul>
<li>
During the middle of term the class will be divided into about 12 (n) groups, each of whom will negotiate amongst
themselves a topic of concentration from the list below with at least three ranked by selected priority.
At an early designated lecture, each group will be linked to a topic of their choice in a first-come/first-served
basis -- only one group per project.
</li>
<li>
Group members should all have their associated member email addresses and use these to generate a wiki in one of the
groups member names. Note that ALL changes made to a wiki are logged by IP address of the machine, as well as time
and date. By law Derek Lipiec MUST always be running an audit trail system which essentially operates as a key logger
in that if any vandalism is done electronically, he can determine who is logged on, from where as well as what was typed.
This is a warning that anyone modifying a group's wiki who is NOT a member of that group will be caught and risk a zero
grade for this assignment exists. Therefore "play safe" and do not fool around. (wfsp)
</li>
<li>
Just after several weeks of class duration, a created wiki from each group will be completed
and marked. As soon as scheduled, these dates will be posted in the ELM calendar for this course.
</li>
<li>
Part of this mark will be composed of 12 other rankings (by three groups of four members each as listed below)
from <b>each</b> of the other group members, <b>done individually</b>, who will rank and provide one sentence
of what is best and one sentence of what is worst about the subject wiki under consideration. This is done
through sending Dr.Poehlman an email with the three marks and single sentences for like and dislike reasons.
The ranking for each wiki will be compiled by the instructor and posted anonymously for class consideration
and discussion near the end of term.
</li>
</ul>

===Topics:===
Reference -- adapted from ACM (Association for Computing Machinery -- but people can join, too!) http://wiki.acm.org/cs2001/index.php?title=HUMAN-COMPUTER_INTERACTION
<OL>
<Li> '''Motivation:''' Why the study of how people interact with technology is vital for the development of most usable and acceptable systems. [[Motivations for the Studying of HCI]] (Taken by Group 10 -- wfsp/15nov09@14:30) </Li>
<Li> '''Contexts for HCI:''' mobile devices, consumer devices, business applications, web, business applications, collaboration systems, games, etc. [[Contexts for HCI]] (Taken by Group 8 -- wfsp/05nov09@14:00)</Li>
<Li> '''[[Process_for_User-centered_Development]]:''' early focus on users, empirical testing, iterative design. (Specified for Group 11 -- wfsp/15nov09@14:30) </Li>
<Li> '''[[Different measures for evaluation]]:''' utility, efficiency, learnability, user satisfaction. (Taken by Group 5 -- wfsp/10nov09@13:00)</Li>
<Li> '''Models that inform human-computer interaction (HCI) design:''' attention, perception and recognition, movement, and cognition.</Li>
<Li> '''[[Social issues influencing HCI design and use]]''': culture, communication, and organizations. (Taken by Group 3 -- wfsp/13nov09@15:30) </Li>
<Li> '''[[HCI - Accommodating human diversity]]:''' including universal design and accessibility and designing for multiple cultural and linguistic contexts. (Taken by Group 9 -- wfsp/12nov09@13:30)</Li>
<Li> The most '''[[Common Interface Mistakes]]'''. (Taken by Group 1 -- wfsp/04nov09@17:00)</Li>
<Li> '''[[User Interface Standards]]'''. (Taken by Group 6 -- wfsp/05nov09@19:30)</Li>
<Li> The '''five interaction styles''' as espoused by [[B.Scheidermann]]. [[Five Interaction Styles]] (Taken by Group 7 -- wfsp/04nov09@17:30)</Li>
<Li> The '''Object-Action''' (or visa-versa) '''model''' and its applications. [[The Object-Action (or_visa-versa) model and its applications]](Specified for Group 2 -- wfsp/15nov09@14:30) </Li>
<Li> The '''direct manipulation method''' and its importance to CHI. [[Direct Manipulation]] (Taken by Group 4 -- wfsp/06nov09@09:30) </Li>
</OL>
<h4>
Marking Duties for Each Group:
</h4>
<table border="1">
<tr>
<th>
<u>Group Mark1 Mark2 Mark3</u>
</th>
</tr>
<tr>
<td>
1 Group 2 Group 3 Group 4
</td>
</tr>
<tr>
<td>
2 Group 3 Group 4 Group 5
</td>
</tr>
<tr>
<td>
3 Group 4 Group 5 Group 6
</td>
</tr>
<tr>
<td>
4 Group 5 Group 6 Group 7
</td>
</tr>
<tr>
<td>
5 Group 6 Group 7 Group 8
</td>
</tr>
<tr>
<td>
6 Group 7 Group 8 Group 9
</td>
</tr>
<tr>
<td>
7 Group 8 Group 9 Group 10
</td>
</tr>
<tr>
<td>
8 Group 9 Group 10 Group 11
</td>
</tr>
<tr>
<td>
9 Group 10 Group 11 Group 01
</td>
</tr>
<tr>
<td>
10 Group 11 Group 01 Group 02
</td>
</tr>
<tr>
<td>
11 Group 01 Group 02 Group 03
</td>
</tr>
</table>

----

=='''This is the VRML assignment main page for cs4hc3 and se4f03''' <br> -- ''HCI / CHI'' Courses.==
NOTE: This is NOT required for the 2009-2010 version of this course.
===Some Important References:===

<UL>
<li>
The Custom Courseware for this course has an Appendix section for VRML beginners so this is a good place to begin studying if you are not familiar with the Virtual Reality Modelling Language. We will be using this to create 3-D interfaces for 3-D worlds, just to get some practice in thinking in more than two dimensions. Although VRML has been around for more than a decade, it is still found as the 3-D layer in MPEG4, has been updated and in a standard in the W3C world known as X3D, which is just VRML with <elements> instead of reserved keywords. If you know VRML, you know X3D.
</li>
<li>
To begin our study of the Virtual Reality Modeling Language (VRML), we need to get setup to view the VRML code (which is in pure ASCII, as is Javascript, etc.) To create VRML, use any ASCII editor that you like best. I use Crimson Editor which has a built-in context sensitive markup that understands VRML, so it is easy to distinguish comments from verbs and nouns, etc.
Go to http://sourceforge.net/projects/emeraldeditor/files/ where Emerald Editor (the newest version of the Crimson editor) can be downloaded freely. To interpret VRML code (nested in HTML code) you need a plug-in. The best that I have found is called Cortona from Parallel Graphics at http://www.cortona3d.com/cortona/ . It works best with Apple Safari Browser version 4 from http://www.apple.com/safari/download/ . All of this information is at the end of the course web site section on VRML at http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML headed with the title "Recommended Client Applications". By the way, Parallel Graphics has an editor called VRMLPad that is not free but can be downloaded as a trial version, which may help the beginner as it provides a thumbnail sketch at the margin right when it recognizes any VRML code shape primitives -- interesting thing to see work.
</li>
<li>
As far as web references go, the best place to start is on the course web site: <br> --
http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML
</li>
<ol>
<li>
Once here you can take the tutorial, done by a senior thesis student Polo Cerone several year's ago.
It can be taken on-line or downloaded and worked through locally -- either is equivalent.
</li>
<li>
Once the tutorial is taken, there are many example VRML code snippets that can be viewed with whatever browser plug-in that you have installed. Pay particular attention to the graduated examples that show how one specifically goes about creating an interface in VRML that controls objects in the main scene graph. This is located back near the beginning of the VRML section titled "Graduated VRML2 Interface Examples".
</li>
</ol>
</UL>

Social issues influencing HCI design and use

2009-11-23T05:19:21Z

Hamilr3:

== Communication Considerations ==

The concept of ‘user interfaces for all’ implies the availability of and easy access to computer-based systems and services among all people in all countries worldwide. Therefore, it is essential to consider the differences among user groups with different cultural backgrounds during user interface design. Interaction is defined as the means by which users communicate input to the system and the feedback supplied by the system. [1]
Thus the design of computer user interfaces for multicultural groups presents a challenge to interface designers since, for user interface behavior to be perceived as a message it must be observed by someone, and it must elicit meaning. The meanings and interpretations of these messages depends on how the participants perceive the message, and this perception is dependent on the participants’ cultural backgrounds that provide the framework within which messages are encoded and decoded. Culture therefore plays an important role in communication. [3]
Another communication challenge for Human Computer Interface design comes in the design stage between different teams trying to create a final product.
Thus we divide the communication challenges in two categories as follows:

=== Multidisciplinary team communication consideration for HCI design and use: ===

The development team working for designing the HCI should consist of people from a variety of disciplines, including human factors, programming, graphic design, documentation, marketing and management. While these people bring different areas of expertise to a project, they frequently have different agendas. Ideally, team members will communicate to reach a common ground, and work towards a shared vision of the final product. Communication problems and lack of consensus within a diverse group can hinder the design in its initial stages, and as development progresses. After decisions are finalized, poor communication can prevent design decisions from being applied. Issues should be resolved clearly, and decisions enforced, to reduce implementation error and costly revisions.
Schedules and requirements of departments external to development frequently impact the flexibility of the design as documented. The importance of coordinating schedules and communicating design revisions with departments supporting application development should be understood by designers. Revision once development is underway may be limited or precluded by the needs of departments such as Documentation, Graphic Design, Marketing, and Quality Assurance. [2]

=== Cross cultural communication consideration for HCI design and use: ===

As mentioned earlier for user interface behavior to be perceived as a message it must be observed by someone, and it must elicit meaning. The meanings and interpretations of these messages would depend on how the participants perceive the message, and this perception is dependent on the participants cultural background.

For e.g. the garbage can symbol on the Windows OS represents deleted items this idea is intuitive to people who have seen garbage cans but it is possible that in some other part of the world the people do not know the concept of garbage can and so the garbage can symbol would mean nothing to them.
Thus when trying to design a HCI to communicate with people from different cultural background:

<UL>
<li>
The first step is to determine user differences to find out which user characteristics predict differences in overall performance.
</li>
<li>
The next step is to isolate the source of variation in a particular task
</li>
<li>
The final step is to redesign the interface to accommodate the differences among users [3]
</li>
</UL>

== Organizational Considerations ==
A good HCI should take into account the business rules and operating procedures of a particular organization. If organizational factors are not taken into account, the end result could be software that is verifiably correct, but not useful for its purpose. One way of accomplishing this is through frequent interaction between the designer and the client (the organization). The Manifesto For Agile Software Development <http://agilemanifesto.org/principles.html> suggests that designers follow a twelve principles approach. A few of the key principles can be summarized into the following (Manifesto for Agile Software Development, 2001):

<h5>Software should follow an evolutionary life cycle.</h5> <i>That is, the software should be prototyped at various stages in the development cycle and tested by the clients. The clients should provide feedback relating to their likes and dislikes about the prototype. This iterative design process assures that the client is getting software that is not simply correct, but also useful to the organization.</i>

<h5> A Time Boxed project management approach should be applied.</h5> <i> Milestones should be small and manageable, and distinct. In other words, if a client is not satisfied by a particular prototype, the developers should be able to work on the next milestone and correcting the current milestone in parallel. According to the manifesto, this allows the project to still be completed in a timely manner.</i>

<h5>Maximize the amount of work not done.</h5><i> This, however, is not to say that the software should not perform all of the intended tasks. This principle states that the software should be kept simple. It should be exactly what the client has requested, and not more than that.</i>

==Cultural Considerations==
HCI or Human Computer Interaction, is a study of how people interact with computers and to what extent computers are developed for successful
interaction with human beings.
One of the most important factors of HCI is the fact that different users form different conceptions or mental models about their interactions
and have different ways of learning and keeping knowledge and skills.
In addition to this cultural differences play a part.

Living in a globalized world, cultural identities strongly influence our interpretation of behaviour in others. Users are forced to adapt their way of interaction and interpretation
to a given perspective.
Earlier cultural background was not a key factor in designing computer systems, however now it is an important subject, since computers are used world wide. A great example is of the windows operating systems.
To a person who is familiar with a Recycle Bin, the icon of the Recycle Bin on the Desktop means delete an object. However, to people who have never seen a recycle bin, it may be a mystery.

===Guidelines used during HCI construction===
<h5>Visibility of system status:</h5>
<i>The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.</i>

<h5>Match between system and the real world:</h5>
<i>The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. </i>

<h5>User control and freedom: </h5>
<i>Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.</i>

<h5>Consistency and standards:</h5>
<i>Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.</i>

<h5>Error prevention:</h5>
<i>Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.</i>

<h5>Recognition rather than recall</h5>
<i>Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. </i>

<h5>Flexibility and efficiency of use: </h5>
<i>Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. </i>

<h5>Allow users to tailor frequent actions</h5>

<h5>Aesthetic and minimalist design:</h5>
<i>Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.</i>

<h5>Help users recognize, diagnose, and recover from errors:</h5>
<i>Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.</i>

<h5>Help and documentation: </h5>
<i>Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.</i>

===Conclusion===
As we know some non-educated people who are not familiar with technical devices, may be encouraged to use it if a well understood HCI is composed. Translating language for example is of no use if the user cannot read.
any entity that is meaningful to a culture may be added to the product so that it not only makes it easy for people to use but adds emotional value hence a better liking for the product.

==Bibliography==
<UL>
<li>
[1] International Journal of Intercultural Relations. (2008). Cross-cultural influence on communication effectiveness and user interface design. Retrieved 11, 20, 2009, from International Journal of Intercultural Relations: http://www.contrib.andrew.cmu.edu/~ytseng/images/ibm/Cross-cultural influence.pdf
</li>
<li>
[2] Practical User Interface Design: Developing within Real-World Constraints. (1997). Retrieved 11, 20, 2009, from Conference on Human Factors in Computing Systems: http://www.sigchi.org/chi97/proceedings/tutorial/dmh.htm
</li>
<li>
[3] Issues in the Design of Computer User Interfaces for Multicultural Communities. (1998). Retrieved 11, 20, 2009, from Issues in the Design of Computer User Interfaces for Multicultural Communities: http://www.it.murdoch.edu.au/~sudweeks/catac98/pdf/21_stander.pdf
</li>

<li>
Manifesto for Agile Software Development. (2001). Principles Behind the Agile Manifesto. Retrieved 11 20, 2009, from Manifesto for Agile Software Development: http://agilemanifesto.org/principles.html
</li>

<li>
http://www.useit.com/papers/heuristic/heuristic_list.html
</li>
<li>
http://www.springerlink.com/content/qr6m2fptevd730u1/
</li>

Social issues influencing HCI design and use

2009-11-23T05:04:28Z

Hamilr3: Communication and culture additions

== Communication Considerations ==

The concept of ‘user interfaces for all’ implies the availability of and easy access to computer-based systems and services among all people in all countries worldwide. Therefore, it is essential to consider the differences among user groups with different cultural backgrounds during user interface design. Interaction is defined as the means by which users communicate input to the system and the feedback supplied by the system. [1]
Thus the design of computer user interfaces for multicultural groups presents a challenge to interface designers since, for user interface behavior to be perceived as a message it must be observed by someone, and it must elicit meaning. The meanings and interpretations of these messages depends on how the participants perceive the message, and this perception is dependent on the participants’ cultural backgrounds that provide the framework within which messages are encoded and decoded. Culture therefore plays an important role in communication. [3]
Another communication challenge for Human Computer Interface design comes in the design stage between different teams trying to create a final product.
Thus we divide the communication challenges in two categories as follows:

=== Multidisciplinary team communication consideration for HCI design and use: ===

The development team working for designing the HCI should consist of people from a variety of disciplines, including human factors, programming, graphic design, documentation, marketing and management. While these people bring different areas of expertise to a project, they frequently have different agendas. Ideally, team members will communicate to reach a common ground, and work towards a shared vision of the final product. Communication problems and lack of consensus within a diverse group can hinder the design in its initial stages, and as development progresses. After decisions are finalized, poor communication can prevent design decisions from being applied. Issues should be resolved clearly, and decisions enforced, to reduce implementation error and costly revisions.
Schedules and requirements of departments external to development frequently impact the flexibility of the design as documented. The importance of coordinating schedules and communicating design revisions with departments supporting application development should be understood by designers. Revision once development is underway may be limited or precluded by the needs of departments such as Documentation, Graphic Design, Marketing, and Quality Assurance. [2]

=== Cross cultural communication consideration for HCI design and use: ===

As mentioned earlier for user interface behavior to be perceived as a message it must be observed by someone, and it must elicit meaning. The meanings and interpretations of these messages would depend on how the participants perceive the message, and this perception is dependent on the participants cultural background.

For e.g. the garbage can symbol on the Windows OS represents deleted items this idea is intuitive to people who have seen garbage cans but it is possible that in some other part of the world the people do not know the concept of garbage can and so the garbage can symbol would mean nothing to them.
Thus when trying to design a HCI to communicate with people from different cultural background:

<UL>
<li>
The first step is to determine user differences to find out which user characteristics predict differences in overall performance.
</li>
<li>
The next step is to isolate the source of variation in a particular task
</li>
<li>
The final step is to redesign the interface to accommodate the differences among users [3]
</li>
</UL>

==Cultural Considerations==
HCI or Human Computer Interaction, is a study of how people interact with computers and to what extent computers are developed for successful
interaction with human beings.
One of the most important factors of HCI is the fact that different users form different conceptions or mental models about their interactions
and have different ways of learning and keeping knowledge and skills.
In addition to this cultural differences play a part.

Living in a globalized world, cultural identities strongly influence our interpretation of behaviour in others. Users are forced to adapt their way of interaction and interpretation
to a given perspective.
Earlier cultural background was not a key factor in designing computer systems, however now it is an important subject, since computers are used world wide. A great example is of the windows operating systems.
To a person who is familiar with a Recycle Bin, the icon of the Recycle Bin on the Desktop means delete an object. However, to people who have never seen a recycle bin, it may be a mystery.

===Guidelines used during HCI construction===
<h5>Visibility of system status:</h5>
<i>The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.</i>

<h5>Match between system and the real world:</h5>
<i>The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. </i>

<h5>User control and freedom: </h5>
<i>Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.</i>

<h5>Consistency and standards:</h5>
<i>Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.</i>

<h5>Error prevention:</h5>
<i>Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.</i>

<h5>Recognition rather than recall</h5>
<i>Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. </i>

<h5>Flexibility and efficiency of use: </h5>
<i>Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. </i>

<h5>Allow users to tailor frequent actions</h5>

<h5>Aesthetic and minimalist design:</h5>
<i>Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.</i>

<h5>Help users recognize, diagnose, and recover from errors:</h5>
<i>Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.</i>

<h5>Help and documentation: </h5>
<i>Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.</i>

===Conclusion===
As we know some non-educated people who are not familiar with technical devices, may be encouraged to use it if a well understood HCI is composed. Translating language for example is of no use if the user cannot read.
any entity that is meaningful to a culture may be added to the product so that it not only makes it easy for people to use but adds emotional value hence a better liking for the product.

==Bibliography==
<UL>
<li>
[1] International Journal of Intercultural Relations. (2008). Cross-cultural influence on communication effectiveness and user interface design. Retrieved 11, 20, 2009, from International Journal of Intercultural Relations: http://www.contrib.andrew.cmu.edu/~ytseng/images/ibm/Cross-cultural influence.pdf
</li>
<li>
[2] Practical User Interface Design: Developing within Real-World Constraints. (1997). Retrieved 11, 20, 2009, from Conference on Human Factors in Computing Systems: http://www.sigchi.org/chi97/proceedings/tutorial/dmh.htm
</li>
<li>
[3] Issues in the Design of Computer User Interfaces for Multicultural Communities. (1998). Retrieved 11, 20, 2009, from Issues in the Design of Computer User Interfaces for Multicultural Communities: http://www.it.murdoch.edu.au/~sudweeks/catac98/pdf/21_stander.pdf
</li>

<li>
http://www.useit.com/papers/heuristic/heuristic_list.html
</li>
<li>
http://www.springerlink.com/content/qr6m2fptevd730u1/
</li>

Template:Reflist

2009-11-23T04:37:21Z

Hamilr3: New page: {{reflist|3}}

Social issues influencing HCI design and use

2009-11-23T04:22:26Z

Hamilr3:

= Social issues influencing HCI design and use =

== Communication Considerations ==

stsssss [[classical liberalism]].<ref>Jeffers, 8–12; Nevins, 4–5</ref>

==References==
{{reflist|3}}

Social issues influencing HCI design and use

2009-11-23T04:20:56Z

Hamilr3:

= Social issues influencing HCI design and use =

== Communication Considerations ==

stsssss [[classical liberalism]].<ref>Jeffers, 8–12; Nevins, 4–5</ref>

Social issues influencing HCI design and use

2009-11-23T04:16:45Z

Hamilr3: New page: = Social issues influencing HCI design and use = <h4> Group 3: </h4> <UL> <li> Robert Hamilton </li> <li> Daniel Moore </li> <li> Premal Parekh </li> <li> Lokesh Thakur </li> </U...

= Social issues influencing HCI design and use =

<h4>
Group 3:
</h4>
<UL>
<li>
Robert Hamilton
</li>
<li>
Daniel Moore
</li>
<li>
Premal Parekh
</li>
<li>
Lokesh Thakur
</li>
</UL>

User:Skip

2009-11-14T01:48:07Z

Hamilr3: /* Topics: */

= Human Computer Interaction =

=='''This is the projects main page for cs4hc3 and se4f03''' -- ''HCI / CHI'' Courses.==

===Objectives===

===Logistics===
<ul>
<li>
During the middle of term the class will be divided into about 12 (n) groups, each of whom will negotiate amongst
themselves a topic of concentration from the list below with at least three ranked by selected priority.
At an early designated lecture, each group will be linked to a topic of their choice in a first-come/first-served
basis -- only one group per project.
</li>
<li>
Group members should all have their associated member email addresses and use these to generate a wiki in one of the groups member names. Note that ALL changes made to a wiki are logged by IP address of the machine, as well as time and date. By law Derek MUST always be running an audit trail system which essentially operates as a key logger in that if any vandalism is done electronically, he can determine who is logged on, from where as well as what was typed. This is a warning that anyone modifying a group's wiki who is NOT a member of that group will be caught and risk a zero grade for this assignment. Therefore "play safe" and do not fool around. (wfsp)
</li>
<li>
Just after several weeks of class duration, a created wiki from each group will be completed
and marked.
</li>
<li>
Part of this mark will be composed of (n-1) other rankings from each of the other groups,
who will rank and provide one sentence of what is best and one sentence of what is worst about the
subject wiki under consideration. The ranking for each wiki will be posted anonymously for class consideration and discussion near the end of term.
</li>
</ul>

===Topics:===
Reference -- adapted from ACM (Association for Computing Machinery -- but people can join, too!) http://wiki.acm.org/cs2001/index.php?title=HUMAN-COMPUTER_INTERACTION
<OL>
<Li> '''Motivation:''' Why the study of how people interact with technology is vital for the development of most usable and acceptable systems.</Li>
<Li> '''Contexts for HCI:''' mobile devices, consumer devices, business applications, web, business applications, collaboration systems, games, etc. (Taken by Group 8 -- wfsp/05nov09@14:00)</Li>
<Li> '''Process for user-centered development:''' early focus on users, empirical testing, iterative design.</Li>
<Li> '''Different measures for evaluation:''' utility, efficiency, learnability, user satisfaction. (Taken by Group 5 -- wfsp/10nov09@13:00)</Li>
<Li> '''Models that inform human-computer interaction (HCI) design:''' attention, perception and recognition, movement, and cognition.</Li>
<Li> '''Social issues influencing HCI design and use:''' culture, communication, and organizations. (Taken by Group 3 -- wfsp/13nov09@15:30) </Li>
<Li> '''Accommodating human diversity:''' including universal design and accessibility and designing for multiple cultural and linguistic contexts. (Taken by Group 9 -- wfsp/12nov09@13:30)</Li>
<Li> The most '''common''' interface '''design mistakes'''. (Taken by Group 1 -- wfsp/04nov09@17:00)</Li>
<Li> '''User interface standards'''. (Taken by Group 6 -- wfsp/05nov09@19:30)</Li>
<Li> The '''five interaction styles''' as espoused by [[B.Scheidermann]]. (Taken by Group 7 -- wfsp/04nov09@17:30)</Li>
<Li> The '''Object-Action''' (or visa-versa) '''model''' and its applications. </Li>
<Li> The '''direct manipulation method''' and its importance to CHI. (Taken by Group 4 -- wfsp/06nov09@09:30) </Li>
</OL>

----

=='''This is the VRML assignment main page for cs4hc3 and se4f03''' <br> -- ''HCI / CHI'' Courses.==

===Some Important References:===

<UL>
<li>
The Custom Courseware for this course has an Appendix section for VRML beginners so this is a good place to begin studying if you are not familiar with the Virtual Reality Modelling Language. We will be using this to create 3-D interfaces for 3-D worlds, just to get some practice in thinking in more than two dimensions. Although VRML has been around for more than a decade, it is still found as the 3-D layer in MPEG4, has been updated and in a standard in the W3C world known as X3D, which is just VRML with <elements> instead of reserved keywords. If you know VRML, you know X3D.
</li>
<li>
To begin our study of the Virtual Reality Modeling Language (VRML), we need to get setup to view the VRML code (which is in pure ASCII, as is Javascript, etc.) To create VRML, use any ASCII editor that you like best. I use Crimson Editor which has a built-in context sensitive markup that understands VRML, so it is easy to distinguish comments from verbs and nouns, etc.
Go to http://sourceforge.net/projects/emeraldeditor/files/ where Emerald Editor (the newest version of the Crimson editor) can be downloaded freely. To interpret VRML code (nested in HTML code) you need a plug-in. The best that I have found is called Cortona from Parallel Graphics at http://www.cortona3d.com/cortona/ . It works best with Apple Safari Browser version 4 from http://www.apple.com/safari/download/ . All of this information is at the end of the course web site section on VRML at http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML headed with the title "Recommended Client Applications". By the way, Parallel Graphics has an editor called VRMLPad that is not free but can be downloaded as a trial version, which may help the beginner as it provides a thumbnail sketch at the margin right when it recognizes any VRML code shape primitives -- interesting thing to see work.
</li>
<li>
As far as web references go, the best place to start is on the course web site: <br> --
http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML
</li>
<ol>
<li>
Once here you can take the tutorial, done by a senior thesis student Polo Cerone several year's ago.
It can be taken on-line or downloaded and worked through locally -- either is equivalent.
</li>
<li>
Once the tutorial is taken, there are many example VRML code snippets that can be viewed with whatever browser plug-in that you have installed. Pay particular attention to the graduated examples that show how one specifically goes about creating an interface in VRML that controls objects in the main scene graph. This is located back near the beginning of the VRML section titled "Graduated VRML2 Interface Examples".
</li>
</ol>
</UL>

User:Skip

2009-11-12T22:01:37Z

Hamilr3: /* Topics: */

= Human Computer Interaction =

=='''This is the projects main page for cs4hc3 and se4f03''' -- ''HCI / CHI'' Courses.==

===Objectives===

===Logistics===
<ul>
<li>
During the middle of term the class will be divided into about 12 (n) groups, each of whom will negotiate amongst
themselves a topic of concentration from the list below with at least three ranked by selected priority.
At an early designated lecture, each group will be linked to a topic of their choice in a first-come/first-served
basis -- only one group per project.
</li>
<li>
Group members should all have their associated member email addresses and use these to generate a wiki in one of the groups member names. Note that ALL changes made to a wiki are logged by IP address of the machine, as well as time and date. By law Derek MUST always be running an audit trail system which essentially operates as a key logger in that if any vandalism is done electronically, he can determine who is logged on, from where as well as what was typed. This is a warning that anyone modifying a group's wiki who is NOT a member of that group will be caught and risk a zero grade for this assignment. Therefore "play safe" and do not fool around. (wfsp)
</li>
<li>
Just after several weeks of class duration, a created wiki from each group will be completed
and marked.
</li>
<li>
Part of this mark will be composed of (n-1) other rankings from each of the other groups,
who will rank and provide one sentence of what is best and one sentence of what is worst about the
subject wiki under consideration. The ranking for each wiki will be posted anonymously for class consideration and discussion near the end of term.
</li>
</ul>

===Topics:===
Reference -- adapted from ACM (Association for Computing Machinery -- but people can join, too!) http://wiki.acm.org/cs2001/index.php?title=HUMAN-COMPUTER_INTERACTION
<OL>
<Li> '''Motivation:''' Why the study of how people interact with technology is vital for the development of most usable and acceptable systems.</Li>
<Li> '''Contexts for HCI:''' mobile devices, consumer devices, business applications, web, business applications, collaboration systems, games, etc. (Taken by Group 8 -- wfsp/05nov09@14:00)</Li>
<Li> '''Process for user-centered development:''' early focus on users, empirical testing, iterative design.</Li>
<Li> '''Different measures for evaluation:''' utility, efficiency, learnability, user satisfaction. (Taken by Group 5 -- wfsp/10nov09@13:00)</Li>
<Li> '''Models that inform human-computer interaction (HCI) design:''' attention, perception and recognition, movement, and cognition.</Li>
<Li> '''Social issues influencing HCI design and use:''' culture, communication, and organizations.</Li>
<Li> '''Accommodating human diversity:''' including universal design and accessibility and designing for multiple cultural and linguistic contexts. (Taken by Group 9 -- wfsp/12nov09@13:30)</Li>
<Li> The most '''common''' interface '''design mistakes'''. (Taken by Group 1 -- wfsp/04nov09@17:00)</Li>
<Li> '''User interface standards'''. (Taken by Group 6 -- wfsp/05nov09@19:30)</Li>
<Li> The '''five interaction styles''' as espoused by [[B.Scheidermann]]. (Taken by Group 7 -- wfsp/04nov09@17:30)</Li>
<Li> The '''Object-Action''' (or visa-versa) '''model''' and its applications. (Taken by Group 2 -- wfsp/12nov09@17:00)</Li>
<Li> The '''direct manipulation method''' and its importance to CHI. (Taken by Group 4 -- wfsp/06nov09@09:30) </Li>
</OL>

----

=='''This is the VRML assignment main page for cs4hc3 and se4f03''' <br> -- ''HCI / CHI'' Courses.==

===Some Important References:===

<UL>
<li>
The Custom Courseware for this course has an Appendix section for VRML beginners so this is a good place to begin studying if you are not familiar with the Virtual Reality Modelling Language. We will be using this to create 3-D interfaces for 3-D worlds, just to get some practice in thinking in more than two dimensions. Although VRML has been around for more than a decade, it is still found as the 3-D layer in MPEG4, has been updated and in a standard in the W3C world known as X3D, which is just VRML with <elements> instead of reserved keywords. If you know VRML, you know X3D.
</li>
<li>
To begin our study of the Virtual Reality Modeling Language (VRML), we need to get setup to view the VRML code (which is in pure ASCII, as is Javascript, etc.) To create VRML, use any ASCII editor that you like best. I use Crimson Editor which has a built-in context sensitive markup that understands VRML, so it is easy to distinguish comments from verbs and nouns, etc.
Go to http://sourceforge.net/projects/emeraldeditor/files/ where Emerald Editor (the newest version of the Crimson editor) can be downloaded freely. To interpret VRML code (nested in HTML code) you need a plug-in. The best that I have found is called Cortona from Parallel Graphics at http://www.cortona3d.com/cortona/ . It works best with Apple Safari Browser version 4 from http://www.apple.com/safari/download/ . All of this information is at the end of the course web site section on VRML at http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML headed with the title "Recommended Client Applications". By the way, Parallel Graphics has an editor called VRMLPad that is not free but can be downloaded as a trial version, which may help the beginner as it provides a thumbnail sketch at the margin right when it recognizes any VRML code shape primitives -- interesting thing to see work.
</li>
<li>
As far as web references go, the best place to start is on the course web site: <br> --
http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML
</li>
<ol>
<li>
Once here you can take the tutorial, done by a senior thesis student Polo Cerone several year's ago.
It can be taken on-line or downloaded and worked through locally -- either is equivalent.
</li>
<li>
Once the tutorial is taken, there are many example VRML code snippets that can be viewed with whatever browser plug-in that you have installed. Pay particular attention to the graduated examples that show how one specifically goes about creating an interface in VRML that controls objects in the main scene graph. This is located back near the beginning of the VRML section titled "Graduated VRML2 Interface Examples".
</li>
</ol>
</UL>

Wi-Fi

2009-04-13T00:19:31Z

Hamilr3: /* External Links */

[[Image:Wifilogo.jpg|thumb|Wi-Fi logo]]
''Wi-Fi is a consortium that verifies 802.11b wireless network products interoperate, and a marketing term vendors use to sell their products.''<sup>[1]</sup>

Wi-Fi is a subsection of the IEEE 802, a subcategory in the link layer of the TCP/IP [[The Five-Layer TCP/IP Model: Description/Attacks/Defense|Internet Protocol Suite]]. The Wi-Fi alliance is a trade group that owns the 'Wi-Fi' trademark, a symbol that certifies interoperability between wireless devices. Not every Internet product is Wi-Fi certified however, and there exists many devices that are able to interoperate wirelessly without the Wi-Fi logo. Some products have chosen to omit having Wi-Fi certification to avoid paying certification costs.

The use of Wi-Fi has boomed in recent years and is supported by a multitude of different devices. Laptops. game consoles, smartphones, printers and other peripherals usually have Wi-Fi certification.

==History==
[[Image:Metro Wireless Node.jpg|thumb|A municipal wireless antenna. Such devices are integral in creating a mesh network of access points. ]]
Wi-Fi was invented by Vic Hayes (dubbed 'the father of Wi-Fi') at the NCR Corporation/AT & T (later Lucent & Agere Systems), in 1991. Hayes had been designing IEEE standards for 802.11b, 802.11a and 802.11g and subsequent technology, initially meant for cashier systems. NCR initially released the technology under the name of 'WaveLAN' which operated in a range of 1Mbps-2 Mbps. <sup>[2]</sup> The Wi-Fi alliance was created soon after the technology.

The alliance is a consortium of separate, independent companies that promotes and develops IEEE 802.11 standards. The alliance also tests products to establish interoperability and certifies products that pass. The 'Wi-Fi' logo is allowed to be used by manufacturers who subscribe to the alliance and whose products pass testing. There exists sever unofficial "Wi-Fi" products that may work, but lack true certification.<sup>[6]</sup>

The term "Wi-Fi" was coined by Interbrand Corporation in August 1999 when hired by the Alliance to change the name from 'IEEE 802.11b Direct Sequence.' Interbrand also created the official 'Wi-Fi' logo. It is often assumed that Wi-Fi stands for "Wireless Fidelity", however officially Wi-Fi is an abstract term and the Wi-Fi alliance is trying to downplay any association to "Hi-Fi" (High Fidelity).

Many cities globally, have announced plans for a city-wide Wi-Fi network. Many such project have since been cancelled due to unforseen difficulties however, a few (such as Sunnyvale, California) were successful. The city-wide networks were created by meshing several wireless antenna together and effectively creating a very large hotspot.

==Uses==
There are typically two ses for Wi-Fi: it can be used as an access technology whereby a single base station (access point) accomodates multiple clients, or it can be used in a point-to-point configuration, connecting exactly 2 access points. The latter is typically reserved for standard 802.16 (Wi-Max) and used by network providers or corporations to connect two sites.

A Wi-Fi enabled device can connect to the internet if the access point it reaches is part of a network containing the internet. A wi-Fi enabled device can essentially use the internet for any networking purpose.

There exists many wireless 'hotspots' which integrate one or more access points and the hotspots can span a range of a few meters to several kilometers( Sunnyvale, California for example, offers free city-wide Wi-Fi). Many businesses offer wireless hotspots as either free or pay services in order to attract customers.

Wi-Fi devices can operate in different modes such as peer-to-peer mode, which allows a direct connection between two people. In ad-hoc mode Wi-Fi devices are able to make client-to-client connections without a router.

Wi-Fi can enable wireless voice application (VoIP). The widespread growth of Wi-Fi now allows access to the internet outside 'traditional' setups (such as the bathroom). Wi-Fi installations can ultimately provide: a sequre computer networking gateway, firewall, DHCP server, intrusion detection system and many other services.<sup>[7]</sup>

==Advantages and Challenges==
Wi-Fi uses an unlicensed radio spectrum (unlike packet radio systems) and does not require regulatory approval for individual developers, which makes Wi-Fi products widely available. Different brands are able to make products that are interoperable at a basic service level because of the technological foundations in Wi-Fi. Competition amounsts vendors has also considerably lowered prices of Wi-Fi products, and they continue to drop as technology improves. <sup>[3]</sup>

Wi-Fi allows local area networks (LANs) to be set up without wires, which simultaneously lowers costs (of creating and exapnding) and allows much freedom in where a network can be accessed. The Wi-Fi certification aheres to a global set of standards as well so Wi-Fi products are compatible in any region.

===Range===
[[Image:Point-to-point-wifi-antenna.jpg|thumb|A point-to-point parabolic Wi-Fi antenna. Such devices can dramatically increase the range of a Wi-Fi network (in a single direction). The devices may be costly to buy and run however.]]

Typically a Wi-Fi router in a home setup with a 802.11b stock antenna has a range of about 32m indoors (due to barriers like walls) and about 95m with no obstructions, outdoors. The frequency block a router uses also affects the range: 2.4GHz has a greater range than 5 GHz. Wi-Fi has greater range compared to bluetooth and can provide huge outdoor range if a network incorporates a directional antenna.

Wi-Fi began with IEEE standards for short range wireless broadband technology, and appointed the standard numbers: 802.11b(Wi-Fi), 802.11a and 802.11g (can interoperate with 802.11b). Typically Wi-Fi operates between 2.5 to 4Mbps, but can go as high as 11 Mbps.

===Mobility===
Wi-Fi technology allows LANs to be deployed without cabling, potentially reducing the costs of network deployment and expansion. Spaces where cables cannont be run, such as outdoor areas or historical buildings can host wireless LANs. Wi-Fi technology increases the ease of setting up a network as well.

Wi-Fi networks support roaming, in which a mobile client station (like a laptop or smartphone) can move from one access point to another as the user moves. It is because Wi-Fi certified devices are able to interoperate that this is possible without complications as well.

==Security==
The greatest security issue with Wi-Fi (and all other wireless networks) is the easy of connectivity compared to traditional wired networks like Ethernet. Wireless communication (bluetooth especially) is designed to be simple and easily connected to. To make an attack on a wired network, the attacker must physically connect to the internal network or break through an external firewall. External access however is usually disallowed by business networks in order to protect sensitive data. It is because firewall encryption could be broken that most business networks disallow external access. Getting wireless reception is considered an attack to most business networks.<sup>[3]</sup>

The nature most wireless networks is to allow external access in order to maintain an degree of usability. If attackers gain access to a wireless network they can harm the user in a variety of ways from monitoring others' activity to fabricating a DNS spoofing attack.

===Preventative Measures===
[[Image:Wep.gif|thumb|The WEP encryption standard. The vunerabilities are shown by malicious software and a single key for all users on the network.]]
WEP (Wired Equivalent Privacy) keys uses a deprecated algorithm to secure Wireless networks. First introduced in 1997, WEP keys were intended to make wireless networks have comparable security to that of wired networks. A WEP key could be interpreted as a 26 digit password allowing access to a home network. There are several security flaws in the WEP keys currently being used and there exists readily available software (such as AirSnort or AirCrack) that can obtain a WEP key in minutes. WEP keys are now considered completely broken. The security flaws of WEP keys was first counteracted in 2002 with 'Wi-Fi Protected Access' (WPA) but the attack vector are now known. Now (as of 2004), full IEEE 802.11i (WPA2) encryption standards have been release and are still considered secure as of 2009.

Another security measure in effect involves suppressing the Access Points' SSID broadcast to only allow a predefined set of MAC addresses the ability to join the network. This security measure has since proven ineffective, since if an allowed MAC address is known (or found out) by an attacker then they could potentially change their own MAC address to spoof as an allowed machine.

===DNS Spoofing and Kaminsky Attack===
In June 2005 Dan Kaminsky used a DNS hack in order to get free Wi-Fi at an area starbucks. He later realized the huge security issues this presented and brought attention to the Wi-Fi and DNS security flaws. Starbucks offers a Wi-Fi service but it costs a premium, the Kaminsky hack fools the domain name system and thorough Wi-Fi, exposed a glaring Internet security flaw.

The following is an excerpt from WIRED magazine:

'''How DNS works'''

1. Type anybank.com into your Web brower and the query packet is sent to your internet service provider (ISP)

2. If anybank.com's location isn't cached, your ISP's name server repeatedly searches the domain name system for it. Each search is assigned a 16-bit transaction ID for security and tracking. Responses to the searches must carry the correct transaction ID to be accepted by the name server. The packet would travel through the root name server, the .com name server then anybank.com name server.

3. Eventually, anybank.com sends an answer to your ISP; Our home page is at 60.190.216.103. This authenticated address is cached.

4. Your browser connects you.

'''How the Kaminsky DNS hack works'''

1. The attacker tries to hijack anybank.com by sending thousands of requests for fake Web pages. Malicious query packets are sent to your ISP.

2. The ISP gives each query a transaction ID (unknown to the attacker) and attempts to locates the pages.

3. At the same time, the attacker sends hundreds of responses for each malicious request. Every answer includes a randomly generated ID number.

4. Eventually one of the answers carries an ID that matches, tricking the ISP into accepting and caching the information. The now-legitimized answer contains false details about anybank.com, such as the location of its servers. Legitimate answers from anybank.com("No such page exists") will now be rejected.

5. Users looking for anybank.com get sent to the fake location already in the ISP's cache.

6. Anybank.com customers are now using a look-alike site built by the hacker.

'''Patch fixing Kaminsky attack'''

Most computers have 63, 536 ports, but DNS commonly uses only port 53 for all queries and responses. The patch works by randomly changing the port number for each DNS request. Now any response to a request must contain an accurate transaction ID number and return to the same port. The change increases the odds of beating the system from one in 65, 536 to one in 4 billion.<sup>[4]</sup>

===Piggybacking===
Piggybacking refers to accessing a wireless internet connection by bringing a wireless device in range of another connection and using the service without the owners knowledge or permission. Piggybacking is completely outlawed in some jurisdictions, but allowed in others. It is not considered piggybacking if a bussiness offers a Wi-Fi hotspot for free or as a pay service.

Piggybacking ofter goes unnoticed since most people only use a fraction of their upstream bandwidth. Piggybacking may also be carried out unintentionally, as most access points are configured without encryption (WPA2) and operating systems can automatically connect to wireless networks. The danger in piggybacking exists in users logging into an insecure network where illicit activity is conducted (danger for network owner) or sensitive information is broadcast (danger for user).<sup>[5]</sup>

===The Wi-Fi Scam, Home Security Scam and Bluetooth Scam===
'The Real Hustle' a UK television show is premised as an educational program demonstrating how people are getting ripped-off by confidence men around the world. The hustlers demonstrate how easy it is to gain access to a Wireless network through various scams.

In the [http://www.youtube.com/watch?v=jqic_aY3TqQ&feature=related Wi-Fi Scam], the hustlers hijack a wireless network then rename their own wireless network and route people to a dummy site that looks completely legitimate.

In the Home Security Scam, the hustlers walk through a residential neighborhood and enter home wireless networks by either hacking WEP keys or finding an unlocked network. The hustlers then monitor others online activity.

In the [http://www.youtube.com/watch?v=gvDp-DBh4Gc&feature=related Bluetooth Scam], the hustlers scan a shopping mall for bluetooth signals from mobile phones. Once a signal is found and a connection is made, the hustlers call their premium rate line and rack up a bill for the cell phone owner.

There exists dozens of tutorials on the Internet on how to use Wi-Fi for illicit purposes, demonstrating just how vunerable a wireless network is.

==Other 802 Standards and Amendments==
[http://en.wikipedia.org/wiki/IEEE_802 See: IEEE 802 Wiki]

==References==
# Comer, D. E. (2006). Wi-Fi. ''Internetworking with TCP/IP'' (Fifth ed., pp. 419-441). Upper Saddle River, NJ: Pearson Prentice Hall.
# "[http://www.wilcorpinc.com/wifi_history.htm Wi-Fi History]". Retrieved on 2009-04-07
# "[http://networkbits.net/wireless-printing/80211-g-pros-cons-of-a-wireless-network-in-a-business-environment/ Pros and Cons...]". Retrieved on 2009-04-07
# Davis, Joshua (Dec 2008). Collapse. ''WIRED Magazine'' (pp. 200-205,224, 231)
# "[http://en.wikipedia.org/wiki/Piggybacking_(internet_access) Piggybacking]". Retrieved on 2009-04-07
# "[http://www.wi-fi.org/about_overview.php Overview of the Wi-Fi Alliance]". Retrieved on 2009-04-08
# "[http://computer.howstuffworks.com/municipal-wifi.htm How Municipal Wi-Fi works]". Retrieved on 2009-04-09

==See Also==
* [http://www.cas.mcmaster.ca/wiki/index.php/Denial_Of_Service_Attacks Denial of Service Attacks]
* [http://www.cas.mcmaster.ca/wiki/index.php/Security_for_Small_Home_Networks Security for Small Home Networks]

* [http://www.cas.mcmaster.ca/wiki/index.php/Peer_To_Peer_Network_Security Peer To Peer Network Security]
* [http://www.cas.mcmaster.ca/wiki/index.php/Man_in_the_Middle_Attack Man in the Middle Attacks]
* [http://www.cas.mcmaster.ca/wiki/index.php/Domain_Name_System Domain Name System (DNS)]

==External Links==

--[[User:Hamilr3|Hamilr3]] 20:19, 12 April 2009 (EDT)