2012 INL 370 REPORT

01

What are the age culture specific factors that need to be taken into account when designing a natural user interfaces or NUI, for a global community of users?

Kai Jen Tsai 29350698 Lesego Makhafola 29320098 Tiaan Van Staden Clifford Labea

2012 INL 370 REPORT

02

Introduction
Our topic was What are the age culture specific factors that need to be taken into account when designing a natural user interfaces or NUI, for a global community of users? . The term natural user interfaces is seen by as a new trend and the staple factor to development even though the technology has been a part of our daily lives for many years now. It comprises the way we interact with computers and it have been changing over the years, from the traditional command line interface to the highly interactive natural interfaces we find on computers, cell phones and others devices. This is that basis of what we based the direction of our project upon. The key objective was to identify the factors that have an active influence on the design and development of a natural user interface and how the impact of these factors can improve usability for global communities. We offer users the service of organising content for them by using the Microsoft SharePoint foundation in such a way that it improves the retrieval of their resources. By using standards in the categorisation of content we are able to eliminate duplications, implement version control and correct input errors in the resource centre. Microsoft SharePoint portal is a web based collection of various components, designed to work together to encourage and maximize your collaboration and sharing capabilities. It offers the ability for advanced and effective document and content management. Thus our project is a reflection and application of the vision and principles provided by Microsoft. We aim to exploit the capabilities of SharePoint in order to maximize.

2012 INL 370 REPORT

03

Table of Content
1. Introduction/Background 2. Primary Process 3. Components and Their Underlying Design Principles 3.1Home page 3.2 Project Work Space 3.2.1 Research tools 3.2.2 Alerting services 3.2.3 Mobile Centre 3.2.5 Contacts 3.2.6 Client Blog 3.3 Resource Centre 3.3.1 Supporting Documentation 3.3.2 Background Information 3.3.3. Factors to Consider 3.4 Search Centre 4. Supporting documentation 4.1 Taxonomy 4.2 Metadata Schema 4.3 Workflow diagrams 4.4 Name convention 4.5 Card sorting 5. Conclusions. 6. List of references/ References /Bibliography

2012 INL 370 REPORT

04

Preliminary Processes
Task Name Project Start Sharepoint Portal Day 1: 9th July 2012 Introdution and Briefing Project plan Retention plan and Scedule Establish research criterea Create Blog for daily reflection Milestone 1: Completion of day 1 Duration Start 10.5 days Mon 12/07/09 7 days Sat 12/07/07 1 day Mon 12/07/09 1 day Mon 12/07/09 1 day Mon 12/07/09 1 day Mon 12/07/09 1 day Mon 12/07/09 1 day Mon 12/07/09 1 day Tue 12/07/10 Finish Sun 12/07/22 Tue 12/07/17 Mon 12/07/09 Mon 12/07/09 Mon 12/07/09 Mon 12/07/09 Mon 12/07/09 Mon 12/07/09 Tue 12/07/10

During this initial stage of development goal and concept is simple. To gain an understanding of what needs to be done. Thus all data that would be helpful or related was all commented and analysed to form the core data and foundation of the project. A list of key words was established in which each member was assigned a section to research. Thus a comprehensive and extensive net was cast with a wide area of retrieval, we were able to collect a wealth of information. Please check the addendum for the hit list. Day 2: 10th July 2012 Daily meeting: Chairperson KJT Initiate Research Day 3: 11th July 2012 Daily meeting: Chairperson KJT Research Day 2 Card sorting Formulate taxonomy Develop Structure Milestone 2: Completion basic file structure 1 day 1 day 3 days 1 day 1 day 1 day 1 day 1 day 1 day 1 day Tue 12/07/10 Tue 12/07/10 Tue 12/07/10 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Tue 12/07/10 Tue 12/07/10 Thu 12/07/12 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11 Wed 12/07/11

