Data, context and interaction
This article relies too much on references to primary sources. (February 2016) (Learn how and when to remove this template message)
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.
The data are "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. They may correspond closely to the model objects of MVC.
An example of a data object could be a bank account. Its interface would have basic operations for increasing and decreasing the balance and for inquiring about the current balance. The interface would likely not offer operations that involve transactions, or which in any way involve other objects or any user interaction. So, for example, while a bank account may offer a primitive for increasing the balance, it would have no method called
deposit. Such operations belong instead in the interaction part of DCI.
Data objects are instances of classes that might come from domain-driven design, and such classes might use subtyping relationships to organize domain data. Though it reduces to classes in the end, DCI reflects a computational model dominated by object thinking rather than class thinking. Therefore, when thinking "data" in DCI, it means thinking more about the instances at run time than about the classes from which they were instantiated.
The context is the class (or its instance) whose code includes the Roles for a given algorithm, scenario, or use case, as well as the code to map these Roles into objects at run time and to enact the use case. Each Role is bound to exactly one object during any given use case enactment; however, a single object may simultaneously play several Roles. A context is instantiated at the beginning of the enactment of an algorithm, scenario, or use case. In summary, a context comprises use cases and algorithms in which data objects are used through specific Roles.
Each context represents one or more use cases. A context object is instantiated for each enactment of a use case for which it is responsible. Its main job is to identify the objects that will participate in the use case and to assign them to play the Roles which carry out the use case through their responsibilities. A Role may comprise methods, and each method is some small part of the logic of an algorithm implementing a use case. Role methods run in the context of an object that is selected by the context to play that Role for the current use case enactment. The Role-to-object bindings that take place in a context can be contrasted with the polymorphism of vernacular object-oriented programming. The overall business functionality is the sum of complex, dynamic networks of methods decentralized in multiple contexts and their Roles.
Each context is a scope that includes identifiers that correspond to its Roles. Any Role executing within that context can refer to the other Roles in that context through these identifiers. These identifiers have come to be called methodless Roles. At use case enactment time, each and every one of these identifiers becomes bound to an object playing the corresponding Role for this context.
An example of a context could be a wire transfer between two accounts, where data models (the banking accounts) are used through Roles named SourceAccount and DestinationAccount.
The interaction is "what the system does." The interaction is implemented as Roles which are played by objects at run time. These objects combine the state and methods of a data (domain) object with methods (but no state, as Roles are stateless) from one or more Roles. In good DCI style, a Role addresses another object only in terms of its (methodless) Role. There is a special Role called
self which binds to the object playing the current Role. Code within a Role method may invoke a method on
self and thereby invoke a method of the data part of the current object. One curious aspect of DCI is that these bindings are guaranteed to be in place only at run time (using a variety of approaches and conventions; C++ templates can be used to guarantee that the bindings will succeed). This means that interactions, the Role methods, are generic. In fact, some DCI implementations use generics or templates for Roles.
A Role is a stateless programming construct that corresponds to the end user's mental model of some entity in the system. A Role represents a collection of responsibilities. Whereas vernacular object-oriented programming speaks of objects or classes as the loci of responsibilities, DCI ascribes them to Roles. An object participating in a use case has responsibilities: those that it takes on as a result of playing a particular Role. Most modern programming languages have a way to express Roles, and to express the injection of Role methods into objects, and implementation techniques vary depending on the language. The injection can be fully dynamic at run-time in languages like Ruby and Python; it is more static in languages like Smalltalk-Squeak, Scala and C++. The Qi4j programming environment offers a way to express Role method injection into Java objects. Java 8 default method on interfaces can be used to implement Roles in a typesafe way.
In the above money transfer use case, for example, the Role methods in the SourceAccount and DestinationAccount enact the actual transfer.
Distinguishing traits of DCI
DCI limits all permissible networks of communicating objects to networks that share common topologies, one for each use case. Such networks are explicit in the interactions between DCI Roles, whereas in classical object orientation they are emergent. A Role is a node in such a topology; it is a partial classification of the behaviors of all objects that can occupy this node. The topology is a description of the run-time structure of a system.
An object-oriented program is a complex and dynamic network of objects, in the same sense that relationships between real-world objects are complex and dynamic. Consider a waiter at a restaurant. The waiter himself is a complex object that can be viewed in many ways: as my Waiter (e.g., who describes tonight's menu and takes my order), as an Employee of the restaurant (with a certain salary and working hours), and as a Person in the restaurant (which has an occupancy limitation of 150 people). If a Waiter class was written to capture the real-world essence of Waiters (which is what object orientation is really all about), it would have to be very complex to support all of these perspectives.
In DCI these different views are factored into Roles. At run time, the Role is the identity of the object. During the enactment of a use case (like Serve the Wine) the Role Waiter unambiguously identifies a single object at any given time. You might argue there may be several Waiters at the table. However, they are likely to differ in their responsibilities within a use case, such as are found in Role names HeadWaiter and Busboy. Even if their responsibilities are identical, they would still be described as Waiter-1 and Waiter-2, or as individual (named) elements of a Waiter vector, if someone intended to write software for them. So a Role like HeadWaiter becomes the identifier, the handle, by which objects refer to each other in a use case.
DCI recognizes the Waiter as an object rather than, say, a composition of an Employee part, a Waiter part and a Person part. The object has its own identity independent of the use case; this is the Data facet of DCI. Roles are aliased names for their objects but are never separate objects themselves; that would cause self schizophrenia. In this sense, every Waiter is a homo sapiens. This is the Waiter's rudimentary what-the-system-is part. The object has many possible identities depending on the use case it is involved in; this surfaces in the Role identities that form part of the Interaction facet of DCI. These are the (usually more interesting) what-the-system-does part. However, in DCI, there is only a single object that carries both these perspectives at run time. These perspectives may be grouped differently at coding time. The code is dominated by the use case structure, which cuts across the objects, and which also is part of the Interaction facet of DCI.
DCI allows an object to take on one or more Roles during a use case enactment. In other words, an object is re-bound to Role identifiers on each use case enactment. These Roles infer an interface, referred to as the Role type. Each object is "re-cast" (in the theatrical sense) anew on every use case. Though a Role is bound only to a single object, an object may play several Roles. For example, a HeadWaiter may be involved in a use case to count all the occupants of the restaurant during a fire inspection, and will play the Person Role as well as the HeadWaiter Role. The single object supports the behaviors of both Roles necessary to carry out the use case.
In summary, DCI architectures tend to be characterized by the following properties:
- The Data model reflects the domain structure rather than partitions of its behavior;
- Objects dynamically take on Roles during use case enactments;
- Every Role of a use case is played by an object determined by the Context at the start of the use case enactment;
- The network of Interactions between Roles in the code (i.e., at coding time) is the same as the corresponding network of objects at run time;
- These networks are potentially re-created on every use case enactment;
- Roles come in and out of scope with use case lifetimes, but objects that may play these Roles may persist across multiple use case lifetimes and may potentially play many Roles over their own lifetime.
DCI can be thought of as an event-driven programming paradigm, where some event (as a human gesture in a model-view-controller (MVC) architecture) triggers a use case. The use case can be short-lived or long-lived. The events are called triggers, and they are handled in the environment in which DCI is embedded. This environment may be the controller of a conventional MVC architecture or any other system-level code.
The trigger causes the environment to instantiate a context object. The type of object is chosen according to the kind of use case that will ensue, based on information about the trigger or the system state or both. For example, a cash machine might have separate Context classes for money transfer, withdrawal, deposit, balance inquiry, and so forth. Once the environment instantiates the Context object, it invokes its trigger method to start the use case enactment.
As described above, each Context provides a design scope for the Roles that participate in the use case enactment. It is the job of the Context to assign objects to play these Roles.
- The Context first finds the objects that are to take part in this use case enactment. These objects may be anywhere in the environment, or in a database, or created on the fly; DCI does not restrict these objects. Within a Context there is at most one instance playing any given Role at any given time.
- Second, the Context assigns a single object to play each of its Roles (though a single object often plays multiple Roles in a single Context). In strongly dynamic languages (Ruby, Python) the Context injects the Role methods into the object. In most dynamic languages, any extant object can be asked to play any Role at any time (though some object-Role combinations may of course make no sense; nonsense combinations of objects and Roles would lead to
MESSAGE NOT UNDERSTOODat run time if the Role method were invoked.) In more statically typed languages (Scala, C++) there has to have been some prior arrangement for the object to support the Role methods. For example, Scala creates an anonymous class that combines the rudimentary logic of a domain class with the use case logic of the trait used to implement a Role; Roles are effectively assigned to domain objects when they are instantiated.
- Third, the Context invokes a Role method on the first object to take part in the use case.
- From that point forward, Roles invoke each other's methods to carry out the use case. A Role method may invoke a method on
selfwhich in fact is handled by the object currently playing the Role. This is how Roles invoke the rudimentary data operations of the objects currently playing them at the time.
DCI depends on a design process that separates use cases from the data model. The data model is often based on an informal domain analysis. The Roles that characterize the end-user's model of system functionality come from the use cases. One approach to overall DCI design is Lean Architecture described in a book of the same name.
Implementation techniques differ across programming languages. What is common to many approaches is that Roles are represented by such constructs as generics, templates, classes, or traits. Code for the basic domain logic is implemented separately, following conventional object-oriented practice and most commonly using classes. Each Role's code is injected into the domain object that will play it during the use case enactment. To implement Roles, method injection is usually needed. Traits are one common programming language technique to support method injection. Some languages, such as Scala, have native support for traits, while other languages (e.g., Ruby and Python) allow run time injection of methods. In Java, pre-compiler tricks based on annotations are needed to support DCI.
DCI arose largely as an outgrowth of Trygve Reenskaug's work on role-based modeling. Trygve had long recognized that Roles played a central part in the way programmers think about objects, and that the class-based progression of programming language technology took away much of the motivation to think about the objects in a program. That in turn made it difficult to reason about the program at run time. Further, the fact that object-oriented programming languages offered only classes to express program logic left the programmer at the mercy of the structural layout of the data to delineate behavior, which is unnatural compared with a delineating behavior on Role boundaries. This in turn made program behavior more difficult to reason about than in, say, a procedural program in Fortran.
Trygve felt it was important to create program structures about which one can reason, and started socializing these ideas as early as 2000. By 2006 he had a working design model, and his discovery in 2008 of Schärli's work on Traits provided the keystone that would provide natural programming language expression of these ideas. He prototyped the ideas in the Baby programming environment, written in Squeak. Jim Coplien joined Trygve on this effort in about 2007 and by mid-2008 had a prototype running in C++. Steen Lehmann, Rickard Öberg and Niclas Hedhman accelerated adaptating these ideas to Ruby and Java over the next year or so with the Qi4j framework. Many additional language adaptations followed a session at the JaOO conference in Denmark in September 2008.
Many key advances in the past twenty years of object-orientation exhibit components of DCI. While no one of them fully provides the DCI computational model, the overlap suggests[according to whom?] that the problems addressed by DCI are longstanding and fundamental.
- Mixins were a way of encapsulating code for specific what-the-system-does functionality in closed form; however, there is no consistent mechanism to link multiple mixins into a unit at the level of a use case. Mixins are very close to the concept of Role in DCI.
- Multiple dispatch was an early attempt to more fully separate an algorithm from the objects that were involved in its execution, but it lacked DCI's separation of common recurring algorithms from the code fragments that could individually be localized to individual objects. DCI conceptually leads to broader re-use of a single algorithm in closed form across many sets of objects of widely heterogeneous types. DCI's Context object acts like an explicit, intelligence dispatcher that is analogous to the dispatching mechanisms of languages with multiple dispatch.
- True object-oriented programming languages like Self tried to break down the dichotomy between the domains of classful programming and objectful execution. While this helped programmers focus on run-time objects, it sacrificed code-level knowledge about the relationships between them. DCI restores this knowledge in Contexts and in the static relationships between Role methods.
- Dependency injection is a longstanding approach to change the functionality of an object at run time by allowing it to "outsource" some of its execution to an external object that can be re-bound at will. Most implementations[which?] of dependency injection lead to the self schizophrenia problem, which implementations of DCI address properly. Systems such as Elmo use this approach, which brings additional complexity to resolve method ambiguity and duplicate data member names.[full citation needed]
- Multi-paradigm design attempted to separate behavior and structure by according the behavior to a procedural design and the structural component to objects, allowing free access between them, in accord with the design principles of C++. However, multi-paradigm design does a poor job of expressing the relationship between the procedural and structural parts of design, and in general cannot realize the cohesiveness of the DCI approach.
- Aspect-oriented programming (AOP) is perhaps the closest historic relative to DCI. However, most use of Aspects is closely tied to the programmer perspective rather than to the end user mental model of use cases. Further, without strong tool support, Aspects usually make code less readable from the perspective of understanding what actually goes on at a given pointcut. The main difference is that in DCI, the structure of the algorithm is primary, and its interaction with code outside of itself is viewed as secondary and minimal. Furthermore, such interaction honors the encapsulation of the code with which it interacts. In AOP, the pointcut and advice carry equal importance and though physically disjoint, must be understood together to understand the code, because the advice is invasive at the pointcut. While AOP provides an administrative grouping of a related collection of individual local modifications that together cross-cut the primary structure of the code, DCI is a semantic expression of an algorithm with first-class analysis standing that invokes existing object methods. DCI cann be thought of as a way of taking a large advice and allowing parts of it to be injected into a number of regularized pointcuts.
- Role-oriented programming brings together ideas from Aspect-oriented programming, conceptual modeling  and more. Early attempts (1991) defined roles in an independent fashion, but more recent approaches (2002 and onward) converge in emphasizing that roles depend on context (also "teams"  or "institutions" ). In role-oriented programming, roles are defined with respect to some intrinsic (or base) entity, which corresponds to the data-role dichotomy in DCI. The concept of context is essentially the same in both approaches. Both approaches emphasize the interaction among a group of roles.
- Several differences can be identified. Role-oriented programming is focused on adding support for roles to object-oriented programming languages where emphasis is on increasing the expressiveness of a programming language and enabling more designs. In comparison, DCI has stronger focus on the method of how mental models should be captured, defining this method in part as restrictions on what should be regarded a legal design corresponding to DCI. For example: Authors of DCI tend to discourage some use of inheritance (e.g. "within DCI you do not inherit roles" ) whereas role-oriented programming embraces (and even enhances) inheritance as a central concept of object-orientated programming, supporting free combination with other concepts. DCI emphasises that self schizophrenia should be avoided, whereas role-oriented programming claimed to manage split objects in such a way that schizophrenia was no longer a problem  but a facilitator for more flexible designs. A later paper by the DCI authors claims that self-schizophrenia remains a problem in role-oriented programming using a counter-example based on a modified implementation of Dijkstra's algorithm.
- Qi4j framework
- Lean Software Architecture web page, http://www.leansoftwarearchitecture.com
- James Coplien and Gertrud Bjørnvig, Lean Architecture for Agile Software Development. Wiley: 2010.
- Nathaniel Schärli et al. Traits: Composable units of behavior. http://scg.unibe.ch/archive/papers/Scha03aTraits.pdf
- The Common Sense of Object Oriented Programming by Trygve Reenskaug, http://heim.ifi.uio.no/~trygver/2009/commonsense.pdf
- Full OO DCI Documentation C++ Examples, http://fulloo.info/Examples/C++Examples/index.html
- C# source code on Object-Composition Google group,http://object-composition.googlegroups.com/web/20090504_C%23_DCI.zip?gda=KuAYkEcAAADrRvU1tICZInrYQGkdqcjVB9LJpDFQtNZStXvSrZaE07Ryyh4ndddBwXohD2r2F8gbzHe87USdioT9uNiA7PHaeV4duv6pDMGhhhZdjQlNAw 17.10.2009
- Ruby source code on Object-Composition Google group,https://groups.google.com/group/object-composition/browse_thread/thread/561f638b43f1b960# 17.10.2009
- Qi4j source code on Object-Composition Google group,https://groups.google.com/group/object-composition/browse_thread/thread/fe317e615b9008fe# 17.10.2009
- Release on CPAN: https://metacpan.org/release/DCI
- PHP source code on Google, https://code.google.com/p/php-coredci
- Trygve Reenskaug. Working with Objects: The OOram Software Engineering Method. Prentice-Hall, 1995.
- James Leigh, Elmo User Guide, http://www.openrdf.org/doc/elmo/1.5/user-guide.html
- James Coplien, Multi-paradigm design for C++. Addison-Wesley, 1998.
- Friedrich Steimann, On the representation of roles in object-oriented and conceptual modelling, 2000, http://www.fernuni-hagen.de/ps/veroeffentlichungen/zeitschrift_46129.shtml
- Joel Richardson and Peter Schwarz, Aspects: extending objects to support multiple, independent roles, 1991, http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/RichardsonS91.html
- Stephan Herrmann, Object Teams: Improving Modularity for Crosscutting Collaborations, http://www.objectteams.org/publications/index.html#NODe02, 2002
- Guido Baldoni et al., Roles as a coordination construct: introducing powerJava, 2005, http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.77.6337
- J. Coplien, posted in Object-Composition Google group, https://groups.google.com/forum/?hl=en#!topic/object-composition/haza-J2Doz8 21.10.2010
- Stephan Herrmann, Demystifying Object Schizophrenia, 2010, http://www.objectteams.org/publications/index.html#MASPEGHI10
- James O. Coplien, and Trygve Mikkjel Heyerdahl Reenskaug, The data, context and interaction paradigm. In Gary T. Leavens (Ed.): Conference on Systems, Programming, and Applications: Software for Humanity, SPLASH '12, Tucson, AZ, USA, October 21–25, 2012. ACM 2012, ISBN 978-1-4503-1563-0, pp. 227 - 228, http://dl.acm.org/citation.cfm?id=2384782&dl=ACM&coll=DL.