- Details
- Category: Category (en-gb)
- Hits: 3027
TRIAL EXPERIMENTAL DETERMINATION OF THE AVERAGE TIMES OF ACTIONS EXECUTED IN A CAD APPLICATION
The efficiency of CAD programs largely depends of the efficiency of their user interface. Relative efficiency can be defined as the inverse value of the effort involved during the design process. One of the possibilities for expressing the effort is to calculate, i.e. to sum up, the time required to fulfil one design task. Such value depends on the physical characteristics of the specific designer and hence cannot be valid. Another possibility is to determine average times of typical actions in the design process, such as mouse click, mouse move, typing of a number etc., and then evaluate the total effort by summing the products of average action times and counted number of actions in a design session. This paper presents an original methodology for experimental determination of the average times of the actions executed in a CAD application. In order to conduct the experiment, a web application, based on the proposed methodology, was developed. Based on the first experiences, it can be concluded that the presented methodology and application are suitable for experimental determination of the average times of CAD modeling actions. However, there is still room for improvement in its usability.
TOWARDS A METHODOLOGY FOR CAD PROGRAM EFFICIENCY ASSESSMENT
All CAD programs differ when it comes toAll CAD programs differ when it comes toefficiency. The efficiency of a CAD program depends on itsfunctionality and the user interface. The aim of this researchis to investigate possible methodologies for the assessment ofefficiency of CAD software in regard to its user interface.Based on an analysis of the interactions between the user andthe CAD programs user interface, six elementary user actionswere detected. Every user action requires some effort.Efficiency is defined as an inverse value of the total effort thathas been invested in the design process. Therefore, toevaluate the efficiency of a CAD program, it is necessary tocalculate the total effort. In this paper, four possiblemethodologies for determining the overall effort during thedesign process are presented. For each method, processparameters that should be measured in order to calculate theefficiency are defined.
- Details
- Category: Category (en-gb)
- Hits: 21795
Test results are written in nine files. Each file contains results of one test. Format of file is CSV. Next table presents metadata for each file.
Attribute |
Description |
Mouse click test |
|
Time for one click |
Time needed for one mouse click |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Mouse positioning speed test |
|
Real speed |
Actual positioning speed of the mouse. This is measured in pixels per second. It is calculated by dividing the total distance that the mouse passed with time. |
Ideal speed |
Ideal positioning speed of the mouse. This is measured in pixels per second. It is calculated by dividing the shortest distance between the initial and the final point with time. |
Efficiency |
The ratio of ideal and real speed. It is always less than 1 |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Selecting auxiliary key test |
|
Shift key time |
Time needed to select SHIFT key |
Esc key time |
Time needed to select ESC key |
Alt key time |
Time needed to select ALT key |
Ctrl key time |
Time needed to select CONTROL key |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Selecting two keys simultaneously |
|
Key combination time |
The necessary time to simultaneously select two keyboard keys |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Time required for typing regular text |
|
Errors per ten chars |
Number of errors per 10 characters entered |
Time for one char |
the time needed for entering one character |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Time for mouse wheel scroll |
|
Time for one step |
the time needed for one step when scrolling the mouse |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Alternate mouse button selection |
|
Left button time |
the time needed for left mouse button click |
Right button time |
the time needed for right mouse button click |
Middle button time |
the time needed for middle mouse button click |
Double click time |
the time needed for left mouse button double click |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Time for transfer the right hand from the mouse to the keyboard and vice versa |
|
Mouse to keyboard time |
the time it takes to move the hand from the mouse to the keyboard |
Keyboard to mouse time |
the time it takes to move the hand from the keyboard to the mouse |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
Time required for typing numbers |
|
Errors per ten digits |
number of errors per 10 entered digits |
Time for one digit |
the time needed for entering of one digit |
User ID |
user identification |
Test date |
Date and time of the test |
Gender |
User gender. This field can have two values: male and female |
Right hand |
this field can have values 0 and 1. Value 1 indicates that the user's dominant hand is right. 0 indicates that the dominant arm is left |
Birth year |
year of birth of the user |
- Details
- Category: Category (en-gb)
- Hits: 53768
Project OpenClick aims to discover physical status, skills and abilities of people based on human – computer interaction tests.
OpenClick is research project fully based on Open Science principles.
OpenClick allows to registered persons, researcher or institution to use OpenClick project’s infrastructure (portal, tools, methodology, database, data sets) to conduct their own research as long as they respect project’s principles, rules, Intellectual Property Rights and licensing policy.
OpenClick project offers set of testing tools which measure specific user performance in human – computer interaction. Each test is designed to measure one, exactly defined, type of interaction. During the test, several samples are taken, the average value is calculated, and then this average value is recorded in the database as a result of the test for specific person.
Citizens can test their physical status and they can compare it with the population. Also, in case more tests are done, they can monitor their condition over time.
OpenClick project allows creation and implementation of the projects that use the common OpenClick infrastructure, and therefore OpenClick can be considered as an open framework. Researchers can launch their own open project by configuring the desired set of tests, and thus became project leader. They are responsible for applied methodology and project results.