This phase of the project involve creating the basic foundation of what he structure will be based upon. As with all things in life a strong foundation is vital. TO create the proposed taxonomy is vitally important as when this is established everything can easily be seen where and how to fit into the whole of things. The next process was to determine the metadata scheme in order to sped thing up. In the next steps.

2012 INL 370 REPORT

05

Day 4: 12th July 2012 Daily meeting: Chairperson KJT Formulate Metadata Schema File renaming Filling in Metadata Populate Database Milestone 3: Completion of populated database

1 day 1 day 1 day 2 days 2 days 1 day 1 day

Thu 12/07/12 Thu 12/07/12 Thu 12/07/12 Thu 12/07/12 Thu 12/07/12 Thu 12/07/12 Thu 12/07/12

Thu 12/07/12 Thu 12/07/12 Thu 12/07/12 Fri 12/07/13 Fri 12/07/13 Thu 12/07/12 Thu 12/07/12

Once the structure was formulated its an all downhill ride, as its just a simple matter of populating the database. Thus went relatively quickly. We did meet a hiccup here metadata and structure needed to be constantly adjusted as problems were found. However despite the setback it was a quick and smooth process. Day 5: 13th July 2012 Daily meeting: Chairperson KJT File renaming day 2 Filling in Metadata day 2 Populate Database day 2 Milestone 4: Completion of metadata schema 1 day 1 day 1 day 1 day 1 day 1 day

Fri 12/07/13 Thu 12/07/12 Fri 12/07/13 Fri 12/07/13 Fri 12/07/13

Fri 12/07/13 Thu 12/07/12 Fri 12/07/13 Fri 12/07/13 Fri 12/07/13

Thus is the completion of the portal ultimately. Thus started phase 2. To create the functional services associated with our systems. We had to do some research on the technique and function available for us to use with in SharePoint. Over all a fun and full fling part of the project. However many a times very frustrating as some of the functions just does not function as it should? Example security protocols blocking essential sites like face books and UP homepage. Day 6,7,8: 14th-15th July 2012 Weekend (overtime) Day 9: 16th July 2012 Daily meeting: Chairperson KJT Search Function Integration of 2 web 2.0 technologies Suscribe to 5 alert services Testing and Refiinment Milestone 5: Completion sharepoint prototype Day 10: 17th July 2012 Daily meeting: Chairperson KJT 2 days 2 days 1 day 1 day 1 day 1 day 1 day 1 day 1 day 1 day 1 day Sat 12/07/14 Sat 12/07/07 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Tue 12/07/17 Tue 12/07/17 Mon 12/07/16 Mon 12/07/09 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Mon 12/07/16 Tue 12/07/17 Tue 12/07/17

2012 INL 370 REPORT

06

Interface Aesthetics and polishing Milestone 6: Completion of sharepoint portal

1 day 1 day

Tue 12/07/17 Tue 12/07/17

Tue 12/07/17 Tue 12/07/17

I fun and joyful stage of development, error testing and stress testing. One can really come to appreciate the power that come with establishing strong and logical taxonomy, metadata schema and file naming convention. Manual and Report Day 11: 18th July 2012 photographic evidence Supprting Documentation Day 12: 19th July 2012 User manual Day 13: 20th July 2012 Finalisation and error checking Day 14,15,16: 21st-24th July 2012 Finalisation and error checking Milestone 7: Completion of documentation Day 17: 24th July 2012 End of Project 1 day 1 day 1 day 1 day 1 day 4 days 1 day 1 day 1 day 1 day 1 day Wed 12/07/18 Wed 12/07/18 Wed 12/07/18 Thu 12/07/19 Fri 12/07/20 Sat 12/07/21 Sat 12/07/21 Sat 12/07/21 Wed 12/07/18 Wed 12/07/18 Wed 12/07/18 Wed 12/07/18 Wed 12/07/18 Thu 12/07/19 Wed 12/07/25 Sat 12/07/21 Sat 12/07/21 Sat 12/07/21 Wed 12/07/18 Wed 12/07/18

