joriszwart.nl

Usability

Expertise spectrum UIs

Introduction

I’m building this tool to create boring business applications. However, I discovered that people use different terminologies for the same thing based on their expertise.

Some speak of tables and columns, for example, others of entities and attributes. Still others make it even more confusing; they say relationship when they talk about a table. You wonder how they name a relationship1.

When I wanted to introduce globalization, that gave me the solution. Terminology can be used as language. It does make it difficult to do this for all languages, though. An explosion of combinations to build and maintain.

Demo

This is what it can look like in a simple form. The UI uses terminology based on the expertise level of the user.

Expertise spectrum prototype
Entities
Name Rows Links
Customers 17 Orders
Orders 21 Customers, Products
Products 52 Orders
3 entities

Duke Nukem says

This table shows an overview of used terms and their translations.

Difficulty LevelTableColumnRowValueRelationship
Piece of CakeSheetColumnRowValueLink
Let’s RockTableFieldRowValueRelationship
Come Get SomeRelationAttributeRecordValueForeign Key
Damn, I’m GoodEntityAttributeTupleDatumRelationship Set

  1. It’s called a ‘relationship set’. ↩︎

Related