Jump to: navigation, search

this frame is an inclusion of the usability testing page

Contents 1 Usability Tests for Kali-ma v2 1.1 Requirements 1.2 Setting up the environment 1.3 Tests 1.3.1 Test 1: Find a plugin by its capabilities 1.3.1.1 Synopsis 1.3.1.2 With Kali-ma 1.3.1.3 Without Kali-ma 1.3.2 Test 2: Finding the capabilities of a plugin 1.3.2.1 Synopsis 1.3.2.2 With Kali-ma 1.3.2.3 Without Kali-ma 1.3.3 Test 3: Find out documentation for a plugin 1.3.3.1 Synopsis 1.3.3.2 With Kali-ma 1.3.3.3 Without Kali-ma 1.3.4 Test 4: Extract documentation from an ontology and save it 1.3.4.1 Synopsis 1.3.4.2 With Kali-ma 1.3.4.3 Without Kali-ma 1.3.5 Test 5: Search for an Argumentation Issue 1.3.5.1 Synopsis 1.3.5.2 With Kali-ma 1.3.5.3 Without Kali-ma

Usability Tests for Kali-ma v2

Requirements

Setting up the environment

Tests

Test 1: Find a plugin by its capabilities

Find out which plugins are useful for performing a SPARQL query. 
Pick one of them and open its interface.

Synopsis

Your task is to find something (a plugin, a core interface element) that allows you to query an ontology with SPARQL. The SPARQL language allows you to search (query, browse, etc.) RDF graphs, including ontologies, for statements involving certain resources. It can also be used to create new statements.

When you think you've found such a tool, try to access its user interface. You don't have to perform an actual query.

Time : 3 minutes since the NeOn Toolkit (or Kali-ma) is started.

With Kali-ma

1. Start the NeOn Toolkit and Kali-ma.
2. Find a way to browse NeOn Toolkit plugins from the Kali-ma interface that appears
3. Look for a tool that seems like it can be used for performing SPARQL queries.
4. When you find it, activate the node that represents it
5. Find a way to launch the tool and do so.

Without Kali-ma

1. Start the NeOn Toolkit (or 'Go back to it', if you are in the Kali-ma interface).
2. Browse the top menus for a SPARQL tool (HINT: it's in the "Window" menu).
3. When you find it, open its interface.

Test 2: Finding the capabilities of a plugin

Find out what activities the RaDON plugin is capable of performing.

Synopsis

Among the tools that can be installed on the NeOn Toolkit there is one called RaDON. You won't be told what it does as, this time you'll have to find for yourself. Remember, though, that a plugin can serve more activities

Time : 2 minutes since the NeOn Toolkit (or Kali-ma) is started.

With Kali-ma

1. Start the NeOn Toolkit and configure the Kali-ma preferences if you see fit.
2. Start Kali-ma
3. Browse the Kali-ma interface like you did for Test 1, and look for the RaDON plugin.
4. When you find it, note down its category (or categories) until you find five of them.

(HINT: if you can't find enough categories, you can change the classification criterion in the Preferences, but remember to restart the NeOn Toolkit after doing that).

Without Kali-ma

1. Have the NeOn Toolkit and Kali-ma running.
2. Browse the top menus for the RADON plugin (HINT: it's in the Window menu)
3. When you find it, note down which activities it allows you to perform (HINT: an insight should be found in the same window where you located the plugin).

Test 3: Find out documentation for a plugin

Find a help page, or "cheatsheet", that tells you how to translate the labels of Ontology entities.

Synopsis

The NeOn Toolkit provides a plugin that allows you to localize labels for OWL entities, i.e. to find translations for labels or entity names into other languages than the one originally used. Test subjects are not required to use it, but they are required to find a way to understand how it works, i.e. a page, or cheatsheet, that tells them what steps should be performed.

Time : 3 minutes since the NeOn Toolkit (or Kali-ma) is started.

With Kali-ma

1. Have the NeOn Toolkit and Kali-ma running.
2. Find a tool that allows you to translate the labels of an ontology.
3. When found, open its widget the usual way.
4. Using the widget you just opened, configure the plugin to display its cheatsheet, then open it.

Without Kali-ma

1. Have the NeOn Toolkit running.
2. Browse the top menus to open a cheatsheet about translating labels (HINT: it's among the last 3 menus on the list).

Test 4: Extract documentation from an ontology and save it

Find a tool that can help you save the documentation for an existing ontology, and do it.

Synopsis

Pick an ontology in the workspace and save its documental information. There is a plugin that provides a wizard to allow users to save documentation in HTML format with a similar style as Javadoc. You are required to find this plugin and use it.

(HINT: being similar to JavaDoc, the document format is called OWLDoc).

Time : 2 minutes since the NeOn Toolkit (or Kali-ma) is started.

With Kali-ma

1. Have the NeOn Toolkit and Kali-ma running.
2. Browse the Tool Organiser for a tool that allows you to store the documentation of an ontology.
3. When found, open its widget.
4. Try to run the plugin from this widget.
5. If a Wizard appears, select the project, the ontology and specify a target file, then click Finish.

Without Kali-ma

1. Have the NeOn Toolkit running.
2. Browse the menus and/or the Ontology Navigator for whatever might help you either launch a documentation plugin or find help about how to do it (HINT: You're saving, or "exporting" documentation).
3. If a Wizard appears, select the project, the ontology and specify a target file, then click Finish.

Test 5: Search for an Argumentation Issue

Search the rockbands.owl ontology in the Rock project. 'Find a class and an object property 
that are annotated with an argumentation issue whose URI or title  matches "do we really need this class?" 
(possibly with underscores as separators).

Synopsis

Otology Argumentation is a fundamental activity that occurs when engineering networked ontologies. Argumentation is the act of discussing collaboratively whether an ontology, or part thereof, is technically sound and conforms to the original specifications. Argumentation can be done in realtime (e.g. IRC chat) or asynchronously (e.g. message boards, Wikis, even by email).

The NeOn Toolkit has a tool called Cicero, that allows you to create and participate to such discussions (Called Argumentation Issues or just Issues). In this case, the actual discussion is not stored locally, but on a Wiki. However, the Cicero plugin annotates local OWL entities with pointers to issues in this Wiki.

The rockbands.owl ontology in the Rock project contains two entities that are already annotated with an issue, where people are discussing about the actual need for certain classes. The task is to find these two entities (a class and an object property).

Time : 3 minutes since the NeOn Toolkit (or Kali-ma) is started.

With Kali-ma

1. Have the NeOn Toolkit and Kali-ma running.
2. Use the Kali-ma Search in Projects function to retrieve an argumentation issue whose URI contains the "Do_we_really_need_this_class?" string.
3. If you find one, note down what OWL entities it refers to.

HINT: you can restrict the search within projects. Also, there is a settings button for further restrictions, or facets...

Without Kali-ma

1. Have the NeOn Toolkit running and make sure to have your network connection running.
2. Using the Ontology Navigator, examine OWL Classes and Object Properties in the "rockbands.owl" ontology in the "Rock" project, and look for those annotated with an issue with title "Do we really need this class?" (HINT: Each OWL entity has a context menu). Note down what entities they are.
3. If asked for login, use (case-sensitive) user: ProjectMember and password: 1234. Check the "remember password" box.
4. When you have found two entities annotated like that, stop.