2012 INL 370 REPORT

07

Components and Their Underlying Design Principles

One tool that does it all. The concept of our portal is to be an evolutionary tool. We understand that one cannot possibly anticipate and cater to all needs during the academic research process. However we are determined to try. Thus the have created is not merely an information repository. It is a complete action command centre with an arsenal of theWe hope that our system would offer the features needed to best fit the users needs. However we designed the system as a base or blank canvas. The user can customise and expand on any feature allowing a level of customisation to the portal that would allow an evolution and become fine-tuned to match the user habits, style, and needs. Such as the nature and aim of this project to create a system that not caters to a specific singular need but a system that can adapt . -best and latest research tools. We perfected the balance of functionality and aesthetic to bring to the user a combination of carefully thought out design principles and features that maximises and streamlines the workflow and process encountered in the research process and importantly, it looks like a dream and comprehensively cater to an entire array of a user of needs. As a present we have incorporated a browser in the browser. Powered by Microsoft IE, this is a fully functional internet browser. Have already pre-set to the UP Library site the user is able to immediately start their research without even having to open a new tab or window stitching out of the page, breaking concentration.

2012 INL 370 REPORT

08

2012 INL 370 REPORT

09

The reasoning behind the concept is to provide the all tools that one might need or encounter during the design process. We wish our system to not only be a single tracked file depository but a multifaceted and comprehensive platform from which one is able to perform all activities of research. We had anticipated many of the users needs and had created the service to be at your fingertips. However having access to the services is not enough, we wish for user to have all the tools, from notes taking, to social networks, to contacting their professor all from less than a click away. For myself the biggest headache when doing research is making little memos that one scribbles down on some obscure piece of paper or save it unto some text document that vanishes into oblivion. Even when one does manage to successfully locates these notes, when revisited, due to the then, current cognitive state, one expect that by merely jotting down a few simple key words they = are able to unlock a wealth of knowledge and trigger an avalanche of memories. This is never the case. We imagined and assumed the majority of our users, being students, just like us, suffer from the same dilemma. When we do attempt to decipher the nuggets of

wisdom, we only get a sense of confusion and really start to question our own intellectual capabilities. However this lost information has the potential to become seeds of great ideas and it is very counterproductive to have such flaws. How do we preserve it? Is there a kind of method for effectively capturing not only the information but also contain the context, emotional connections and cognitive state of mind? No, unfortunately, but with the help of our system we can to a degree help you achieve the level of usability needed and effectively that it creates the value and benefits to assist the user. A seamless and natural process that seeks to augment the current technique so researching and support the user on multiple levels. Whether it is simply taking down key words or keeping a track of relevant websites, the support services are integrated into the work interface. All of the tools and services has been built into the main interface thus minimising the need to change pages or switch programs or tabs. Positioned on the base level of the browser allows for the user to quickly access, cross check and update the surrounding support services without

2012 INL 370 REPORT

10

2012 INL 370 REPORT

11

We all know that alerting services provides many benefits, however not everyone has the technical ability or time or need for advance systems. Whether the need is not justified because the project or information need is small, the project has too short a life span, or one cannot afford to pay for the service, there are various legitimate reasons why one cannot make use of professional alerting service.

However we feel that our users should not be disadvantages at all thus we have brought together some simple and easy to use tools that would help them in creating their own network of information filters, crawlers and news feeds, to they too can stay up to date, informed and knowledgeable. All of these services are easy to use and free. We have set up some predefined search net to allow the user for ease of use.

Delicious

Delicious is used as a central point to share information between users within a company whom share common interest by means of Rss feeds. You are able to view the amount of times content have been saved by others on the Internet and whether your colleagues have accessed the item or not. It offers the user the capability to build his or her collection from the subjects of their liking. The aim of this is to encourage you to explore the available collections with the chance of identifying content that might be related to yours. Users build their collections or stacks by adding or updating it with new links. Each subject topic can have its own stack which in essence helps the user to categorise his or her stacks better. Describing content has never been easier, as user can now edit the tags given to the content and even add optional tags to it.

