Content deleted Content added
m →Data: named reference. |
m →Data: added reference. |
||
Line 16:
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.
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<ref name="DCI Paradigm">{{cite web |author1=James O. Coplien |author2=Trygve Reenskaug |title=The DCI Paradigm: Taking Object Orientation Into the Architecture World |url=https://fulloo.info/Documents/CoplienReenskaugASA2012.pdf}}</ref>.
===Context===
| |||