Data, context and interaction: Difference between revisions

Revision as of 13:02, 17 July 2019

Revision as of 18:03, 7 January 2020

Line 12:

===Data===

The data areremains "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 <code>deposit</code>. Such operations belong instead in the interaction part of DCI.