2012 INL 370 REPORT

12

Email integration

By integrating the Email accounts of employees with the SharePoint site, it will assist them to be up to date with their latest Emails and to control versions of Emails and the Users will be able to access their contact list. The main issue faced during the integration process was the fact that the user needs to have an active Gmail account in order to link it to the SharePoint Email inbox.

RSS Feed

Really simple syndication is one of the most effective ways to stay up to date with the newest trends and developments in a specific subject field. By subscribing to the subject of interest users will receive updates on the newest findings and developments in that specific field of interest. The use of Rss Feeds in our SharePoint site proved to be very successful as it helped us to identify even more important factors to consider in the development and research of natural user interfaces.

2012 INL 370 REPORT

13

We subscribed to the following Rss feeds because of the frequency of updates and the fact that their content is most relevant to our research and of a quality nature

NUI Group

The NUI Group is one of South Africas largest research groups in the field of natural user interfaces. They cover the topic of natural user interfaces extensively and provide subscribers with up to date information on developments and trends. They focus mainly on the problems users experience when they use natural user interfaces and discuss solutions for those problems.

Gesture Tech

Gesture Tech provides subscribers with scholarly related content on the development of natural user interfaces. They give access to related articles through their Rss feeds and information from Institutions of higher education on upcoming developments industrialised by students. Gesture Tech has an active Rss feed channel and generates multiple quality posts daily which makes it a great feed to subscribe to.

Reality-based User Interface

Reality based user interface systems or RUIS, helps innovators to develop their ideas in a state of the art environment with the use of existing technologies such as the Nintendo Wii remote to serve as and input device for their advances. The selection of RUIS as a feed was because of the interesting developments and movements they come across and the technical explanations to the readers.

2012 INL 370 REPORT

14

2012 INL 370 REPORT

15

We had provided a list of the most frequently used sites and online services that would be used by a UP student. It must be noted that we did not include too many service such as adding an array of

academic databases as we feel that the user should not be bombarded by an information overload. If needed the user can added the preferred databases to their list.

Google

We added the option of exploring Google so that users can do quick searches to create a basic knowledge of the subject. Google can be used as a starting point for any research strategy so that the user can get and over view of what are conceivably available on the net.

Google Scholar

For the search of scholarly content users are given the option to use of the Google Scholar search engine. Users can also use the advance search option within Google Scholar to refine their searches and make use of Boolean operators. The advantage of using Google Scholar is that users are able to retrieve academic resources for their research.

UP Home

For users on the SharePoint site that need access to the Universities home page, they can access it through the portal without the need to open a new browser window. This function reduces browsing time and the chance of entering the wrong URL.

UP Portal

We included this option if any of the users need access to their UP Portal.

UP Library

For the users that are familiar with the University of Pretorias library interface and have access to the available resources. The reason we picked this function is because of the extensive collection of available resources on the Library.

2012 INL 370 REPORT

16

2012 INL 370 REPORT

17

Need your SharePoint on the go? In todays fast paced lifestyle, one cannot afford to be without access to their research. Thus we have incorporated our mobile support centre. From here you will be able to access your portal from anywhere with an internet connection with a viable smart phone or mobile device. Full functionality is provide as long as your device is can support the functions. Not due to security issues

currently you may only gain access to your portal when you are connected onto the UP wireless network intranet. All you need to do is scan the QR code and you will be directed to your SharePoint portal on your mobile device. No app or special software required. Just a java supported smart phone and an *active internet connection and less than a click away is access to everything you need.

2012 INL 370 REPORT

18

The concept of our contact book is more than just a telephone directory but rather an Integrated and interdepartmental support tool. For example when one reads an article by a professor, they can add it to their contact book and create their own collection of networks and contacts. However if the details already exist in the university extensive contact base one is able to obtain the necessary contact details needed to further their interaction.

