> For the complete documentation index, see [llms.txt](https://annemarleen.gitbook.io/immersive-design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annemarleen.gitbook.io/immersive-design/evaluation/control.md).
# Evaluation Topics: Human-System Control
**Intention of Use:** *What does the designer want the user to choose from and for which purpose?*
\- In **human control** (selection, manipulation and travel) tasks, the user typically specifies not only *what* should be done, but also *how* it should be done, more or less directly controlling the action. \
\- In **system control** tasks, the user typically specifies only *what* should be done and leaves it up to the system to determine the details. The system control is considered to ben an explicit action in stead of an implicit action.
### Human Control: taxonomy or usability characteristics
### 
**1. Users and User Tasks**
* navigation
* locomotion
* selection
* manipulation
* user tasks
**2. User Interface Input Mechanisms**
* tracking user location & orientation
* speech recognition & natural language input
* interface mechanisms in general
* pointers\&clicks\&props, like magic wands, flying mice, space balls, real-world props.
* data gloves & gestural recognition
**3. Virtual Model**
* system information
* user representation & presentation
* agent representation & behaviour
* virtual surrounding & selling
**4. User Interface Presentation Components**
* visual feedback & graphical presentation
* haptic feedback & force and tactile presentation
* aural feedback & acoustic presentation
* environmental feedback and other presentation.
### Human-System Control: taxonomy of input controllers
According to the extended placement options by Bowman et al. menus can be placed in the following ways:
* world-referenced (most desktop VR menus).
* object-referenced (e.g. combo box in).
* head-referenced (e.g. look-at-menu).
* body-referenced (e.g. TULIP).
* device-referenced (e.g. tool menu of the responsive workbench.
* PIP tool-palette.
* fade-up menu.
### System Control
System Control can be defined as the user task in which commands are issued to:
* (1) request the system to perform a particular function
* (2) change the mode of interaction
* (3) change the system state.
##
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://annemarleen.gitbook.io/immersive-design/evaluation/control.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.