Database Interfaces

Defining and Describing Database Interfaces

  • A database interface is the boundary that lets people inspect, query, modify, and administer stored data without requiring the same level of knowledge as the underlying database system.
  • Database interfaces translate human actions—such as filling in forms, selecting icons, navigating relationships, or writing queries—into database operations. Early research emphasized that interfaces had to serve nontechnical users, while later systems expanded toward graphical browsing, multimodal interaction, and natural-language access. [1] [2] [3]
  • The concept applies wherever users need to work with structured data: business applications, engineering systems, personal databases, research tools, and administrative software. Its central design problem is balancing expressive power with learnability, accuracy, and protection against invalid or unintended operations. [4] [1] [3]
flowchart LR U["User"] --> I["Database interface"] I --> Q["Query or action translation"] Q --> D["Database system"] D --> R["Results and feedback"] R --> I

Uses in Context

  • Business applications: Forms and tables let staff create, maintain, and manipulate relational data without directly writing formal queries. [4]
  • Exploratory search: Browsing interfaces help users investigate vague information needs when a precise query is difficult to formulate. [2]
  • Visual querying: Icons, diagrams, and graphical schema views represent database objects and relationships in ways intended to reduce dependence on query-language expertise. [5] [6]
  • Engineering design: Interfaces can combine constraints, examples, pointing at graphical parts, and query language in a multimodal workstation environment. [3]
  • Natural-language access: Natural-language interfaces attempt to let users express requests in ordinary language, although experiments found that natural-language users could produce more unanswerable queries than users of artificial query languages. [1] [7]
  • Casual-user access: Graphical interfaces are designed for users who may lack formal database training or familiarity with database organization. [2] [8]

History of Use

Origins

  • The modern research agenda emerged from human-factors work on database interaction. Ben Shneiderman’s 1978 paper argued that the spread of information systems to nontechnically trained users required “a new approach” to database-interface design and proposed controlled experiments comparing natural and artificial query languages. [1]
  • Earlier relational-interface research explored ways to make databases usable through browsing rather than formal query specification. The 1986 BAROQUE system presented a relational database as a semantic-network-like environment and supported exploratory retrieval with few formal skills. [2]
  • The concept was also shaped by entity-relationship and graphical interaction research. The 1984 Living in a Database system used a bit-mapped display and mouse interaction for an entity-relationship database, while noting the implementation difficulty of dynamic displays and the challenge of operating on sets of instances. [9]

Evolution

  • 1978–1984 — Human factors and graphical interaction: Research shifted from treating database access primarily as query formulation toward studying usability, visual presentation, dynamic displays, and the needs of nontechnical users. [1] [9]
  • 1986–1990 — Browsing, icons, and graphical query construction: Systems such as BAROQUE and IconicBrowser made exploratory retrieval and object selection central interaction modes; IconicBrowser used icons for classes and objects and interpreted combinations of overlapping icons as database operations. [2] [5]
  • Late 1980s onward — Domain-specific and multimodal interfaces: Database interfaces expanded beyond business-style text interaction to engineering environments combining graphics, constraints, examples, and specialized query languages, while form-based systems mapped familiar screen layouts onto normalized relational structures. [3] [4]

Best Real-World Examples

  • BAROQUE — a relational-database browser designed for exploratory search when users could not specify precise queries. [2]
  • IconicBrowser — an icon-based object-oriented database retrieval system that translated visual combinations into database operations. [5]
  • Living in a Database — an early graphical entity-relationship interface using a bit-mapped display and mouse pointer. [9]
  • A user interface for database creation, use and maintenance — a form-and-table interface that allowed users to manipulate relational data through screen images rather than direct relational operations. [4]
  • A graphical database interface for casual, naive users — research focused explicitly on making database access practical for casual and inexperienced users. [8]
  • A Graphical Interface to a Complex-Object Database Management System — a graphical system that displayed schemas, formulated queries visually, and presented results as navigable complex-object graphs. [6]
  • A practical natural language interface to databases — an early applied treatment of translating ordinary-language requests into database access. [7]

Case Studies

BAROQUE and exploratory retrieval. Published in 1986, BAROQUE addressed a limitation of formal query systems: users often know the general area of information they want but cannot express the target precisely in advance. [2] Its designers created a browser that represented schema and data together in a semantic-network-like view and supported scanning, navigation, and access by value. [2] The result was an interface that treated browsing as a legitimate retrieval strategy rather than as a fallback for failed querying. [2] The case shows that database interfaces can lower the cost of uncertainty by helping users discover both the data and the structure of the database while searching.
IconicBrowser and visual query composition. IconicBrowser, published in 1990, targeted object-oriented databases whose query languages were considered difficult for casual users. [5] It represented classes and objects with icons; users specified queries by overlapping icons, after which the system interpreted the combination as database operations and generated predicate-based queries for other applications. [5] This approach moved part of query construction from symbolic language into spatial manipulation. [5] The case demonstrates how an interface can preserve the expressive capabilities of a complex database model while presenting users with a more concrete interaction vocabulary.
Form-based relational interaction. The 1988 form-and-table interface addressed people who were accustomed to collecting and maintaining information in forms or tables but were not professionally trained in computer science. [4] Users worked through screen images of tables or forms while the system mapped those views to a relational database whose underlying structure was normalized. [4] The research focused on the mappings required to connect familiar visual representations with relational operations. [4] This case illustrates a recurring pattern in interface design: the visible model can be shaped around users’ work practices even when the underlying data model is more abstract and technically constrained.

Sources

[2] 2026, Nov 12. dl.acm.org . BAROQUE: a browser for relational databases | ACM Transactions on Information Systems . Updated: 2026, Nov 15. Generated: 2026, Nov 16. Perplexity API response.

[6] 2026, May 03. link.springer.com . A Graphical Interface to a Complex-Object Database Management ... . Updated: 2026, Nov 13. Generated: 2026, Nov 16. Perplexity API response.

[9] 2026, Oct 20. dl.acm.org . Lessons from a "living in a database" graphical query interface . Updated: 2026, Oct 23. Generated: 2026, Nov 16. Perplexity API response.