It is a socially based system where everyone contributes to the maintaining and creating a network of contact for interaction. It is not only a helpful too to contact your professor but also to allow others to contact you as well if needed. All the information remains on the internal system and the required details are all professionally motivated thus minimising security risks.

2012 INL 370 REPORT

19

2012 INL 370 REPORT

20

2012 INL 370 REPORT

21

Supporting documentation We decided to include a section called supporting documentation which is all about technological systems and developments that are already in place and also systems and designs that are possibly going to emerge in the near future. Most of the sources included are about developments in the information technology field. Under supporting documentation we have the following categories: Current systems (mobile technology, Microsoft developments) Future designs (future in NUI, voice touch and beyond, whats next, quantum of solaces multi-touch UI) Current systems are all about mobile technology that is already in place, for example, smart phones such Apples iPhone and android smart phones; also included are developments by prominent or well-known software companies such as Microsoft so our clients can get information on what this company is currently working on as so forth. Since we already have technological gadgets with touch pads and voice recorders which can be used to search your cell phone or when you want to input something without having to use your hands, we have an article or two in our SharePoint site which deal with the future on human user interactions, whereby it is stated that somewhere in the future, there may be technological gadgets that will have voice recognition and other things that may exceed the already intelligent software that has already been developed. In a month, a year or a couple of years from now, something new may come up that we cannot even imagine possible now. Our section on future designs give the user insight or information on how technology is being developed, changed and improved as the time goes by.

2012 INL 370 REPORT

22

Background information We decided to include background information on natural interfaces, which we deemed important because maybe some of the clients would be interested to know that and also because we want them to know that we are not making up any of the information we have made available in the SharePoint site, for example, we included an article called Interactive sketching for the early stages of user interface design. The articled gives you the history of GUI and design principles over the years in order to gain an understanding of how GUI and NUI were designed in the past. We selected such sources as we feel that apart from just the relevant pertaining to the topic, the user needs to have a strong foundation of knowledge based on topics that are relevant to their respective field. Resources such as Technology websites and conference proceedings provide us with great information regarding the topic we are dealing with and they are able to provide us with deeper insight into the IT field. This is important as the technology field is always evolving. Under background information we have the following three categories: History of GUI Human Computer Interaction and Natural User Interface. The first category deals with the origin of natural user interfaces, which evolved or originated from graphical user interfaces in a sense. In this section we have information from the origins of GUI to how it changed over the years and also, how natural user interfaces came about. The second category deals with human computer interaction which deals with how humans started interacting with computers thus, the transition from graphical user interfaces to natural user interfaces. The third and last category deals with natural user interfaces which are our topic under multimedia. This section deals with the history of natural user interfaces; here the client will find information on how natural user interfaces came about. You can switch between the simple view and the advanced view. The advanced view shows you the metadata when you hover over an item instead of having to click on it.

2012 INL 370 REPORT

23

Factors to consider We had to identify the factors that have to be taken into account when designing natural user interfaces for a global community of users; we identified the factors and grouped them into three categories namely: Age-Cultural-Ethnic Aspects Visual language Technical Aspects Age-Cultural-Ethnic aspects are very important when designing natural user interfaces as they help you answer very important questions which may include: how old are the users that we intend or are designing this interface for? What language is mainly used by most technology users and what other languages are we going to include in order to have fair coverage or rather, more coverage of our users? How educated are our intended users, for instance, will they find it easy or hard to use the interface? These aspects will help our clients to understand the basic influences of such technologies on users by learning more about these factors. With regard to other disciplines such as communication management and business management, those users can also find information on culture and communication in this section, so our SharePoint site is not only restricted to users who are interested in technology only. Visual language has sub-categories under it which are: fashion in IT, trends in IT, cultural influences, design principles, accessibility, influences from film and media. Under this section, one can agree that the most important element mentioned is accessibility. In this case, we included visual language as it is about things that one can see or notice when observing the technologically influenced market; one is able to pick up on what the latest developments are, for example, we have an article on online shopping which is one of the latest trends in technology as more and more people are moving towards this as it is timesaving among other things. Technical Aspects has the following sub-categories under it which are: hardware, software, training, costs, and security concerns. One would want to know on the latest hardware and software used in the creation and implementation of natural user interfaces, as well as how much these would cost, what training one would need and the security concerns attached to this kind of technology
2012 INL 370 REPORT 24

