CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

Data, context and interaction

architectural pattern in computer software development

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionAug 28, 2026
Entity authorityQ1172196 ↗
Source-derived summary

Data, context, and interaction (DCI) is a paradigm used in computer software to program systems of communicating objects. Its goals are:

To improve the readability of object-oriented code by giving system behavior first-class status;

To cleanly separate code for rapidly changing system behavior (what a system does) versus slowly changing domain knowledge (what a system is), instead of combining both in one class interface;

To help software developers reason about system-level state and behavior instead of only object state and behavior;

To support an object style of thinking that is close to programmers' mental models, rather than the class style of thinking that overshadowed object thinking early in the history of object-oriented programming languages.

The paradigm separates the domain model (data) from use cases (context) and Roles that objects play (interaction). DCI is complementary to model–view–controller (MVC). MVC as a pattern language is still used to separate the data and its processing from presentation.

Description

Data

The data remains "what the system is." The data part of the DCI architecture is its (relatively) static data model with relations. The data design is usually coded up as conventional classes that represent the basic domain structure of the system. These classes are barely smart data, and they explicitly lack the functionality that is peculiar to support of any particular use case. These classes commonly encapsulate the physical storage of the data. These data implement an information structure that comes from the mental model of end users, domain experts, programmers, and other people in the system.

Editorial summary

Begin with the source’s own compact description: “Data, context and interaction” is architectural pattern in computer software development. The dossier treats that line as a proposition to test through Data, context and interaction, not as a finished interpretation.

Editorial reviewA sound reference starting point where classification, measurement and the date of the underlying evidence remain visible. The current 253-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. For this dossier, Data, context and interaction is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “architectural pattern in computer software development” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Aug 28, 2026. The linked authority identifier is Q1172196. None of the 0 selected statements returned an explicit reference.

Critical limits

A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “Data, context and interaction”, its source revision and the description used here.
  2. Expand the search: follow Data, context and interaction primary sources, Data, context and interaction archive and Data research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Data, context and interaction”?
  2. Has classification or technical consensus changed since the cited source?
  3. Is the terminology current, historical or disputed?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Data, context and interaction” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.