Research any topic before you write.
Find related topics. | Discover entities. | See connections. | Build a topical map.
Object–action interface, also abbreviated as OAI, is an extension to the graphical user interface, especially related to direct manipulation user interface and it can help to create better human–computer interfaces and increase the usability of a product.
Products, Interface hierarchy of objects and actions & OAI model
Explore the main themes, entities and connections around Object–action interface. Start with the topic map, then use the sections below for research and deeper semantic analysis.
Start with a few of the strongest sections from the source topic. These are research directions, not a list of keywords you must use.
High-confidence facts extracted from structured source data. Use them as anchors for further research.
Browse the full topic structure. Each item opens a new analysis centered on that subject.
Deeper signals for content research, entity SEO and topical coverage. The plain-language headings explain what each technical view is useful for.
See the strongest relationship patterns around the current topic before diving into the raw triples.
Use these terms to understand the vocabulary surrounding the topic, not as a checklist for keyword stuffing.
actions objects user interface model action object oai tasks hierarchy users task performed perform world level related computer designer sequence
| Subject | Predicate | Object | Confidence | Src |
|---|---|---|---|---|
| pointing | instance of | The interface actions are usually performed by pointing device or keyboard and hence have to be visual to the user so that the latter can decompose his plan into steps of actions | 0.80 | text |
| clicking | instance of | The interface actions are usually performed by pointing device or keyboard and hence have to be visual to the user so that the latter can decompose his plan into steps of actions | 0.80 | text |
| dragging | instance of | The interface actions are usually performed by pointing device or keyboard and hence have to be visual to the user so that the latter can decompose his plan into steps of actions | 0.80 | text |
| etc.This way DMUIs provide a snapshot of the real world situations | instance of | The interface actions are usually performed by pointing device or keyboard and hence have to be visual to the user so that the latter can decompose his plan into steps of actions | 0.80 | text |
| map the natural way of user's work sequence through the interface | instance of | The interface actions are usually performed by pointing device or keyboard and hence have to be visual to the user so that the latter can decompose his plan into steps of actions | 0.80 | text |
| creating a file | instance of | A high level plan to create a text file might involve mid-level actions | 0.80 | text |
| inserting text | instance of | A high level plan to create a text file might involve mid-level actions | 0.80 | text |
| saving that file | instance of | A high level plan to create a text file might involve mid-level actions | 0.80 | text |
| storing the file with a backup copy | instance of | The mid-level action of saving a file the file can be decomposed into lower level actions | 0.80 | text |
| applying the access control rights | instance of | The mid-level action of saving a file the file can be decomposed into lower level actions | 0.80 | text |
| demonstrations | instance of | dealing with errors such as space shortage and so on.For the userThere are several ways users learn interface objects and actions | 0.80 | text |
| sessions | instance of | dealing with errors such as space shortage and so on.For the userThere are several ways users learn interface objects and actions | 0.80 | text |
These clusters group vocabulary that occurs around closely connected concepts in the source material.
Bridges can reveal useful research angles that are easy to miss in a flat list of related terms.