2012 INL 370 REPORT

25

Our search centre is a powerful and comprehensive system that retrieves both information documents and people. It is highly customisable to be able refine your search to the smallest detail. With easy to use, advance and simple search mode, to cater to users of different skill set.

Our search system also supports Boolean logic and proximity operators. This is useful for the power user as retrieval can be sped up if one wishes to do rapidly search for multiple sources without filling all the advance search fields.

List of operators
ALL(*term) Search for and retrieve all content that contains all of (*term)

EXACT(*term)

Search for and retrieve all content that contains exact phrase (*phrase)

ANY(*term)

Search for and retrieve all content that contains any of (*term)

NONE(*term)

Search for and retrieve all content but filter all results that contains (*term)

EG. ALL(design)

This statement will return all content that contain the term design.

As our metadata and naming convention is built upon assisting and providing and powerful and comprehensive search functions. With many dedicated fields and process all created to ensure that our search is comprehensive accurate fast and powerful.

2012 INL 370 REPORT

26

2012 INL 370 REPORT

27

Metadata Schema
For the description of our content we used the Dublin Core initiative. Although the Dublin Core element set primarily consists of 15 elements we only used a few basic elements of the element set since the others werent needed to describe our content. We added a few extra elements where we identified the need for them. The reason behind the selection of this element set is because every element is both optional and repeatable. The elements should be as straightforward to use as possible so that any user of networked resources would be able to describe the work without undergoing extensive training (Gill: 2008). Our metadata were divided into three categories; Admin, Compulsory and Optional. Admin are the information that describes the contents hierarchical layout. It identifies in which category and subcategory items are stored in. Compulsory being the elements needed to describe the actual item itself. These are elements that give the user a detailed description on the specifications of the object being described. Optional being the additional information that can be added to assist with the retrieval process of the content.

2012 INL 370 REPORT

28

Metadata Schema
Type Name Section This is to say whether it is a document, image, video or folder This is the name of the category in which the file falls under, eg visual language We have three sections and for easy retrieval, we have given each item a section number, eg I, II, III Same thing with the sections, every source has a category alphabet, A, B, C This is if a file is within a specific category that has sub-categories, eg 1, 2, 3 This is the original title of the information source This is the name of the author or editor of the information sourc This is what the source deals with, eg visual language This is for easy retrieval This is the date in which the source was published This is to say whether it is a PDF, word document folder, etc. This is so that the user can know what the source is about without reading the whole source This is the place or site where we found the source, eg SAGE journals, EBSCO host, etc We specified whether a source has copyright or not, most if not all should be under copyright This is an abstract that give you brief information about the contents of the resource. This is the internet address where we found the source if the user wants to follow the link to find the source

Category Sub-category Title of source Author Topic Keywords (tags) Date Format Description

Source

Copyright

Annotated abstract URL

2012 INL 370 REPORT

29

Site map

Search Centre

Tutorials Home Page

Project Workspace Home Page

Alert Services Mobile Support Centre

NUI-Client Site Home Page My Email Services Contacts Client Blog

Resource Centre Home Page

I. Supporting Documents II. Background Information III. Factors to Consider

Hit list. Culture and age dependent factors: Search Criterea.

Cultural/Ethical/psychological issues Language Gestures Difference in in perception Non-verbal and verbal cues Hand gestures Sign language Cultural belief Visual language Fashion IT trends Cultural influences Iconology Aids(visual) Status(class) Education Values Technical Hardware Input/output devices Costs Training User support Maintenance Software Os Security Internet infrastructure

2012 INL 370 REPORT

30

Taxonomy
What are the age- and culture specific factors that need to be taken into account when designing natural user interfaces for a global community of users? *red and green point has file descriptions

I.Support material A. Current systems X Y Z B. Future Design X Y Z have a link (x1) Trends in IT and technology II.Back ground Information A. History X Y Z B.Human Computer Interaction sees also(x1) Gestures Hand gestures Sign language X Y Z III.Factors to consider A.Age/Cultural/Ethnic Aspects Differences in culture. See also(x1) Influences from films and media Language
2012 INL 370 REPORT 31

Gestures Hand gestures Sign language see also (x1) Accessibly Non-verbal and verbal cues Difference in in perception Cultural beliefs Status (class) Values Education Age

B.Visual Language Aspects Fashion links to (x1) Current systems Trends in IT and technology see also(x1) Future Design Cultural influences Design principles Iconology in descrpitption Accessibly Aids(visual) links in the file(x1) Gestures Hand gestures Sign language Influences from films and media. see also(x1) Differences in culture C.Technical Aspects Hardware how touch screen work Input/output devices Internet infrastructure see also(x1) Software Os see also(x1) Training see also(x1) Costs Maintenance Security

2012 INL 370 REPORT

32

Name convention

The naming convention was develop purely for ease of access and to assist the status and searching of the files. However capitals on all words and other standards was also adopted. Power user may also adopt the file name as a method of filtering the searches. Example searching for II.A would limit the files to main category II and subcategory A only.

Card sorting
Sorting the files into a well-structured format that makes sense logically might not seem very important as per say, but it matters allot in terms of the retrieval process. By having a logical file sorting structure one can see a provisional view of the end product even before its completed. In the sorting of our documents the use of three categories were used; I. Supporting Documents, II. Background Information and finally III. Factors to consider. Within these categories we had sub sections which were indicated by means of A, B and C. The actual files can then be located at even a lower level of order which is indicated by the specific number of the file within the sub category. E.g. III.C.1 How NUI Works can be found in the main category Factors to consider, then the sub category Technical Aspects and 1 indicates that its the first file within this sub category. These can be used to identify each file uniquely within the collection which helps with the retrieval process. Please refer to the card sorting activity in the addendum

2012 INL 370 REPORT

33

Conclusion
What we found to be working well for us is the fact that our group was organised from the start, by day two we already had a plan for the rest of the week and by day four, we had already done most of the work that we were supposed to do, for instance, we had gathered all the information (articles, web links, websites, blogs, etc.) we needed to complete our project. What did not work on the other hand is that, from the start, we failed to read the additional requirements about the project and we overlooked one crucial point: the sources we had to gather had to be from the year 2008 or later; we realised that most of our sources were pre-dated but very relevant to the topic we were given as we had a section on background information which includes the history of GUI and NUI which of course, the information is most likely to have been published before 2008. When we consulted the lecturers, they all told us different things, some said we should go according to the specifications, some said we should check for relevance and some said we should use the pre-dated sources if we cannot find later sources which became very confusing for us. What was best for us is the fact that we actually enjoyed working on our project; two out of the four members in the group are former multimedia students so they already had some information about the topic given. They helped steer the group in the right direction and which sources to consult for information. The worst thing about the project is that the lecturers were not always available to help us, especially with technical problems, we had to rely on one lecturer and if she was not available, we had to wait until she was available again to help us with our problem.

Our recommendations are as follows: firstly, the lecturers should really make an effort to know everything about the project and not refer all of us to one lecturer for help as it delays our projects in a way and it is not really fair that only one lecturer knows the technical side of SharePoint because if that lecturer is not available for whatever reason, we cannot continue with our project. Secondly, in future, the students should be informed in the beginning of the year, maybe at registration that they will not have a June holiday and they should not book it for anything because this year, a lot of the information science students had internships, interviews and vacation work with companies and a lot had to cancel them to do the experiential learning project because some lecturers were not understanding. Lastly, for students, we are not used to working long hours with just a 30 minute break, we understand that this is a work situation but in future, we think that they should also make provision for tea breaks because we cannot sit and concentrate for more than three or four hours without a break.

2012 INL 370 REPORT

34

Bibliography
Graf, R. L. (2011). Behaviour and information technology. Age related differences in the initial usability of mobile device icons, 629-642.

Baumgartner, A. M.-J. (1997). A Practical Set of Culture Dimensions for Global User-Interface Development.

Liang, P.-L. P.-F. (2008). good computing systems for everyone- how on earth?, 287-292. Koike, H. (2004). Interactive textbook and interactive Venn diagram: natural and intuitive interfaces on augmented desk system.

shi, y. (2003). The smart classroom: merging technologies for seamless tele-education . bialkowski, v. (2011). international journal of the book. A Codicology of the Interface: Reading Practices and Digital Reading Environments., 101-106

Ultan. (2010, 08 18). Natural User Interface Gestures. Are They Global? zimmerman, T. G. (1986). a hand gesture interface device.

pavlock, v. (1997). Visual interpretation of hand gestures for human-computer interaction: a review Douglas J. Brems, M. D. (1995). Using Natural Language Conventions in the User Interface Design of Automatic Speech Recognition Systems.

wang, Y. y.-w. (2003). different perceptions visualizition and computer graphics, 131-144. Staner, T. (1998). Real-time American sign language recognition using desk and wearable computer based video .

Cassel, J. (2001). Non-verbal cues for discourse structure. Murphy, S. (2010). Retrieved February 9, 2012, from www.ti.com: http://www.ti.com/lit/wp/spry181/spry181.pdf

Murphy, S. (2012, February). Design Considerations for a Natural User Interface (NUI). Retrieved February 9, 2012, from www.ti.com: http://www.ti.com/lit/wp/spry181/spry181.pdf
2012 INL 370 REPORT 35

Russell, S. A. (2012, February). Do Natural User Interfaces Need GPGPU and OpenCL Support? . Canada, Ontario.

Ruiz-Hidalgo, J., Casas, J., Suau, X., Gibb, A., Prins, M., Zoric, G., et al. (2012). End User, Production and Hardware and Network Requirements. FascinatE consortium.

Introna, L., & Nissenbaum, H. (2009). Facial Recognition Technology - A Survey of Policy and Implementation Issues. New York: The Center for Catastrophe Preparedness & Response.

Steinberg, G. (2012). Natural User Interfaces. Auckland: University of Auckland.

Russell, S. A. (2012). Levering GPGPU and OpenCL Technologies for Natural User Interfaces. Ottawa: You i Labs.

Salat, L. (2010, September 23). Multitouch & Natural User Interface:. 1-4. Paris, France.

Blake, J. (2010). Natural User Interfaces in .NET. Manning Early Access Program.

Grandjean, N. (2008). Sociological and Ethical Issues in Facial Recognition Systems: Exploring the Possibilities for Improved Critical Assessments of Technologies? Multimedia, 2008. ISM 2008. Tenth IEEE International Symposium on (pp. 602-606). Berkeley: Tenth IEEE International Symposium.

Villaroman, N., Rowe, D., & Swan, B. (2011). Teaching natural user interaction using OpenNI and the Microsoft Kinect sensor. Special Interest Group for Information Technology, pp. 227-232. Tonfilm (Director). (2009). DIY Multi-touch screen [Motion Picture].

Brown, S. (2008, June 18). How it Works: Multi-touch Surfaces Explained. Scientific American. Brandon, J. (2009, October 9). How the iPhone works. ComputerWorld.

Tan, G. (2009). Quantum of Solace's multitouch UI / video wall gives us a glimpse at what's to come. United Kingdom.

2012 INL 370 REPORT

36